@@ -123,15 +123,16 @@ In the present document "**shall** ", "**shall not** ", "**should** ", "**should
# Introduction
The present document is a European harmonised standard that defines cybersecurity requirements for products whose primary purpose is providing an operating system. Demonstrating compliance with the present document is not necessary, but doing so provides a presumption of conformity with Regulation (EU) 2024/2847, the Cyber Resilience Act.
The present document does not apply to products that contain an operating system or are part of an operating system if the core purpose of the product is not that of an operating system. However, it may be useful as one part of the process of demonstrating compliance for a product containing or interacting with an operating system.
# 1 Scope
## 1.1 General
The present document describes how to demonstrate the compliance of operating systems with the requirements in the EU Regulation 2024/2847, within the context described in clause 4, Product Context.
The present document specifies security requirements and related assessment criteria regarding the compliance of Operating Systems with EU Regulation 2024/2847.
Following harmonised standards in the design and manufacture of products may ensure that the products comply with corresponding EU rules.
The use of harmonised standards are voluntary.
## 1.2 Products in scope
@@ -158,43 +159,23 @@ The scope is limited to the security-relevant parts of the operating system. Thi
Security-relevant parts of the operating system include but are not limited to:
* the kernel
* device drivers if supplied with the operating system
* the operating system's kernel
* device drivers, if supplied with the operating system
* libraries used to provide security-relevant services
* authentication services
* processes running with elevated privileges
* software installation and update system
* logging and monitoring
* configuration of security-relevant items
*security-relevant system default configuration
*core authentication services required for operating system functionality
*operating system processes running with elevated privileges
* software installation and update system, if supplied with the operating system
* logging and monitoring, if performed by the operating system
* configuration of security-relevant operating system functions
*provisioning of a secure default configuration for the operating system, based on its configured use
## 1.3 Products not in scope
The present document does not cover parts of the operating system that are not security-relevant.
The present document does not cover:
* Hypervisors or containers
* Boot managers or boot loaders
* Hardware, microcode, or special purpose device firmware
* Device drivers not shipped with the operating system, including those stored on devices
* Usermode "operating systems," applications which emulate parts of an operating system on top of another operating system's user API
While hypervisors abstract the underlying hardware and may provide services similar to operating systems such as resource management and scheduling, the set of services they supply to clients are far more limited than those of an operating system. Hypervisors provide clients an emulated hardware platform rather than a set of abstract operating system services.
Containers are a set of process isolation features provided by operating systems. They are an operating system feature, not an operating system.
Usermode "operating systems" are applications simulating an operating system in an application, implemented on top of another operating system's user API. These applications are often used to learn about, develop, or emulate the parts of operating systems that do not directly interface with underlying hardware. They do not and cannot provide the core functions of an operating system as defined for the purposes of the present document.
Boot managers have the primary purpose of initializing the hardware after power on or reset with the goal of choosing, loading, and/or transferring execution to an operating system or other program. While many boot managers provide some or all of the services of an operating system (or are literally operating systems adapted for use as a boot manager), they are designed and intended primarily to transfer control to an operating system or other program, rather than continuously operate and provide services.
Firmware running on a device is an operating system if its core function is to abstract the hardware platform and control the execution of software that uses services it provides. Otherwise it is special purpose device-specific firmware.
> FIXME: make the above more specific.
The present document does not apply to products that contain an operating system or are part of an operating system if the core purpose of the product is not that of an operating system. However, it may be useful as one part of the process of demonstrating compliance for a product containing or interacting with an operating system.
Device drivers are generally included in the security-relevant parts of an operating system. However, the manufacturer of the operating system is only responsible for device drivers included in the product.
The present document does not cover functions of the operating system that are not security-relevant.
> FIXME: add diagram(s) showing relationship to hypervisors, containers, boot managers, IAM, network interfaces, antivirus, hardware, and software.
The present document does not cover other product categories defined in EU Regulation 2024/2847, such as hypervisors, container runtime systems, or boot managers, even where such products provide security-relevant functionality which overlaps that of an operating system.
