Checklist · Technology, Media & Telecommunications / IT Contracts
Register of Critical Infrastructure Assets: what the CISC page asks for
Checklist for operational information and interest and control information on the Register of Critical Infrastructure Assets, from the CISC regulatory-obligations page. The register is not public. The registration-form guidance PDF was not opened.
- Kind
- Checklist. Steps or checks to work through and tick off.
- Where it applies
- Australia, Commonwealth
- AI use
- Yellow You and the tool draft together, with you directing. You check every statement you rely on.
- Law stated as at
- 22 October 2026
- Status
- Maintained. Checked on 22 October 2026 against the authority it cites, for Australia and Commonwealth.
- Version
- 1
- Source
- Written for this library
When to use it
Use when an entity may be a responsible entity or a direct interest holder for a critical infrastructure asset and must give or update register information. Section 12L, which the page says defines the responsible entity for each class, was not opened.
Used for these tasks
Each task page says how far AI may help with the task and what the lawyer must review.
How AI may be used
AI may list corporate details the lawyer supplies against the fields the CISC page names. The lawyer decides whether the entity is a responsible entity or a direct interest holder.
AI may
- Record the asset, the reporting entity, and the interest percentage shown in a document the lawyer supplies
- Note a change of operator, data arrangement or ownership as an event the page says may need an update
- Flag a direct-interest-holder change with no date of becoming the holder
AI must not
- Must not decide that an asset is a critical infrastructure asset
- Must not publish register information. The page says the register is not public
- Must not invent the contents of a notice to a data service provider. That factsheet was not opened
The lawyer checks
- The role is responsible entity, direct interest holder, or both
- A new direct interest in an existing asset is reported within 30 days, and a new or newly critical asset within 6 months, as the page states
- Any update of interest and control information is within 30 days of the change
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is available after you log in. It is free. When you log in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- IT services statement of work template (under a master services agreement)
- Ransomware or cyber extortion payment report: fields on the ACSC form
- SaaS / cloud services agreement (Australian law, business customers)
- CCPA service provider and contractor addendum
- SaaS subscription and negative-option checklist
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- Service level schedule with service credits (SaaS, managed or hosted services)
- Checklist for electronic consumer records
- SaaS subscription agreement
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Email and SMS marketing campaign checklist (Spam Act consent, sender identification and unsubscribe)
- SOCI Act cyber incident report: 12-hour and 72-hour clocks
- Software source code escrow agreement (three-party: supplier, customer and escrow agent)
- AI vendor terms review checklist
- Statement of work
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Critical infrastructure risk management program: annual report contents
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Open source licence compliance review checklist (technology transactions and product releases)
- Security incident clause
- Consumer Data Right: data holder obligations on the CDR site
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area