CYBERJA · PRACTICE GUIDE

Security Audit & Compliance Evidence Hub

Use synthetic evidence. Enter your own observations, then compare them with the worked direction below.

Open the tool · Open this file in a browser or print it to PDF.

Practice scenario

A release approval record is missing from a sampled production change.

Record the assessment

Open Connected Workspaces and select Audit & compliance. Use the assessment form to work through these prompts.

Requirement and control objective — Identify the exact policy, contract or framework requirement and the intended control outcome. A framework mapping does not establish compliance.

Scope, exclusions and criteria — Name the systems, timeframe, accountable owner, exclusions and test criteria.

Assessment method — Select the method used; combine methods when a document alone cannot demonstrate operation.

Population and sample rationale — State population size, sample size, period and selection method. Explain what the sample cannot prove.

Test procedure and observed result — Document reproducible steps and actual results. Separate design adequacy from operating effectiveness.

Test conclusion — Use insufficient evidence when evidence is missing or the sample is not adequate.

Finding: criterion, condition, cause and effect — Explain the expected state, observed deviation, supported cause and business consequence. Do not invent causes.

Corrective action and retest criteria — Assign an owner, due date and specific closure evidence. Capture management response and independent follow-up where practical.

Worked direction

Compare the change ticket, deployment timestamp and approval criteria. Write a finding and specify evidence needed for retest.

Review your work

Agree scope and criteria before collecting evidence.

Choose a defensible sample and method.

Record facts, exceptions and limitations.

Communicate the finding and verify corrective action.

Evidence and handoff

Capture a mock evidence reference and its limitations. Record the finding, accountable owner and next review. Where a material risk remains, record it in the shared risk register and schedule a follow-up.

Reference: NIST SP 800-53A Rev. 5: Assessing Security and Privacy Controls — https://csrc.nist.gov/pubs/sp/800/53/a/r5/final

Continue with the community

Compare your practice approach with other CyberJA Connect members.

Join CyberJA Connect ↗