Skip to content
Compliance for Technical Staff

Lesson 6: Prove it and keep it working

You will be able to: judge whether evidence shows a control operated across a whole period, and take a finding through to verified remediation.

About 4 min

Evidence answers specific questions. Which control? Which period? Which population? Who performed it, and when? What did they find, and what happened to the findings? If a record cannot answer those, it will not hold up.

  • Dated and attributable: you can tell when it happened and who did it.
  • Complete: it covers the whole population (every account, every change), not a convenient subset.
  • Covers the period: it shows the control operating each time it should have during the review period: every quarter, not just the last one.
  • System-generated where possible: exports and logs are stronger than screenshots, which capture one moment and often lack dates, filters, and context.
  • Closed loop: findings are tracked to resolution, and the resolution is verified.

Assessors often test a sample drawn from the population, so the population itself has to be complete and accurate. A control owner keeps the control running between assessments, and a review catches drift before an assessor does.

Exercise 1 of 2: Assemble the evidence packet

Control: Production access is reviewed quarterly by the platform lead. Inappropriate access is removed within five business days. Review period: 1 January – 31 December 2025.

Inspect each artifact and decide whether it is sufficient or what is wrong with it.

Sufficient
Undated or unattributable
Incomplete population
Incomplete approval
Unresolved finding
  1. 01

    Q1 access review export

    Date
    2 Apr 2025
    Scope
    42 of 42 accounts
    Sign-off
    Platform lead
    Findings
    2 removed, both closed 7 Apr
  2. 02

    Q2 access review export

    Date
    1 Jul 2025
    Scope
    44 of 44 accounts
    Sign-off
    Ravi, platform engineer
    Note
    Ravi’s own admin account is on the list
  3. 03

    Q3 access review export

    Date
    30 Sep 2025
    Scope
    8 of 45 accounts (prod-admin group only)
    Sign-off
    Platform lead
    Findings
    None
  4. 04

    Q4 access review export

    Date
    18 Dec 2025
    Scope
    45 of 45 accounts
    Sign-off
    Platform lead
    Findings
    3 flagged; 2 removed; 1 ticket open for 34 days
  5. 05

    IAM console screenshot

    Submitted as proof that the Q2 removals happened.

    Date
    Not visible
    Account
    Not visible
    Filters
    Unknown

Apply it 2 of 2: Close the finding

An access review finds that a contractor whose engagement ended six weeks ago still has production access.

Put the remediation steps in order, first to last.

  1. 1

    Find out why offboarding missed it

  2. 2

    Record the finding, actions, and verification, with the control owner’s sign-off

  3. 3

    Remove the access and confirm it is gone

  4. 4

    Fix the process, for example by including contractors in automated deprovisioning

  5. 5

    Check logs for any use of the account since the engagement ended

Key points

  • Evidence must answer: which control, which period, which population, who, when, and what happened to findings.
  • Exports and logs beat screenshots. Undated, unattributable records do not hold up.
  • A control has to operate every time during the period, not just before the audit.
  • Remediation means fixing the instance, finding the cause, fixing the process, and recording verification.