ASD ISM 1968 Obtain authorisation for TOP SECRET systems
What it says
System owners obtain an authorisation to operate for each TOP SECRET system, including for each sensitive compartmented information system, from Director-General ASD (or their delegate).
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
System owners must obtain an authorisation to operate from Director-General ASD (or their delegate) for each TOP SECRET system, including each sensitive compartmented information system.
System owners must obtain an authorisation to operate for each TOP SECRET system, including each sensitive compartmented information system, from Director-General ASD (or their delegate). An authorisation to operate is the formal decision that a system may run, based on accepting the security risks of running it. Sensitive compartmented information is limited to people briefed into its compartment. A decision by anyone else in the organisation does not meet this control, unless they hold a delegation from Director-General ASD.
Free. Save your status, tasks and notes.
Why it matters
On these systems the decision to accept security risk sits with Director-General ASD (or their delegate), not the organisation's own executives. Without that authorisation, a TOP SECRET system runs on risks nobody with the authority has accepted, however confident its owners are.
How to implement
Contact ASD during system planning to find out who will decide.
Ask whether Director-General ASD or a delegate will make the decision and what they need to see. Allow for this in your schedule, and keep any delegation details on file.
Complete the assessment by ASD assessors first.
That assessment (ISM-1967) gives the decision its evidence. Plan for each sensitive compartmented information system separately, because each needs its own authorisation.
Prepare the authorisation package.
Include the system security plan (ISM-0041), cyber security incident response plan (ISM-0043), change and configuration management plan (ISM-0912), continuous monitoring plan (ISM-1163), security assessment report (ISM-1563) and plan of action and milestones (ISM-1564). Ask ASD if it wants anything else.
Hold go-live until the authorisation is granted.
Keep the decision, who made it, its date and any limits or expiry date. An approval from your own executives is an internal step only. For a system already running without one, tell Director-General ASD (or their delegate) now and ask for a decision.
Keep it running
Honour any limits, start renewal before an expiry date and report security status at least annually (ISM-1587). After major changes or a major incident, update the package so Director-General ASD (or their delegate) can keep, limit or revoke the authorisation.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
A list of every TOP SECRET and sensitive compartmented information system, records to compare it with (such as facility or network records), and the authorisation for each.
Look at
Whether any system is missing from the list or has no authorisation of its own.
Good evidence
Every TOP SECRET system, including each sensitive compartmented information system, is on the list and holds its own current authorisation to operate.
- Check 2 of 4What an auditor asks for
Ask for
The authorisation to operate for a sampled system, and any delegation behind it.
Look at
Who made the decision and what authority they held.
Good evidence
Director-General ASD, or a delegate whose delegation is on record, made the decision, and no internal approval stands in for it.
- Check 3 of 4What an auditor asks for
Look at
Whether authorisation came before operation, whether it followed the assessment and whether it covers the system as it is now.
Good evidence
The system began operating after the authorisation date or, if it was already running when authorisation was introduced, now holds an authorisation, and that authorisation follows an assessment under ISM-1967 and covers the current boundary.
- Check 4 of 4What an auditor asks for
Ask for
The limits and any expiry date set in the authorisation, with the live configuration they apply to.
Look at
Whether each limit is in force and whether the authorisation has expired.
Good evidence
The authorisation is either recorded as ongoing with no limits, or has not expired and each limit it sets is in force on the live system.
Mappings
No mappings to other frameworks are recorded for this control yet.




