Skip to content
Gateways
ASD ISMISM-0611

ASD ISM 0611 Restrict privileges for gateway administrators

What it says

System administrators for gateways are assigned the minimum privileges required to perform their duties.

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

What it means

In plain English

Gateway admins have only the necessary access permissions for their tasks.

This guideline is about making sure that people who manage gateway systems have just enough access to do their job and no more. If they have too much access, there's a higher chance of accidental or malicious damage, which could lead to data breaches or loss of service.

Why it matters

Excess gateway admin privileges can lead to unauthorised data access, increasing the risk of data breaches and service outages.

How to implement

  1. The IT manager should create a list of all the tasks that gateway administrators do so they can decide what access is necessary.

    This involves talking to the administrators about their daily duties and understanding each task's requirements.

  2. HR and IT should work together to define roles and responsibilities clearly.

    They should document what access each role needs, and ensure this is reflected in the IT systems by setting permissions accordingly.

  3. System administrators should regularly review and audit the access levels of gateway administrators to ensure they have only what is necessary.

    They can do this by running reports on who has access to what and assessing whether it aligns with their current job responsibilities.

  4. The IT team should use a system that logs and monitors access attempts and activities on gateways.

    They can set up alerts for unusual access patterns to detect any misuse of privilege.

Keep it running

Regularly review gateway admin accounts and role memberships to confirm only minimum required privileges are assigned, and promptly remove any unnecessary access.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    A document that lists all gateway administrators and their access levels.

    Look at

    The specific permissions each administrator has been granted.

    Good evidence

    Shows each person has only the permissions required for their role, with unnecessary permissions removed.

  2. Check 2 of 5What an auditor asks for

    Look at

    Documented outcomes that indicate if any changes or revocations of access were necessary.

    Good evidence

    Includes evidence of regular reviews and prompt adjustments.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Logs or records of access attempts to the gateways.

    Look at

    Whether there are any alerts or incidents related to unauthorised access.

    Good evidence

    Shows that the organisation monitors access continuously and responds to potential threats swiftly.

  4. Check 4 of 5What an auditor asks for

    Good evidence

    Is a complete training record with recent updates.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Access change requests documentation.

    Look at

    How changes to access levels are requested and authorised.

    Good evidence

    A clear process with approvals documented in each instance, demonstrating control over access modifications.

Mappings

Closest match in ASD Essential Eight: E8-RA-ML3.1, Limit privileged access to what is necessary for duties, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 3 mappings

Essential Eight

ASD Essential Eight: 1 mapping

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