本文へ移動
cccskills
無料GitHub で公開

soc2-privacy-audit

Guides SOC 2 Type II Privacy Trust Services Criteria preparation and audit execution. Covers AICPA TSP Section 100 Privacy criteria P1-P8 including notice, choice/consent, collection, use/retention/disposal, access, disclosure, security, and quality. Includes evidence collection, control testing, and report review. Keywords: SOC 2, privacy criteria, TSP, AICPA, Type II, trust services.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md19.2 KB
  • assets/template.md6.3 KB
  • references/standards.md3.5 KB
  • references/workflows.md3.9 KB
  • scripts/process.py13.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

SOC 2 Type II Privacy Trust Services Criteria

Overview

SOC 2 (System and Organization Controls 2) is a reporting framework developed by the American Institute of Certified Public Accountants (AICPA) that evaluates an organization's controls relevant to the Trust Services Criteria (TSC). The Privacy category is one of five TSC categories (Security, Availability, Processing Integrity, Confidentiality, and Privacy) and specifically addresses how the organization collects, uses, retains, discloses, and disposes of personal information in conformity with commitments in its privacy notice and with criteria set forth by the AICPA.

A SOC 2 Type II report covers a specified examination period (typically 6-12 months) during which the auditor (a licensed CPA firm) tests whether controls were not only designed appropriately (Type I) but also operated effectively throughout the period. For the Privacy TSC, this means demonstrating sustained compliance with criteria P1.0 through P8.1 as defined in TSP Section 100 (2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy).

Sentinel Compliance Group undergoes annual SOC 2 Type II examinations including the Privacy TSC to provide contractual assurance to enterprise clients in financial services, healthcare technology, and SaaS sectors.

Privacy Trust Services Criteria (P1.0 — P8.1)

P1.0 — Notice

Criterion: The entity provides notice to data subjects about its privacy practices.

P1.1: The entity provides notice to data subjects about its privacy practices to meet the entity's objectives related to privacy. The notice is updated and communicated to data subjects in a timely manner for changes to the entity's privacy practices, including changes in the use of personal information.

Required Controls:

Control IDControl DescriptionEvidence Required
P1.1-01Privacy notice is published on all data collection points (website, mobile app, paper forms)Screenshots of privacy notices on all collection points, version history log
P1.1-02Privacy notice describes: types of personal information collected, purposes of collection and use, categories of third parties to whom data is disclosed, data subject rights, retention periodsPrivacy notice text, legal review records
P1.1-03Privacy notice is reviewed and updated at minimum annually and when processing changes occurAnnual review meeting minutes, change log, approval records
P1.1-04Material changes to privacy notice are communicated to affected data subjects via email or in-app notification prior to the change taking effectNotification records, email delivery logs, communication templates
P1.1-05Privacy notice is available in languages corresponding to the user baseTranslated notice versions, translation vendor records

P1.2 — Choice and Consent

Criterion: The entity communicates choices available regarding the collection, use, retention, disclosure, and disposal of personal information.

Required Controls:

Control IDControl DescriptionEvidence Required
P1.2-01Consent is obtained prior to or at the time of collection of personal informationConsent records, timestamp logs, consent mechanism screenshots
P1.2-02Data subjects are informed of consequences of refusing to provide personal informationPrivacy notice text, consent form text
P1.2-03Opt-out mechanisms are provided for marketing communications and non-essential processingOpt-out mechanism evidence, preference center screenshots
P1.2-04Explicit consent is obtained for sensitive personal information (health, financial, biometric, children's data)Explicit consent records, separate consent forms
P1.2-05Consent withdrawal mechanisms are available and accessibleWithdrawal mechanism documentation, processing records showing withdrawal honored

P2.1 — Collection

Criterion: Personal information is collected consistent with the entity's objectives related to privacy.

Required Controls:

Control IDControl DescriptionEvidence Required
P2.1-01Personal information collected is limited to that described in the privacy notice and necessary for identified purposesData inventory, data mapping, comparison against privacy notice
P2.1-02Data collection points are inventoried and reviewed quarterlyCollection point inventory, quarterly review records
P2.1-03Collection of personal information from third-party sources is documented and subject to due diligenceThird-party data source register, due diligence records
P2.1-04Implicit collection (cookies, device fingerprinting, tracking pixels) is disclosed in the privacy noticeCookie audit results, tracking technology inventory

P3.1 — Use, Retention, and Disposal

Criterion: Personal information is used, retained, and disposed of consistent with the entity's objectives.

Required Controls:

Control IDControl DescriptionEvidence Required
P3.1-01Personal information is used only for purposes identified in the privacy noticePurpose limitation audit results, processing activity register
P3.1-02Retention schedules are defined for each category of personal informationRetention schedule document, category-level retention periods
P3.1-03Automated deletion or anonymization processes execute upon retention period expiryDeletion job logs, anonymization records, automated process configuration
P3.1-04Disposal methods ensure personal information is rendered unrecoverable (NIST SP 800-88 Rev. 1 media sanitization)Disposal certificates, sanitization logs, destruction vendor contracts
P3.1-05Retention exceptions (litigation hold, regulatory requirement) are documented and time-boundLitigation hold register, exception approval records

P4.1 — Access

Criterion: The entity provides data subjects with access to their personal information for review and update.

Required Controls:

Control IDControl DescriptionEvidence Required
P4.1-01Data subject access request (DSAR) intake mechanism is available (web form, email, in-app)DSAR portal screenshots, process documentation
P4.1-02Identity verification is performed prior to fulfilling access requestsVerification procedure document, verification logs
P4.1-03Access requests are fulfilled within documented timeframes (30 days for GDPR, 45 days for CCPA)DSAR tracking log with timestamps, response time metrics
P4.1-04Data subjects can request corrections to inaccurate personal informationCorrection mechanism documentation, correction request logs
P4.1-05Denials of access requests are documented with reasons and communicated to the data subjectDenial records, denial notification templates

P5.1 — Disclosure to Third Parties

Criterion: Personal information is disclosed to third parties only for identified purposes and with consent.

Required Controls:

Control IDControl DescriptionEvidence Required
P5.1-01Third parties receiving personal information are identified and documentedThird-party recipient register, data flow diagrams
P5.1-02Data processing agreements or equivalent contracts are in place with all third parties receiving personal informationExecuted DPAs, contract inventory
P5.1-03Third-party disclosures are consistent with purposes described in the privacy noticeDisclosure audit results, purpose-to-recipient mapping
P5.1-04Third parties are assessed for adequate privacy and security controls prior to disclosureThird-party assessment records, vendor risk assessments
P5.1-05Unauthorized disclosures are reported and investigatedIncident response records, disclosure investigation logs

P6.1 — Security for Privacy

Criterion: Personal information is protected against unauthorized access, whether physical or logical.

This criterion is met through the Security TSC (CC1.0 through CC9.0, the Common Criteria). Privacy-specific security controls include:

Control IDControl DescriptionEvidence Required
P6.1-01Personal information is encrypted at rest using AES-256 or equivalentEncryption configuration evidence, key management documentation
P6.1-02Personal information is encrypted in transit using TLS 1.2 or higherTLS configuration scans, certificate inventory
P6.1-03Access to personal information is restricted using role-based access controls (RBAC)RBAC matrix, access review records, least privilege evidence
P6.1-04Access to personal information is logged and logs are retained per the audit log retention policyLog configuration evidence, sample log entries, retention policy
P6.1-05Privacy-impacting security incidents trigger the breach notification processIncident classification criteria, breach notification procedure

P7.1 — Quality

Criterion: Personal information is maintained accurately, completely, and timely for the purposes for which it is used.

Required Controls:

Control IDControl DescriptionEvidence Required
P7.1-01Data quality processes validate personal information at point of collectionValidation rules documentation, input validation configurations
P7.1-02Data subjects can request correction of inaccurate personal informationCorrection mechanism documentation, correction log
P7.1-03Personal information is reviewed for accuracy on a periodic basisData quality review schedule, review results

P8.1 — Monitoring and Enforcement

Criterion: The entity monitors compliance with its privacy policies and procedures and has procedures to address privacy-related inquiries, complaints, and disputes.

Required Controls:

Control IDControl DescriptionEvidence Required
P8.1-01Privacy compliance monitoring is conducted at minimum quarterlyCompliance monitoring reports, finding logs
P8.1-02A privacy complaint intake mechanism is available and publicizedComplaint mechanism screenshots, privacy notice reference
P8.1-03Privacy complaints are tracked, investigated, and resolved within documented timeframesComplaint tracking log, resolution records, SLA metrics
P8.1-04Employees are trained on privacy obligations at onboarding and annually thereafterTraining records, completion rates, training content
P8.1-05Disciplinary actions are taken for privacy policy violationsDisciplinary policy, anonymized violation records

Evidence Collection Framework

Documentation Categories

CategoryExamplesRetention Requirement
Policies and ProceduresPrivacy policy, DSAR procedure, breach notification procedureCurrent versions plus two prior versions
Operational EvidenceDSAR logs, consent records, deletion logs, training recordsThroughout examination period plus one year
Technical ConfigurationEncryption settings, RBAC matrices, log configurationsPoint-in-time screenshots plus change records
Governance RecordsCommittee meeting minutes, management review records, risk assessmentsThroughout examination period
Third-Party DocumentationDPAs, vendor assessments, sub-processor listsCurrent plus examination period

Evidence Collection Timeline

Month 1-2 (Pre-Examination Period):

  • Establish evidence repository with access controls
  • Create evidence request list mapped to each P-criterion
  • Assign evidence owners for each control
  • Conduct readiness assessment against all P-criteria

Months 3-8 (During Examination Period):

  • Collect operational evidence continuously (DSAR logs, deletion records, consent records)
  • Maintain running evidence calendar with monthly evidence capture checkpoints
  • Document all exceptions and compensating controls
  • Conduct mid-period self-assessment at month 5

Month 9-10 (Pre-Audit Preparation):

  • Complete evidence gap analysis against auditor's request list
  • Prepare evidence binders (physical or digital) organized by criterion
  • Pre-review all evidence for completeness and consistency
  • Prepare key personnel for auditor interviews

Sample Population Testing

SOC 2 auditors test controls using sampling methodologies based on AICPA AU-C Section 530:

Examination PeriodPopulation SizeMinimum Sample Size
6 months1-50All
6 months51-25025
6 months251+40
12 months1-50All
12 months51-25030
12 months251+45

For privacy controls, common populations tested include:

  • DSAR processing records (testing response timeliness and completeness)
  • Consent records (testing capture and withdrawal mechanisms)
  • Third-party DPAs (testing completeness and signature)
  • Data deletion records (testing timeliness per retention schedule)
  • Privacy complaint records (testing investigation and resolution)

Control Testing Procedures

Inquiry

The auditor interviews control owners and operators to understand how the control operates in practice:

  • Privacy Officer: Overall privacy program governance, policy management, risk assessment
  • IT Security: Encryption, access controls, logging, incident response
  • Legal: DPA management, privacy notice updates, regulatory monitoring
  • Customer Support: DSAR handling, complaint management, consent processes
  • HR: Employee training, disciplinary procedures, onboarding privacy requirements

Observation

The auditor observes controls in operation:

  • Walkthrough of DSAR intake and fulfillment process
  • Demonstration of consent management platform
  • Demonstration of data deletion/anonymization processes
  • Walkthrough of privacy complaint handling
  • Demonstration of access control review process

Inspection

The auditor examines evidence artifacts:

  • Privacy notice versions and change logs
  • DSAR tracking spreadsheets or ticketing system records
  • Consent database records with timestamps
  • Data deletion job execution logs
  • Third-party DPA repository
  • Privacy training completion records
  • Privacy committee meeting minutes
  • Privacy risk assessment documentation

Reperformance

The auditor independently reperforms a control to verify its effectiveness:

  • Submit a test DSAR and verify the response process
  • Verify that retention period expiry triggers automated deletion
  • Verify that access controls prevent unauthorized access to personal information
  • Verify that privacy notice accurately reflects current processing activities

Report Review

Management Assertion

The service organization's management provides a written assertion that:

  1. The system description is fairly presented
  2. Controls were suitably designed (Type I and II)
  3. Controls operated effectively throughout the examination period (Type II)

Auditor's Opinion

The auditor's report contains:

  • Unqualified (clean) opinion: Controls were suitably designed and operated effectively
  • Qualified opinion: One or more exceptions noted but controls are generally effective
  • Adverse opinion: Significant deficiencies exist in control design or operation
  • Disclaimer of opinion: Sufficient evidence could not be obtained

Exception Handling

When the auditor identifies exceptions during testing:

  1. Deviation: A single instance where a control did not operate as designed (e.g., one DSAR exceeded the 30-day response window). The auditor documents the deviation and evaluates whether it represents a systematic failure.
  2. Exception: A pattern of deviations or a significant individual deviation. Exceptions are described in the report with management's response.
  3. Modified Opinion Threshold: Typically 3+ exceptions in a single control or exceptions across multiple controls in the same criterion may result in a qualified opinion for that criterion.

User Entity Considerations (Complementary User Entity Controls — CUECs)

The SOC 2 report identifies controls that user entities (customers) must implement for the system of controls to be effective. Privacy-related CUECs commonly include:

  • User entities are responsible for providing accurate personal information to the service organization
  • User entities are responsible for reviewing and approving data processing purposes
  • User entities are responsible for obtaining consent from their own data subjects before providing personal information to the service organization
  • User entities are responsible for notifying the service organization of DSARs that require the service organization's assistance

SOC 2 Privacy vs. GDPR Comparison

AspectSOC 2 Privacy TSCGDPR
Regulatory natureVoluntary attestationMandatory legislation
ScopeService organization's systemAll personal data processing
EnforcerCPA auditor (AICPA standards)Supervisory authorities
Consequence of failureQualified/adverse reportFines up to EUR 20M or 4% global turnover
CoverageEight criteria (P1-P8)99 articles, 173 recitals
Lawful basisNot addressed (consent-focused)Six lawful bases under Art. 6
Cross-border transfersNot specifically addressedChapters V (Art. 44-49)
Data subject rightsAccess and correction (P4)Eight rights (Art. 15-22)
Breach notificationCovered under Security TSC72-hour DPA notification, data subject notification

Sentinel Compliance Group SOC 2 Privacy Implementation

Sentinel Compliance Group maintains an annual SOC 2 Type II examination (12-month period, January 1 — December 31) including the Privacy TSC alongside Security and Confidentiality:

  • Examination Period: January 1, 2025 — December 31, 2025
  • Auditor: Deloitte & Touche LLP
  • Criteria Included: Security (CC), Confidentiality (C), Privacy (P)
  • Controls Tested: 142 total controls, 38 Privacy-specific
  • Result: Unqualified opinion with zero exceptions for Privacy criteria
  • Key Metrics During Period: 847 DSARs processed (average response time: 12 days), 0 privacy complaints unresolved beyond 30 days, 100% employee privacy training completion, 4 privacy notice updates published
  • Bridge Letter: Issued quarterly to address the gap between examination period end and report issuance (typically 8-12 weeks after period end)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する