Functional separation between computing environments Physical servers often use a software-based isolation mechanism to share their hardware among multiple computing environments. In doing so, a computing environment could consist of an entire operating system installed in a virtual machine where the isolation mechanism is a hypervisor, such as cloud services providing Infrastructure as a Service, or alternatively, a computing environment could consist of an application which uses the shared kernel of the underlying operating system of the physical server where the isolation mechanism is an application container or application sandbox, such as cloud services providing Platform as a Service. Note, however, the logical separation of data within a single application, such as cloud services providing Software as a Service, is not considered to be the same as multiple computing environments. An adversary who has compromised a single computing environment, or who legitimately controls a single computing environment, might exploit a misconfiguration or security vulnerability in the isolation mechanism to compromise other computing environments on the same physical server or compromise the underlying operating system of the physical server. As such, it is important that additional security controls are implemented when a software-based isolation mechanism is used to share a physical server’s hardware. Security Control: ISM-1460; Revision: 3; Updated: Mar-22; Applicability: All; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware, the isolation mechanism is from a vendor that has made a commitment to secure-by-design principles, secure programming practices and maintaining the security of their products. Security Control: ISM-1604; Revision: 0; Updated: Aug-20; Applicability: All; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware, the configuration of the isolation mechanism is hardened by removing unneeded functionality and restricting access to the administrative interface used to manage the isolation mechanism. Security Control: ISM-1605; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware, the underlying operating system is hardened. Security Control: ISM-1606; Revision: 1; Updated: Mar-22; Applicability: All; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware, patches, updates or vendor mitigations for security vulnerabilities are applied to the isolation mechanism and underlying operating system in a timely manner. Security Control: ISM-1607; Revision: 0; Updated: Aug-20; Applicability: All; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware, integrity and log monitoring are performed for the isolation mechanism and underlying operating system in a timely manner. Security Control: ISM-1461; Revision: 5; Updated: Mar-22; Applicability: S, TS; Essential Eight: N/A When using a software-based isolation mechanism to share a physical server’s hardware for SECRET or TOP SECRET computing environments, the physical server and all computing environments are of the same classification and belong to the same security domain. Further information Further information on container security can be found in National Institute of Standards and Technology Special Publication 800-190, Application Container Security Guide. Further information on the use of cloud services can be found in the managed services and cloud services section of the Guidelines for Outsourcing. Further information on cyber supply chain risk management can be found in the cyber supply chain risk management section of the Guidelines for Outsourcing. 90

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents