EvidenceSheet
APRA CPS 234 · Roles and responsibilities (paras 13 to 14)

CPS 234 para 14 Information security roles and responsibilities defined

The entity sets out, clearly and in writing, who holds which information security duties: the Board, senior management, committees, working groups, forums and individuals who decide, approve, oversee, operate or otherwise carry out security functions.

Source: APRA CPS 234, CPS 234 para 14. 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
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • RACI or responsibility matrix for information security covering Board, executives, committees and named roles · Policy repository / GRC workspace
  • Position descriptions for the CISO and security staff stating their security duties · Document repository
  • Committee charters (for example technology risk or cyber committee) stating their security remit · Document repository
  • Accountability map or BEAR/FAR accountability statements where security responsibilities are assigned · Policy repository / GRC workspace
  • Delegations register for approval of security policies, exceptions and risk acceptances · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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 13 Board accountability for information security · CPS 234 para 15 Maintain an information security capability