soc2-readiness
Prepare an organization for a SOC 2 Type I or II audit — trust services criteria mapping, evidence collection, control implementation, and remediation planning. Use when starting a SOC 2 journey or preparing for an audit window.
v2026.8.26-b2b6b522 installazioni+2 in 7 giorni0 Stellesincronizzato 19 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/soc2-readinessScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto31b8e9d0…eb3d2052
31b8e9d043fc…15a4eb3d20521 file · 1.2 KBScansioneMedio1 segnalazione
- Nessuna licenza trovata
Sorgentegithub.com/securityskills/skills/tree/main/compliance/soc2/soc2-readiness@b2b6b52
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Drive an organization from "no controls documented" to audit-ready.
1. Scoping
- Determine report type: Type I (point-in-time) vs Type II (period of time — start the observation window early)
- Define the system description: services in scope, infrastructure, boundaries (subprocessors, cloud providers)
- Select Trust Services Criteria: Security (required) + Availability, Confidentiality, Processing Integrity, Privacy as applicable
2. Gap Assessment
Map current practices to the criteria:
| Area | Typical Criteria | Common Gaps |
|---|---|---|
| Access control | CC6.1–CC6.3 | No MFA, no role-based access, shared accounts |
| Change management | CC8.1 | No peer review on deploys, no environment separation |
| Risk assessment | CC3.1–CC3.4 | No annual risk assessment or vendor reviews |
| Monitoring | CC7.1–CC7.3 | No log review, no alerting on anomalies |
| Incident response | CC7.4–CC7.5 | No IR plan or tabletop evidence |
| BC/DR | A1.2–A1.3 | Untested backups, no documented RTO/RPO |
| Vendor management | CC9.2 | No subprocessor due diligence |
| Onboarding/offboarding | CC6.1 | Access removal not timely or evidenced |
3. Remediation
- Prioritize by audit-blocker status first, then risk
- Implement policy + practice + evidence together: a policy without execution evidence fails
- Typical timeline: 2–4 months for a Type I; Type II needs 2–12 months of operating evidence
4. Evidence Package
Per control: policy documents, implementation artifacts (screenshots, configs), and dated operating evidence over the review period (access reviews, change tickets, training logs, IR exercises)
5. Audit Logistics
- Choose auditor; confirm scope wording matches your system description
- Readiness assessment (optional but useful) → fieldwork → draft report review
- Track findings/exceptions honestly; management responses documented
Output
Gap register with owners and dates, control matrix mapped to criteria, evidence repository structure, and auditor-ready system description.
File di questa versione
- SKILL.md2.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaLicenza · Nessuna licenza trovata
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.8.26-b2b6b52 | 13 nov 2026 | b2b6b52 | 31b8e9d0 | Firmata | – |
Altro da securityskills
Tutto da questo editoreAltro in Report e compliance
Vai alla categoria- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login