Skip to content
System access
ASD ISMISM-1611

ASD ISM 1611 Use break glass accounts only in emergencies

What it says

Break glass accounts are only used when normal authentication processes cannot be used.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Break glass accounts should be used only if normal login methods fail.

A 'break glass' account is like an emergency key that should be used only if the usual way of getting into a computer system is not working. It's important because if you can use this emergency access too easily or often, it could let people sneak in who shouldn't be there, putting your organisation's sensitive information at risk.

Why it matters

Excessive use of break glass accounts can lead to unauthorised access, compromising sensitive data and weakening overall security posture.

How to implement

  1. The IT team should designate specific break glass accounts for emergency situations only.

    They will need to create these accounts with minimal permissions and securely store the credentials where only authorised personnel can access them in times of crisis.

  2. The system owner should ensure that appropriate personnel know when and how to use break glass accounts.

    This can be done by including this procedure in regular training or communication meetings, explaining the specific scenarios when it's permissible to use these accounts.

  3. Managers should enforce strict logging and monitoring whenever a break glass account is used.

    This means ensuring that every use is tracked with details such as user, time, and reason for access, ideally with automated alerts to flag any unusual activity.

  4. Senior management should periodically review the necessity of each break glass account with the IT department.

    They can do this by assessing how often these accounts are used and confirming that their use aligns with documented emergency scenarios.

  5. The cyber security officer should implement a regular audit to ensure break glass accounts are kept secure and not used for non-emergency access.

    They can do this by checking logs and conducting surprise checks to verify adherence to security protocols.

Keep it running

Audit and review break glass use regularly; ensure each use is logged, monitored, and justified as an emergency.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The log of break glass account usage: Request a report detailing each time a break glass account was accessed.

    Look at

    Entries specifying the time, user, and reason for access.

    Good evidence

    Each entry matches a documented emergency situation and is verified by management approval.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see the list of authorised personnel: Request the latest list of staff authorised to use break glass accounts.

    Look at

    The roles and departments of the listed personnel. Good practice is having only key IT and senior staff with this authority, ensuring it's not overly broad.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Training records on break glass accounts: Request evidence of training related to the use of these accounts.

    Look at

    Recent sessions and participation logs.

    Good evidence

    Includes details where training scenarios reflect actual emergency situations and the list of attendees includes all relevant personnel.

  4. Check 4 of 5What an auditor asks for

    Ask for

    To review security policy documentation: Request the latest version of your security policy, highlighting sections on emergency access.

    Look at

    Clear procedures on when and how break glass accounts can be used.

    Good evidence

    Is having documented step-by-step guidelines that align with best practices.

  5. Check 5 of 5What an auditor asks for

    Ask for

    An audit summary report: Request the latest audit results for break glass accounts.

    Look at

    What issues were found and how they were resolved. Good practice is when no unauthorised access was found and prompt corrective steps were taken for any deviations.

Mappings

Closest match in ISO/IEC 27001: A.5.15, Access control policies and procedures, which this control partially meets.

ISO 27001

ISO/IEC 27001: 1 mapping

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