--- name: soc2-compliance-0d7560d68c59 description: >- Achieve SOC 2 Type II compliance for SaaS — Trust Service Criteria, evidence collection, and controls implementation. Use when preparing for a SOC 2 audit, meeting B2B SaaS security requirements, or onboarding enterprise customers who require a SOC 2 report. license: Apache-2.0 compatibility: "Language-agnostic. Code examples in Python and Node.js." metadata: author: terminal-skills version: "1.1.0" category: development tags: "soc2, compliance, saas, audit, trust-services" use-cases: "Implement SOC 2 controls for a B2B SaaS product, Prepare evidence for a SOC 2 Type II audit, Set up automated compliance monitoring with Vanta or Drata" agents: "claude-code, openai-codex, gemini-cli, cursor" --- # SOC 2 Compliance ## Overview SOC 2 (System and Organization Controls 2) is an attestation framework from the AICPA for service organizations. An independent licensed CPA firm examines your controls against the Trust Services Criteria (the 2017 criteria with the revised points of focus issued in 2022) and issues a report. There is no SOC 2 "certificate" and no government registry: the deliverable is the auditor's report. A **Type I** report says controls were suitably designed at a point in time; a **Type II** report says they also operated effectively over an observation period. The AICPA sets no fixed minimum for that period; auditors commonly accept 3 months for a first report, 6 to 12 months is typical, and 12 months is the norm for renewals. Enterprise buyers often ask for a Type II report before signing. ## Instructions 1. Scope: list the systems, people, vendors and data that deliver your service, and choose the criteria (Security always; add Availability, Confidentiality, Processing Integrity or Privacy only if customers need them). 2. Run a gap assessment against the Common Criteria below, using a readiness tool or an auditor's readiness review. 3. Write and approve the policies, then implement the missing controls (MFA, encryption, logging, change control, access reviews, vendor reviews). 4. Collect evidence continuously from the first day of the observation period, not at audit time. 5. Pick an independent CPA firm early and agree the scope, period and evidence format; compliance platforms are not auditors. 6. Fix findings, review the draft report and management assertion, and repeat annually. ## Trust Service Criteria (TSC) | Criteria | Abbrev | Required? | Description | |----------|--------|-----------|-------------| | Security | CC | ✅ Always | Protection against unauthorized access | | Availability | A | Optional | System available for operation and use | | Confidentiality | C | Optional | Information designated as confidential is protected | | Processing Integrity | PI | Optional | Processing is complete, valid, accurate, timely | | Privacy | P | Optional | Personal information collected, used, retained, disclosed properly | Most SaaS companies start with **Security + Availability**. Add Confidentiality if handling sensitive data; add Privacy if handling personal data covered by GDPR/CCPA. ## Common Controls Framework (CC) ### CC1 — Control Environment - Written security policies reviewed annually - Code of conduct acknowledged by all staff - Org chart with clear security accountability ### CC2 — Communication and Information - Security policies communicated to all personnel - Vendor risk assessments documented - Security awareness training records ### CC3 — Risk Assessment ```markdown Risk Register entry: - Risk ID: RISK-001 - Title: Unauthorized database access - Likelihood: Medium - Impact: High - Inherent Risk: High - Controls: MFA, network segmentation, IAM least-privilege - Residual Risk: Low - Owner: CTO - Review Date: 2026-12-15 ``` ### CC4 — Monitoring Activities - Vulnerability scanning on a schedule you define in policy (weekly or monthly is common) - Periodic access reviews (quarterly is common) - Alerts from monitoring or intrusion detection reviewed and ticketed SOC 2 prescribes no frequencies; auditors test that you do what your own policies say. ### CC5 — Control Activities - Change management process with peer review - Incident response plan tested at least annually - Penetration testing annually (customers usually expect it, although the criteria do not name it) ### CC6 — Logical and Physical Access Controls **MFA enforcement (Node.js example):** ```javascript // Enforce MFA for all admin users const requireMFA = async (req, res, next) => { const user = req.user; if (user.role === 'admin' && !user.mfaVerified) { return res.status(403).json({ error: 'MFA required for admin access', code: 'MFA_REQUIRED' }); } next(); }; // Log all authentication events for CC6 evidence const logAuthEvent = async (req, userId, event, success) => { await db.auditLog.create({ userId, event, // 'login' | 'logout' | 'mfa_verify' | 'password_reset' success, ipAddress: req.ip, userAgent: req.headers['user-agent'], timestamp: new Date().toISOString() }); }; ``` **Access review automation:** ```python import boto3 from datetime import datetime, timezone def generate_access_review_report(): """Generate quarterly access review evidence for CC6.""" iam = boto3.client('iam') report = [] users = [u for page in iam.get_paginator('list_users').paginate() for u in page['Users']] for user in users: login_profile = None try: login_profile = iam.get_login_profile(UserName=user['UserName']) except iam.exceptions.NoSuchEntityException: pass groups = iam.list_groups_for_user(UserName=user['UserName']) policies = iam.list_attached_user_policies(UserName=user['UserName']) report.append({ "user": user['UserName'], "created": user['CreateDate'].isoformat(), "password_last_used": user['PasswordLastUsed'].isoformat() if 'PasswordLastUsed' in user else None, "groups": [g['GroupName'] for g in groups['Groups']], "policies": [p['PolicyName'] for p in policies['AttachedPolicies']], "has_console_access": login_profile is not None, "review_date": datetime.now(timezone.utc).isoformat(), "reviewed_by": "security-team" }) return report ``` ### CC7 — System Operations - Infrastructure monitoring with alerts - Log aggregation and anomaly detection - Capacity planning reviews ### CC8 — Change Management **Git-based change management:** ```bash # All changes via PR (enforced in GitHub branch protection) # - Required reviewers: 2 # - Required CI checks: tests, security scan, lint # - No direct pushes to main # Deployment approval record (for audit evidence) cat deployment-log.json # { # "deploy_id": "deploy-2026-1015-001", # "author": "alice@company.com", # "reviewer": "bob@company.com", # "approved_at": "2026-10-15T14:30:00Z", # "deployed_at": "2026-10-15T14:45:00Z", # "changes": "JIRA-123: Add MFA to admin panel", # "rollback_plan": "Revert commit abc123" # } ``` ### CC9 — Risk Mitigation - Vendor management program - Business continuity plan - Cyber insurance ## Evidence Collection SOC 2 auditors need **evidence** that controls operated continuously during the audit period. | Control | Evidence Type | Frequency | Storage | |---------|--------------|-----------|---------| | MFA enabled | Screenshot + IAM export | Quarterly | Vanta/Drata | | Access reviews | Signed review records | Quarterly | Google Drive | | Vulnerability scans | Scan reports | Weekly | S3/Drive | | Pen test | Report + remediation | Annual | Drive | | Security training | Completion certificates | Annual | HRIS | | Incident response test | Tabletop exercise notes | Annual | Drive | | Encryption at rest | Config screenshot | Change-based | Drive | | Backup tested | Restore test log | Quarterly | Drive | ## Automation Tools ### Vanta, Drata, Secureframe and similar platforms These SaaS tools connect read-only to your cloud, identity provider, source control and HR systems, run automated tests mapped to the criteria (MFA enforcement, encryption at rest, scanning, offboarding, background checks), keep a policy library and give auditors a portal for evidence. Compare integrations, price and which audit firms they partner with; the choice does not change what the audit requires. The platform is not the auditor, and passing its dashboard is not a SOC 2 report. ## Key Policies to Write Create these written policies (stored in a policy management system): ```markdown Required Policies: 1. Information Security Policy 2. Access Control Policy 3. Encryption Policy 4. Incident Response Plan 5. Business Continuity / Disaster Recovery Plan 6. Vulnerability Management Policy 7. Change Management Policy 8. Vendor Management Policy 9. Acceptable Use Policy 10. Data Classification Policy ``` **Encryption Policy example snippet:** ```markdown ## Encryption Policy **Effective Date:** 2026-11-01 **Owner:** CTO **Review Cycle:** Annual ### Requirements - All data at rest classified as Confidential or Restricted MUST be encrypted using AES-256 or equivalent. - All data in transit MUST use TLS 1.2 or higher. - Encryption keys MUST be stored separately from encrypted data, in an approved key management system (AWS KMS, GCP KMS, or HashiCorp Vault). - Keys MUST be rotated annually or upon suspected compromise. ``` ## SOC 2 Timeline | Phase | Duration | Activities | |-------|----------|-----------| | Readiness assessment | 4-6 weeks | Gap analysis, policy writing | | Remediation | 2-4 months | Implement controls, fix gaps | | Evidence collection period (Type II) | 3-12 months | Run controls, collect evidence | | Auditor fieldwork | 4-8 weeks | Auditor reviews evidence | | Report issuance | 2-4 weeks | Final report, management response | **Typical timeline from start to a first Type II report: 6-15 months depending on the observation period you and the auditor agree. A Type I report can be issued sooner as a stopgap.** ## Compliance Checklist - [ ] Scope defined (which systems handle customer data) - [ ] Auditor selected (independent licensed CPA firm) - [ ] Security policies written and approved - [ ] MFA enforced for all users - [ ] Encryption at rest and in transit enabled - [ ] Vulnerability scanning automated - [ ] Access review process established - [ ] Change management process documented - [ ] Incident response plan written and tested - [ ] Vendor risk assessments completed - [ ] Background checks for employees - [ ] Security awareness training completed - [ ] Evidence collection tool in place (Vanta/Drata/Secureframe) ## Examples ### Example 1: Gap assessment for a Series A SaaS User: "We are an AWS and GitHub shop with 40 people and a customer asking for SOC 2 Type II. What do we do first?" Scope the production AWS account, GitHub, the identity provider and the support tooling; choose Security plus Availability; list missing controls against CC1 to CC9 (typically: written policies, MFA on every account, branch protection with required review, quarterly access reviews, vendor reviews, a tested incident plan). Output a gap table with owner and due date per item and a recommended start date for the observation period. ### Example 2: Quarterly access review evidence User: "Generate the IAM access review for CC6 this quarter." Run `generate_access_review_report()` from this skill, write the JSON to the evidence folder with the date in the file name, have the system owner sign off, and file any removed accounts as tickets. Result: a dated export, a reviewer name and linked remediation tickets that an auditor can sample. ## Guidelines - Do not claim you are "SOC 2 certified" or "compliant" before a CPA firm has issued a report; say "SOC 2 Type II report available under NDA". - Evidence must be dated, attributable and retained for the whole period; a screenshot taken the week before the audit does not show continuous operation. - Write policies you can actually follow: auditors test against your own documents, so an unrealistic policy creates exceptions. - Keep scope small and accurate; every extra system and vendor adds testing. - Controls here are a starting point. The auditor decides the final control set and testing; confirm specifics with them. - This is guidance, not legal or audit advice. --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/soc2-compliance/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/soc2-compliance/SKILL.md Attribution basis: Source repository record Fields of work: Legal, Sales, Product Management Roles: Compliance Officer, Business Development, Product Manager Specialties: API Tools: Vanta, Drata Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: c250618cb7db086ad6c17c4b8736ed7ff6d02d40a1c35d6f46fbec86471adea9