[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMC4Y9DQ3C1VVMJ7XSMM6S":3,"skill-same:01M7AMC4Y9DQ3C1VVMJ7XSMM6S":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AMC4Y9DQ3C1VVMJ7XSMM6S","soc2-compliance",null,"Use when working on SOC2 Type 1 or Type 2 readiness, TSC (Trust Services Criteria) gap analysis, policy development, or mapping controls to NIST 800-53. Covers the 5 TSC categories, minimum policy set, evidence collection, and audit preparation. Trigger on any mention of SOC2, SOC 2, Trust Services Criteria, AICPA, Type 1, Type 2, or auditor readiness.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcompliance-frameworks\u002Fskills\u002Fsoc2-compliance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: soc2-compliance\ndescription: Use when working on SOC2 Type 1 or Type 2 readiness, TSC (Trust Services Criteria) gap analysis, policy development, or mapping controls to NIST 800-53. Covers the 5 TSC categories, minimum policy set, evidence collection, and audit preparation. Trigger on any mention of SOC2, SOC 2, Trust Services Criteria, AICPA, Type 1, Type 2, or auditor readiness.\n---\n\n# SOC 2 Compliance — Trust Services Criteria\n\n## What This Skill Does\n\nThis skill guides you through SOC 2 Type 1 and Type 2 readiness: understanding the Trust Services Criteria (TSC), identifying the minimum required policy set, collecting evidence for auditors, and mapping SOC 2 controls to NIST 800-53. It covers common gaps in SaaS and cloud environments and provides actionable audit preparation checklists.\n\n---\n\n## Framework Overview\n\nSOC 2 is an AICPA (American Institute of Certified Public Accountants) framework for reporting on the internal controls of service organizations. It is NOT a certification — it is an audit-based attestation report.\n\n**Types of SOC 2 reports:**\n- **Type 1:** Point-in-time assessment. The auditor opines that controls are suitably designed as of a specific date. Faster (2-4 months); lower cost; limited assurance.\n- **Type 2:** Period-based assessment (typically 6-12 months). The auditor opines that controls are suitably designed AND operated effectively over the audit period. Higher assurance; required by most enterprise customers and regulated industries.\n\n**Who needs SOC 2:**\n- SaaS companies that handle customer data\n- Cloud infrastructure and managed service providers\n- Any B2B technology company responding to enterprise security questionnaires\n- Companies handling healthcare, financial, or government data (often required)\n\n**The report is:**\n- Issued by a licensed CPA firm (not a consultant or certifying body)\n- Scoped to specific Trust Service Categories elected by management\n- Shared under NDA with customers and prospects\n\n---\n\n## The Five Trust Service Categories (TSC)\n\n### Security (CC — Common Criteria) — ALWAYS REQUIRED\nThe foundational category. Every SOC 2 report must include Security. The Common Criteria (CC) covers logical and physical access controls, change management, risk management, and monitoring.\n\nSecurity is organized into CC1–CC9 subcriteria:\n\n**CC1: Control Environment**\n- Commitment to integrity and ethical values (tone at the top)\n- Board\u002Fmanagement oversight of security program\n- Organizational structure and reporting lines\n\n**CC2: Communication and Information**\n- Internal communication of security responsibilities\n- External communication to relevant parties about security obligations\n\n**CC3: Risk Assessment**\n- Identify and analyze risks to achieving security objectives\n- Fraud risk assessment\n- Changes to systems\u002Fprocesses that create new risks\n\n**CC4: Monitoring Activities**\n- Ongoing and separate evaluations of controls\n- Deficiency identification and remediation\n\n**CC5: Control Activities (Policies)**\n- Selection and development of controls\n- Technology controls (general IT controls)\n- Policy deployment and enforcement\n\n\n**CC6: Logical and Physical Access Controls**\n- User access provisioning, de-provisioning, and reviews\n- Principle of least privilege\n- Multi-factor authentication\n- Physical facility access controls\n- Encryption of data at rest and in transit\n- Network security and segmentation\n\n**CC7: System Operations**\n- Detection and monitoring of new vulnerabilities\n- System monitoring and anomaly detection\n- Incident identification and response\n- Change management and infrastructure reliability\n\n**CC8: Change Management**\n- Controlled change process (development → testing → production)\n- Software development lifecycle controls\n- Infrastructure change controls\n- Emergency change procedures\n\n**CC9: Risk Mitigation**\n- Risk treatment and mitigation strategies\n- Vendor\u002Fthird-party risk management (subservice organizations)\n- Business disruption risk\n\n### Availability (A) — Optional\nThe system is available for operation and use as committed or agreed.\n\nCovers: uptime SLA commitments, redundancy and failover, backup and recovery, capacity management, incident response for availability events, DR testing.\n\n**Include if:** You have SLA commitments to customers; customers depend on uptime for their operations; you are a SaaS platform where downtime = customer revenue loss.\n\n### Processing Integrity (PI) — Optional\nSystem processing is complete, accurate, timely, and authorized.\n\nCovers: Input validation, processing controls, error handling, output accuracy, transactional completeness, anomaly detection in processing.\n\n**Include if:** You process financial transactions, payroll, healthcare data processing, or any workflow where processing errors have material consequences.\n\n### Confidentiality (C) — Optional\nInformation designated as confidential is protected as committed or agreed.\n\nCovers: Data classification, confidentiality agreements (NDAs), encryption of confidential data, access restrictions to confidential information, secure disposal.\n\n**Include if:** You handle customer-designated confidential data, IP, trade secrets, or regulated data categories where confidentiality is a contractual or regulatory obligation.\n\n### Privacy (P) — Optional\nPersonal information is collected, used, retained, disclosed, and disposed of in conformity with the entity's privacy notice and GAPP.\n\nCovers: Notice and consent, data collection limitation, use\u002Fretention\u002Fdisposal, access to personal data, disclosure to third parties, security of personal data.\n\n**Include if:** You collect or process personal information and have made privacy commitments (GDPR alignment, CCPA compliance, etc.).\n\n\n---\n\n## Minimum Policy Set for SOC 2 Type 2\n\nThe following policies are required to satisfy the Common Criteria and any additional TSC categories elected. These come from the SOC2-Type2 Minimum Policy Set documentation.\n\n### 1. Information Security Policy\nThe overarching policy defining the organization's approach to information security.\n- Roles and responsibilities for information security\n- Acceptable use rules for systems and data\n- Consequences for policy violations\n- Annual review and update process\n- Executive sign-off and communication to all personnel\n\n### 2. Access Control Policy\nDefines who has access to what information and the procedures for granting and revoking access.\n- User provisioning and de-provisioning process\n- Principle of least privilege requirements\n- Access review frequency (quarterly for privileged; semi-annual for standard)\n- Segregation of duties requirements\n- Privileged access management rules\n- Remote access controls\n\n### 3. Data Encryption Policy\nOutlines how and when data is encrypted, both at rest and in transit.\n- Encryption standards (AES-256 at rest; TLS 1.2+ in transit)\n- Key management and rotation schedule\n- Encryption requirements for portable devices and storage media\n- Certificate management procedures\n\n### 4. Incident Response Policy\nDetails how to respond to a security incident.\n- Incident classification and severity definitions\n- Roles and responsibilities (IR team)\n- Incident detection and reporting procedures\n- Containment, eradication, and recovery steps\n- Communication plan (internal; customer notification)\n- Post-incident review and lessons learned\n- Retention of incident records\n\n### 5. Disaster Recovery and Business Continuity Plan (BCP\u002FDRP)\nOutlines how the organization recovers from a disaster or significant event.\n- Business impact analysis (BIA) with RTO\u002FRPO for critical systems\n- Recovery procedures per system\u002Fservice\n- Backup strategy and verification\n- DR testing schedule (annual minimum for Type 2)\n- Communication and escalation tree\n\n### 6. Change Management Policy\nControls how changes to the IT environment are requested, approved, tested, and deployed.\n- Change request and approval workflow\n- Separation of duties: developers cannot deploy to production unilaterally\n- Testing requirements before promotion to production\n- Emergency change procedures\n- Rollback procedures\n- Change log maintenance\n\n### 7. Risk Assessment Policy\nOutlines how risks are identified, evaluated, and mitigated.\n- Risk assessment methodology and frequency (annual minimum)\n- Risk scoring criteria (likelihood × impact)\n- Risk acceptance criteria\n- Risk treatment options (accept, mitigate, transfer, avoid)\n- Risk register ownership and maintenance\n\n### 8. Vendor Management Policy\nGoverns evaluation and monitoring of third-party vendors.\n- Vendor risk tiering (critical, significant, standard)\n- Security due diligence requirements by tier\n- Contract requirements (security obligations, audit rights, breach notification)\n- Annual review of critical vendors\n- Subservice organization monitoring (for SOC 2 carve-out or inclusive reports)\n\n\n### 9. Data Backup Policy\nOutlines how and when data is backed up, and how it can be restored.\n- Backup frequency per data classification\u002Fcriticality\n- Backup storage location (offsite\u002Fcloud)\n- Encryption of backups\n- Restoration testing frequency (quarterly recommended)\n- Retention periods\n\n### 10. Network Security Policy\nDocuments network protection controls.\n- Firewall and network segmentation requirements\n- Intrusion detection\u002Fprevention systems\n- Wireless network controls\n- Network monitoring and alerting\n- Remote access VPN requirements\n\n### 11. Data Retention and Disposal Policy\nGoverns how long data is kept and how it is securely disposed of.\n- Retention periods by data category\n- Legal hold procedures\n- Secure disposal methods (shredding, NIST 800-88 media sanitization)\n- Records of destruction\n\n### 12. Privacy Policy (if Privacy TSC selected)\nCovers collection, use, retention, disclosure, and disposal of personal information.\n- Data subject rights (access, deletion, correction)\n- Cookie and tracking disclosures\n- Third-party sharing disclosures\n- Data breach notification commitments\n\n---\n\n## Control Mapping: SOC 2 Common Criteria to NIST 800-53\n\nSOC 2 auditors increasingly expect organizations to be able to map their controls to established frameworks. The mapping from TSC to NIST 800-53 is published by the AICPA.\n\n| SOC 2 Criteria | NIST 800-53 Control Families |\n|----------------|------------------------------|\n| CC1 (Control Environment) | PM (Program Management), AT (Awareness & Training) |\n| CC2 (Communication) | PL (Planning), PM |\n| CC3 (Risk Assessment) | RA (Risk Assessment), PM |\n| CC4 (Monitoring) | CA (Assessment), AU (Audit) |\n| CC5 (Control Activities) | PL, SA (System Acquisition), PM |\n| CC6.1 (Logical Access — Identification) | IA (Identification & Authentication) |\n| CC6.2 (Logical Access — Provisioning) | AC (Access Control) |\n| CC6.3 (Role-Based Access) | AC |\n| CC6.6 (External Threats — Boundary) | SC (System & Comms Protection), SI |\n| CC6.7 (Encryption) | SC, MP (Media Protection) |\n| CC6.8 (Malware Protection) | SI |\n| CC7.1 (Vulnerability Management) | RA, SI, CA |\n| CC7.2 (Monitoring) | AU, SI, IR |\n| CC7.3–CC7.5 (Incident Response) | IR (Incident Response) |\n| CC8 (Change Management) | CM (Configuration Management), SA |\n| CC9 (Risk Mitigation \u002F Vendors) | SA-9, PM |\n| A1 (Availability) | CP (Contingency Planning), SC |\n| PI1 (Processing Integrity) | SI, AU |\n| C1 (Confidentiality) | AC, SC, MP |\n| P1–P8 (Privacy) | PT (PII Processing) |\n\n\n---\n\n## Evidence Collection for Auditors\n\nSOC 2 auditors (for Type 2) will request evidence of control operation over the entire audit period. Evidence must be dated to show it occurred during the period under review.\n\n### Access Control Evidence\n- [ ] User access list with roles — point in time + evidence of periodic review\n- [ ] Terminated employee access revocation records (show prompt deprovisioning)\n- [ ] MFA enrollment confirmation for all users\n- [ ] Privileged access request and approval tickets\n- [ ] Access review documentation (reviewer sign-off, date, actions taken)\n- [ ] New employee access provisioning records\n\n### Change Management Evidence\n- [ ] Git commit history and pull request approvals showing peer review\n- [ ] Deployment records (who deployed what, when, from which environment)\n- [ ] Change tickets with approvals and test results\n- [ ] Separation of duties evidence: developers cannot merge their own PRs\n- [ ] Production deployment approvals (separate from development team)\n\n### Security Monitoring Evidence\n- [ ] Vulnerability scan reports with dates (quarterly minimum)\n- [ ] Penetration test report (annual)\n- [ ] SIEM\u002Flog monitoring screenshots showing active alerting\n- [ ] Alert investigation records\n- [ ] Patch deployment records aligned to vulnerability reports\n\n### Vendor Management Evidence\n- [ ] Vendor inventory with tier classifications\n- [ ] SOC 2 reports or security questionnaire responses from critical vendors\n- [ ] Vendor contracts with security clauses\n- [ ] Annual review documentation\n\n### Incident Response Evidence\n- [ ] Incident log (even if no major incidents — log minor events)\n- [ ] Tabletop exercise record (scenario, attendees, findings, actions)\n- [ ] IRP document with version history\n- [ ] For any incidents during period: incident ticket, timeline, resolution, notifications\n\n### Business Continuity \u002F DR Evidence\n- [ ] BCP\u002FDRP document with RTO\u002FRPO definitions\n- [ ] DR test results (restore from backup, failover test)\n- [ ] Backup job success logs\n- [ ] Restoration test records (did the backup actually restore?)\n\n---\n\n## Common SOC 2 Gaps in SaaS\u002FCloud Environments\n\n### No Formal Access Review Process (CC6.2, CC6.3)\n**Gap:** User access is provisioned but never reviewed; departed employees may retain access.\n**Fix:** Implement quarterly access reviews in Jira, Vanta, Drata, or a spreadsheet. Document who reviewed, when, what changes were made. Automate deprovisioning via HRIS-SSO integration.\n\n### Developers Can Deploy to Production (CC8)\n**Gap:** Engineers have direct production deployment access; no separation of duties.\n**Fix:** Require pull request approval from a second engineer. Restrict production deployments to CI\u002FCD pipeline with approvals. Even for small teams, document the control: \"Engineer A writes code; Engineer B reviews and approves before merge; CI\u002FCD deploys.\"\n\n### No Documented Incident Response Testing (CC7.3–CC7.5)\n**Gap:** IRP exists on paper but has never been tested.\n**Fix:** Conduct a tabletop exercise (even 1 hour with 3 people). Document scenario, participants, walk-through, and action items. Auditors want evidence of testing, not just the plan.\n\n### Monitoring Without Investigation Records (CC7.2)\n**Gap:** SIEM generates alerts but no records of alert investigation.\n**Fix:** Create a simple alert log: date, alert type, who investigated, finding, action taken. Even \"investigated, false positive, no action required\" counts.\n\n### Vendor SOC Reports Not Collected (CC9.2)\n**Gap:** Critical cloud providers (AWS, Stripe, Salesforce) not included in vendor management program.\n**Fix:** Download SOC 2 reports for critical subservice organizations annually (most are available via their trust portals). Document where you reviewed them and what you found.\n\n### Backup Restoration Not Tested (A1, if Availability in scope)\n**Gap:** Backups run but restoration is never verified.\n**Fix:** Perform a documented restoration test at least annually. Restore to a non-production environment and confirm data integrity. Record date, what was restored, results.\n\n---\n\n## Readiness Assessment Checklist\n\nBefore engaging a SOC 2 auditor, verify:\n\n**Governance**\n- [ ] Information Security Policy approved and distributed\n- [ ] All minimum policies exist (12 policies above)\n- [ ] Risk assessment completed in last 12 months\n- [ ] Security awareness training completed by all personnel\n\n**Access Controls**\n- [ ] MFA enabled for all systems in scope\n- [ ] Privileged access documented and reviewed\n- [ ] Terminated employees removed from all systems (documented process)\n- [ ] Access provisioning follows documented approval process\n\n**Change Management**\n- [ ] Code review\u002FPR approval process enforced in version control\n- [ ] CI\u002FCD pipeline has approval gates before production\n- [ ] Change log maintained for infrastructure changes\n\n**Monitoring**\n- [ ] Security alerts configured and investigated\n- [ ] Vulnerability scans running and documented\n- [ ] Log retention meets audit period (12 months)\n\n**Availability (if in scope)**\n- [ ] Backup policy defined and implemented\n- [ ] Restoration test completed and documented\n- [ ] DR\u002FBCP plan tested in last 12 months\n\n**Vendors**\n- [ ] Critical vendor list maintained\n- [ ] SOC 2 reports collected for critical SaaS\u002Fcloud vendors\n\n","# SOC 2 Compliance — Trust Services Criteria\n\n## What This Skill Does\n\nThis skill guides you through SOC 2 Type 1 and Type 2 readiness: understanding the Trust Services Criteria (TSC), identifying the minimum required policy set, collecting evidence for auditors, and mapping SOC 2 controls to NIST 800-53. It covers common gaps in SaaS and cloud environments and provides actionable audit preparation checklists.\n\n---\n\n## Framework Overview\n\nSOC 2 is an AICPA (American Institute of Certified Public Accountants) framework for reporting on the internal controls of service organizations. It is NOT a certification — it is an audit-based attestation report.\n\n**Types of SOC 2 reports:**\n- **Type 1:** Point-in-time assessment. The auditor opines that controls are suitably designed as of a specific date. Faster (2-4 months); lower cost; limited assurance.\n- **Type 2:** Period-based assessment (typically 6-12 months). The auditor opines that controls are suitably designed AND operated effectively over the audit period. Higher assurance; required by most enterprise customers and regulated industries.\n\n**Who needs SOC 2:**\n- SaaS companies that handle customer data\n- Cloud infrastructure and managed service providers\n- Any B2B technology company responding to enterprise security questionnaires\n- Companies handling healthcare, financial, or government data (often required)\n\n**The report is:**\n- Issued by a licensed CPA firm (not a consultant or certifying body)\n- Scoped to specific Trust Service Categories elected by management\n- Shared under NDA with customers and prospects\n\n---\n\n## The Five Trust Service Categories (TSC)\n\n### Security (CC — Common Criteria) — ALWAYS REQUIRED\nThe foundational category. Every SOC 2 report must include Security. The Common Criteria (CC) covers logical and physical access controls, change management, risk management, and monitoring.\n\nSecurity is organized into CC1–CC9 subcriteria:\n\n**CC1: Control Environment**\n- Commitment to integrity and ethical values (tone at the top)\n- Board\u002Fmanagement oversight of security program\n- Organizational structure and reporting lines\n\n**CC2: Communication and Information**\n- Internal communication of security responsibilities\n- External communication to relevant parties about security obligations\n\n**CC3: Risk Assessment**\n- Identify and analyze risks to achieving security objectives\n- Fraud risk assessment\n- Changes to systems\u002Fprocesses that create new risks\n\n**CC4: Monitoring Activities**\n- Ongoing and separate evaluations of controls\n- Deficiency identification and remediation\n\n**CC5: Control Activities (Policies)**\n- Selection and development of controls\n- Technology controls (general IT controls)\n- Policy deployment and enforcement\n\n\n**CC6: Logical and Physical Access Controls**\n- User access provisioning, de-provisioning, and reviews\n- Principle of least privilege\n- Multi-factor authentication\n- Physical facility access controls\n- Encryption of data at rest and in transit\n- Network security and segmentation\n\n**CC7: System Operations**\n- Detection and monitoring of new vulnerabilities\n- System monitoring and anomaly detection\n- Incident identification and response\n- Change management and infrastructure reliability\n\n**CC8: Change Management**\n- Controlled change process (development → testing → production)\n- Software development lifecycle controls\n- Infrastructure change controls\n- Emergency change procedures\n\n**CC9: Risk Mitigation**\n- Risk treatment and mitigation strategies\n- Vendor\u002Fthird-party risk management (subservice organizations)\n- Business disruption risk\n\n### Availability (A) — Optional\nThe system is available for operation and use as committed or agreed.\n\nCovers: uptime SLA commitments, redundancy and failover, backup and recovery, capacity management, incident response for availability events, DR testing.\n\n**Include if:** You have SLA commitments to customers; customers depend on uptime for their operations; you are a SaaS platform where downtime = customer revenue loss.\n\n### Processing Integrity (PI) — Optional\nSystem processing is complete, accurate, timely, and authorized.\n\nCovers: Input validation, processing controls, error handling, output accuracy, transactional completeness, anomaly detection in processing.\n\n**Include if:** You process financial transactions, payroll, healthcare data processing, or any workflow where processing errors have material consequences.\n\n### Confidentiality (C) — Optional\nInformation designated as confidential is protected as committed or agreed.\n\nCovers: Data classification, confidentiality agreements (NDAs), encryption of confidential data, access restrictions to confidential information, secure disposal.\n\n**Include if:** You handle customer-designated confidential data, IP, trade secrets, or regulated data categories where confidentiality is a contractual or regulatory obligation.\n\n### Privacy (P) — Optional\nPersonal information is collected, used, retained, disclosed, and disposed of in conformity with the entity's privacy notice and GAPP.\n\nCovers: Notice and consent, data collection limitation, use\u002Fretention\u002Fdisposal, access to personal data, disclosure to third parties, security of personal data.\n\n**Include if:** You collect or process personal information and have made privacy commitments (GDPR alignment, CCPA compliance, etc.).\n\n\n---\n\n## Minimum Policy Set for SOC 2 Type 2\n\nThe following policies are required to satisfy the Common Criteria and any additional TSC categories elected. These come from the SOC2-Type2 Minimum Policy Set documentation.\n\n### 1. Information Security Policy\nThe overarching policy defining the organization's approach to information security.\n- Roles and responsibilities for information security\n- Acceptable use rules for systems and data\n- Consequences for policy violations\n- Annual review and update process\n- Executive sign-off and communication to all personnel\n\n### 2. Access Control Policy\nDefines who has access to what information and the procedures for granting and revoking access.\n- User provisioning and de-provisioning process\n- Principle of least privilege requirements\n- Access review frequency (quarterly for privileged; semi-annual for standard)\n- Segregation of duties requirements\n- Privileged access management rules\n- Remote access controls\n\n### 3. Data Encryption Policy\nOutlines how and when data is encrypted, both at rest and in transit.\n- Encryption standards (AES-256 at rest; TLS 1.2+ in transit)\n- Key management and rotation schedule\n- Encryption requirements for portable devices and storage media\n- Certificate management procedures\n\n### 4. Incident Response Policy\nDetails how to respond to a security incident.\n- Incident classification and severity definitions\n- Roles and responsibilities (IR team)\n- Incident detection and reporting procedures\n- Containment, eradication, and recovery steps\n- Communication plan (internal; customer notification)\n- Post-incident review and lessons learned\n- Retention of incident records\n\n### 5. Disaster Recovery and Business Continuity Plan (BCP\u002FDRP)\nOutlines how the organization recovers from a disaster or significant event.\n- Business impact analysis (BIA) with RTO\u002FRPO for critical systems\n- Recovery procedures per system\u002Fservice\n- Backup strategy and verification\n- DR testing schedule (annual minimum for Type 2)\n- Communication and escalation tree\n\n### 6. Change Management Policy\nControls how changes to the IT environment are requested, approved, tested, and deployed.\n- Change request and approval workflow\n- Separation of duties: developers cannot deploy to production unilaterally\n- Testing requirements before promotion to production\n- Emergency change procedures\n- Rollback procedures\n- Change log maintenance\n\n### 7. Risk Assessment Policy\nOutlines how risks are identified, evaluated, and mitigated.\n- Risk assessment methodology and frequency (annual minimum)\n- Risk scoring criteria (likelihood × impact)\n- Risk acceptance criteria\n- Risk treatment options (accept, mitigate, transfer, avoid)\n- Risk register ownership and maintenance\n\n### 8. Vendor Management Policy\nGoverns evaluation and monitoring of third-party vendors.\n- Vendor risk tiering (critical, significant, standard)\n- Security due diligence requirements by tier\n- Contract requirements (security obligations, audit rights, breach notification)\n- Annual review of critical vendors\n- Subservice organization monitoring (for SOC 2 carve-out or inclusive reports)\n\n\n### 9. Data Backup Policy\nOutlines how and when data is backed up, and how it can be restored.\n- Backup frequency per data classification\u002Fcriticality\n- Backup storage location (offsite\u002Fcloud)\n- Encryption of backups\n- Restoration testing frequency (quarterly recommended)\n- Retention periods\n\n### 10. Network Security Policy\nDocuments network protection controls.\n- Firewall and network segmentation requirements\n- Intrusion detection\u002Fprevention systems\n- Wireless network controls\n- Network monitoring and alerting\n- Remote access VPN requirements\n\n### 11. Data Retention and Disposal Policy\nGoverns how long data is kept and how it is securely disposed of.\n- Retention periods by data category\n- Legal hold procedures\n- Secure disposal methods (shredding, NIST 800-88 media sanitization)\n- Records of destruction\n\n### 12. Privacy Policy (if Privacy TSC selected)\nCovers collection, use, retention, disclosure, and disposal of personal information.\n- Data subject rights (access, deletion, correction)\n- Cookie and tracking disclosures\n- Third-party sharing disclosures\n- Data breach notification commitments\n\n---\n\n## Control Mapping: SOC 2 Common Criteria to NIST 800-53\n\nSOC 2 auditors increasingly expect organizations to be able to map their controls to established frameworks. The mapping from TSC to NIST 800-53 is published by the AICPA.\n\n| SOC 2 Criteria | NIST 800-53 Control Families |\n|----------------|------------------------------|\n| CC1 (Control Environment) | PM (Program Management), AT (Awareness & Training) |\n| CC2 (Communication) | PL (Planning), PM |\n| CC3 (Risk Assessment) | RA (Risk Assessment), PM |\n| CC4 (Monitoring) | CA (Assessment), AU (Audit) |\n| CC5 (Control Activities) | PL, SA (System Acquisition), PM |\n| CC6.1 (Logical Access — Identification) | IA (Identification & Authentication) |\n| CC6.2 (Logical Access — Provisioning) | AC (Access Control) |\n| CC6.3 (Role-Based Access) | AC |\n| CC6.6 (External Threats — Boundary) | SC (System & Comms Protection), SI |\n| CC6.7 (Encryption) | SC, MP (Media Protection) |\n| CC6.8 (Malware Protection) | SI |\n| CC7.1 (Vulnerability Management) | RA, SI, CA |\n| CC7.2 (Monitoring) | AU, SI, IR |\n| CC7.3–CC7.5 (Incident Response) | IR (Incident Response) |\n| CC8 (Change Management) | CM (Configuration Management), SA |\n| CC9 (Risk Mitigation \u002F Vendors) | SA-9, PM |\n| A1 (Availability) | CP (Contingency Planning), SC |\n| PI1 (Processing Integrity) | SI, AU |\n| C1 (Confidentiality) | AC, SC, MP |\n| P1–P8 (Privacy) | PT (PII Processing) |\n\n\n---\n\n## Evidence Collection for Auditors\n\nSOC 2 auditors (for Type 2) will request evidence of control operation over the entire audit period. Evidence must be dated to show it occurred during the period under review.\n\n### Access Control Evidence\n- [ ] User access list with roles — point in time + evidence of periodic review\n- [ ] Terminated employee access revocation records (show prompt deprovisioning)\n- [ ] MFA enrollment confirmation for all users\n- [ ] Privileged access request and approval tickets\n- [ ] Access review documentation (reviewer sign-off, date, actions taken)\n- [ ] New employee access provisioning records\n\n### Change Management Evidence\n- [ ] Git commit history and pull request approvals showing peer review\n- [ ] Deployment records (who deployed what, when, from which environment)\n- [ ] Change tickets with approvals and test results\n- [ ] Separation of duties evidence: developers cannot merge their own PRs\n- [ ] Production deployment approvals (separate from development team)\n\n### Security Monitoring Evidence\n- [ ] Vulnerability scan reports with dates (quarterly minimum)\n- [ ] Penetration test report (annual)\n- [ ] SIEM\u002Flog monitoring screenshots showing active alerting\n- [ ] Alert investigation records\n- [ ] Patch deployment records aligned to vulnerability reports\n\n### Vendor Management Evidence\n- [ ] Vendor inventory with tier classifications\n- [ ] SOC 2 reports or security questionnaire responses from critical vendors\n- [ ] Vendor contracts with security clauses\n- [ ] Annual review documentation\n\n### Incident Response Evidence\n- [ ] Incident log (even if no major incidents — log minor events)\n- [ ] Tabletop exercise record (scenario, attendees, findings, actions)\n- [ ] IRP document with version history\n- [ ] For any incidents during period: incident ticket, timeline, resolution, notifications\n\n### Business Continuity \u002F DR Evidence\n- [ ] BCP\u002FDRP document with RTO\u002FRPO definitions\n- [ ] DR test results (restore from backup, failover test)\n- [ ] Backup job success logs\n- [ ] Restoration test records (did the backup actually restore?)\n\n---\n\n## Common SOC 2 Gaps in SaaS\u002FCloud Environments\n\n### No Formal Access Review Process (CC6.2, CC6.3)\n**Gap:** User access is provisioned but never reviewed; departed employees may retain access.\n**Fix:** Implement quarterly access reviews in Jira, Vanta, Drata, or a spreadsheet. Document who reviewed, when, what changes were made. Automate deprovisioning via HRIS-SSO integration.\n\n### Developers Can Deploy to Production (CC8)\n**Gap:** Engineers have direct production deployment access; no separation of duties.\n**Fix:** Require pull request approval from a second engineer. Restrict production deployments to CI\u002FCD pipeline with approvals. Even for small teams, document the control: \"Engineer A writes code; Engineer B reviews and approves before merge; CI\u002FCD deploys.\"\n\n### No Documented Incident Response Testing (CC7.3–CC7.5)\n**Gap:** IRP exists on paper but has never been tested.\n**Fix:** Conduct a tabletop exercise (even 1 hour with 3 people). Document scenario, participants, walk-through, and action items. Auditors want evidence of testing, not just the plan.\n\n### Monitoring Without Investigation Records (CC7.2)\n**Gap:** SIEM generates alerts but no records of alert investigation.\n**Fix:** Create a simple alert log: date, alert type, who investigated, finding, action taken. Even \"investigated, false positive, no action required\" counts.\n\n### Vendor SOC Reports Not Collected (CC9.2)\n**Gap:** Critical cloud providers (AWS, Stripe, Salesforce) not included in vendor management program.\n**Fix:** Download SOC 2 reports for critical subservice organizations annually (most are available via their trust portals). Document where you reviewed them and what you found.\n\n### Backup Restoration Not Tested (A1, if Availability in scope)\n**Gap:** Backups run but restoration is never verified.\n**Fix:** Perform a documented restoration test at least annually. Restore to a non-production environment and confirm data integrity. Record date, what was restored, results.\n\n---\n\n## Readiness Assessment Checklist\n\nBefore engaging a SOC 2 auditor, verify:\n\n**Governance**\n- [ ] Information Security Policy approved and distributed\n- [ ] All minimum policies exist (12 policies above)\n- [ ] Risk assessment completed in last 12 months\n- [ ] Security awareness training completed by all personnel\n\n**Access Controls**\n- [ ] MFA enabled for all systems in scope\n- [ ] Privileged access documented and reviewed\n- [ ] Terminated employees removed from all systems (documented process)\n- [ ] Access provisioning follows documented approval process\n\n**Change Management**\n- [ ] Code review\u002FPR approval process enforced in version control\n- [ ] CI\u002FCD pipeline has approval gates before production\n- [ ] Change log maintained for infrastructure changes\n\n**Monitoring**\n- [ ] Security alerts configured and investigated\n- [ ] Vulnerability scans running and documented\n- [ ] Log retention meets audit period (12 months)\n\n**Availability (if in scope)**\n- [ ] Backup policy defined and implemented\n- [ ] Restoration test completed and documented\n- [ ] DR\u002FBCP plan tested in last 12 months\n\n**Vendors**\n- [ ] Critical vendor list maintained\n- [ ] SOC 2 reports collected for critical SaaS\u002Fcloud vendors\n\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcompliance-frameworks\u002Fskills\u002Fsoc2-compliance",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill soc2-compliance",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill soc2-compliance",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill soc2-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcompliance-frameworks\u002Fskills\u002Fsoc2-compliance\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]