Clean up services and add some example references (caae57b2) · Commits · STAN4CRA / EN 304 626 Operating Systems

EN-304-625.md

+28 −28

Original line number	Diff line number	Diff line
		@@ -126,35 +126,27 @@ This category includes but is not limited to:
		- embedded operating systems
		- special purpose operating systems

		EDITS

		Everything will be generic in final draft

		should include:
		- systemd (and all dependencies)
		- udev
		- loading firmware
		- windowing system
		- anything necessary to use the hardware
		- Authentication
		- libc etc
		- system libraries by path?
		- privileged processes?
		- kernel :)
		The scope is limited to the security-relevant parts of the operating
		system. This includes any element capable of modifying elements that
		control security of the system, including but not limited to:

		- the kernel
		- device drivers
		- basic command utils?
		- language interpreters
		- bash :)
		- software update
		- logging (in init stuff usually)
		- package manager (part of updates)
		- remember xz
		- libraries used to provide security-relevant services
		- authentication services
		- processes running with elevated privileges
		- processes capable of granting elevated privileges
		- file systems allowing setuid
		- package management
		- update mechanism
		- logging of security-related events
		- configuration of security-relevant items

		exclude
		FIXME: Anything can run with elevated privileges if root runs it... is there a mitigation here?

		- not all privileged processes (depends)
		- device drivers supplied by external vendors?? beyond API
		FIXME: not all processes with elevated privilges?

		FIXME: device drivers supplied by external vendors, require certification, secure default, complex opt-in

		# 1.3 Products not in scope

		@@ -162,6 +154,8 @@ _Detailed list of things whose scope might be confusing, including parts of a sy

		This standard does not cover products in use in contexts other than those identified in annex <L>.

		This standard does not cover parts of the operating system that are not security-relevant.

		This standard does not cover:
		- hypervisors or containers
		- boot managers or boot loaders
		@@ -172,8 +166,6 @@ While hypervisors and containers abstract the underlying hardware and may provid

		FIXME diagram(s) showing relationship to hypervisors, containers, boot managers, IAM, network interfaces, antivirus, hardware, and software.

		FIXME specify parts that are close related but not part of this vertical, e.g. core userspace stuff

		# 2 References

		## 2.1 Normative references
		@@ -197,6 +189,7 @@ The following referenced documents are necessary for the application of the pres

		- <a name="_ref_1">[1]</a> <Standard Organization acronym> <document number> (<version number>): "<Title>".


		FIXME more normative references


		@@ -208,8 +201,15 @@ References are either specific (identified by date of publication and/or edition

		The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding but are not required for conformance to the present document.

		- <a name="_ref_i.1">[i.1]</a> BSI CC-PP-0067 v2.0: Operating System Protection Profile
		- <a name="_ref_i.number">[i.2]</a> ETSI hEN IAM
		- <a name="_ref_i.number">[i.3]</a> ETSI hEN ???
		- <a name="_ref_i.number">[i.4]</a> ETSI hEN ???
		- <a name="_ref_i.number">[i.5]</a> <Standard Organization acronym> <document number> (<version number>): "<Title>".
		- <a name="_ref_i.number">[i.6]</a> <Standard Organization acronym> <document number> (<version number>): "<Title>".
		- <a name="_ref_i.number">[i.7]</a> <Standard Organization acronym> <document number> (<version number>): "<Title>".

		- <a name="_ref_i.1">[i.1]</a> <Standard Organization acronym> <document number> (<version number>): "<Title>".
		FIXME some of these could be normative references

		FIXME more informative references