Skip to main content
Compliance guideReviewed

SOCI Act: what the Security of Critical Infrastructure Act asks of responsible entities, and where a website or app fits

The SOCI Act ties its duties to defined classes of critical infrastructure asset and to the entities that hold set roles for them.

Among those duties are giving ownership and operational information for a register the Secretary keeps, a written risk management program, cyber security incident reports under sections 30BC and 30BD, each with its own trigger and time limit, and further obligations for Systems of National Significance. This guide reads the Act and its rules from the Federal Register of Legislation, shows where a website, portal or app can fall inside them, sets out the evidence that testing a web application can supply, and its limits, and comes with a decision tree for a responsible entity and the businesses that supply one.

SOCI Act responsible-entity decision tree

A decision tree in table form for the responsible entity for a critical infrastructure asset and for a business that supplies one. Rows T1 to T3 work through asset scope and which parts of the Act apply; T4 and T5 place websites, portals, APIs and data stores; T6, T7 and T10 cover risk management program evidence; T8 and T9 follow the cyber incident reporting duties in sections 30BC and 30BD; T11 and T12 cover systems of national significance and the separate vulnerability assessment notice regime; and T13 to T15 are for a supplier.

How to use it

Start at T1, write each answer in a dated note with the document behind it, and follow the "If yes" or "If no, or not sure" column to the next row. Each row works from documents (the Act, the rules, notices, contracts and your own records); no row sends anything to any system. The second column gives each provision in its words or a faithful short form, with its section number, from Compilation No. 9 of the Act and the compilations of the rules named on this page. The tree records facts and evidence. Whether the Act applies, and whether an obligation is met, is for the responsible entity, its governing body and its adviser, and the officials the Act names; for a supplier, it is for its customer and its own adviser.

15 rows

SOCI Act responsible-entity decision tree

Row and questionWhat the Act or rules sayIf yesIf no, or not sureWhat a website or app test can evidenceWhat a test cannot show, and who decidesLimits of this row
T1. Asset scope: does your business own, operate, manage or hold an interest in an asset that may be a critical infrastructure asset?Section 9(1) lists the classes of critical infrastructure asset, from a critical telecommunications asset to a critical defence industry asset, plus an asset declared under section 51 or prescribed by the rules; each class has its own definition, some with thresholds in the Act or the rules. Section 9(2), (2A) and (2B) take some assets out; under section 9(2B), subject to subsections (2C) and (2D), an asset is not a critical infrastructure asset if, or to the extent to which, it is located outside Australia. Section 8D lists the critical infrastructure sectors, and section 8E says which sector each class is taken to relate to.Record the class and the definition the asset may meet, then go to T2.If your business has no such asset, go to T13. If you are not sure, take the question and the facts about the asset to your adviser, and come back to this row with the answer; CISC points readers who are unsure to its Critical Infrastructure Asset Class Definition Guidance.Nothing. Asset status turns on the Act's definitions and the facts, not on how a system behaves.Whether the asset falls within a class or an exclusion. The entity establishes it with its adviser, and the Minister may declare an asset under section 51.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T2. Which role does your business hold for that asset?Section 12L names the responsible entity for each class, or another entity the rules prescribe or a declaration specifies. Section 8(1): a direct interest holder holds, with any associates, an interest of at least 10% in the asset, or an interest that puts it in a position to directly or indirectly influence or control the asset, subject to the exemptions in subsections 8(2), 8(4) and 8(5). Section 5: a relevant entity is the responsible entity, a direct interest holder, an operator of the asset or a managed service provider for it.Responsible entity: go to T3. Direct interest holder: CISC says direct interest holders only have the obligation to register if you have a direct interest in the CI asset; confirm your position with your adviser, including whether section 18A applies Part 2 to the asset. Direct interest holder, operator or managed service provider: each is a relevant entity under section 5, so record the role, go to T11 to see whether the asset is a system of national significance, then go to T13.Where ownership, operation and management are split between businesses, set out who does what and take it to your adviser before going further. If none of the roles fits, go to T13.Nothing.Which role applies. The entity and its adviser establish it from the Act, the rules and any declaration.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T3. Which parts of the Act apply to the asset?Part 2 (register): section 18A and section 4(1) of the Application Rules. Part 2A (program): section 30AB and section 4(1) of the CIRMP Rules, subject to the exceptions in section 30AB(3) to (6). Part 2B (incident reports): section 30BB and section 5(1) of the Application Rules. Section 12F(3): CISC says it applies to all critical infrastructure assets. Grace periods: section 4(3) of the Application Rules (Part 2), section 4(2) of the CIRMP Rules (Part 2A) and section 5(5) of the Application Rules (Part 2B).Record each part that applies and from what date, then go to T4.Record why a part does not apply (the class is not specified, an exception applies, or a grace period is running) and any date on which that changes. If no part applies, go to T11 and then T13.Nothing.Which parts apply. The entity establishes it with its adviser; a declaration under section 51 can also determine that a part applies.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T4. Website and app dependencies: is a website, portal, API or data store part of the asset?Section 5: asset includes a system, a computer, a computer program and computer data. Section 9(7): a data storage system is taken to be part of a critical infrastructure asset when the responsible entity owns or operates it, it is used or is to be used in connection with the asset, business critical data is stored or processed in or by it, and a hazard with a material risk of an impact on the data storage system also carries a material risk of a relevant impact on the asset. CISC: a single critical infrastructure asset includes multiple parts which function together as a system or network.List each web-facing system that is part of the asset, with the data it holds and who runs it. For a data storage system under section 9(7), the subsection's note gives as examples that Part 2 obligations take it into account, a Part 2A program covers it, and Part 2B notification takes into account any relevant impact on it. Go to T5.List the system as related to the asset rather than part of it, with the reason, and still go to T5: the CIRMP Rules define a cyber and information security hazard to include improper access to, or misuse of, information or computer systems about or related to the CI asset.Older API versions that still respond are flagged in a Clever Ops web application and API penetration test and brought into scope once you confirm them in writing, which can reveal a route missing from your list. The written scope of each past test shows which systems it examined.Whether a system is part of the asset, a data storage system under section 9(7) or a critical system under the CIRMP Rules. The responsible entity decides with its adviser.Read-only row: the list comes from your own records and contracts, and nothing is sent to any system.
T5. Is business critical data stored or processed in a web-facing system, or by an outside provider?Section 5: business critical data means personal information (within the meaning of the Privacy Act 1988) that relates to at least 20,000 individuals, information relating to any systems needed to operate a critical infrastructure asset, information needed to operate one, or information relating to research and development, or to risk management and business continuity (however described), in relation to one. Section 12F(3): a responsible entity that becomes aware that a data storage or processing service provided by another entity on a commercial basis to it relates to business critical data must take reasonable steps to inform that entity that it has become aware of this, as soon as practicable after becoming so aware. Section 7(1)(f) and Definitions Rules section 17: operational information includes a description of the arrangements for prescribed data another entity maintains, including the name of the cloud service where one is used.Record the system or provider, the kinds of data, and, for an outside provider, the date and manner in which it was informed under section 12F(3). Go to T6.Record the reasons, and the date to look again if the data held changes. Go to T6.For the build and test accounts tested, whether one account could read another account's records and what the system returned to a request made while signed out.How much data a system holds, or whether it is business critical data. Those come from the entity's records, and the entity and its adviser decide whether a provider has to be informed.Read-only row: data inventories and contracts only. No record holding real personal information is opened, and nothing is sent to any system.
T6. Program evidence: does the program identify and treat cyber and information security hazards for each system in T4 and T5?CIRMP Rules section 8(2): a process or system to, as far as it is reasonably practicable to do so, minimise or eliminate any material risk of a cyber and information security hazard occurring and mitigate its relevant impact on the asset. Section 6: material risk includes impact to the availability, integrity, reliability or confidentiality of the data storage system holding business critical data. Section 7(1): identify the operational context of the asset and its material risks.Record where the program covers each system, the date of the evidence it relies on, and the owner. Go to T7.Record the gap, its owner and a date, and raise it in the program review under section 30AE. Go to T7.For the build, accounts and roles tested: findings and negative results on sign-in and sessions, access between accounts and roles, the API called directly and file uploads, each finding carrying its retest status. That is evidence the entity can use when it identifies and treats these hazards for that system.Whether Part 2A covers your business, which you establish with your own adviser, and whether the program meets section 8 or Part 2A. The responsible entity decides the second, and its governing body, if it has one, approves the annual report under section 30AG.Read-only row: the program and existing reports only, with nothing sent to any system. A new test of a system in T4 is planned separately, under the responsible entity's written authorisation and rules of engagement it approves.
T7. Which framework does the program follow, and do enhanced requirements apply?CIRMP Rules section 8(4): a process or system to comply with a framework contained in a listed document and meet any listed condition: AS ISO/IEC 27001:2015; the Essential Eight Maturity Model (maturity level one); the NIST Framework for Improving Critical Infrastructure Cybersecurity; the US Department of Energy Cybersecurity Capability Maturity Model (Maturity Indicator Level 1); or the 2020-21 AESCSF Framework Core (Security Profile 1). Section 8(5): or an equivalent framework, including any conditions. For classes in section 4A(1): section 8A(3) lists its own documents and conditions, section 8A(4) allows an equivalent framework to some of them, section 8B covers phishing resistant multi-factor authentication where the framework does not require it, and section 8C asks, among other things, for an inventory of critical systems and how they connect.Record the framework and its condition, whether the asset is in section 4A(1) and which grace period in section 4A(6) applies, and the evidence held for each web-facing system. Go to T8.Take it to the program owner and your adviser; section 8(3) sets the period for complying with section 8(4) or 8(5). Go to T8.For sign-in to the tested application: whether the test accounts were asked for a second factor and which kinds the application accepted, on the build tested. The report also states its coverage.Whether the program follows any framework or meets its condition, whether a factor is phishing resistant under the rules, and the logging and review in section 8B(5)(b). The entity and its adviser settle these.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T8. Section 30BC, the 12-hour path: has the responsible entity become aware that a cyber security incident has occurred or is occurring and has had, or is having, a significant impact (whether direct or indirect) on the availability of an asset Part 2B applies to?Section 30BC(1): report to the relevant Commonwealth body as soon as practicable, and in any event within 12 hours, after the entity becomes so aware. Section 30BEA: a significant impact on availability if, and only if, the asset is used in connection with the provision of essential goods or services and the incident has materially disrupted the availability of those essential goods or services, or circumstances specified in the rules exist. Section 30BC(3): if the report is given orally, the entity must make a written record of it in the approved form and give a copy to the relevant Commonwealth body within 84 hours after the report is given; under section 30BC(5), the head of that body may exempt the entity from this, by written notice, for a report about a specified incident. Section 12M defines a cyber security incident.Follow the entity's incident process for the 12-hour path, recording when the entity became aware and when and how the report was given. The note to section 18 of the Definitions Rules says the relevant Commonwealth body for the other provisions of Part 2B is ASD. Then go to T9.Go to T9.Nothing. A test is not a report, and testing during an incident can disturb what responders need to see.Whether section 30BC covers your business and the asset, whether an event is a cyber security incident with a significant impact, and when the entity became aware. You establish each of these with your own adviser.Read-only row: the incident record only, with nothing sent to any system. It is a planning row, not an incident response procedure.
T9. Section 30BD, the 72-hour path: has the responsible entity become aware that a cyber security incident has occurred, is occurring or is imminent, and has had, is having, or is likely to have, a relevant impact on an asset Part 2B applies to?Section 30BD(1): report to the relevant Commonwealth body as soon as practicable, and in any event within 72 hours, after the entity becomes so aware. Section 8G(2): the relevant impacts of an incident are its impacts, whether direct or indirect, on the availability, integrity and reliability of the asset and on the confidentiality of information about it, of information stored in it or, if the asset is computer data, of that data. Section 30BD(3): if the report is given orally, the entity must make a written record in the approved form and give a copy to that body within 48 hours after the report is given; section 30BD(5) gives the head of that body the same power to exempt by written notice.Follow the 72-hour path and record the same times as in T8. Ask your adviser separately whether another regime, such as the Notifiable Data Breaches scheme, reaches the same event. Then go to T10.Record that no Part 2B report was made, and why. Go to T10.Nothing, for the reasons in T8. Separately, rules of engagement for any test should name who the tester tells, and how fast, if testing turns up signs that someone else has been in the system.Whether section 30BD covers your business and the asset, and whether a relevant impact has occurred or is likely. You establish both with your own adviser.Read-only row: as in T8, the incident record only, and nothing is sent to any system. Use it to plan; it does not replace an incident response procedure.
T10. Is the program reviewed, kept up to date and reported on?Section 30AE: review the program on a regular basis. Section 30AF: take all reasonable steps to ensure it is up to date. Section 30AG(2): within 90 days after the end of the financial year, a report in the approved form to the relevant Commonwealth regulator that has functions relating to the security of those assets, if there is one, or otherwise to the Secretary, stating whether the program was up to date (where the entity had it at the end of the year) and covering any hazard that had a significant relevant impact, approved by the board, council or other governing body if the entity has one. Section 30AI: a relevant official may direct a variation for a serious deficiency.Record the review date, the report date and the approving body. Go to T11.Record what is missing and who owns it. Go to T11.Dated reports and retest statuses for each web-facing system, which a review can cite as the evidence from the last test of that system.Whether sections 30AE to 30AG cover your business, which you establish with your own adviser, and whether the program is up to date or the report is accurate, which the entity and its governing body decide.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T11. Has the Minister declared the asset a system of national significance?Section 52B(1): the Minister may declare a critical infrastructure asset to be a system of national significance if satisfied that it is of national significance, having regard to the matters in section 52B(2), and section 52B(3) says the Minister must notify the responsible entity, among others, in writing within 30 days. The note to section 52A says it is an offence to disclose that an asset has been declared one (see section 45). CISC: ECSOs can only be applied to SoNS, not critical infrastructure more broadly.Keep the declaration in a restricted file, and go to T12.Record that no declaration has been notified. Go to T13 if your business also supplies other entities; otherwise the tree ends here.Nothing.Whether an asset is of national significance. The Minister decides.Read-only row: the declaration, if there is one, and nothing is sent to any system. Check section 45 and Division 3 of Part 4, on the use and disclosure of protected information, with your adviser before telling anyone about a declaration.
T12. Has the Secretary given a written notice requiring a vulnerability assessment?Section 30CU: the Secretary may, by written notice to the responsible entity for a system of national significance, require it to undertake, or cause to be undertaken, a vulnerability assessment of the system for all types of cyber security incidents or specified types, within the period the notice specifies, after having regard to the matters in section 30CU(3), such as costs, reasonableness and proportionality, and consulting the entity and any relevant Commonwealth regulator with functions relating to the security of the system. Section 30CV: the entity must comply. Section 30CY: the assessment's purpose is to test the vulnerability of the system to those types of cyber security incidents, and it complies with requirements (if any) in the rules. Section 30CZ: the entity must prepare, or cause to be prepared, a vulnerability assessment report and give a copy to the Secretary within 30 days after the completion of the assessment, or a longer period if the Secretary allows one. Section 30CW: in the cases it sets out, a designated officer may undertake the assessment.Read the notice for the system, the incident types and the period. Decide who undertakes the assessment against the notice, the Act and any rules, with your adviser and, where useful, CISC. Diary the report date, 30 days after completion unless the Secretary allows longer. Then go to T13 if your business also supplies other entities; otherwise the tree ends here.No assessment under section 30CU has been required. Separately, section 30CB lets the Secretary, by written notice to the responsible entity for a system of national significance, determine that the statutory incident response planning obligations apply to it. Go to T13 if your business also supplies other entities; otherwise the tree ends here.A web application test commissioned for another purpose is not an assessment under section 30CU. Its report can be background the entity shares with whoever undertakes the assessment, if the notice and the entity allow.Whether an assessment meets the notice, the Act and the rules. The entity is responsible for complying, and the Secretary receives the report.Read-only row: the notice only, and nothing is sent to any system. A vulnerability assessment under section 30CU is for the responsible entity to arrange, with a provider suited to that work and to what the notice, the Act and any rules require.
T13. Supplier: do you supply a responsible entity, or has a customer informed you under section 12F(3)?Section 12F(3): a responsible entity must take reasonable steps to inform a provider of a data storage or processing service provided to it on a commercial basis that relates to business critical data, as set out in T5. CISC says this ensures that companies that handle sensitive data are aware that they may also have obligations under the SOCI Act. Section 12F(1) and (2) define a critical data storage or processing asset, and section 12L(4) makes the provider that owns or operates it the responsible entity, unless the rules prescribe another entity.If a customer has informed you under section 12F(3), take what it told you, with a description of the services and customers concerned, to your adviser and ask whether section 12F(1) or (2) makes any of your assets a critical data storage or processing asset; if it does, start again at T2 for that asset. Then go to T14.Go to T14 if a customer has raised the Act in a contract or a questionnaire. Otherwise the tree ends here.Nothing for this row.Whether you hold a role under the Act. You decide with your adviser.Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
T14. What has the customer asked of you about its program, your testing or your access?CIRMP Rules section 10(1): the responsible entity must establish and maintain in its program a process or system to minimise or eliminate, as far as it is reasonably practicable to do so, supply chain material risks including misuse of privileged access to the asset by any provider in the supply chain and risks arising from major suppliers. Section 10A, for classes with enhanced requirements: a system or process to map the supply chain for major suppliers and critical components, and one to assess the risks of each existing or proposed major supplier, identifying among other things the access, influence and control it has over the asset in connection with the product or service it provides.List each request in the customer's exact words, the contract clause behind it, the evidence you hold and the date you answered. Go to T15.Keep this row ready for the next contract renewal or questionnaire, then go to T15.Your own dated test reports and retest statuses for the product or service you provide, shared on the terms your contract allows, answer questions about your testing. For wording the answers themselves, see the security questionnaires guide.Whether the customer's program can rely on your evidence is the customer's judgement. What your agreement obliges you to do is something to ask your own adviser.Read-only row: the customer's requests, your contracts and your own reports, with nothing sent to any system.
T15. What have you agreed to tell the customer about an incident, and how fast?The reporting duties in sections 30BC and 30BD fall on the responsible entity, with limits counted from when it becomes aware. Section 30BE(4): a contracted service provider responsible under a contract for providing services to an entity subject to section 30BC or 30BD, and that provider's officers, employees and agents, are not liable to an action or other proceeding for damages for or in relation to an act done or omitted in good faith for the purposes of ensuring or facilitating compliance with the requirement.Put the agreement's notification terms, contact names and channels into your own incident plan, and check that the contacts are current. The tree ends here.Ask the customer what it needs from you and how fast, and record the answer in writing. Have your own adviser explain what your agreement obliges you to do. The tree ends here.Nothing about notification.What the agreement obliges you to do. Ask your own adviser.Read-only row: your agreement and your incident plan, with nothing sent to any system.

Row and question

What the Act or rules say

  1. T1. Asset scope: does your business own, operate, manage or hold an interest in an asset that may be a critical infrastructure asset?
    What the Act or rules say
    Section 9(1) lists the classes of critical infrastructure asset, from a critical telecommunications asset to a critical defence industry asset, plus an asset declared under section 51 or prescribed by the rules; each class has its own definition, some with thresholds in the Act or the rules. Section 9(2), (2A) and (2B) take some assets out; under section 9(2B), subject to subsections (2C) and (2D), an asset is not a critical infrastructure asset if, or to the extent to which, it is located outside Australia. Section 8D lists the critical infrastructure sectors, and section 8E says which sector each class is taken to relate to.
    If yes
    Record the class and the definition the asset may meet, then go to T2.
    If no, or not sure
    If your business has no such asset, go to T13. If you are not sure, take the question and the facts about the asset to your adviser, and come back to this row with the answer; CISC points readers who are unsure to its Critical Infrastructure Asset Class Definition Guidance.
    What a website or app test can evidence
    Nothing. Asset status turns on the Act's definitions and the facts, not on how a system behaves.
    What a test cannot show, and who decides
    Whether the asset falls within a class or an exclusion. The entity establishes it with its adviser, and the Minister may declare an asset under section 51.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  2. T2. Which role does your business hold for that asset?
    What the Act or rules say
    Section 12L names the responsible entity for each class, or another entity the rules prescribe or a declaration specifies. Section 8(1): a direct interest holder holds, with any associates, an interest of at least 10% in the asset, or an interest that puts it in a position to directly or indirectly influence or control the asset, subject to the exemptions in subsections 8(2), 8(4) and 8(5). Section 5: a relevant entity is the responsible entity, a direct interest holder, an operator of the asset or a managed service provider for it.
    If yes
    Responsible entity: go to T3. Direct interest holder: CISC says direct interest holders only have the obligation to register if you have a direct interest in the CI asset; confirm your position with your adviser, including whether section 18A applies Part 2 to the asset. Direct interest holder, operator or managed service provider: each is a relevant entity under section 5, so record the role, go to T11 to see whether the asset is a system of national significance, then go to T13.
    If no, or not sure
    Where ownership, operation and management are split between businesses, set out who does what and take it to your adviser before going further. If none of the roles fits, go to T13.
    What a website or app test can evidence
    Nothing.
    What a test cannot show, and who decides
    Which role applies. The entity and its adviser establish it from the Act, the rules and any declaration.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  3. T3. Which parts of the Act apply to the asset?
    What the Act or rules say
    Part 2 (register): section 18A and section 4(1) of the Application Rules. Part 2A (program): section 30AB and section 4(1) of the CIRMP Rules, subject to the exceptions in section 30AB(3) to (6). Part 2B (incident reports): section 30BB and section 5(1) of the Application Rules. Section 12F(3): CISC says it applies to all critical infrastructure assets. Grace periods: section 4(3) of the Application Rules (Part 2), section 4(2) of the CIRMP Rules (Part 2A) and section 5(5) of the Application Rules (Part 2B).
    If yes
    Record each part that applies and from what date, then go to T4.
    If no, or not sure
    Record why a part does not apply (the class is not specified, an exception applies, or a grace period is running) and any date on which that changes. If no part applies, go to T11 and then T13.
    What a website or app test can evidence
    Nothing.
    What a test cannot show, and who decides
    Which parts apply. The entity establishes it with its adviser; a declaration under section 51 can also determine that a part applies.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  4. T4. Website and app dependencies: is a website, portal, API or data store part of the asset?
    What the Act or rules say
    Section 5: asset includes a system, a computer, a computer program and computer data. Section 9(7): a data storage system is taken to be part of a critical infrastructure asset when the responsible entity owns or operates it, it is used or is to be used in connection with the asset, business critical data is stored or processed in or by it, and a hazard with a material risk of an impact on the data storage system also carries a material risk of a relevant impact on the asset. CISC: a single critical infrastructure asset includes multiple parts which function together as a system or network.
    If yes
    List each web-facing system that is part of the asset, with the data it holds and who runs it. For a data storage system under section 9(7), the subsection's note gives as examples that Part 2 obligations take it into account, a Part 2A program covers it, and Part 2B notification takes into account any relevant impact on it. Go to T5.
    If no, or not sure
    List the system as related to the asset rather than part of it, with the reason, and still go to T5: the CIRMP Rules define a cyber and information security hazard to include improper access to, or misuse of, information or computer systems about or related to the CI asset.
    What a website or app test can evidence
    Older API versions that still respond are flagged in a Clever Ops web application and API penetration test and brought into scope once you confirm them in writing, which can reveal a route missing from your list. The written scope of each past test shows which systems it examined.
    What a test cannot show, and who decides
    Whether a system is part of the asset, a data storage system under section 9(7) or a critical system under the CIRMP Rules. The responsible entity decides with its adviser.
    Limits of this row
    Read-only row: the list comes from your own records and contracts, and nothing is sent to any system.
  5. T5. Is business critical data stored or processed in a web-facing system, or by an outside provider?
    What the Act or rules say
    Section 5: business critical data means personal information (within the meaning of the Privacy Act 1988) that relates to at least 20,000 individuals, information relating to any systems needed to operate a critical infrastructure asset, information needed to operate one, or information relating to research and development, or to risk management and business continuity (however described), in relation to one. Section 12F(3): a responsible entity that becomes aware that a data storage or processing service provided by another entity on a commercial basis to it relates to business critical data must take reasonable steps to inform that entity that it has become aware of this, as soon as practicable after becoming so aware. Section 7(1)(f) and Definitions Rules section 17: operational information includes a description of the arrangements for prescribed data another entity maintains, including the name of the cloud service where one is used.
    If yes
    Record the system or provider, the kinds of data, and, for an outside provider, the date and manner in which it was informed under section 12F(3). Go to T6.
    If no, or not sure
    Record the reasons, and the date to look again if the data held changes. Go to T6.
    What a website or app test can evidence
    For the build and test accounts tested, whether one account could read another account's records and what the system returned to a request made while signed out.
    What a test cannot show, and who decides
    How much data a system holds, or whether it is business critical data. Those come from the entity's records, and the entity and its adviser decide whether a provider has to be informed.
    Limits of this row
    Read-only row: data inventories and contracts only. No record holding real personal information is opened, and nothing is sent to any system.
  6. T6. Program evidence: does the program identify and treat cyber and information security hazards for each system in T4 and T5?
    What the Act or rules say
    CIRMP Rules section 8(2): a process or system to, as far as it is reasonably practicable to do so, minimise or eliminate any material risk of a cyber and information security hazard occurring and mitigate its relevant impact on the asset. Section 6: material risk includes impact to the availability, integrity, reliability or confidentiality of the data storage system holding business critical data. Section 7(1): identify the operational context of the asset and its material risks.
    If yes
    Record where the program covers each system, the date of the evidence it relies on, and the owner. Go to T7.
    If no, or not sure
    Record the gap, its owner and a date, and raise it in the program review under section 30AE. Go to T7.
    What a website or app test can evidence
    For the build, accounts and roles tested: findings and negative results on sign-in and sessions, access between accounts and roles, the API called directly and file uploads, each finding carrying its retest status. That is evidence the entity can use when it identifies and treats these hazards for that system.
    What a test cannot show, and who decides
    Whether Part 2A covers your business, which you establish with your own adviser, and whether the program meets section 8 or Part 2A. The responsible entity decides the second, and its governing body, if it has one, approves the annual report under section 30AG.
    Limits of this row
    Read-only row: the program and existing reports only, with nothing sent to any system. A new test of a system in T4 is planned separately, under the responsible entity's written authorisation and rules of engagement it approves.
  7. T7. Which framework does the program follow, and do enhanced requirements apply?
    What the Act or rules say
    CIRMP Rules section 8(4): a process or system to comply with a framework contained in a listed document and meet any listed condition: AS ISO/IEC 27001:2015; the Essential Eight Maturity Model (maturity level one); the NIST Framework for Improving Critical Infrastructure Cybersecurity; the US Department of Energy Cybersecurity Capability Maturity Model (Maturity Indicator Level 1); or the 2020-21 AESCSF Framework Core (Security Profile 1). Section 8(5): or an equivalent framework, including any conditions. For classes in section 4A(1): section 8A(3) lists its own documents and conditions, section 8A(4) allows an equivalent framework to some of them, section 8B covers phishing resistant multi-factor authentication where the framework does not require it, and section 8C asks, among other things, for an inventory of critical systems and how they connect.
    If yes
    Record the framework and its condition, whether the asset is in section 4A(1) and which grace period in section 4A(6) applies, and the evidence held for each web-facing system. Go to T8.
    If no, or not sure
    Take it to the program owner and your adviser; section 8(3) sets the period for complying with section 8(4) or 8(5). Go to T8.
    What a website or app test can evidence
    For sign-in to the tested application: whether the test accounts were asked for a second factor and which kinds the application accepted, on the build tested. The report also states its coverage.
    What a test cannot show, and who decides
    Whether the program follows any framework or meets its condition, whether a factor is phishing resistant under the rules, and the logging and review in section 8B(5)(b). The entity and its adviser settle these.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  8. T8. Section 30BC, the 12-hour path: has the responsible entity become aware that a cyber security incident has occurred or is occurring and has had, or is having, a significant impact (whether direct or indirect) on the availability of an asset Part 2B applies to?
    What the Act or rules say
    Section 30BC(1): report to the relevant Commonwealth body as soon as practicable, and in any event within 12 hours, after the entity becomes so aware. Section 30BEA: a significant impact on availability if, and only if, the asset is used in connection with the provision of essential goods or services and the incident has materially disrupted the availability of those essential goods or services, or circumstances specified in the rules exist. Section 30BC(3): if the report is given orally, the entity must make a written record of it in the approved form and give a copy to the relevant Commonwealth body within 84 hours after the report is given; under section 30BC(5), the head of that body may exempt the entity from this, by written notice, for a report about a specified incident. Section 12M defines a cyber security incident.
    If yes
    Follow the entity's incident process for the 12-hour path, recording when the entity became aware and when and how the report was given. The note to section 18 of the Definitions Rules says the relevant Commonwealth body for the other provisions of Part 2B is ASD. Then go to T9.
    If no, or not sure
    Go to T9.
    What a website or app test can evidence
    Nothing. A test is not a report, and testing during an incident can disturb what responders need to see.
    What a test cannot show, and who decides
    Whether section 30BC covers your business and the asset, whether an event is a cyber security incident with a significant impact, and when the entity became aware. You establish each of these with your own adviser.
    Limits of this row
    Read-only row: the incident record only, with nothing sent to any system. It is a planning row, not an incident response procedure.
  9. T9. Section 30BD, the 72-hour path: has the responsible entity become aware that a cyber security incident has occurred, is occurring or is imminent, and has had, is having, or is likely to have, a relevant impact on an asset Part 2B applies to?
    What the Act or rules say
    Section 30BD(1): report to the relevant Commonwealth body as soon as practicable, and in any event within 72 hours, after the entity becomes so aware. Section 8G(2): the relevant impacts of an incident are its impacts, whether direct or indirect, on the availability, integrity and reliability of the asset and on the confidentiality of information about it, of information stored in it or, if the asset is computer data, of that data. Section 30BD(3): if the report is given orally, the entity must make a written record in the approved form and give a copy to that body within 48 hours after the report is given; section 30BD(5) gives the head of that body the same power to exempt by written notice.
    If yes
    Follow the 72-hour path and record the same times as in T8. Ask your adviser separately whether another regime, such as the Notifiable Data Breaches scheme, reaches the same event. Then go to T10.
    If no, or not sure
    Record that no Part 2B report was made, and why. Go to T10.
    What a website or app test can evidence
    Nothing, for the reasons in T8. Separately, rules of engagement for any test should name who the tester tells, and how fast, if testing turns up signs that someone else has been in the system.
    What a test cannot show, and who decides
    Whether section 30BD covers your business and the asset, and whether a relevant impact has occurred or is likely. You establish both with your own adviser.
    Limits of this row
    Read-only row: as in T8, the incident record only, and nothing is sent to any system. Use it to plan; it does not replace an incident response procedure.
  10. T10. Is the program reviewed, kept up to date and reported on?
    What the Act or rules say
    Section 30AE: review the program on a regular basis. Section 30AF: take all reasonable steps to ensure it is up to date. Section 30AG(2): within 90 days after the end of the financial year, a report in the approved form to the relevant Commonwealth regulator that has functions relating to the security of those assets, if there is one, or otherwise to the Secretary, stating whether the program was up to date (where the entity had it at the end of the year) and covering any hazard that had a significant relevant impact, approved by the board, council or other governing body if the entity has one. Section 30AI: a relevant official may direct a variation for a serious deficiency.
    If yes
    Record the review date, the report date and the approving body. Go to T11.
    If no, or not sure
    Record what is missing and who owns it. Go to T11.
    What a website or app test can evidence
    Dated reports and retest statuses for each web-facing system, which a review can cite as the evidence from the last test of that system.
    What a test cannot show, and who decides
    Whether sections 30AE to 30AG cover your business, which you establish with your own adviser, and whether the program is up to date or the report is accurate, which the entity and its governing body decide.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  11. T11. Has the Minister declared the asset a system of national significance?
    What the Act or rules say
    Section 52B(1): the Minister may declare a critical infrastructure asset to be a system of national significance if satisfied that it is of national significance, having regard to the matters in section 52B(2), and section 52B(3) says the Minister must notify the responsible entity, among others, in writing within 30 days. The note to section 52A says it is an offence to disclose that an asset has been declared one (see section 45). CISC: ECSOs can only be applied to SoNS, not critical infrastructure more broadly.
    If yes
    Keep the declaration in a restricted file, and go to T12.
    If no, or not sure
    Record that no declaration has been notified. Go to T13 if your business also supplies other entities; otherwise the tree ends here.
    What a website or app test can evidence
    Nothing.
    What a test cannot show, and who decides
    Whether an asset is of national significance. The Minister decides.
    Limits of this row
    Read-only row: the declaration, if there is one, and nothing is sent to any system. Check section 45 and Division 3 of Part 4, on the use and disclosure of protected information, with your adviser before telling anyone about a declaration.
  12. T12. Has the Secretary given a written notice requiring a vulnerability assessment?
    What the Act or rules say
    Section 30CU: the Secretary may, by written notice to the responsible entity for a system of national significance, require it to undertake, or cause to be undertaken, a vulnerability assessment of the system for all types of cyber security incidents or specified types, within the period the notice specifies, after having regard to the matters in section 30CU(3), such as costs, reasonableness and proportionality, and consulting the entity and any relevant Commonwealth regulator with functions relating to the security of the system. Section 30CV: the entity must comply. Section 30CY: the assessment's purpose is to test the vulnerability of the system to those types of cyber security incidents, and it complies with requirements (if any) in the rules. Section 30CZ: the entity must prepare, or cause to be prepared, a vulnerability assessment report and give a copy to the Secretary within 30 days after the completion of the assessment, or a longer period if the Secretary allows one. Section 30CW: in the cases it sets out, a designated officer may undertake the assessment.
    If yes
    Read the notice for the system, the incident types and the period. Decide who undertakes the assessment against the notice, the Act and any rules, with your adviser and, where useful, CISC. Diary the report date, 30 days after completion unless the Secretary allows longer. Then go to T13 if your business also supplies other entities; otherwise the tree ends here.
    If no, or not sure
    No assessment under section 30CU has been required. Separately, section 30CB lets the Secretary, by written notice to the responsible entity for a system of national significance, determine that the statutory incident response planning obligations apply to it. Go to T13 if your business also supplies other entities; otherwise the tree ends here.
    What a website or app test can evidence
    A web application test commissioned for another purpose is not an assessment under section 30CU. Its report can be background the entity shares with whoever undertakes the assessment, if the notice and the entity allow.
    What a test cannot show, and who decides
    Whether an assessment meets the notice, the Act and the rules. The entity is responsible for complying, and the Secretary receives the report.
    Limits of this row
    Read-only row: the notice only, and nothing is sent to any system. A vulnerability assessment under section 30CU is for the responsible entity to arrange, with a provider suited to that work and to what the notice, the Act and any rules require.
  13. T13. Supplier: do you supply a responsible entity, or has a customer informed you under section 12F(3)?
    What the Act or rules say
    Section 12F(3): a responsible entity must take reasonable steps to inform a provider of a data storage or processing service provided to it on a commercial basis that relates to business critical data, as set out in T5. CISC says this ensures that companies that handle sensitive data are aware that they may also have obligations under the SOCI Act. Section 12F(1) and (2) define a critical data storage or processing asset, and section 12L(4) makes the provider that owns or operates it the responsible entity, unless the rules prescribe another entity.
    If yes
    If a customer has informed you under section 12F(3), take what it told you, with a description of the services and customers concerned, to your adviser and ask whether section 12F(1) or (2) makes any of your assets a critical data storage or processing asset; if it does, start again at T2 for that asset. Then go to T14.
    If no, or not sure
    Go to T14 if a customer has raised the Act in a contract or a questionnaire. Otherwise the tree ends here.
    What a website or app test can evidence
    Nothing for this row.
    What a test cannot show, and who decides
    Whether you hold a role under the Act. You decide with your adviser.
    Limits of this row
    Read-only row: you work from the Act, the rules and your own records here, and nothing is sent to any system.
  14. T14. What has the customer asked of you about its program, your testing or your access?
    What the Act or rules say
    CIRMP Rules section 10(1): the responsible entity must establish and maintain in its program a process or system to minimise or eliminate, as far as it is reasonably practicable to do so, supply chain material risks including misuse of privileged access to the asset by any provider in the supply chain and risks arising from major suppliers. Section 10A, for classes with enhanced requirements: a system or process to map the supply chain for major suppliers and critical components, and one to assess the risks of each existing or proposed major supplier, identifying among other things the access, influence and control it has over the asset in connection with the product or service it provides.
    If yes
    List each request in the customer's exact words, the contract clause behind it, the evidence you hold and the date you answered. Go to T15.
    If no, or not sure
    Keep this row ready for the next contract renewal or questionnaire, then go to T15.
    What a website or app test can evidence
    Your own dated test reports and retest statuses for the product or service you provide, shared on the terms your contract allows, answer questions about your testing. For wording the answers themselves, see the security questionnaires guide.
    What a test cannot show, and who decides
    Whether the customer's program can rely on your evidence is the customer's judgement. What your agreement obliges you to do is something to ask your own adviser.
    Limits of this row
    Read-only row: the customer's requests, your contracts and your own reports, with nothing sent to any system.
  15. T15. What have you agreed to tell the customer about an incident, and how fast?
    What the Act or rules say
    The reporting duties in sections 30BC and 30BD fall on the responsible entity, with limits counted from when it becomes aware. Section 30BE(4): a contracted service provider responsible under a contract for providing services to an entity subject to section 30BC or 30BD, and that provider's officers, employees and agents, are not liable to an action or other proceeding for damages for or in relation to an act done or omitted in good faith for the purposes of ensuring or facilitating compliance with the requirement.
    If yes
    Put the agreement's notification terms, contact names and channels into your own incident plan, and check that the contacts are current. The tree ends here.
    If no, or not sure
    Ask the customer what it needs from you and how fast, and record the answer in writing. Have your own adviser explain what your agreement obliges you to do. The tree ends here.
    What a website or app test can evidence
    Nothing about notification.
    What a test cannot show, and who decides
    What the agreement obliges you to do. Ask your own adviser.
    Limits of this row
    Read-only row: your agreement and your incident plan, with nothing sent to any system.

The SOCI Act at a glance: the Act, its compilation and its rules

The Security of Critical Infrastructure Act 2018 is Act No. 29 of 2018, and the Cyber and Infrastructure Security Centre (CISC) calls it the SOCI Act.

The Federal Register of Legislation lists its status as in force, with the Department of Home Affairs shown as administering it. This guide reads Compilation No. 9, which has a compilation date of 4 June 2026, was registered on 5 June 2026 and includes amendments made by Act No. 75 of 2025.

Section numbers on this page refer to that compilation. Check the Register for a later one before you rely on a section.

Section 3 sets out the object: to provide a framework for managing risks relating to critical infrastructure, including by (a) improving the transparency of the ownership and operational control of critical infrastructure in Australia in order to better understand those risks; (b) facilitating cooperation and collaboration between all levels of government, and regulators, owners and operators of critical infrastructure, in order to identify and manage those risks; (c) requiring responsible entities for critical infrastructure assets to identify and manage risks relating to those assets; (d) imposing enhanced cyber security obligations on relevant entities for systems of national significance in order to improve their preparedness for, and ability to respond to, cyber security incidents; (da) imposing enhanced security obligations on responsible entities for critical telecommunications assets; and (e) providing a regime for the Commonwealth to respond to serious incidents relating to critical infrastructure assets.

Much of the detail sits in rules, which section 5 defines as the rules made by the Minister under section 61. Each set is its own legislative instrument, and the Register lists them, with their status, on the Act's Authorises tab. This guide relies on three, each read in the compilation named here: the Security of Critical Infrastructure (Critical infrastructure risk management program) Rules (LIN 23/006) 2023, Compilation No. 2 of 10 June 2026, called the CIRMP Rules below; the Security of Critical Infrastructure (Application) Rules (LIN 22/026) 2022, Compilation No. 1 of 4 April 2025, called the Application Rules; and the Security of Critical Infrastructure (Definitions) Rules (LIN 21/039) 2021, Compilation No. 2 of 4 January 2023, called the Definitions Rules.

The rules listed there for the Australian National University, a naval shipbuilding precinct and telecommunications security and risk management programs are outside this page.

This guide is written for whoever runs, or looks after the technology of, a business that may hold a role under the Act for an asset, and for a business that supplies such an entity, such as a software, hosting or managed service provider that has met the Act in a contract clause, a due diligence questionnaire or a request about incident reporting.

None of it is legal advice, and none of it audits anyone's position.

The page reports what the Act and its rules say, conditions included, and leaves every decision about whether and how they apply to the entity, its adviser and the officials the Act names.

Who the Security of Critical Infrastructure Act covers: assets first, then roles

The Act's definitions begin with assets.

Section 9(1) lists the classes of critical infrastructure asset, running from a critical telecommunications asset to a critical defence industry asset and including a critical data storage or processing asset and a critical hospital, and adds an asset declared under section 51 and an asset prescribed by the rules.

Each class has its own definition, and some definitions carry thresholds set in the Act or the rules. Section 10(1)(a), for one, counts as a critical electricity asset a network, system, or interconnector, for the transmission or distribution of electricity to ultimately service at least 100,000 customers or any other number of customers prescribed by the rules.

Section 8D lists the critical infrastructure sectors of the Australian economy, and section 8E says which sector each class is taken to relate to. The sectors in section 8D are communications; data storage or processing; financial services and markets; water and sewerage; energy; health care and medical; higher education and research; food and grocery; transport; space technology; and defence industry.

Section 9 also takes assets out. Under section 9(2), the rules may prescribe that a specified asset of a listed class is not a critical infrastructure asset. Section 9(2A) says an asset owned by the Commonwealth, or by a body corporate established by a law of the Commonwealth, is not one unless it is declared under section 51 or prescribed by the rules for the purposes of paragraph 9(1)(f); the subsection carves a defined class of body out of that second group, using a term that section 5 gives the meaning it has in the Public Governance, Performance and Accountability Act 2013.

And section 9(2B) says that, subject to subsections (2C) and (2D), an asset is not a critical infrastructure asset if, or to the extent to which, it is located outside Australia.

Duties then attach to roles. Section 12L names the responsible entity for each class listed in section 9(1), each in a subsection of its own that also allows for another entity prescribed by the rules; for an asset declared under section 51, it is the entity the declaration specifies.

Under section 8(1), an entity is a direct interest holder if, together with any associates, it holds an interest of at least 10% in the asset, or holds an interest that puts it in a position to directly or indirectly influence or control the asset, with exemptions in subsections 8(2), 8(4) and 8(5) for some moneylending, custodial or depository, and specified service arrangements, on the conditions those subsections set.

Section 5 defines a relevant entity as the responsible entity, a direct interest holder, an operator of the asset or a managed service provider for it, and a managed service provider as an entity that manages the asset or a part of it, manages an aspect of the asset or a part of it, or manages an aspect of the operation of the asset or a part of it.

CISC's regulatory obligations page puts it in plain terms: the type of obligations that apply depends on the role held in relation to the critical infrastructure asset and the type of asset, and the responsible entity for each asset class will vary. For readers who are not sure whether the obligations apply to their asset, it points to its Critical Infrastructure Asset Class Definition Guidance.

This page cannot settle any of that. Whether an asset you own, operate, manage or hold an interest in falls within a class, whether an exclusion applies and which role your business holds are questions to work through with your own adviser, from the definitions in the Act and the rules and, where it helps, CISC's guidance. The page makes no finding about any business, of any size or in any sector.

Which parts of the Act apply to an asset

Parts 2, 2A and 2B each have a section that says which assets the Part applies to, so for each asset the question is which of them reach it.

Part 2C and section 12F(3) work differently, as the last two items say. For every item below, establish with your own adviser whether it covers an asset your business is responsible for, operates, manages or holds an interest in.

  • Part 2, the Register of Critical Infrastructure Assets. Section 18A applies the Part to an asset specified in the rules, an asset declared under section 51 with a determination that the Part applies, or an asset that was a critical infrastructure asset (within the meaning of the Act as then in force) immediately before section 18A commenced, and section 4(1) of the Application Rules specifies the classes, with the exceptions it lists. Section 18, the outline of the Part, says among other things that the responsible entity must give the Secretary operational information about the asset, a direct interest holder must give interest and control information, the Register must not be made public, and the rules may provide for exemptions from these requirements.
  • Part 2A, the critical infrastructure risk management program. Section 30AB applies the Part to an asset specified in the rules or declared with a determination that the Part applies, and section 4(1) of the CIRMP Rules specifies the classes. Subsections 30AB(3) to (6) set exceptions, among them one where the responsible entity holds a certificate of hosting certification (strategic level) under the Commonwealth scheme known as the hosting certification framework and the asset, or part of it, is used in connection with providing the certified services.
  • Part 2B, notification of cyber security incidents. Section 30BB applies the Part to an asset specified in the rules or declared with a determination that the Part applies, and section 5(1) of the Application Rules specifies the classes, with the exceptions it lists. Its list includes classes that section 4(1) of the CIRMP Rules does not, such as a critical banking asset, a critical superannuation asset, a critical insurance asset, a critical education asset and a critical port.
  • Part 2C, enhanced cyber security obligations. These relate to systems of national significance, which the Minister may declare under section 52B, and CISC says ECSOs can only be applied to SoNS, not critical infrastructure more broadly.
  • Section 12F(3), the duty to take reasonable steps to inform an outside data storage or processing provider. CISC's overview says this obligation applies to all critical infrastructure assets.

Grace periods and dates

The rules also set periods after an asset becomes a critical infrastructure asset during which a part does not apply to it: section 4(3) of the Application Rules for Part 2, section 4(2) of the CIRMP Rules for Part 2A, and section 5(5) of the Application Rules for Part 2B, each with its own start and end points.

Assets of a class listed in section 4A(1) of the CIRMP Rules have further grace periods for the enhanced requirements in section 4A(6). Read the section itself for the date that applies to an asset, rather than a summary of it.

Where a website, portal or app can fall inside a critical infrastructure asset

Websites and web applications are not one of the classes in section 9(1).

On this guide's reading, though, the Act's definitions reach the parts they are built from. Section 5 says asset includes a system, a network, a facility, a computer, a computer device, a computer program, computer data, premises and any other thing, and CISC's overview says a single critical infrastructure asset includes multiple parts which function together as a system or network, including premises, computers and data.

Section 9(7) speaks to data directly. If an asset is a critical infrastructure asset, a data storage system is taken to be part of it when all of the subsection's requirements are satisfied: the responsible entity for the asset owns or operates the data storage system; the system is used, or is to be used, in connection with the asset; business critical data is stored, or is processed in or by, the system (whether or not other information is also stored or processed there); and, for a hazard where there is a material risk that the occurrence of the hazard could have an impact on the data storage system, there is also a material risk that the occurrence of the hazard could have a relevant impact on the critical infrastructure asset.

The note to the subsection gives examples of its effect: obligations under Part 2 will also need to take the data storage system into account, a program under Part 2A will also need to cover it, and notification obligations under Part 2B will also need to take into account any relevant impact on it.

Section 5 defines business critical data as personal information (within the meaning of the Privacy Act 1988) that relates to at least 20,000 individuals; information relating to any research and development in relation to a critical infrastructure asset; information relating to any systems needed to operate one; information needed to operate one; or information relating to risk management and business continuity (however described) in relation to one.

The CIRMP Rules define further terms, and on this guide's reading some of them bear on web-facing systems. A cyber and information security hazard includes where a person, whether authorised or not, improperly accesses or misuses information or computer systems about or related to the CI asset, or uses a computer system to obtain unauthorised control of, or access to the CI asset that might impair its proper functioning.

A credential compromise hazard is one where credentials associated with internet-connected computers or critical components, or with remote access to them, are used to introduce vulnerabilities that could compromise the availability, integrity, reliability or confidentiality of the CI asset.

A critical system is any systems including operational technology or enabling systems that form critical components which are vital to the delivery of a CI asset's function, or the compromise or degradation of which could have a relevant impact on the asset.

Read together, those words can take in, depending on the facts, a customer portal that holds business critical data for the asset, a web console staff use to run an operational system, an API other systems use to send instructions, and the sign-in service behind remote access. That list is this guide's illustration, not a statement of the law.

Whether a particular site, portal or API is part of an asset, a data storage system under section 9(7), a critical system, or a system related to the asset is the responsible entity's assessment with its advisers.

Hosting arrangements in the register

Where Part 2 applies, the information given for the register can also cover where data is held. Section 7(1)(f) includes in operational information a description of the arrangements under which data prescribed by the rules relating to the asset is maintained.

Section 17 of the Definitions Rules prescribes data that relates to the asset and is maintained by an entity that is not the responsible entity, of listed kinds that include personal information, within the meaning of the Privacy Act 1988, of at least 20,000 persons and information about any systems needed to operate the asset.

The description must include, among other things, the name of the entity that maintains the data, the address where the data is held (including, to the extent practicable, where the computers or servers holding it are located, whether or not they are part of a cloud service) and, for data held using a cloud service, the name of the cloud service.

The SOCI risk management program: what Part 2A and the CIRMP Rules ask

Section 30AC says that if an entity is the responsible entity for one or more critical infrastructure assets, it must adopt and maintain a critical infrastructure risk management program that applies to the entity.

The section sits in Part 2A, which section 30AB applies to the assets it names. Sections 30AD to 30AF add that the entity must comply with the program, review it on a regular basis, and take all reasonable steps to ensure that it is up to date. Whether these duties cover your business is a question to establish with your own adviser.

Section 30AH(1) defines the program as a written program that applies to a particular responsible entity and whose purpose is, for each of its assets, to identify each hazard where there is a material risk that the occurrence of the hazard could have a relevant impact on the asset, and, so far as it is reasonably practicable to do so, to minimise or eliminate any material risk of such a hazard occurring and to mitigate the relevant impact of such a hazard on the asset; and that complies with such requirements (if any) as are specified in the rules.

Section 30AH(7) says that in deciding whether a risk is material, regard must be had to the likelihood of the hazard occurring and its relevant impact on the asset if it were to occur.

Section 8G lists the relevant impacts of a hazard (subsection (1)) and of an incident (subsection (2)) on a critical infrastructure asset: the impact, whether direct or indirect, on the availability, the integrity or the reliability of the asset, and on the confidentiality of information about it, of information stored in it or, if the asset is computer data, of that data.

Section 30AG adds an annual report for an entity that was a responsible entity with a program during the whole or part of a financial year. Within 90 days after the end of the financial year, it must give a report in the approved form to the relevant Commonwealth regulator that has functions relating to the security of those assets, if there is one, or in any other case to the Secretary.

Among other contents, the report states, if the entity had the program at the end of the financial year, whether the program was up to date at that time, and, if a hazard had a significant relevant impact on one or more of the assets during the period, identifies the hazard, evaluates the effectiveness of the program in mitigating that impact and outlines any variation made to the program as a result of the hazard.

If the entity has a board, council or other governing body, that body approves the report.

Under section 30AI, a relevant official may direct an entity to vary its program if satisfied there are serious deficiencies, meaning deficiencies that pose a material risk to national security, the defence of Australia, or the social or economic stability of Australia or its people.

What the CIRMP Rules ask for cyber and information security hazards

The CIRMP Rules specify requirements for the program under section 30AH(1)(c). 2 min read

Enhanced requirements for some asset classes

Section 4A(1) of the CIRMP Rules lists the classes subject to enhanced requirements, among them a critical electricity asset, a critical water asset, a critical domain name system and a critical broadcasting asset, and section 4A(3) says a program for one of them must comply with both the enhanced and the baseline requirements. 2 min read

Hazards a web test does not reach

Section 9 deals with personnel hazards, including identifying critical workers and permitting a critical worker access to critical components of the asset only where the worker has been assessed to be suitable to have such access. 1 min read

SOCI Act cyber incident reporting: sections 30BC and 30BD

Part 2B sets its reporting duties in sections 30BC and 30BD, for the responsible entity of an asset the Part applies to.

Each section has its own trigger, and each time limit is counted from when the entity becomes aware of the facts its section names. Take the question of whether either section reaches your business, and an asset it is responsible for, to your own adviser.

Section 30BC: an incident with a significant impact on availability, within 12 hours

Section 30BC(1) applies when the entity becomes aware that a cyber security incident has occurred or is occurring, and that the incident has had, or is having, a significant impact (whether direct or indirect) on the availability of the asset. 1 min read

Section 30BD: an incident with a relevant impact, within 72 hours

Section 30BD(1) applies when the entity becomes aware that a cyber security incident has occurred, is occurring or is imminent, and that the incident has had, is having, or is likely to have, a relevant impact on the asset. 1 min read

What counts as a cyber security incident, and who receives the report

Sections 30BC and 30BD turn on section 12M. 1 min read

Other reporting regimes after the same event

Part 2B is not the only regime a business can meet after one event. 1 min read

Systems of National Significance and the vulnerability assessment regime

Section 52B(1) says the Minister may, in writing, declare a particular asset to be a system of national significance if it is a critical infrastructure asset and the Minister is satisfied that it is of national significance.

Under section 52B(2) the Minister must have regard to the consequences for the social or economic stability of Australia or its people, the defence of Australia, or national security if a hazard were to occur that had a significant relevant impact on the asset; if the Minister is aware of one or more interdependencies between the asset and other critical infrastructure assets, to the nature and extent of those interdependencies; and to any other matters the Minister considers relevant.

Section 52B(3) says the Minister must notify the responsible entity, among others, in writing within 30 days after making the declaration, and the note to section 52A says it is an offence to disclose that an asset has been declared a system of national significance (see section 45).

CISC says the Minister for Home Affairs has declared some critical infrastructure assets a System of National Significance (SoNS), and that ECSOs can only be applied to SoNS, not critical infrastructure more broadly. The outline in section 30CA says the responsible entity for a system of national significance may be subject to statutory incident response planning obligations, may be required to undertake a cyber security exercise and may be required to undertake a vulnerability assessment, and that if a computer is a system of national significance, or is needed to operate one, a relevant entity for the system may be required to give ASD periodic or event-based reports of system information, or to install software that transmits system information to ASD. Your own adviser is the one to confirm whether any of these obligations covers your business.

How a vulnerability assessment notice works

Section 30CU lets the Secretary, by written notice given to the responsible entity for a system of national significance, require it to undertake, or cause to be undertaken, a vulnerability assessment in relation to the system and either all types of cyber security incidents or one or more specified types, within the period specified in the notice.

In deciding whether to give one, the Secretary must have regard to the costs the entity is likely to incur in complying, the reasonableness and proportionality of the requirement and any other matters the Secretary considers relevant, and before giving one must consult the entity and any relevant Commonwealth regulator that has functions relating to the security of that system. Section 30CV says the entity must comply with the notice.

Section 30CY(1) defines the assessment as one that relates to a system of national significance, relates to all types of cyber security incidents or to specified types, has the purpose of testing the vulnerability of the system to those types of cyber security incidents, and complies with such requirements (if any) as are specified in the rules.

Under section 30CZ(1), an entity that undertakes, or causes to be undertaken, an assessment under section 30CU must prepare, or cause to be prepared, a vulnerability assessment report and give a copy to the Secretary within 30 days after the completion of the assessment, or within a longer period if the Secretary allows one.

Where the Secretary has reasonable grounds to believe the entity would not be capable of complying with a notice, or the entity has not complied with one, section 30CW lets the Secretary ask a designated officer to undertake the assessment and, by written notice, require the entity to do any or all of these: provide the officer with access to premises, provide access to computers, and provide reasonable assistance and facilities that are reasonably necessary to allow the officer to undertake it.

This guide draws three points from those sections, as its own reading. An assessment under section 30CU follows from a notice, and the notice, the Act and any rules decide what it covers. The notice regime sits apart from the program duties in Part 2A. And a web application test commissioned for another purpose is not, on that account, a vulnerability assessment under the Act.

If you supply a responsible entity: data, supply chain and contracts

A supplier can hold a role itself.

Under section 12F(1) and (2), an asset owned or operated by a data storage or processing provider is a critical data storage or processing asset where it is used wholly or primarily to provide a data storage or processing service that relates to business critical data, to an end-user that is the Commonwealth, a State, a Territory or a body corporate established by a law of one of them, or to an end-user that is the responsible entity for a critical infrastructure asset; the provider knows the asset is used that way; and the asset is not covered by another paragraph of section 9(1).

Section 12L(4) makes that provider its responsible entity, unless the rules prescribe another entity.

Section 5 counts a managed service provider for an asset among its relevant entities.

Confirm with your own adviser whether either applies to your business. A supplier that holds none of the Act's roles can still meet it through a customer, in these ways.

  • Being informed under section 12F(3). If a responsible entity becomes aware that a data storage or processing service is provided by another entity on a commercial basis to it and relates to business critical data, section 12F(3) says it must take reasonable steps to inform that other entity that it has become aware of this, as soon as practicable after becoming so aware. CISC says this obligation ensures that companies that handle sensitive data are aware that they may also have obligations under the SOCI Act.
  • Supply chain hazards in the customer's program. Section 10 of the CIRMP Rules asks for a process or system in the program to minimise or eliminate, as far as it is reasonably practicable to do so, material risks including unauthorised access, interference or exploitation of the asset's supply chain, misuse of privileged access to the asset by any provider in the supply chain, and risks arising from major suppliers, which section 3 defines as any vendor that by nature of the product or service they offer, has a significant influence over the security of a responsible entity's CI asset. For assets with enhanced requirements, section 10A adds a system or process to map the supply chain for major suppliers and critical components, and one to assess the risks associated with an existing or proposed major supplier, identifying for each, among other things, the access, influence and control the supplier has over the asset in connection with the product or service it provides. On this guide's reading, questions to a supplier about its access, testing and incident handling can come from that work.
  • Incident reporting support. Section 30BE(4) says that where an entity is or was subject to a requirement under section 30BC or 30BD, a contracted service provider that is or was a party to a contract with it and responsible under the contract for providing services to it, and that provider's officers, employees and agents, are not liable to an action or other proceeding for damages for or in relation to an act done or omitted in good faith for the purposes of ensuring or facilitating compliance with the requirement.

Your agreement with the customer

Section 12F(3) of the Act and section 10 of the CIRMP Rules are addressed to the responsible entity, and section 30BE(4) deals with a contracted service provider's liability. This page does not say what a supplier owes its customer. Look at what your agreement with the customer says about incident notice and its timing, the testing you do and share, and the access you hold, and have your own adviser explain what that agreement obliges your business to do.

CISC says the SOCI Act protects information about critical infrastructure assets, so that it is an offence to disclose information about these assets, even if you are a responsible entity, unless your disclosure complies with the SOCI Act.

On this guide's reading, that can limit what a customer tells its suppliers. Take any question about whether the Act reaches your own assets to your own adviser as well.

Evidence a website or application test can give towards SOCI obligations

A test of a website, portal or API produces evidence about one system: the build tested, during the window it ran, with the test accounts and roles agreed for it, inside a written scope.

For a system that sits inside or beside a critical infrastructure asset, that evidence can feed a few specific places in the Act and the rules, and no more.

  • Cyber and information security hazards (CIRMP Rules section 8(2)): findings and negative results showing whether test accounts could reach records or functions they should not, whether sessions ended when they should, and whether the API enforced the same rules when called without the screens, on the build tested. That is input for identifying and treating hazards for that one system. It is not the process or system the rules ask the program to contain.
  • The framework in section 8(4) or 8A(3): a report records what was tested and states its coverage. Whether a program follows any document those tables list, or an equivalent framework under section 8(5) or 8A(4), is outside what a report can show.
  • Credential compromise hazards (section 8B, which applies to an asset in section 4A(1) whose framework does not require phishing resistant multi-factor authentication controls): what the tested application's sign-in asked of the test accounts, such as whether it required a second factor and which kinds it accepted. Whether that is phishing resistant multi-factor authentication, which systems and networks the program must outline under section 8B(3)(a), and the central logging and review in section 8B(5)(b) are outside the test.
  • Supply chain (section 10): a supplier's own report about the product or service it provides, shared on the terms its contract allows, is material the responsible entity can weigh. Whether the supplier's risk is acceptable is the entity's judgement.
  • Incident reporting (sections 30BC and 30BD): nothing. A test is not a report, and whether anything a test turns up is a cyber security incident under section 12M is the entity's question, with its adviser.
  • Vulnerability assessment (section 30CU): a test run for another reason is not an assessment under the Act. Where a notice is given, the notice, the Act and any rules decide what the assessment covers.

What a web test cannot speak for

Nothing in a web application test speaks to whether an asset is a critical infrastructure asset or who its responsible entity is. Nor does it speak to register information under Part 2, to critical workers and the personnel rules in section 9, to physical security and natural hazards under section 11, to operational technology, internal networks and the lateral movement rules in section 8C, or to the annual report and its approval under section 30AG.

A test does not decide whether a program meets Part 2A or whether an incident has to be reported, and it makes no finding that any entity or supplier meets the Act.

How to use the responsible-entity decision tree

The decision tree on this page runs: asset scope, then websites and apps, then the program (T6 and T7), the reporting duties in sections 30BC and 30BD (T8 and T9) and the program's review and annual report (T10), then systems of national significance, then the supplier's position.

Each row asks one question, gives the provision it comes from in its own words or a faithful short form, and says where to go next on each answer.

  • Start at row T1. A row further down matters only when an earlier row sends you to it.
  • Write each answer in a dated note, with the document it came from (a declaration, a notice, a contract, your own records or your adviser's reply) and who gave it.
  • Where a row says to establish something with your adviser, it gives you a question to take to them, not an answer.
  • Every row works from documents: the Act, the rules, notices, contracts and your own records. No row sends anything to any system. This page does not ask you to test a critical infrastructure asset, and any test of a system connected to one belongs under the responsible entity's written authorisation and rules of engagement it has approved.
  • Rows T13 to T15 are for a business that supplies a responsible entity. A business can need rows from both groups.
  • Keep the completed tree with the declarations, notices and contracts it relied on, and work through the affected rows again when one of them changes or a new compilation of the Act or the rules is registered.

Who decides under the SOCI Act

The Act names its decision-makers, and none of them is a tester.

The Minister makes the rules under section 61, may declare an asset to be a critical infrastructure asset under section 51 and may declare a system of national significance under section 52B. The responsible entity adopts, maintains, complies with, reviews and updates its program, and its board, council or other governing body, if it has one, approves the annual report under section 30AG.

A relevant official may direct an entity to vary its program for a serious deficiency under section 30AI.

The Secretary may give notices for enhanced cyber security obligations, including a vulnerability assessment notice under section 30CU. Whether an incident meets section 30BC or 30BD is the entity's call, made with its adviser.

For a supplier, it is the customer that chooses what evidence to ask for. Put to your own adviser what the agreement you have with that customer obliges you to do, and whether any duty in the Act falls on your business. A report gives your answers a dated, factual basis; the customer still makes its own judgement about them.

Where a Clever Ops test fits, and where it stops

This page is awareness and referral material.

A vulnerability assessment under section 30CU, and any test of a critical infrastructure asset or of operational technology, are for the responsible entity to arrange with a provider suited to that work and to what its regulator requires. What Clever Ops tests is what a browser or an API exposes to customers and staff, through the services its web security hub describes: a website security check that examines a public site from outside without signing in, a WordPress security audit, a web application and API penetration test of a custom application its customers or staff sign in to, a vibe-coded app security check for an app built with an AI builder, and an AI chatbot and agent security test.

A supplier to a responsible entity can commission one of those tests on its own website or application. Whether that system is itself a critical infrastructure asset, or part of one, is a point for the supplier to settle with its adviser before scoping.

The resulting report gives the scope as tested; for every finding, redacted evidence, with a business-risk rating alongside a CVSS v3.1 score when the finding is rated; negative results, where checks found nothing, tied to the build and accounts covered; and a remediation plan.

After that, a single consolidated retest gives each finding a status of not retested, still reproducible, partially fixed or fixed.

Clever Ops holds no certification or accreditation in security. A report from it is evidence that the entity, its adviser or its customer can weigh. It does not certify anything, and it does not say whether anyone complies with the Act. Because Clever Ops is not CREST accredited, a responsible entity, contract or tender that requires CREST accreditation is referred to an accredited provider.

If Clever Ops built the application or hosts it, the work is described as a security review, and the report identifies who built and who hosts it; it is not offered as an independent test.

Services run by other businesses, such as the hosting provider's platform beneath an application, stay out of a Clever Ops scope unless their owner agrees.

Red teaming, phishing, physical testing, and work on staff devices, servers, Active Directory or internal networks are referred to a network or red team specialist. Clever Ops services leave out denial-of-service, load and volumetric testing altogether; a load-testing specialist does that work, once the host has approved it in writing.

In an incident, Clever Ops is not the responder: it offers no incident response, so the entity's own incident process, its adviser and an incident response specialist take priority. Whether the Act applies, which role a business holds and what a notice requires are for the entity's adviser and CISC.

Frequently asked questions

It is the Security of Critical Infrastructure Act 2018, which CISC calls the SOCI Act. Section 3 says its object is to provide a framework for managing risks relating to critical infrastructure, including by requiring responsible entities for critical infrastructure assets to identify and manage risks relating to those assets, and by imposing enhanced cyber security obligations on relevant entities for systems of national significance in order to improve their preparedness for, and ability to respond to, cyber security incidents. This guide reads Compilation No. 9, with a compilation date of 4 June 2026. The Register shows the Act as in force, with the Department of Home Affairs as its administering department. Much of its detail sits in rules made under section 61, among them the CIRMP Rules and the Application Rules.

Not from this page, which assumes no answer for any size or kind of business. The Act's definitions begin with assets: section 9(1) lists the classes of critical infrastructure asset, with definitions and thresholds in the Act and the rules, and section 12L names the responsible entity for each class. Part 2 also gives register duties to direct interest holders, defined in section 8, and section 5 defines a relevant entity to include an operator of the asset and a managed service provider for it. CISC says the obligations that apply depend on the role held and the type of asset, and points readers who are unsure to its Critical Infrastructure Asset Class Definition Guidance. Work through rows T1 to T3 of the decision tree, then take your note to your adviser.

Sections 30BC and 30BD each set one, counted from when the responsible entity becomes aware of what the section names, and each only for an asset Part 2B applies to. Your own adviser can tell you whether either applies to your business. Under section 30BC, once the entity becomes aware that a cyber security incident has occurred or is occurring and has had, or is having, a significant impact (whether direct or indirect) on the availability of the asset, it must report to the relevant Commonwealth body as soon as practicable, and in any event within 12 hours. Under section 30BD, once it becomes aware that a cyber security incident has occurred, is occurring or is imminent and has had, is having, or is likely to have, a relevant impact on the asset, it must report to that body as soon as practicable, and in any event within 72 hours. Where a report is given orally, the entity must make a written record in the approved form and give a copy to that body within 84 hours under section 30BC, or 48 hours under section 30BD, after the report is given, unless the head of that body has exempted it by written notice. Section 30BEA defines significant impact, and the note to section 18 of the Definitions Rules says that, apart from the written-record exemptions, the relevant Commonwealth body for Part 2B is ASD.

Section 30AH defines it as a written program that applies to a responsible entity and whose purpose is, for each of its critical infrastructure assets, to identify each hazard where there is a material risk that the occurrence of the hazard could have a relevant impact on the asset and, so far as it is reasonably practicable to do so, to minimise or eliminate any material risk of such a hazard occurring and to mitigate its relevant impact. Section 30AC says that if an entity is the responsible entity for one or more critical infrastructure assets it must adopt and maintain one, and section 30AB sets which assets Part 2A applies to. Section 30AG asks an entity that was a responsible entity with a program during the whole or part of a financial year for an annual report within 90 days after the end of that year. The CIRMP Rules specify requirements for the program, including processes for cyber and information security, personnel, supply chain, and physical security and natural hazards, and, within the period section 8(3) sets, a cyber framework from the table in their section 8(4) or an equivalent one. Ask your own adviser whether Part 2A covers your business.

Not by being called one. Under section 30CU, the Secretary may, by written notice, require the responsible entity for a system of national significance to undertake, or cause to be undertaken, a vulnerability assessment of the system within the period the notice specifies. Section 30CY defines that assessment as one whose purpose is to test the vulnerability of the system to the types of cyber security incidents it relates to, and that complies with such requirements (if any) as are specified in the rules, and section 30CZ says the entity must prepare, or cause to be prepared, a report and give a copy to the Secretary within 30 days after the completion of the assessment, or within a longer period if the Secretary allows one. A test commissioned for another purpose is not, on that account, such an assessment. Any notice your business receives is one to take to your own adviser. A vulnerability assessment under section 30CU is for the responsible entity to arrange, with a provider suited to that work and to what the notice, the Act and any rules require.

What you have agreed to do for the customer sits in your agreement with it, and your own adviser can tell you what that agreement obliges you to do; this page does not. The program duties fall on the responsible entity, and section 10 of the CIRMP Rules asks for a process or system in its program to deal with supply chain risks, including risks arising from major suppliers, so you may be asked about your access, testing and incident handling. If the customer is the responsible entity for a critical infrastructure asset and becomes aware that you provide it a data storage or processing service on a commercial basis that relates to business critical data, section 12F(3) says it must take reasonable steps to inform you that it has become aware of this, as soon as practicable after becoming so aware. A provider that has been informed in that way has reason to ask its adviser whether section 12F makes any of its own assets a critical data storage or processing asset. Rows T13 to T15 of the decision tree set out the steps.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.