TRUST ATLAS WORKSHEET
Safeguard evidence
POPIA · Step 3 · Contract with operators and assess safeguards- Who prepares it
- Legal + security
- When to prepare it
- Before outsourcing or transfers
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Evidence ID
- EV-021
- Control or request
- AC-04, October administrator review
- Period and scope
- 1 to 31 Oct 2026 UTC, production tenant
- Source and capture
- IAM export filtered to active elevated roles
- Link or record ID
- Restricted workpaper EV-021 plus ticket IAM-114
- Reviewer and status
- Security assurance, verified
Gather first
- Control descriptions and test request
- Source system records
- Defined period and evidence access rules
How to prepare it
- Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
- Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
- Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.
Review
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Handoff
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.