Skip to content
System access
ASD ISMISM-0854

ASD ISM 0854 Access restrictions for AUSTEO and AGAO data

What it says

AUSTEO and AGAO data can only be accessed from systems under the sole control of the Australian Government that are located within facilities authorised by the Australian Government.

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

What it means

In plain English

AUSTEO and AGAO data is only accessible via government-controlled systems within authorised facilities.

AUSTEO (Australian Eyes Only) and AGAO (Australian Government Access Only) data must be accessed only through government-controlled systems within approved locations. This is crucial because if this sensitive data falls into the wrong hands, it could threaten national security or harm diplomatic relations.

Why it matters

If AUSTEO and AGAO data is accessed outside authorised systems, it risks exposure to unauthorised entities, undermining national security.

How to implement

  1. IT managers should ensure systems that store or access AUSTEO or AGAO data are physically located within government-approved facilities.

    They can do this by conducting regular audits of the data storage locations and verifying if they meet government standards.

  2. System administrators need to set up strict permissions on government systems that handle AUSTEO or AGAO data.

    They should use a checklist provided by the Australian Cyber Security Centre (ACSC) to ensure only authorised personnel have access.

  3. Facility managers must confirm that physical security controls, like surveillance and access badges, are in place at locations handling sensitive data.

    They should regularly inspect these controls to ensure they are functioning correctly.

  4. Compliance officers should work closely with government agencies to keep updated on authorised facilities.

    This involves checking with the Australian Signals Directorate (ASD) for any changes in facility authorisation.

  5. Human Resources should train staff on the importance of using only authorised systems and facilities for AUSTEO and AGAO data.

    This can be done through regular workshops and mandatory security training sessions.

Keep it running

Audit access logs to confirm AUSTEO/AGAO data is only accessed from Australian Government-controlled systems in authorised facilities.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The list of systems authorised to handle AUSTEO/AGAO data: Request documentation from IT showing which systems are used.

    Look at

    The locations and control measures listed.

    Good evidence

    All systems are within authorised facilities with government-controlled access permissions.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Facility authorisation records: Request proof that facilities storing or accessing the data are approved by the government.

    Look at

    The dates and signatures of authorisation.

    Good evidence

    Records are current and signed by the relevant government authority.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Access logs for systems used for AUSTEO/AGAO data: Request system logs from IT to see who accessed the data.

    Look at

    Access times and user IDs.

    Good evidence

    Only authorised users accessed data, and logs show consistent patterns with no anomalies.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Security training records: Request evidence of security training for personnel accessing AUSTEO/AGAO data.

    Look at

    Attendance records and training content.

    Good evidence

    Comprehensive training was conducted regularly, and all staff attended.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Physical security inspection reports: Request records of physical security checks for facilities with sensitive data.

    Look at

    Detailed checklists and dates.

    Good evidence

    Regular inspections were conducted, showing all security measures are in place and functional.

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: 2 mappings

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