Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Guides organizations through SOC 2 compliance lifecycle with gap analysis, control implementation, evidence collection, audit prep, and continuous monitoring.
Guides organizations through SOC 2 compliance lifecycle with gap analysis, control implementation, evidence collection, audit prep, and continuous monitoring.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Your agent for achieving and maintaining SOC 2 Type I and Type II compliance โ from readiness assessment through audit completion.
Guides organizations through the full SOC 2 lifecycle: gap analysis, control implementation, evidence collection, audit prep, and continuous monitoring. Covers all 5 Trust Service Criteria with practical implementation steps.
Tell your agent what stage you're at: "Run SOC 2 readiness assessment" โ 64-point gap analysis across all Trust Service Criteria "Build SOC 2 control matrix" โ Maps controls to criteria with ownership and evidence requirements "Create SOC 2 evidence collection plan" โ Automated and manual evidence gathering schedule "Prepare for SOC 2 audit" โ Auditor-ready documentation package checklist "SOC 2 continuous monitoring dashboard" โ Ongoing compliance tracking after certification
CC1: Control Environment (tone at top, org structure, accountability) CC2: Communication & Information (internal/external, system boundaries) CC3: Risk Assessment (risk identification, fraud risk, change impact) CC4: Monitoring Activities (ongoing evaluations, deficiency reporting) CC5: Control Activities (policies, technology controls, deployment) CC6: Logical & Physical Access (access management, authentication, physical security) CC7: System Operations (vulnerability management, incident response, recovery) CC8: Change Management (change authorization, testing, approval) CC9: Risk Mitigation (vendor management, business continuity)
Availability (A1): Uptime SLAs, DR/BCP, capacity planning Processing Integrity (PI1): Data accuracy, completeness, timeliness Confidentiality (C1): Classification, encryption, retention, disposal Privacy (P1): Notice, consent, collection, use, disclosure, access
System Description Checklist: โก Infrastructure components (cloud, on-prem, hybrid) โก Software stack (applications, databases, middleware) โก People (roles, responsibilities, third parties) โก Procedures (operational, security, change management) โก Data flows (ingress, processing, storage, egress) โก Trust Service Criteria selection (Security + which optional?) โก Subservice organizations (cloud providers, SaaS tools) โก Carve-out vs inclusive method for subservice orgs
Score each control area 1-5: 1 โ Not Started: No policy, no process, no evidence 2 โ Ad Hoc: Informal processes exist but undocumented 3 โ Defined: Documented but inconsistent execution 4 โ Managed: Documented, executed, some evidence 5 โ Optimized: Automated, monitored, auditable evidence Priority Matrix: Gap ScoreActionTimeline1-2Critical โ implement immediately2-4 weeks3Important โ formalize and document1-2 weeks4Minor โ fill evidence gaps3-5 days5Maintain โ continue monitoringOngoing
For each gap: 1. Assign control owner (by name, not role) 2. Define implementation steps 3. Set evidence collection method (automated preferred) 4. Establish testing cadence 5. Document exception handling process
Access Management: SSO, MFA on all systems, quarterly access reviews Encryption: TLS 1.2+ in transit, AES-256 at rest, key management Logging: Centralized logging, 90-day retention minimum, tamper-evident Incident Response: Documented plan, defined roles, tested annually Change Management: Approval workflows, code review, deployment gates Vendor Management: Vendor inventory, risk assessments, SOC 2 reports from critical vendors Employee Security: Background checks, security awareness training, acceptable use policy Vulnerability Management: Regular scanning, patch cadence (critical <72hrs), penetration testing
Business Continuity: DR plan, RTO/RPO defined, tested semi-annually Data Classification: 4-tier model (Public, Internal, Confidential, Restricted) Network Security: Segmentation, IDS/IPS, WAF for web applications Endpoint Protection: EDR, device encryption, MDM for mobile
Security Metrics Dashboard: Real-time compliance posture Automated Compliance Monitoring: Continuous control testing Zero Trust Architecture: Beyond perimeter security
ControlEvidence SourceTool ExamplesAccess ReviewsIAM exportsOkta, Azure AD, AWS IAMEncryptionConfig snapshotsAWS Config, CloudTrailLoggingLog aggregationDatadog, Splunk, ELKVulnerability ScansScan reportsQualys, Nessus, SnykChange ManagementPR/deploy historyGitHub, GitLab, JiraUptimeMonitoring dashboardsDatadog, PagerDuty
ControlEvidence TypeFrequencyBackground ChecksHR recordsPer hireSecurity TrainingCompletion certificatesAnnualRisk AssessmentAssessment documentAnnualPen TestingReportAnnualDR TestingTest resultsSemi-annualBoard/Mgmt ReviewMeeting minutesQuarterlyVendor ReviewsAssessment recordsAnnualPolicy ReviewsVersion historyAnnual
Week 1-2: Auditor selection + engagement letter Week 2-4: System description draft Week 4-6: Control documentation + evidence prep Week 6-8: Fieldwork (auditor testing) Week 8-10: Draft report review Week 10-12: Final report issued
Month 1: Observation period begins (minimum 3 months, recommend 6-12) Ongoing: Evidence collection, control operation Month 3-12: Observation period ends +Week 1-2: Fieldwork scheduling +Week 2-4: Fieldwork (testing over observation period) +Week 4-6: Draft report + final report
Company SizeType IType IIAnnual MaintenanceStartup (<50)$20K-$50K$30K-$80K$15K-$40KMid-Market (50-500)$40K-$100K$60K-$150K$30K-$80KEnterprise (500+)$80K-$200K$120K-$300K$60K-$150K Includes: auditor fees, tooling, personnel time, remediation costs. Hidden costs to budget: Compliance automation platform: $10K-$50K/year Additional security tooling: $5K-$30K/year Personnel time (internal): 200-800 hours Policy/procedure writing (if outsourced): $5K-$20K
Access not revoked within 24 hours of termination โ #1 finding Missing or incomplete risk assessment โ annual requirement No evidence of management review โ need meeting minutes Incomplete vendor management โ missing SOC reports from critical vendors Inconsistent change management โ emergency changes without retroactive approval Security training gaps โ new hires not trained within 30 days Logging gaps โ not all in-scope systems sending to central logging
When deploying AI agents in SOC 2 environments: Data boundaries: Agents must not access data outside their defined scope Audit trail: All agent actions must be logged and attributable Access controls: Agent service accounts need same rigor as human accounts Model governance: Document which models process customer data Prompt injection defense: Part of CC7 (system operations) controls Output validation: Processing integrity controls for agent outputs
IndustryExtra CriteriaKey ControlsFintechAll 5 TSC typicalSOX mapping, encryption everywhere, PCI if paymentsHealthcarePrivacy, ConfidentialityHIPAA crosswalk, BAAs, PHI handlingSaaSAvailability, ConfidentialityMulti-tenant isolation, SLA complianceLegalConfidentiality, PrivacyPrivilege protection, matter isolationConstructionSecurity, AvailabilityField data protection, offline capabilityE-commerceAll 5 TSC typicalPCI DSS alignment, transaction integrity
Starting with Type II โ Get Type I first, prove controls work, then observe Scoping too broadly โ Only include systems that touch customer data Choosing the wrong auditor โ Pick one who knows your industry Manual evidence collection โ Automate from day 1 or drown in spreadsheets Treating it as a project, not a program โ SOC 2 is continuous Ignoring subservice organizations โ Your cloud provider's SOC 2 matters No executive sponsor โ Compliance without budget authority = failure
This skill gives you the framework. For industry-specific compliance playbooks with regulatory crosswalks, cost models, and vendor selection guides: ๐ AfrexAI Context Packs โ $47 per industry vertical Available packs: Fintech, Healthcare, Legal, Construction, E-commerce, SaaS, Real Estate, Recruitment, Manufacturing, Professional Services ๐ AI Revenue Leak Calculator โ Find where compliance gaps cost you money ๐ Agent Setup Wizard โ Deploy compliance monitoring agents in minutes Bundle pricing: Pick 3 packs: $97 All 10 packs: $197 Everything bundle: $247
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.