Template library
COPRSETR WORKSHEET

IRAP control evidence register

Australia IRAP assessment · Step 2 · Build control evidence for the actual environment
Who prepares it
Security lead + platform operations + control owners
When to prepare it
Before assessment fieldwork

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Evidence row
Banksia privileged access review. Security links a dated review record, the approved access list and evidence of owner sign-off for the production region.
Inherited assurance
Hosting provider report covers a named data centre. Compliance verifies the location against the system inventory and documents facility and customer responsibilities.

Gather first

  • Agreed ISM release
  • Applicability matrix
  • Architecture
  • Configuration and operating records
  • Inherited assurance documentation

How to prepare it

  1. For each relevant control, record its reference, intended implementation, responsibility, status, evidence date and source owner.
  2. Gather redacted records that show the control in the assessed environment. If reusing assurance, confirm service, configuration, location, period and responsibility before linking it.
  3. Put sensitive records in the agreed restricted workspace. Assign outstanding items a due date and document when the assessor reviews each record.

Review

The assessor can trace each statement to dated evidence, record a finding and identify open gaps.

Handoff

Provide scoped access to the assessor and give each evidence owner a list of unresolved items.

Use the issuer’s current instructions and any required forms when you submit.

Current ISM and cloud security controls matrix (opens in a new tab)

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes