Checklist · Technology, Media & Telecommunications / IT Contracts
Critical infrastructure risk management program: annual report contents
The annual report on a critical infrastructure risk management program, as the CISC page describes it. The report is due within 90 days after the end of the financial year. It does not contain the full program. Enhanced timeframes are in a factsheet that 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 a responsible entity may have to adopt a written risk management program and lodge the annual report. Payment-system assets are regulated by the Reserve Bank, as the page states. The rules text 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 assemble dates and the five contents the page requires, from material the lawyer supplies. The lawyer decides whether the program is up to date and signs off through the governing body.
AI may
- Record the financial year and a date 90 days after it ended
- List hazards the lawyer has already identified against the vectors the page names
- Note whether the asset is in a baseline class, an enhanced class, or is a critical telecommunications asset, using only the classes the page lists
AI must not
- Must not declare that the program is up to date
- Must not state the enhanced-program commencement timetable. That factsheet was not opened
- Must not attach the full program. The page says the report need not contain it
The lawyer checks
- The asset is in a class the page lists for a baseline program, an enhanced program, or a telecommunications program
- The report includes each of the five matters the page says the Act requires
- The board, council or other governing body has approved the report before it is lodged
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)
- Register of Critical Infrastructure Assets: what the CISC page asks for
- 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)
- 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