EVIDENCE PLANNER
Reuse evidence across programs
Choose the programs on your desk. See where a single evidence packet can help and check the scope, dates and proof each reviewer still needs.
6Evidence packets
0Shared across programs
0Marked prepared on this device
| Evidence packet | ISO 27001 |
|---|---|
| Candidate | |
| Candidate | |
| Candidate | |
| Candidate | |
| Candidate | |
| Candidate |
EVIDENCE PACKET
Access reviews
Who prepares it Identity team and system owners
- Dated export of effective access, with filters, system and group counts
- Reviewer decisions, business reasons and approvals
- Removal tickets and a follow-up check of effective access
What it can look like
The September billing review ties 41 entitlement rows to the identity and cloud exports. One removal shows the original admin grant, reviewer decision, ticket and follow-up export.
What each program still needs
ISO 27001
Evidence for privileged access treatment
Trace the review to your selected control, risk treatment and Statement of Applicability. Confirm it covers the ISMS boundary.
View the preparation plan
Evidence preparation plan ISO 27001 Access reviews [to prepare] Suggested owner Identity team and system owners - Dated export of effective access, with filters, system and group counts - Reviewer decisions, business reasons and approvals - Removal tickets and a follow-up check of effective access ISO 27001 · Evidence for privileged access treatment Trace the review to your selected control, risk treatment and Statement of Applicability. Confirm it covers the ISMS boundary. Backup restoration test [to prepare] Suggested owner Infrastructure and the business service owner - Approved recovery targets, test conditions and systems exercised - Dated logs, restored data validation and actual recovery time - Failed measures, corrective actions and results of the next test ISO 27001 · Backup and recovery evidence for selected controls Link the test to risk treatment and selected controls. Show who verifies that the restored data and dependencies are usable. Critical supplier review [to prepare] Suggested owner Procurement, service owner and Security - Service contract, relevant data and systems, and a responsibility matrix - Dated assurance evidence and the boundaries it covers - Open gaps, renewal or exit decision, and accountable owner ISO 27001 · Evidence for supplier risk treatment Check selected supplier controls, contract obligations and the cadence of follow-up for changes or findings. Production change approvals [to prepare] Suggested owner Engineering and release management - Complete production deployment list and documented query - Linked request, independent review or approval and release event - Tests, emergency exceptions and reviews after deployment ISO 27001 · Operational evidence for selected change controls Map changes to risk and approval records under the ISMS and demonstrate applicable operational control. Incident exercise and case file [to prepare] Suggested owner Security operations, Legal and the service owner - Case timeline with detection, awareness and classification recorded separately - Impact, evidence, documented reporting decision and any submission receipts - Exercise observations, corrective actions and retest owner ISO 27001 · Incident handling and improvement evidence Link chronology to roles, severity criteria, lessons learned and corrective actions in the ISMS. Vulnerability scan and retest [to prepare] Suggested owner Security engineering and asset owners - Scoped inventory, scan parameters and coverage reconciliation - Original findings with asset, severity, owner and dates - Remediation or documented decision, followed by dated verification ISO 27001 · Evidence for technical vulnerability treatment Connect prioritization and remediation decisions to risk criteria, control selection and evidence for material changes.