Skip to content
Networking
ASD ISMISM-1912

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 English

Keep 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.

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 27001

ISO/IEC 27001: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.