EvidenceSheet

CPS 234 para 17 Keep capability current as threats and assets change

The entity actively keeps its security capability up to date as vulnerabilities and threats shift, including shifts caused by changes to its own information assets or to its business environment.

Source: APRA CPS 234, CPS 234 para 17. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open APRA CPS 234 in the compliance library.

Applies to APRA-regulated entities.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Change management records showing security review of significant system or business changes · Ticketing / ITSM

periodic reviewEvidence produced at each review

  • Threat intelligence subscriptions and records of how intelligence changed controls or priorities · Document repository
  • Periodic threat and vulnerability assessment refreshed after major change · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

  • Capability roadmap revisions triggered by new threats, acquisitions or new channels · Document repository
  • Post-incident and lessons-learned actions feeding back into capability · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CPS 234 para 16 Assess the security capability of related and third parties · CPS 234 para 18 Maintain an information security policy framework