Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
securityskills/soc2-readinessReporting and compliance

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 installs+2 in 7 days0 Starssynced 19 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install securityskills/soc2-readiness

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
er+t7T7gG4…jA1evjCg==The CLI checks the SHA-256 and the signature before it writes a file.
Package31b8e9d0…eb3d2052
31b8e9d043fc…15a4eb3d20521 file · ⁦1.2 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/securityskills/skills/tree/main/compliance/soc2/soc2-readiness@b2b6b52

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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLicense · No license found

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.8.26-b2b6b52Nov 13, 2026b2b6b5231b8e9d0Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login