ASD ISM 1912 Document device settings for critical and high-value servers
What it says
Network documentation includes device settings for all critical servers, high-value servers, network devices and network security appliances.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishKeep records of settings for important servers and network devices to ensure strong network security.
This control is about keeping detailed records of the settings for important servers and network devices. Proper documentation helps ensure you can quickly restore systems if something goes wrong, like a cyber attack or system failure. Without these records, it could take longer to fix issues, leading to downtime and potential loss of data.
Free. Save your status, tasks and notes.
Why it matters
Without documented settings for critical and high-value servers, incident recovery and rebuilds are slower, increasing downtime and risk of data loss.
How to implement
The IT team should maintain an up-to-date inventory of all critical and high-value servers.
This means having a list that includes each server's purpose, location, and key settings. They can use a simple spreadsheet or a specialised software tool to keep everything organised.
Managers should ensure that documentation processes are formally established.
This means setting up clear guidelines on how and when settings should be recorded or updated. These guidelines should be communicated to everyone involved, ensuring consistency in documentation.
IT staff should regularly back up configuration settings for servers and network devices.
This involves saving the current settings file to a secure location so that it can be used for recovery if needed. This backup should be part of a regular schedule, like weekly or after every major change.
System administrators should review and update server documentation whenever changes are made.
This means every time a significant change occurs, such as installing a new application or updating software, the documentation must reflect these changes to remain accurate.
Business owners should ensure their IT team performs periodic audits of the documentation.
This involves reviewing the documentation to check that all critical systems are accounted for and that no discrepancies exist between what's on the document and what's in reality. This helps to identify areas that may need attention.
Keep it running
Record and version device settings for critical/high-value servers, network devices and security appliances; validate during change windows so rebuilds restore known-good configs.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The server inventory list: Request to see the detailed list of servers and devices.
Look at
Whether the list covers all critical and high-value systems and includes up-to-date settings.
Good evidence
Is a comprehensive list that matches the current hardware and configurations used by the organisation.
- Check 2 of 5What an auditor asks for
Ask for
The latest backup record: Obtain the records confirming backups of device settings.
Look at
The frequency of these backups and where they are stored.
Good evidence
Is recent backups stored securely with a documented schedule showing regular intervals.
- Check 3 of 5What an auditor asks for
Ask for
Logs or tracking documents showing when settings were last updated. Verify that recent and past changes are documented.
Good evidence
Is a tracking system with timestamps and change descriptions, showing it is actively maintained.
- Check 4 of 5What an auditor asks for
Ask for
The guidelines on documentation standards: Request the written guidelines or policies regarding the documentation of server settings.
Look at
How these guidelines ensure accuracy and consistency.
Good evidence
Is a clear, accessible document that outlines processes and responsible parties.
- Check 5 of 5What an auditor asks for
Ask for
Records showing reviews or audits of the documentation.
Look at
How often these audits occur and their findings.
Good evidence
Is periodic audit reports with actionable insights and confirmation of no major discrepancies.
Mappings
Closest match in ISO/IEC 27001: A.8.20, Network and network devices security, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.20.
ISM-1912 requires organisations to document device settings for critical and high-value servers, network devices and security appliances. Annex A 8.20 requires networks and network devices to be secured, managed and controlled, enabled by reliable configuration documentation for baselining and change validation. ISM-1912 is documentation-centric, while Annex A 8.20 is operational security management of networks/devices.
This control partially overlaps A.8.9.
Annex A 8.9 requires organisations to document and maintain configurations for systems and to keep them under review. ISM-1912 relates by requiring network documentation to include device settings for critical/high-value servers and key network/security devices, a form of configuration documentation. ISM-1912 focuses on specific asset classes, while Annex A 8.9 also requires establishing/implementing configurations and monitoring/reviewing them over time.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




