Guidelines for System Hardening
Operating system hardening
Operating system selection
When selecting operating systems, it is important that an organisation preferences vendors that have demonstrated a
commitment to secure-by-design principles, secure programming practices and maintaining the security of their
products. This will assist not only with reducing the potential number of security vulnerabilities in operating systems,
but also increasing the likelihood that timely patches, updates or vendor mitigations will be released to remediate any
security vulnerabilities that are found.
Security Control: ISM-1743; Revision: 0; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Operating systems are chosen from vendors that have made a commitment to secure-by-design principles, secure
programming practices and maintaining the security of their products.
Operating system releases and versions
Newer releases of operating systems often introduce improvements in security functionality. This can make it more
difficult for an adversary to craft reliable exploits for security vulnerabilities they discover. Using older releases of
operating systems, especially those no longer supported by vendors, may expose an organisation to security
vulnerabilities or exploitation techniques that have since been mitigated. In addition, 64-bit versions of operating
systems support additional security functionality that 32-bit versions do not.
Security Control: ISM-1407; Revision: 4; Updated: Sep-21; Applicability: All; Essential Eight: ML3
The latest release, or the previous release, of operating systems are used for workstations, servers and network devices.
Security Control: ISM-1744; Revision: 0; Updated: Mar-22; Applicability: All; Essential Eight: N/A
The latest release, or the previous release, of operating systems are used for other ICT equipment.
Security Control: ISM-1408; Revision: 4; Updated: Mar-22; Applicability: All; Essential Eight: N/A
Where supported, 64-bit versions of operating systems are used for workstations, servers, network devices and other ICT
equipment.
Standard Operating Environments
Allowing users to setup, configure and maintain their own workstations and servers can result in an inconsistent
operating environment. Such operating environments may assist an adversary in gaining an initial foothold on networks
due to the higher likelihood of poorly configured or maintained workstations and servers. Conversely, a Standard
Operating Environment (SOE) is designed to facilitate a standardised and consistent operating environment within an
organisation.
When SOEs are obtained from third parties, such as service providers, there are additional cyber supply chain risks that
should be considered, such as the accidental or deliberate inclusion of malicious code or configurations. To reduce the
likelihood of such occurrences, an organisation should endeavour to obtain their SOEs from trusted third parties while
also scanning them for malicious code and configurations.
As operating environments naturally change over time, such as patches or updates are applied, configurations are
changed, and applications are added or removed, it is essential that SOEs are reviewed and updated at least annually to
ensure that an up-to-date baseline is maintained.
Security Control: ISM-1406; Revision: 2; Updated: Aug-20; Applicability: All; Essential Eight: N/A
SOEs are used for workstations and servers.
75
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents