
Compliance Auditor Skill
- 150 installs
- 404kidwiz/claude-supercode-skills
Audits code and systems for security vulnerabilities, compliance gaps, and regulatory adherence.
About
Compliance auditor skill performs security and regulatory compliance audits on systems. Use when preparing for security review, ensuring standards compliance, or auditing code for vulnerabilities before production launch.
- Security scanning
- Compliance audits
- Vulnerability detection
Compliance Auditor by the numbers
- 150 all-time installs (skills.sh)
- Ranked #918 of 2,222 Security skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill compliance-auditorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 150 |
|---|---|
| Repository | 404kidwiz/claude-supercode-skills ↗ |
What it does
Audits code and systems for security vulnerabilities, compliance gaps, and regulatory adherence.
Files
Compliance Auditor Skill
Purpose
Provides regulatory compliance auditing expertise specializing in SOC2, HIPAA, GDPR, and industry-specific compliance frameworks. Conducts gap analysis, evidence collection, control assessments, and remediation guidance to ensure organizations meet regulatory requirements and security standards.
When to Use
- Conducting SOC 2 Type I & II audits
- Ensuring HIPAA compliance for healthcare systems
- Implementing GDPR data privacy requirements
- Preparing for PCI DSS assessments
- Mapping compliance requirements to organizational controls
- Performing gap analysis and remediation planning
Overview
Expert in regulatory compliance auditing, specializing in SOC2, HIPAA, GDPR, and industry-specific compliance frameworks with gap analysis and remediation guidance.
Compliance Frameworks
Financial & Business Compliance
- SOC 2 Type I & II - Service Organization Control reporting
- SOX - Sarbanes-Oxley Act compliance
- PCI DSS - Payment Card Industry Data Security Standard
- GLBA - Gramm-Leach-Bliley Act
Healthcare Compliance
- HIPAA - Health Insurance Portability and Accountability Act
- HITECH - Health Information Technology for Economic and Clinical Health
- HITECH - Omnibus Rule provisions
- 21 CFR Part 11 - Electronic signatures and records
Data Privacy & Protection
- GDPR - General Data Protection Regulation (EU)
- CCPA/CPRA - California Consumer Privacy Act/Privacy Rights Act
- PIPEDA - Personal Information Protection and Electronic Documents Act
- LGPD - Lei Geral de Proteção de Dados (Brazil)
Industry-Specific Standards
- ISO 27001 - Information Security Management
- ISO 27701 - Privacy Information Management
- NIST Cybersecurity Framework - Critical infrastructure
- CMMC - Cybersecurity Maturity Model Certification
Core Audit Competencies
Evidence Collection & Analysis
# Example patterns for compliance evidence
grep -r "audit" config/ --include="*.json" --include="*.yml" --include="*.properties"
grep -r "access" policies/ --include="*.md" --include="*.txt" --include="*.doc"
grep -r "retention" procedures/ --include="*.md" --include="*.pdf"Control Assessment
- Design effectiveness evaluation
- Operating effectiveness testing
- Control gap identification
- Remediation timeline development
- Continuous monitoring implementation
Documentation Review
- Policy and procedure analysis
- Evidence collection validation
- Risk assessment methodology review
- Incident response documentation
- Third-party assessment reports
Audit Methodology
Planning & Scoping
- Compliance requirement mapping
- Risk-based approach development
- Sampling methodology design
- Stakeholder interviews
- Documentation requests
Fieldwork Execution
- Control testing procedures
- Evidence collection protocols
- Process walk-throughs
- System configuration reviews
- Staff competency validation
Reporting & Findings
- Gap analysis documentation
- Risk rating assignments
- Remediation recommendations
- Implementation roadmaps
- Executive summary preparation
Specific Compliance Areas
SOC 2 Trust Services Criteria
- Security - System protection against unauthorized access
- Availability - System availability for operation and use
- Processing Integrity - System processing completeness and accuracy
- Confidentiality - Information protection from unauthorized disclosure
- Privacy - Personal information collection and use controls
HIPAA Administrative Safeguards
- Security officer designation
- Workforce security procedures
- Information access management
- Security awareness and training
- Security incident procedures
GDPR Data Protection Requirements
- Lawfulness of processing
- Purpose limitation principles
- Data minimization practices
- Accuracy maintenance procedures
- Storage limitation implementations
Audit Scenarios
Cloud Service Provider Assessment
- AWS/Azure/GCP security configurations
- Multi-tenancy isolation controls
- Data encryption verification
- Service provider due diligence
- Subprocessor management
Software Development Lifecycle
- Secure coding practices
- Change management procedures
- Code review processes
- Security testing integration
- DevSecOps pipeline compliance
Third-Party Risk Management
- Vendor assessment procedures
- Contract compliance verification
- Service level agreement monitoring
- Data processing agreement review
- Supply chain security validation
Deliverables
Compliance Reports
- Comprehensive audit findings
- Gap analysis with remediation plans
- Control effectiveness ratings
- Risk mitigation strategies
- Compliance dashboard development
Skill-Specific Scripts and References
Available Compliance Auditor Scripts
Located in scripts/ directory:
- check_gdpr.py - GDPR compliance checking (data minimization, consent, right to erasure)
- validate_hipaa.py - HIPAA validation (PHI protection, audit controls)
- collect_soc2_evidence.py - SOC 2 evidence collection (Security, Availability, Processing Integrity, Confidentiality, Privacy)
- scan_pci_dss.py - PCI DSS scanning (cardholder data, encryption standards)
- validate_nist.py - NIST controls validation (CSF, SP 800-53)
- assess_iso27001.py - ISO 27001 assessment (ISMS controls)
- generate_report.py - Compliance report generation
Available Compliance Auditor References
Located in references/ directory:
- gdpr_requirements.md - GDPR requirements and compliance checks
- hipaa_guidelines.md - HIPAA guidelines and controls
- soc2_controls.md - SOC 2 Type 2 examination criteria and controls
- pci_dss_standard.md - PCI DSS v4.0 requirements and compliance checklist
- nist_controls.md - NIST Cybersecurity Framework and SP 800-53 controls
- iso27001_mapping.md - ISO 27001 control mapping and implementation guidance
Script Usage Examples
# GDPR compliance check
python3 scripts/check_gdpr.py . --config config/compliance.yaml --output gdpr_report.json
# HIPAA validation
python3 scripts/validate_hipaa.py . --format text
# SOC 2 evidence collection
python3 scripts/collect_soc2_evidence.py . --framework SOC2_Type2 --output soc2_evidence/
# PCI DSS scanning
python3 scripts/scan_pci_dss.py . --scan_level full
# NIST controls validation
python3 scripts/validate_nist.py . --framework CSF
# ISO 27001 assessment
python3 scripts/assess_iso27001.py . --controls annex_a --output iso_report.md
# Generate compliance report
python3 scripts/generate_report.py --evidence evidence/ --compliance SOC2 --output compliance_report.mdConfiguration Files
Create config/compliance.yaml for script configuration:
compliance_auditing:
audit_scope: '.'
frameworks: ['SOC2', 'GDPR', 'HIPAA', 'PCI_DSS', 'ISO27001', 'NIST']
check_gdpr:
data_minimization: true
consent_management: true
right_to_erasure: true
data_portability: true
validate_hipaa:
phi_protection: true
audit_controls: true
administrative_safeguards: true
physical_safeguards: true
technical_safeguards: true
collect_soc2_evidence:
trust_services_criteria: ['security', 'availability', 'processing_integrity', 'confidentiality', 'privacy']
common_criteria: true
scan_pci_dss:
scan_level: 'full'
cardholder_data_scope: true
encryption_standards: true
validate_nist:
framework: 'CSF'
control_baselines: ['low', 'moderate', 'high']
assess_iso27001:
controls: 'annex_a'
isms_controls: true
generate_report:
report_format: 'markdown'
include_recommendations: true
include_roadmap: truePolicy & Procedure Templates
- Security policy frameworks
- Incident response procedures
- Data classification guidelines
- Access management policies
- Business continuity plans
Training Materials
- Compliance awareness programs
- Role-specific security training
- Incident response tabletop exercises
- Privacy best practices guides
- Regulatory change management
Continuous Compliance
- Automated compliance monitoring
- Regulatory change tracking
- Control effectiveness testing
- Risk assessment updates
- Compliance management systems integration
Industry Expertise
- Healthcare providers and payers
- Financial services institutions
- SaaS and technology companies
- Government contractors
- Educational institutions
Examples
Example 1: SOC 2 Type II Preparation for SaaS Startup
Scenario: A growing SaaS company preparing for their first SOC 2 Type II audit needs to implement controls and collect evidence for the Security and Availability trust services criteria.
Audit Preparation Approach: 1. Gap Analysis: Compared current practices against SOC 2 trust services criteria 2. Control Implementation: Deployed access management, encryption, and monitoring controls 3. Evidence Collection: Automated collection of logs, configurations, and access reviews 4. Remediation: Addressed 23 gaps identified in initial assessment
Key Controls Implemented:
- Multi-factor authentication for all system access
- Automated log retention and security monitoring
- Encrypted data at rest and in transit (TLS 1.3, AES-256)
- Incident response procedures with documented evidence
- Vendor management program with security assessments
Audit Result: Passed with 2 minor observations (no material findings)
Example 2: HIPAA Compliance for Healthcare Application
Scenario: A healthcare technology company needs to ensure their patient portal meets HIPAA requirements for PHI protection.
Compliance Assessment: 1. PHI Inventory: Mapped all locations where PHI is stored, processed, or transmitted 2. Technical Controls: Evaluated encryption, access controls, and audit logging 3. Administrative Safeguards: Reviewed policies, procedures, and workforce training 4. Business Associate Agreements: Audited all third-party relationships
Critical Findings and Remediation:
- Unencrypted database backups → Implemented TDE and encrypted backup storage
- Excessive user access → Deployed role-based access control (RBAC)
- Missing audit logs → Integrated CloudTrail and database audit logging
- Outdated BAA with vendor → Negotiated updated BAA with current requirements
Outcome: Achieved full HIPAA compliance within 90 days
Example 3: GDPR Data Privacy Implementation
Scenario: An e-commerce company expanding to EU markets needs to implement GDPR compliance for customer data processing.
Privacy Implementation: 1. Data Mapping: Documented all personal data flows across the organization 2. Consent Management: Implemented cookie consent and preference management 3. Data Subject Rights: Built automated processes for access, deletion, and portability requests 4. Data Retention: Defined and implemented retention schedules
Implementation Components:
- Privacy-by-design architecture review
- Consent management platform integration
- Data subject request (DSR) automation workflow
- International data transfer mechanisms (Standard Contractual Clauses)
- Privacy impact assessment (PIA) process
Measurable Outcomes:
- Consent capture rate: 98% (up from 45%)
- DSR response time: 5 days average (regulatory requirement: 30 days)
- Data breach notification process tested quarterly
- Privacy training completion: 100% of employees
Best Practices
Audit Preparation
- Start Early: Begin compliance efforts 6-12 months before audit
- Gap Analysis First: Understand where you stand before planning remediation
- Phased Approach: Address highest-risk gaps first
- Evidence Automation: Collect evidence continuously, not just before audit
- Management Buy-In: Ensure leadership understands compliance requirements
Control Framework
- Risk-Based Controls: Implement controls based on risk assessment findings
- Defense in Depth: Multiple layers of controls for critical areas
- Least Privilege: Grant minimum access required for each role
- Change Management: Document and review all control changes
- Continuous Monitoring: Implement automated control effectiveness testing
Documentation Excellence
- Clear Policies: Write policies that are understandable and actionable
- Procedure Documentation: Detail how policies are implemented operationally
- Evidence Artifacts: Maintain comprehensive evidence of control operation
- Traceability: Link controls to requirements and risks
- Version Control: Track policy changes over time
Third-Party Management
- Due Diligence: Assess security posture before engagement
- Contract Requirements: Include security requirements in contracts
- Ongoing Monitoring: Reassess vendors periodically
- Incident Coordination: Establish breach notification procedures
- Exit Planning: Define data handling at relationship end
Regulatory Updates
- Track Changes: Monitor regulatory developments in your industry
- Impact Assessment: Evaluate how changes affect current compliance
- Proactive Adaptation: Update controls before enforcement deadlines
- Industry Collaboration: Participate in industry compliance groups
- Expert Consultation: Engage specialists for complex requirements
Anti-Patterns
Audit Process Anti-Patterns
- Checkbox Compliance: Treating compliance as a form-filling exercise - focus on actual security outcomes
- Point-in-Time Snapshots: Assessing controls only at audit time - implement continuous compliance monitoring
- Evidence Fabrication: Creating evidence rather than demonstrating real controls - build genuine compliance programs
- Scope Shrinking: Minimizing audit scope to reduce findings - address root causes instead of hiding problems
Control Implementation Anti-Patterns
- Paper Controls: Policies that exist only in documentation - implement technical enforcement mechanisms
- Over-Complex Controls: Controls so complex they cannot be operationalized - balance security with operability
- Control Redundancy: Implementing overlapping controls without coordination - map and rationalize control portfolio
- Control Gaps: Leaving security domains uncovered - maintain comprehensive control coverage
Evidence Collection Anti-Patterns
- Last Minute Rush: Collecting evidence only when auditors arrive - automate continuous evidence collection
- Incomplete Evidence: Providing partial evidence that raises more questions - ensure comprehensive documentation
- Outdated Evidence: Using evidence from outdated systems or processes - maintain current evidence artifacts
- Inaccessible Evidence: Evidence that cannot be located or produced - organize and index evidence systematically
Remediation Anti-Patterns
- Temporary Fixes: Applying bandages instead of solving root causes - implement permanent solutions
- Finding Chasing: Prioritizing based on audit severity rather than risk - assess actual risk impact
- Remediation Debt: Accumulating findings without resolution - maintain remediation backlog with timelines
- Siloed Remediation: Fixing findings in isolation without systemic improvement - identify patterns and prevent recurrence
GDPR Requirements Reference
Overview
Comprehensive guide to GDPR (General Data Protection Regulation) requirements and compliance checks.
GDPR Principles
Article 5: Principles Relating to Processing of Personal Data
1. Lawfulness, Fairness, and Transparency
- Personal data must be processed lawfully, fairly, and transparently
- Legal basis for processing must be documented
- Privacy notices must be clear and accessible
2. Purpose Limitation
- Data must be collected for specified, explicit, and legitimate purposes
- No further processing incompatible with those purposes
- Purposes must be documented and communicated
3. Data Minimization
- Data must be adequate, relevant, and limited to what is necessary
- Collect only data needed for the stated purpose
- Regular reviews of data collected
4. Accuracy
- Data must be accurate and kept up to date
- Inaccurate data must be erased or rectified
- Reasonable steps taken to ensure accuracy
5. Storage Limitation
- Data must be kept in a form that permits identification for no longer than necessary
- Data retention policies must be established
- Secure deletion when no longer needed
6. Integrity and Confidentiality
- Data must be processed securely
- Protection against unauthorized processing
- Protection against accidental loss, destruction, or damage
7. Accountability
- Controller must be responsible for and demonstrate compliance
- Documentation of compliance measures
- Regular audits and reviews
Data Subject Rights
Right to be Informed (Articles 13-14)
- [ ] Privacy notice provided before data collection
- [ ] Clear identification of controller and DPO
- [ ] Purposes and legal basis for processing
- [ ] Data retention period
- [ ] Transfer information (if applicable)
- [ ] Data subject rights information
- [ ] Right to withdraw consent
Right of Access (Article 15)
- [ ] Data subjects can access their personal data
- [ ] Access request process documented
- [ ] Response within 1 month (extendable by 2 months)
- [ ] Information provided in structured, commonly used format
- [ ] Details of processing activities provided
Right to Rectification (Article 16)
- [ ] Data subjects can correct inaccurate data
- [ ] Process for updating personal data
- [ ] Correction acknowledgment provided
- [ ] Third parties informed of corrections
Right to Erasure (Right to be Forgotten) (Article 17)
- [ ] Process for data deletion requests
- [ ] Deletion completed within 1 month
- [ ] Exceptions documented and communicated
- [ ] Third-party deletions tracked
- [ ] Backups and archives addressed
Right to Restrict Processing (Article 18)
- [ ] Process for restricting processing
- [ ] Clear communication of restriction
- [ ] Storage while restriction in place
Right to Data Portability (Article 20)
- [ ] Data can be transferred to another controller
- [ ] Data provided in structured, machine-readable format
- [ ] Direct transfer to another controller where technically feasible
- [ ] Portability request process documented
Right to Object (Article 21)
- [ ] Data subjects can object to processing
- [ ] Objection process documented
- [ ] Automated decision-making objection process
- [ ] Marketing opt-out available
Rights in Relation to Automated Decision Making and Profiling (Articles 22-23)
- [ ] Human intervention available
- [ ] Information about logic used provided
- [ ] Right to contest decision
- [ ] Impact of profiling explained
Legal Bases for Processing (Article 6)
Consent
- [ ] Freely given, specific, informed, unambiguous
- [ ] Explicit consent for sensitive data
- [ ] Consent can be withdrawn
- [ ] Proof of consent maintained
- [ ] Granular consent where appropriate
Contract
- [ ] Processing necessary for contract performance
- [ ] Contract terms specify data processing
- [ ] Data subject party to contract
Legal Obligation
- [ ] Processing required by law
- [ ] Legal basis documented
- [ ] Applicable legislation identified
Vital Interests
- [ ] Processing necessary to protect vital interests
- [ ] Life or death situations
- [ ] Emergency circumstances
Public Task
- [ ] Processing necessary for task in public interest
- [ ] Official authority basis documented
- [ ] Legal basis in law or regulation
Legitimate Interests
- [ ] Legitimate interests of controller or third party
- [ ] Data subject interests and rights override not overridden
- [ ] Legitimate interest assessment completed
- [ ] Balance of interests documented
Special Category Data (Article 9)
Processing Conditions
- [ ] Explicit consent obtained
- [ ] Employment and social security law basis
- [ ] Vital interests basis
- [ ] Legal claims basis
- [ ] Public interest basis
- [ ] Health/public interest basis
- [ ] Public data basis
- [ ] Appropriate safeguards in place
Sensitive Data Types
- Racial or ethnic origin
- Political opinions
- Religious or philosophical beliefs
- Trade union membership
- Genetic data
- Biometric data
- Health data
- Sex life or sexual orientation
Controller and Processor Obligations
Controller Obligations (Articles 24-43)
- [ ] Data Protection by Design and Default implemented
- [ ] Technical and organizational measures in place
- [ ] Processor agreements in place
- [ ] Data Protection Impact Assessments (DPIAs) for high-risk processing
- [ ] DPO appointed (if required)
- [ ] Records of processing activities maintained
- [ ] Security breach notification process (72 hours)
- [ ] Cross-border transfer mechanisms in place
Processor Obligations (Articles 28-32)
- [ ] Only process on controller's instructions
- [ ] Assist controller with SARs
- [ ] Assist controller with security breach notifications
- [ ] Assist controller with compliance obligations
- [ ] Return or delete data after services
- [ ] Allow controller audits and inspections
- [ ] Contractual obligations in writing
Cross-Border Data Transfers (Articles 44-50)
Adequacy Decisions
- [ ] Transfers only to adequate countries
- [ ] Adequacy decisions documented
- [ ] European Commission adequacy list consulted
Appropriate Safeguards
- [ ] Binding Corporate Rules (BCRs) in place
- [ ] Standard Contractual Clauses (SCCs) used
- [ ] Approved codes of conduct
- [ ] Approved certification mechanisms
Derogations
- [ ] Data subject consent obtained
- [ ] Contract performance required
- [ ] Important public interest basis
- [ ] Legal claims basis
- [ ] Vital interests basis
- [ ] Public register basis
Data Protection by Design and by Default (Article 25)
by Design
- [ ] Privacy considered at design phase
- [ ] Data protection principles integrated
- [ ] Impact assessments conducted
- [ ] Stakeholders consulted
by Default
- [ ] Default privacy settings protect data subjects
- [ ] Personal data not automatically made public
- [ ] Minimal data processing by default
- [ ] Access restricted by default
Data Protection Impact Assessment (DPIA) (Article 35)
When Required
- Systematic and extensive processing
- Large-scale monitoring
- Large-scale processing of special categories
- Public access required by law
- Criminal offense related evaluation
- High risk to rights and freedoms
DPIA Process
1. Description of Processing
- Purposes of processing
- Categories of data
- Data subjects involved
- Storage period
- Data flows
2. Assessment of Necessity and Proportionality
- Is processing necessary?
- Are purposes proportionate?
- Less intrusive alternatives considered?
3. Assessment of Risks
- Identify risks to data subjects
- Evaluate likelihood and impact
- Consider special categories
4. Risk Mitigation
- Identify measures to address risks
- Implement safeguards
- Evaluate residual risk
5. Consultation with DPO
- Involve DPO in process
- Document DPO advice
6. Consultation with Supervisory Authority (if needed)
- High-risk processing requires consultation
- Provide assessment to authority
DPIA Template
# Data Protection Impact Assessment
**Project:** [Project Name]
**Date:** [Date]
**DPO:** [Name]
## 1. Processing Description
### Purpose
[Describe purpose of processing]
### Data Categories
- [ ] Identification data
- [ ] Contact data
- [ ] Special category data
- [Other]
### Data Subjects
- [ ] Customers
- [ ] Employees
- [ ] Website visitors
- [Other]
### Data Flow
[Describe how data flows through the system]
## 2. Necessity and Proportionality
Is processing necessary? Yes/No
Explain: [Justification]
Is it proportionate? Yes/No
Explain: [Justification]
Less intrusive alternatives considered:
- [Alternative 1]
- [Alternative 2]
## 3. Risk Assessment
| Risk | Likelihood | Impact | Mitigation | Residual Risk |
|------|------------|--------|------------|---------------|
| Risk 1 | High/Med/Low | High/Med/Low | [Mitigation] | High/Med/Low |
| Risk 2 | ... | ... | ... | ... |
## 4. Mitigation Measures
[Describe measures implemented]
## 5. Conclusion
Processing: Approved/Not Approved
Rationale: [Explanation]Records of Processing Activities (Article 30)
Required Information
- Name and contact details of controller and DPO
- Purposes of processing
- Categories of data subjects and data
- Categories of recipients
- International transfers
- Time limits for erasure
- Security measures
Record Template
# Record of Processing Activities
**Controller:** [Name]
**Date Established:** [Date]
## Processing Activity 1
**Purpose:** [Purpose]
**Data Categories:** [Categories]
**Data Subjects:** [Types]
**Recipients:** [Who]
**International Transfers:** [Details]
**Erase After:** [Time period]
**Security Measures:** [Measures]Security Breach Notification (Articles 33-34)
Notification to Supervisory Authority (Article 33)
- [ ] Notification within 72 hours of awareness
- [ ] Describe nature of breach
- [ ] Categories of data subjects concerned
- [ ] Data likely accessed categories
- [ ] Likely consequences
- [ ] Measures taken or proposed
- [ ] Provide reasons for delay if >72 hours
Notification to Data Subject (Article 34)
- [ ] Notify if high risk to rights and freedoms
- [ ] Notification without undue delay
- [ ] Describe breach clearly
- [ ] Contact point for more information
- [ ] Measures to mitigate risks
Breach Response Process
1. Detection and Containment
- Identify breach source
- Contain breach
- Preserve evidence
2. Assessment
- Determine scope of breach
- Identify affected data
- Assess impact
3. Notification
- Notify DPO (if applicable)
- Notify supervisory authority (if required)
- Notify data subjects (if required)
4. Post-Incident
- Document lessons learned
- Update security measures
- Review DPIA if applicable
Compliance Checklist
General Compliance
- [ ] GDPR policies and procedures documented
- [ ] Staff training completed
- [ ] DPO appointed (if required)
- [ ] Records of processing maintained
- [ ] Data protection by design implemented
- [ ] Data protection by default implemented
Data Subject Rights
- [ ] Right to be informed - implemented
- [ ] Right of access - implemented
- [ ] Right to rectification - implemented
- [ ] Right to erasure - implemented
- [ ] Right to restriction - implemented
- [ ] Right to portability - implemented
- [ ] Right to object - implemented
- [ ] Rights related to automated decision-making - implemented
Security Measures
- [ ] Technical security measures in place
- [ ] Organizational security measures in place
- [ ] Encryption at rest implemented
- [ ] Encryption in transit implemented
- [ ] Access controls implemented
- [ ] Authentication mechanisms in place
- [ ] Regular security reviews conducted
- [ ] Incident response plan in place
Documentation
- [ ] Processing activities recorded
- [ ] Consent recorded and maintained
- [ ] DPIAs completed for high-risk processing
- [ ] Processor agreements in place
- [ ] Cross-border transfer mechanisms documented
- [ ] Breach notification procedures documented
Tools and Resources
DPIA Templates
Consent Management
- Cookie consent banners
- Preference centers
- Granular consent options
- Withdrawal mechanisms
Data Subject Request Management
- [ ] Web form for requests
- [ ] Email-based request handling
- [ ] Request tracking system
- [ ] Response templates
Compliance Monitoring
- Automated compliance checks
- Privacy impact assessments
- Regular audits
- Continuous monitoring
References
PCI DSS Standard Reference
Overview
Payment Card Industry Data Security Standard (PCI DSS) v4.0 requirements and compliance checklist.
PCI DSS v4.0 Requirements Overview
Requirement 1: Install and maintain network security controls
1.1 - Network Security Policy
- [ ] Network security policy established
- [ ] Policy reviewed annually and updated
- [ ] Policy communicated to all personnel
1.2 - Network Security Configuration
- [ ] Default passwords changed on all systems
- [ ] Default security parameters changed
- [ ] Unused services disabled
- [ ] Strong cryptography for passwords
1.3 - Secure Network Connections
- [ ] Network segmentation implemented
- [ ] Wireless networks secured
- [ ] VPN for remote access
- [ ] VPN authentication and encryption
1.4 - Firewalls
- [ ] Firewall configuration reviewed every 6 months
- [ ] Firewall rules documented
- [ ] Unnecessary services blocked
- [ ] Direct internet access prohibited for cardholder systems
1.5 - Wireless Networks
- [ ] Wireless networks scanned quarterly
- [ ] Wireless authentication required
- [ ] Wireless encryption (WPA2+)
- [ ] Wireless infrastructure outside cardholder data environment
1.6 - Mobile Device Security
- [ ] Mobile device security policy
- [ ] Mobile device inventory
- [ ] Mobile device management implemented
- [ ] Remote wipe capability
Requirement 2: Apply secure configurations to all system components
2.1 - Process and Procedures
- [ ] Configuration standards documented
- [ ] Process for secure configuration
- [ ] Configuration verification
- [ ] Configuration management
2.2 - Vendor Defaults
- [ ] All vendor defaults changed
- [ ] Default accounts removed or disabled
- [ ] Default passwords removed
- [ ] Default security parameters modified
2.3 - System Hardening
- [ ] System hardening procedures
- [ ] Unnecessary services disabled
- [ ] System components hardened according to standards
- [ ] Secure protocols only (SSHv2, TLS 1.2+)
2.4 - Shared Systems
- [ ] Shared hosting risks assessed
- [ ] Shared hosting only if cardholder data environment isolated
- [ ] Separate cardholder data environment
2.5 - Configuration Maintenance
- [ ] Configuration changes documented
- [ ] Change control process
- [ ] Testing before deployment
- [ ] Impact analysis
Requirement 3: Protect stored account data
3.1 - Keep Cardholder Data to a Minimum
- [ ] Data retention policy defined
- [ ] Data retention policy communicated
- [ ] Data disposal process
- [ ] Verification of data disposal
- [ ] Storage retention reviewed quarterly
3.2 - Encryption of Stored Cardholder Data
- [ ] Full track data not stored
- [ ] Card verification codes not stored
- [ ] Sensitive authentication data not stored after authorization
- [ ] PAN displayed masked (showing no more than first six/last four digits)
- [ ] PAN rendered unreadable (hashed, truncated, indexed)
- [ ] Cryptographic keys managed securely
3.3 - Primary Account Number (PAN) Protection
- [ ] Display of PAN restricted
- [ ] Unmasked PAN not displayed
- [ ] Access to unmasked PAN restricted
- [ ] Encryption keys stored securely
- [ ] Secure key storage devices
3.4 - Encryption Key Management
- [ ] Key generation process documented
- [ ] Secure key distribution
- [ ] Secure key storage
- [ ] Key rotation schedule
- [ ] Key decommissioning process
- [ ] Dual control for key management
- [ ] Split knowledge for key management
- [ ] Key backup procedures
3.5 - Cryptographic Keys
- [ ] Keys managed in compliance with standards
- [ ] Key management processes documented
- [ ] Key custodians identified
- [ ] Key access restrictions
- [ ] Key compromise procedures
Requirement 4: Protect cardholder data in transit
4.1 - Encryption of Cardholder Data in Transit
- [ ] Strong cryptography and security protocols (TLS 1.2+)
- [ ] Only trusted certificates and keys
- [ ] Trusted keys/certificates maintained
- [ ] Protocol supported by system and client
- [ ] Secure connections only
4.2 - Network Security Controls
- [ ] Sensitive data transmitted only over secure channels
- [ ] Never sent over insecure protocols (HTTP, FTP, telnet)
- [ ] Network security controls prevent interception
- [ ] Wireless transmissions encrypted
- [ ] End-to-end encryption for wireless communications
4.3 - Encryption Key Management
- [ ] Cryptographic keys used for encryption in transit managed securely
- [ ] Key generation and distribution secure
- [ ] Key storage secure
- [ ] Key rotation per industry standards
Requirement 5: Protect all systems and networks from malicious software
5.1 - Anti-Virus Software
- [ ] Anti-virus software deployed on all systems
- [ ] Anti-virus updated regularly
- [ ] Regular anti-virus scans
- [ ] Anti-virus software active at all times
- [ ] Anti-virus protection maintained
5.2 - Malicious Software Protection
- [ ] Systems protected against malicious software
- [ ] Protection mechanisms up-to-date
- [ ] Regular scans for malicious software
- [ ] Malicious software detection and prevention
5.3 - Anti-Malware Processes
- [ ] Anti-malware processes and procedures
- [ ] Malicious software response procedures
- [ ] Malware incident management
- [ ] Post-malware incident review
5.4 - Malicious Software Awareness
- [ ] User awareness training for malicious software
- [ ] Phishing awareness
- [ ] Social engineering awareness
- [ ] Security awareness training
Requirement 6: Develop and maintain secure systems and applications
6.1 - Security Development Lifecycle
- [ ] Secure development lifecycle process
- [ ] Secure coding practices
- [ ] Application security training
- [ ] Security requirements included in development
6.2 - Security Testing
- [ ] Regular security testing of applications
- [ ] Vulnerability scanning
- [ ] Penetration testing
- [ ] Testing after significant changes
6.3 - Secure Authentication
- [ ] Multi-factor authentication implemented
- [ ] Strong authentication for remote access
- [ ] Encryption for authentication over open networks
6.4 - Input Validation
- [ ] Input validation on all data
- [ ] Output validation
- [ ] Data sanitization
- [ ] SQL injection prevention
- [ ] XSS prevention
6.5 - Secure Coding Practices
- [ ] Code reviews
- [ ] Secure coding standards
- [ ] Error handling without information disclosure
- [ ] Parameterized queries
6.6 - Software Updates
- [ ] Security patches applied promptly
- [ ] Software updates according to vendor schedule
- [ ] Critical security patches within 1 month
- [ ] Vulnerability monitoring
6.7 - Development and Test Environments
- [ ] Development/test environments separate from production
- [ ] Test data masked or obfuscated
- [ ] Production data not used for testing
- [ ] Access controls for development environments
Requirement 7: Restrict access to system components and cardholder data
7.1 - Access Control Policy
- [ ] Access control policy established
- [ ] Policy reviewed annually
- [ ] Principle of least privilege
- [ ] Need-to-know basis
7.2 - User Identification and Authentication
- [ ] Unique user ID for each person
- [ ] Multi-factor authentication for remote access
- [ ] Strong password policies
- [ ] Password change at first login
- [ ] Temporary passwords changed at first use
- [ ] Lockout after failed attempts
- [ ] Session timeouts
7.3 - Access Rights
- [ ] Access granted based on business need
- [ ] Access rights documented
- [ ] Regular access reviews (quarterly)
- [ ] Access rights removed when no longer needed
7.4 - System Administrators
- [ ] Separate accounts for administrative duties
- [ ] Administrator authentication required
- [ ] Root/admin access controlled
- [ ] Use of personal accounts for administration prohibited
7.5 - In-House and Third-Party Personnel
- [ ] Background checks for personnel with cardholder data access
- [ ] Personnel screened before access granted
- [ ] Background check policy documented
- [ ] Contractual obligations for third parties
7.6 - Personnel Termination
- [ ] Access revoked immediately upon termination
- [ ] Personnel termination procedures
- [ ] Inventory of all access items returned
- [ ] Logical and physical access removed
7.7 - Access Revocation
- [ ] Access revoked when no longer needed
- [ ] Revocation process documented
- [ ] Regular access review
- [ ] Access log review
Requirement 8: Identify users and authenticate access to system components
8.1 - Authentication Mechanisms
- [ ] Authentication mechanisms for all users
- [ ] Strong authentication (MFA for remote access)
- [ ] Password complexity requirements
- [ ] Password change frequency
- [ ] Password history requirements
- [ ] Password hashing/encryption
8.2 - Multi-Factor Authentication
- [ ] MFA implemented for all access to cardholder data
- [ ] MFA implemented for remote network access
- [ ] MFA for administrative access
- [ ] MFA factors independent (something you have, know, are)
8.3 - Password Management
- [ ] Passwords never shared
- [ ] Passwords never written down
- [ ] Passwords not in scripts or code
- [ ] Passwords rotated periodically
- [ ] Forced password changes
- [ ] Default passwords never used
8.4 - Identification and Authentication
- [ ] Users uniquely identified
- [ ] Identification and authentication mechanisms
- [ ] Authenticated sessions monitored
- [ ] Session timeout configured
8.5 - Security Policy
- [ ] Authentication security policy
- [ ] Policy communicated to all users
- [ ] Policy acceptance confirmation
- [ ] Regular security awareness training
Requirement 9: Restrict physical access to cardholder data
9.1 - Physical Access Control
- [ ] Physical access control policy
- [ ] Physical access restricted to authorized personnel
- [ ] Access logs maintained
- [ ] Access badges/keys controlled
- [ ] Visitor management
9.2 - Media Handling
- [ ] Secure media storage
- [ ] Media transport secured
- [ ] Media destruction procedures
- [ ] Media inventory maintained
- [ ] Hard drive destruction/cryptographic erase
9.3 - Physical Security
- [ ] Physical barriers and fences
- [ ] Security cameras and monitoring
- [ ] Alarm systems
- [ ] Security guards (if applicable)
- [ ] Security lighting
9.4 - Visitors
- [ ] Visitor authorization process
- [ ] Visitor escorts
- [ ] Visitor badges/IDs
- [ ] Visitor log
9.5 - Media Destruction
- [ ] Secure media destruction
- [ ] Destruction process documented
- [ ] Destruction verified
- [ ] Certificates of destruction maintained
9.6 - Equipment Maintenance
- [ ] Equipment maintenance procedures
- [ ] Maintenance personnel authorization
- [ ] Supervision of maintenance
- [ ] Media removal before maintenance
Requirement 10: Log and monitor access to system components and cardholder data
10.1 - Audit Trails
- [ ] Audit trail for all system components
- [ ] Audit logs capture user identification
- [ ] Audit logs capture event type
- [ ] Audit logs capture date and time
- [ ] Audit logs capture success/failure
- [ ] Audit logs capture source of event
10.2 - Log Review
- [ ] Regular review of logs
- [ ] Security event detection
- [ ] Daily review of critical systems
- [ ] Weekly review of other systems
- [ ] Retention of audit logs (at least 1 year, 3 months available)
10.3 - Log Protection
- [ ] Logs protected from tampering
- [ ] Log backup and storage
- [ ] Immediate review of log failures
- [ ] Log integrity verification
10.4 - Synchronization
- [ ] Time synchronization across systems
- [ ] NTP servers used
- [ ] Time drift monitoring
Requirement 11: Test security systems and processes regularly
11.1 - Wireless Network Testing
- [ ] Quarterly wireless network scans
- [ ] Wireless access point testing
- [ ] Unauthorized wireless device detection
- [ ] Wireless security testing tools
11.2 - Vulnerability Scanning
- [ ] Quarterly external vulnerability scans
- [ ] Quarterly internal vulnerability scans
- [ ] Annual penetration testing by ASV
- [ ] Scanning after significant changes
- [ ] Remediation of vulnerabilities
11.3 - Penetration Testing
- [ ] Annual internal penetration testing
- [ ] Annual external penetration testing
- [ ] Testing by qualified internal resources or third party
- [ ] Network and application layer testing
- [ ] Testing of segmentation and scope
- [ ] Remediation of identified vulnerabilities
11.4 - Intrusion Detection Systems
- [ ] IDS/IPS monitoring
- [ ] Intrusion detection logs reviewed daily
- [ ] Security event alerts
- [ ] Incident response procedures
11.5 - Incident Response Plan
- [ ] Incident response plan documented
- [ ] Incident response team identified
- [ ] Response procedures defined
- [ ] Notification procedures
- [ ] Post-incident review
11.6 - Regular Testing
- [ ] Regular testing of security systems
- [ ] Testing of security controls
- [ ] Testing of detection systems
- [ ] Testing of incident response
Requirement 12: Support information security with organizational policies and programs
12.1 - Security Policy
- [ ] Information security policy established
- [ ] Policy reviewed annually
- [ ] Policy communicated to all personnel
- [ ] Security awareness training
- [ ] Policy acknowledgment by personnel
12.2 - Risk Management
- [ ] Risk assessment process
- [ ] Risk assessment performed annually
- [ ] Risk management program
- [ ] Risk remediation tracking
12.3 - Security Incidents
- [ ] Incident response procedures
- [ ] Incident escalation procedures
- [ ] Incident notification procedures
- [ ] Incident documentation
- [ ] Post-incident analysis
12.4 - Security Awareness Training
- [ ] Security awareness program
- [ ] Training upon hire
- [ ] Regular training updates
- [ ] Security incident reporting training
12.5 - Third-Party Service Providers
- [ ] Due diligence for third parties
- [ ] Contracts with security requirements
- [ ] Monitoring of third-party compliance
- [ ] Annual verification of third-party compliance
Evidence Collection
Required Evidence Types
Policies and Procedures
- [ ] Information security policy
- [ ] Network security policy
- [ ] Access control policy
- [ ] Incident response plan
- [ ] Change management process
- [ ] Risk assessment procedures
Configuration Documentation
- [ ] Firewall configurations
- [ ] Router configurations
- [ ] System configurations
- [ ] Security control configurations
- [ ] Encryption configurations
Monitoring and Logging
- [ ] Firewall logs
- [ ] System logs
- [ ] Application logs
- [ ] Access logs
- [ ] Monitoring reports
Testing Evidence
- [ ] Vulnerability scan reports
- [ ] Penetration test reports
- [ ] Wireless scan reports
- [ ] Security control test results
- [ ] Remediation verification
Training Evidence
- [ ] Training materials
- [ ] Training attendance records
- [ ] Training assessments
- [ ] Security awareness programs
Audit Preparation
Pre-Audit Checklist
Documentation
- [ ] All policies reviewed and updated
- [ ] All procedures documented
- [ ] Evidence collected and organized
- [ ] Gap analysis completed
- [ ] Remediation of gaps
Internal Assessment
- [ ] Internal audit conducted
- [ ] Self-Assessment Questionnaire (SAQ) completed
- [ ] Remediation of findings
- [ ] Re-assessment after remediation
Staff Preparation
- [ ] Staff trained on PCI DSS requirements
- [ ] Interview preparation conducted
- [ ] Point of contact identified
- [ ] Staff awareness of audit
System Preparation
- [ ] Evidence collection systems verified
- [ ] Monitoring systems verified
- [ ] Documentation repositories organized
- [ ] Access controls reviewed
Scoping
System Scope Identification
In-Scope Systems
- [ ] Systems that process cardholder data
- [ ] Systems that transmit cardholder data
- [ ] Systems that store cardholder data
- [ ] Systems that provide security for above
Out-of-Scope Systems
- [ ] Systems that do not process cardholder data
- [ ] Systems with network segmentation
- [ ] Systems with no access to cardholder data
- [ ] Systems that meet exclusion criteria
Documentation Required
Network Diagram
- [ ] Current network diagram
- [ ] Data flow diagram
- [ ] System connections documented
- [ ] Out-of-scope systems identified
Data Flow
- [ ] Cardholder data entry points
- [ ] Cardholder data storage points
- [ ] Cardholder data transmission paths
- [ ] Cardholder data exit points
References
SOC 2 Controls Reference
Overview
SOC 2 (System and Organization Controls) Type 2 examination criteria for security, availability, processing integrity, confidentiality, and privacy.
Trust Services Criteria (TSC)
Common Criteria
1. CC1.1 - Control Environment Governance and risk management processes must be established
2. CC2.1 - Communication of Responsibilities Responsibilities must be communicated throughout the organization
3. CC3.1 - Risk Assessment Organization must identify and assess risks
4. CC4.1 - System Monitoring System must be monitored to detect security events
5. CC5.1 - System Control Controls must be designed and implemented
6. CC6.1 - System Maintenance System must be maintained to ensure continued operation
7. CC7.1 - System Data Data must be protected throughout its lifecycle
8. CC8.1 - Vendor Management Third-party relationships must be managed
Security Criteria (CC6)
CC6.1 - Logical and Physical Access Controls
CC6.1
- Logical access to system components must be restricted
- Access granted based on least privilege
- Access approved by authorized personnel
- Periodic access reviews
Implementation Checklist:
- [ ] User accounts created with unique identifiers
- [ ] Password complexity requirements enforced
- [ ] Multi-factor authentication implemented
- [ ] Access approval workflow in place
- [ ] Access granted based on job function
- [ ] Access review schedule established (quarterly)
- [ ] Immediate revocation on termination
Evidence:
- User access request forms
- Access approval documentation
- Access review reports
- MFA configuration documentation
CC6.2 - Logical Access Security
CC6.2
- Logical access security facilities must be managed
- Physical and environmental access protected
- Logical access monitors for suspicious activity
Implementation Checklist:
- [ ] Login failure monitoring configured
- [ ] Account lockout after failed attempts
- [ ] Session timeout implemented
- [ ] Concurrent login restrictions
- [ ] Geographic restrictions configured
- [ ] Suspicious activity alerts configured
Evidence:
- Security configuration files
- Monitoring logs
- Alert configuration documentation
CC6.3 - System Boundaries
CC6.3
- System boundaries must be identified
- Access control at boundaries
- Network segmentation implemented
Implementation Checklist:
- [ ] System architecture documented
- [ ] Network segments defined
- [ ] Firewall rules documented
- [ ] DMZ configured for public-facing services
- [ ] Internal network segmentation
- [ ] Access controls at each boundary
Evidence:
- Network diagrams
- Firewall rule sets
- System architecture documentation
- Boundary documentation
CC6.4 - Encryption
CC6.4
- Encryption implemented for data in transit
- Encryption implemented for data at rest
- Key management procedures
Implementation Checklist:
- [ ] TLS 1.2+ for all connections
- [ ] VPN for remote access
- [ ] Database encryption (AES-256)
- [ ] File system encryption
- [ ] Backup encryption
- [ ] Key rotation schedule
- [ ] Secure key storage
Evidence:
- SSL/TLS certificates
- Encryption configuration files
- Key management procedures
- Encryption policy documentation
CC6.5 - Monitoring of System Components
CC6.5
- System components monitored for security events
- Anomalous activity detection
- Security event correlation
Implementation Checklist:
- [ ] Security information and event management (SIEM)
- [ ] Log collection from all systems
- [ ] Real-time monitoring
- [ ] Alert thresholds configured
- [ ] Anomaly detection rules
- [ ] Incident correlation
Evidence:
- SIEM configuration
- Monitoring policies
- Alert rules
- Log retention policy
CC6.6 - Malware Protection
CC6.6
- Anti-malware software deployed
- Regular updates and scans
- Malware incident response
Implementation Checklist:
- [ ] Endpoint protection installed
- [ ] Server protection installed
- [ ] Definition update schedule
- [ ] Regular scan schedule
- [ ] Email filtering
- [ ] Web filtering
- [ ] Malware response procedures
Evidence:
- Antivirus software records
- Scan reports
- Update logs
- Incident response procedures
CC6.7 - Vulnerability Management
CC6.7
- Vulnerability scanning performed
- Patch management process
- Risk assessment and remediation
Implementation Checklist:
- [ ] Regular vulnerability scanning schedule
- [ ] Automated vulnerability scanning
- [ ] Patch management process
- [ ] Prioritization based on risk
- [ ] Remediation SLAs defined
- [ ] Vulnerability tracking
- [ ] Remediation verification
Evidence:
- Scan reports
- Patch records
- Vulnerability management documentation
- Risk assessment reports
CC6.8 - Network Security
CC6.8
- Network security controls implemented
- Network device hardening
- Network monitoring
Implementation Checklist:
- [ ] Network segmentation implemented
- [ ] Firewall configuration reviewed
- [ ] IDS/IPS deployed
- [ ] Network monitoring
- [ ] Wireless security
- [ ] VPN security
- [ ] Network device hardening
Evidence:
- Network configuration files
- Firewall rules
- IDS/IPS logs
- Network monitoring reports
CC6.9 - Incident Response
CC6.9
- Incident response plan established
- Incident response team identified
- Incident notification procedures
Implementation Checklist:
- [ ] Incident response plan documented
- [ ] Response team roles defined
- [ ] Incident classification process
- [ ] Escalation procedures
- [ ] Communication plan
- [ ] Post-incident reviews
- [ ] Response plan testing
Evidence:
- Incident response plan
- Team contact information
- Incident logs
- Post-incident review reports
Availability Criteria (A1)
A1.1 - Availability Monitoring
A1.1
- System availability monitored
- Performance metrics tracked
- Uptime targets defined
Implementation Checklist:
- [ ] Availability monitoring tools deployed
- [ ] Performance metrics collected
- [ ] Uptime targets defined (e.g., 99.9%)
- [ ] Alerting configured
- [ ] Dashboards for visibility
Evidence:
- Monitoring configuration
- Availability reports
- SLA documentation
- Performance metrics
A1.2 - Redundancy
A1.2
- Redundant components implemented
- Failover mechanisms
- Geographic distribution
Implementation Checklist:
- [ ] Load balancing configured
- [ ] Redundant servers
- [ ] Redundant databases
- [ ] Multiple network paths
- [ ] Geographic distribution (multi-region)
- [ ] Failover tested regularly
- [ ] Backup power supplies
Evidence:
- Architecture diagrams
- Load balancer configuration
- Failover test results
- Redundancy documentation
A1.3 - Data Backup and Recovery
A1.3
- Regular backups performed
- Backup encryption
- Recovery testing
Implementation Checklist:
- [ ] Backup schedule defined
- [ ] Backups encrypted
- [ ] Offsite backup storage
- [ ] Backup integrity verification
- [ ] Recovery procedures documented
- [ ] Regular recovery testing
- [ ] RTO and RPO defined
Evidence:
- Backup schedules
- Backup logs
- Recovery test reports
- RTO/RPO documentation
Processing Integrity Criteria (PI1)
PI1.1 - Data Processing Controls
PI1.1
- Input validation implemented
- Output validation
- Processing controls
Implementation Checklist:
- [ ] Input validation on all inputs
- [ ] Data type checking
- [ ] Business rule validation
- [ ] Output validation
- [ ] Processing logs
- [ ] Error handling
- [ ] Data reconciliation
Evidence:
- Validation code samples
- Business rule documentation
- Processing logs
- Error handling procedures
PI1.2 - Change Management
PI1.2
- Change management process
- Authorization for changes
- Testing before deployment
Implementation Checklist:
- [ ] Change management process documented
- [ ] Change request forms
- [ ] Change approval workflow
- [ ] Testing requirements
- [ ] Rollback procedures
- [ ] Post-change verification
Evidence:
- Change request logs
- Approval records
- Test results
- Deployment records
PI1.3 - Data Quality
PI1.3
- Data quality controls
- Data validation
- Data correction processes
Implementation Checklist:
- [ ] Data quality standards defined
- [ ] Data validation rules
- [ ] Data profiling
- [ ] Data correction procedures
- [ ] Data quality reports
- [ ] Regular data audits
Evidence:
- Data quality standards
- Validation rules
- Quality reports
- Audit results
Confidentiality Criteria (C1)
C1.1 - Confidentiality Controls
C1.1
- Confidential data identified
- Access controls implemented
- Encryption implemented
Implementation Checklist:
- [ ] Data classification performed
- [ ] Confidential data inventory
- [ ] Access controls on confidential data
- [ ] Encryption of confidential data
- [ ] Secure transmission
- [ ] Data masking for non-production
- [ ] NDA requirements
Evidence:
- Data classification policy
- Confidential data inventory
- Access control matrices
- Encryption documentation
Privacy Criteria (P1)
P1.1 - Privacy Principles
P1.1
- Privacy notice provided
- Consent obtained
- Data subject rights implemented
Implementation Checklist:
- [ ] Privacy notice published
- [ ] Consent mechanism implemented
- [ ] Right to access
- [ ] Right to rectification
- [ ] Right to erasure
- [ ] Right to portability
- [ ] Right to object
- [ ] Privacy impact assessments
Evidence:
- Privacy notice
- Consent records
- DSAR procedures
- PIA documentation
Evidence Collection
Required Evidence Types
Governance and Risk Management
- [ ] Risk assessment reports
- [ ] Risk register
- [ ] Governance documentation
- [ ] Policies and procedures
- [ ] Organizational charts
Security
- [ ] Security policies
- [ ] Access control records
- [ ] Encryption certificates
- [ ] Monitoring reports
- [ ] Incident reports
- [ ] Vulnerability scan reports
- [ ] Penetration test reports
Availability
- [ ] Availability reports
- [ ] Performance metrics
- [ ] Uptime calculations
- [ ] Incident reports
- [ ] Backup logs
- [ ] Recovery test reports
Processing Integrity
- [ ] Change management records
- [ ] Validation documentation
- [ ] Data quality reports
- [ ] Processing logs
Confidentiality
- [ ] Data classification documentation
- [ ] Confidentiality agreements
- [ ] Access request records
- [ ] Encryption documentation
Privacy
- [ ] Privacy notice
- [ ] Consent records
- [ ] DSAR logs
- [ ] PIA documentation
Audit Preparation
Pre-Audit Checklist
Documentation Review
- [ ] All policies reviewed and updated
- [ ] Procedures documented
- [ ] Evidence collected and organized
- [ ] Gap analysis completed
Internal Assessment
- [ ] Internal audit conducted
- [ ] Self-assessment completed
- [ ] Remediation of identified gaps
- [ ] Re-assessment after remediation
Staff Preparation
- [ ] Staff trained on SOC 2 requirements
- [ ] Roles and responsibilities communicated
- [ ] Interview preparation conducted
- [ ] Point of contact identified
System Preparation
- [ ] Evidence collection systems tested
- [ ] Monitoring systems verified
- [ ] Documentation repositories organized
- [ ] Access controls reviewed
Audit Response
During Audit
- [ ] Point of contact available
- [ ] Evidence provided promptly
- [ ] Questions answered clearly
- [ ] Additional information gathered as needed
Post-Audit
- [ ] Report reviewed
- [ ] Findings addressed
- [ ] Corrective action plan developed
- [ ] Timeline for remediation established