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.
4Evidence packets
0Shared across programs
0Marked prepared on this device
| Evidence packet | PCI DSS |
|---|---|
| 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
PCI DSS
Account and privilege review evidence
Include the cardholder data environment and systems that can affect its security. Check current applicable review frequency and account types.
View the preparation plan
Evidence preparation plan PCI DSS 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 PCI DSS · Account and privilege review evidence Include the cardholder data environment and systems that can affect its security. Check current applicable review frequency and account types. 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 PCI DSS · Service provider oversight evidence Obtain current coverage for the precise payment services and document which relevant requirements each party manages. 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 PCI DSS · Change control evidence for in-scope systems Include relevant payment systems and security-impacting components. Determine whether a change requires specific validation or testing. 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 PCI DSS · Technical vulnerability management evidence Check applicable scan types, approved external scanning where required, frequency, and acceptable retest results for the payment environment.