Guidelines for System Management
System administration
System administration of cloud services
System administration of cloud services brings unique challenges when compared to system administration of onpremises assets. Notably, responsibility for system administration of cloud services is often shared between service
providers and their customers. As the system administration processes and procedures implemented by service
providers are often opaque to their customers, customers should consider a service provider’s control plane to operate
within a different security domain.
System administration processes and procedures
A key component of system administration is ensuring that administrative activities are undertaken in a repeatable and
accountable manner using system administration processes and procedures. In doing so, requirements for
administrative activities may cover:
configuring applications, operating systems, network devices or other ICT equipment
applying patches, updates or vendor mitigations to applications, drivers, operating systems or firmware
installing or removing applications, operating systems, network devices or other ICT equipment
implementing system changes or enhancements
resolving problems identified by users.
Furthermore, in support of change management processes and procedures, system administrators should document
requirements for administrative activities, consider potential security impacts, obtain any necessary approvals, notify
users of any disruptions or outages, and maintain system and security documentation.
Security Control: ISM-0042; Revision: 5; Updated: Dec-21; Applicability: All; Essential Eight: N/A
System administration processes, and supporting system administration procedures, are developed and implemented.
Security Control: ISM-1211; Revision: 5; Updated: Mar-22; Applicability: All; Essential Eight: N/A
System administrators document requirements for administrative activities, consider potential security impacts, obtain
any necessary approvals, notify users of any disruptions or outages, and maintain system and security documentation.
Separate privileged operating environments
One of the greatest threats to the security of networks is the compromise of privileged accounts. Providing a separate
privileged operating environment for system administrators, in addition to their unprivileged operating environment,
makes it much harder for administrative activities and privileged accounts to be compromised by an adversary.
Using different physical workstations is the most secure approach to separating privileged and unprivileged operating
environments for system administrators. However, a virtualisation-based solution may be sufficient for separating
privileged and unprivileged operating environments. In such cases, privileged operating environments should not be
virtualised within unprivileged operating environments.
Security Control: ISM-1380; Revision: 5; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Privileged users use separate privileged and unprivileged operating environments.
Security Control: ISM-1687; Revision: 0; Updated: Sep-21; Applicability: All; Essential Eight: ML2, ML3
Privileged operating environments are not virtualised within unprivileged operating environments.
92
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents