Files
claude-skills-reference/c-level-advisor/ciso-advisor/references/compliance_roadmap.md
Alireza Rezvani 466aa13a7b feat: C-Suite expansion — 8 new executive advisory roles (2→10) (#264)
* feat: C-Suite expansion — 8 new executive advisory roles

Add COO, CPO, CMO, CFO, CRO, CISO, CHRO advisors and Executive Mentor.
Expands C-level advisory from 2 to 10 roles with 74 total files.

Each role includes:
- SKILL.md (lean, <5KB, ~1200 tokens for context efficiency)
- Reference docs (loaded on demand, not at startup)
- Python analysis scripts (stdlib only, runnable CLI)

Executive Mentor features /em: slash commands (challenge, board-prep,
hard-call, stress-test, postmortem) with devil's advocate agent.

21 Python tools, 24 reference frameworks, 28,379 total lines.
All SKILL.md files combined: ~17K tokens (8.5% of 200K context window).

Badge: 88 → 116 skills

* feat: C-Suite orchestration layer + 18 complementary skills

ORCHESTRATION (new):
- cs-onboard: Founder interview → company-context.md
- chief-of-staff: Routing, synthesis, inter-agent orchestration
- board-meeting: 6-phase multi-agent deliberation protocol
- decision-logger: Two-layer memory (raw transcripts + approved decisions)
- agent-protocol: Inter-agent invocation with loop prevention
- context-engine: Company context loading + anonymization

CROSS-CUTTING CAPABILITIES (new):
- board-deck-builder: Board/investor update assembly
- scenario-war-room: Cascading multi-variable what-if modeling
- competitive-intel: Systematic competitor tracking + battlecards
- org-health-diagnostic: Cross-functional health scoring (8 dimensions)
- ma-playbook: M&A strategy (acquiring + being acquired)
- intl-expansion: International market entry frameworks

CULTURE & COLLABORATION (new):
- culture-architect: Values → behaviors, culture code, health assessment
- company-os: EOS/Scaling Up operating system selection + implementation
- founder-coach: Founder development, delegation, blind spots
- strategic-alignment: Strategy cascade, silo detection, alignment scoring
- change-management: ADKAR-based change rollout framework
- internal-narrative: One story across employees/investors/customers

UPGRADES TO EXISTING ROLES:
- All 10 roles get reasoning technique directives
- All 10 roles get company-context.md integration
- All 10 roles get board meeting isolation rules
- CEO gets stage-adaptive temporal horizons (seed→C)

Key design decisions:
- Two-layer memory prevents hallucinated consensus from rejected ideas
- Phase 2 isolation: agents think independently before cross-examination
- Executive Mentor (The Critic) sees all perspectives, others don't
- 25 Python tools total (stdlib only, no dependencies)

52 new files, 10 modified, 10,862 new lines.
Total C-suite ecosystem: 134 files, 39,131 lines.

* fix: connect all dots — Chief of Staff routes to all 28 skills

- Added complementary skills registry to routing-matrix.md
- Chief of Staff SKILL.md now lists all 28 skills in ecosystem
- Added integration tables to scenario-war-room and competitive-intel
- Badge: 116 → 134 skills
- README: C-Level Advisory count 10 → 28

Quality audit passed:
 All 10 roles: company-context, reasoning, isolation, invocation
 All 6 phases in board meeting
 Two-layer memory with DO_NOT_RESURFACE
 Loop prevention (no self-invoke, max depth 2, no circular)
 All /em: commands present
 All complementary skills cross-reference roles
 Chief of Staff routes to every skill in ecosystem

* refactor: CEO + CTO advisors upgraded to C-suite parity

Both roles now match the structural standard of all new roles:
- CEO: 11.7KB → 6.8KB SKILL.md (heavy content stays in references)
- CTO: 10KB → 7.2KB SKILL.md (heavy content stays in references)

Added to both:
- Integration table (who they work with and when)
- Key diagnostic questions
- Structured metrics dashboard table
- Consistent section ordering (Keywords → Quick Start → Responsibilities → Questions → Metrics → Red Flags → Integration → Reasoning → Context)

CEO additions:
- Stage-adaptive temporal horizons (seed=3m/6m/12m → B+=1y/3y/5y)
- Cross-references to culture-architect and board-deck-builder

CTO additions:
- Key Questions section (7 diagnostic questions)
- Structured metrics table (DORA + debt + team + architecture + cost)
- Cross-references to all peer roles

All 10 roles now pass structural parity:  Keywords  QuickStart  Questions  Metrics  RedFlags  Integration

* feat: add proactive triggers + output artifacts to all 10 roles

Every C-suite role now specifies:
- Proactive Triggers: 'surface these without being asked' — context-driven
  early warnings that make advisors proactive, not reactive
- Output Artifacts: concrete deliverables per request type (what you ask →
  what you get)

CEO: runway alerts, board prep triggers, strategy review nudges
CTO: deploy frequency monitoring, tech debt thresholds, bus factor flags
COO: blocker detection, scaling threshold warnings, cadence gaps
CPO: retention curve monitoring, portfolio dog detection, research gaps
CMO: CAC trend monitoring, positioning gaps, budget staleness
CFO: runway forecasting, burn multiple alerts, scenario planning gaps
CRO: NRR monitoring, pipeline coverage, pricing review triggers
CISO: audit overdue alerts, compliance gaps, vendor risk
CHRO: retention risk, comp band gaps, org scaling thresholds
Executive Mentor: board prep triggers, groupthink detection, hard call surfacing

This transforms the C-suite from reactive advisors into proactive partners.

* feat: User Communication Standard — structured output for all roles

Defines 3 output formats in agent-protocol/SKILL.md:

1. Standard Output: Bottom Line → What → Why → How to Act → Risks → Your Decision
2. Proactive Alert: What I Noticed → Why It Matters → Action → Urgency (🔴🟡)
3. Board Meeting: Decision Required → Perspectives → Agree/Disagree → Critic → Action Items

10 non-negotiable rules:
- Bottom line first, always
- Results and decisions only (no process narration)
- What + Why + How for every finding
- Actions have owners and deadlines ('we should consider' is banned)
- Decisions framed as options with trade-offs
- Founder is the highest authority — roles recommend, founder decides
- Risks are concrete (if X → Y, costs $Z)
- Max 5 bullets per section
- No jargon without explanation
- Silence over fabricated updates

All 10 roles reference this standard.
Chief of Staff enforces it as a quality gate.
Board meeting Phase 4 uses the Board Meeting Output format.

* feat: Internal Quality Loop — verification before delivery

No role presents to the founder without passing verification:

Step 1: Self-Verification (every role, every time)
  - Source attribution: where did each data point come from?
  - Assumption audit: [VERIFIED] vs [ASSUMED] tags on every finding
  - Confidence scoring: 🟢 high / 🟡 medium / 🔴 low per finding
  - Contradiction check against company-context + decision log
  - 'So what?' test: every finding needs a business consequence

Step 2: Peer Verification (cross-functional)
  - Financial claims → CFO validates math
  - Revenue projections → CRO validates pipeline backing
  - Technical feasibility → CTO validates
  - People/hiring impact → CHRO validates
  - Skip for single-domain, low-stakes questions

Step 3: Critic Pre-Screen (high-stakes only)
  - Irreversible decisions, >20% runway impact, strategy changes
  - Executive Mentor finds weakest point before founder sees it
  - Suspicious consensus triggers mandatory pre-screen

Step 4: Course Correction (after founder feedback)
  - Approve → log + assign actions
  - Modify → re-verify changed parts
  - Reject → DO_NOT_RESURFACE + learn why
  - 30/60/90 day post-decision review

Board meeting contributions now require self-verified format with
confidence tags and source attribution on every finding.

* fix: resolve PR review issues 1, 4, and minor observation

Issue 1: c-level-advisor/CLAUDE.md — completely rewritten
  - Was: 2 skills (CEO, CTO only), dated Nov 2025
  - Now: full 28-skill ecosystem map with architecture diagram,
    all roles/orchestration/cross-cutting/culture skills listed,
    design decisions, integration with other domains

Issue 4: Root CLAUDE.md — updated all stale counts
  - 87 → 134 skills across all 3 references
  - C-Level: 2 → 33 (10 roles + 5 mentor commands + 18 complementary)
  - Tool count: 160+ → 185+
  - Reference count: 200+ → 250+

Minor observation: Documented plugin.json convention
  - Explained in c-level-advisor/CLAUDE.md that only executive-mentor
    has plugin.json because only it has slash commands (/em: namespace)
  - Other skills are invoked by name through Chief of Staff or directly

Also fixed: README.md 88+ → 134 in two places (first line + skills section)

* fix: update all plugin/index registrations for 28-skill C-suite

1. c-level-advisor/.claude-plugin/plugin.json — v2.0.0
   - Was: 2 skills, generic description
   - Now: all 28 skills listed with descriptions, all 25 scripts,
     namespace 'cs', full ecosystem description

2. .codex/skills-index.json — added 18 complementary skills
   - Was: 10 roles only
   - Now: 28 total c-level entries (10 roles + 6 orchestration +
     6 cross-cutting + 6 culture)
   - Each with full description for skill discovery

3. .claude-plugin/marketplace.json — updated c-level-skills entry
   - Was: generic 2-skill description
   - Now: v2.0.0, full 28-skill ecosystem description,
     skills_count: 28, scripts_count: 25

* feat: add root SKILL.md for c-level-advisor ClawHub package

---------

Co-authored-by: Leo <leo@openclaw.ai>
2026-03-06 01:35:08 +01:00

16 KiB
Raw Blame History

Compliance Roadmap Reference

Decision Framework: Which Framework First?

Start here — who are your customers?

Enterprise SaaS (B2B, US market)  →  SOC 2 Type II first
Healthcare / health data           →  HIPAA + SOC 2 together
EU customers or EU-resident data   →  GDPR (non-optional if applicable)
EU enterprise sales                →  ISO 27001 + GDPR
Government / defense               →  FedRAMP / CMMC (separate scope)
All of the above (Series B+)       →  Multi-framework efficiency approach

The sequencing principle: SOC 2 Type I is the fastest proof of intent (36 months). Type II is the credibility signal (12 months). Everything else builds on your control library.


1. SOC 2

What It Is

SOC 2 is an attestation (not a certification) that your controls meet the AICPA Trust Service Criteria. An independent CPA firm audits your controls and issues a report.

  • Type I: Controls are suitably designed at a point in time (snapshot). Lower credibility but faster.
  • Type II: Controls operated effectively over a period of time (minimum 6 months). This is what enterprise buyers want.

Trust Service Criteria (TSC)

You must include Security (CC). Others are optional:

Criteria When to add
Security (CC) Always required
Availability If uptime SLAs are contractual
Confidentiality If you process confidential third-party data
Processing Integrity If accuracy of processing is critical (fintech, data processing)
Privacy If you make privacy commitments beyond GDPR/CCPA scope

Most startups: Security + Availability is sufficient.

Timeline: SOC 2 Type I

Phase Duration Activities
Readiness assessment 24 weeks Gap analysis against CC criteria, identify control owners
Policy documentation 46 weeks Write ~1520 policies (acceptable use, access control, change management, etc.)
Control implementation 48 weeks Deploy technical controls, fix gaps identified in readiness
Evidence collection 24 weeks Screenshots, logs, configs — auditor will sample these
Audit fieldwork 24 weeks CPA firm reviews evidence, interviews control owners
Report issuance 24 weeks Report issued, reviewed, shared with customers
Total 36 months

Timeline: SOC 2 Type II (after Type I)

Phase Duration Notes
Observation period 612 months Controls must operate consistently — no exceptions
Audit fieldwork 46 weeks Auditor samples evidence across full period
Report issuance 24 weeks
Total from Type I 918 months Faster if Type I was clean

Cost Estimates

Item SOC 2 Type I SOC 2 Type II
Audit firm fees $15,000$35,000 $25,000$60,000
Compliance platform (Vanta, Drata, Secureframe) $12,000$30,000/yr Same platform
External counsel / vCISO $10,000$30,000 $5,000$15,000 maintenance
Internal time (eng + ops) 200400 hours 100200 hours/yr
Total first year $40,000$100,000 +$30,000$75,000

Cost optimization tips:

  • Use a compliance platform (Vanta, Drata, Secureframe) — automated evidence collection halves audit cost
  • Choose a mid-tier audit firm; Big 4 is overkill for startups
  • Type I and Type II with same auditor = continuity discount

Common Failure Modes

  1. Controls documented but not operating (access reviews on paper only)
  2. Exceptions during observation period (one admin account without MFA = finding)
  3. No formal security awareness training (required for CC criteria)
  4. Change management not followed (no ticket for that production change)
  5. Vendor risk management missing (you must assess your critical vendors)

2. ISO 27001

What It Is

ISO 27001 is an internationally recognized certification for an Information Security Management System (ISMS). Unlike SOC 2, it's a certification (pass/fail), not an attestation report. Issued by accredited certification bodies (BSI, Bureau Veritas, DNV, TÜV).

Why ISO 27001 over SOC 2: EU enterprise buyers, government contracts, and global markets often prefer or require ISO 27001. It's geographically neutral.

Scope Decision

ISO 27001 scope is flexible — you can certify a subset of the organization.

  • Narrow scope: The production environment only — fastest, cheapest
  • Full scope: Entire organization — most credibility, highest effort
  • Recommended for startups: Production environment + key business processes

Certification Timeline

Phase Duration Activities
Gap analysis 24 weeks Assess current state vs. 93 controls in Annex A
ISMS design 48 weeks Scope, risk methodology, SoA (Statement of Applicability)
Policy and procedure development 610 weeks Mandatory documents: risk treatment plan, asset register, ISMS policy
Risk assessment 46 weeks Identify, analyze, evaluate risks; produce risk register
Control implementation 816 weeks Implement gaps from risk assessment
Internal audit 24 weeks First internal audit of ISMS
Management review 12 weeks Leadership sign-off on ISMS
Stage 1 audit (documentation) 12 weeks Certification body reviews docs and scope
Stage 2 audit (implementation) 12 weeks Certification body verifies controls are operating
Certification issued 12 weeks Certificate valid for 3 years with annual surveillance audits
Total 918 months

Cost Estimates

Item Cost
Certification body fees (Stage 1 + Stage 2) $15,000$40,000
Annual surveillance audits $8,000$20,000/yr
vCISO / consultant (if not in-house) $30,000$80,000
GRC platform $10,000$25,000/yr
Internal time 400800 hours
Total first year $55,000$150,000

Mandatory ISO 27001:2022 Documents

  • ISMS scope document
  • Information security policy
  • Risk assessment methodology
  • Risk register with risk treatment plan
  • Statement of Applicability (SoA)
  • Asset inventory
  • Competence and awareness records
  • Internal audit reports
  • Management review minutes
  • Nonconformity and corrective action records

3. HIPAA for Health Tech Startups

When HIPAA Applies

HIPAA applies if you are a Covered Entity (healthcare provider, health plan, clearinghouse) or a Business Associate (you process, store, or transmit Protected Health Information on behalf of a Covered Entity).

Key trigger: If your product touches patient data in any way and a US healthcare provider uses your product, you are likely a Business Associate. You must sign a BAA (Business Associate Agreement) with each Covered Entity customer.

HIPAA Rule Structure

Rule Focus Key Requirements
Privacy Rule How PHI can be used and disclosed Minimum necessary, patient rights, notice of privacy practices
Security Rule Technical and physical safeguards for ePHI Required and addressable safeguards
Breach Notification Rule What to do if PHI is breached Timing and content of breach notifications

Security Rule: Required vs. Addressable

Required safeguards must be implemented exactly as specified. Addressable safeguards must be implemented or documented why an equivalent measure was used.

Key Required Safeguards:

  • Unique user IDs (no shared logins)
  • Emergency access procedure
  • Audit controls (logging access to ePHI)
  • Transmission security (encryption in transit)
  • Person or entity authentication

Key Addressable Safeguards (implement or document why not):

  • Automatic logoff
  • Encryption and decryption (encryption at rest — despite being "addressable," regulators expect it)
  • Audit review procedures
  • Security reminders and training

HIPAA Compliance Timeline

Phase Duration Activities
Risk analysis 46 weeks Document all PHI flows, assess risks to PHI — required by law
Policy development 48 weeks Privacy policies, breach notification, workforce training
Technical safeguard implementation 412 weeks Encryption, audit logging, access controls, BAA templates
Workforce training 24 weeks Annual HIPAA training for all staff with PHI access
BAA execution Ongoing Execute with all vendors who process PHI
Total 48 months

Cost Estimates

Item Cost
Initial risk analysis (consultant) $15,000$40,000
Policy development $8,000$20,000
Technical implementation $20,000$60,000
Annual training and maintenance $5,000$15,000/yr
HIPAA compliance platform $10,000$20,000/yr
Total first year $45,000$130,000

HIPAA Penalties (Why This Matters)

Violation Category Penalty per Violation Annual Cap
Unaware $100$50,000 $25,000
Reasonable cause $1,000$50,000 $100,000
Willful neglect (corrected) $10,000$50,000 $250,000
Willful neglect (not corrected) $50,000 $1,500,000

4. GDPR Compliance Program

When GDPR Applies

GDPR applies if you:

  • Are established in the EU/EEA
  • Process personal data of EU/EEA residents (regardless of your location)
  • Offer goods or services to EU residents
  • Monitor the behavior of EU residents

Key point for US startups: If you have EU users or EU employees, GDPR applies to you.

Core GDPR Principles (Build These In)

  1. Lawfulness, fairness, transparency — have a legal basis for every processing activity
  2. Purpose limitation — collect data for specified, explicit purposes only
  3. Data minimization — collect only what you need
  4. Accuracy — keep data accurate
  5. Storage limitation — delete data when no longer needed
  6. Integrity and confidentiality — appropriate security measures
  7. Accountability — demonstrate compliance
Basis When to use
Consent Marketing, non-essential cookies, optional features
Contract Processing necessary to deliver your service
Legitimate interests Analytics, fraud prevention, security (requires LIA)
Legal obligation Compliance with legal requirements
Vital interests Emergency situations only

Avoid over-relying on consent — it must be freely given, specific, informed, and unambiguous. Contractual basis is more robust for core product data.

GDPR Compliance Checklist

Governance:

  • Data Protection Officer (DPO) appointed (required for large-scale processing or sensitive data)
  • Record of Processing Activities (RoPA) maintained
  • Data Protection Impact Assessments (DPIA) for high-risk processing

Rights Management (respond within 1 month):

  • Right of access (data subject access requests — DSARs)
  • Right to rectification
  • Right to erasure ("right to be forgotten")
  • Right to data portability
  • Right to object to processing

Technical Measures:

  • Privacy by design in product development
  • Data minimization enforced
  • Encryption at rest and in transit
  • Pseudonymization where possible
  • Retention policies and automated deletion

Vendor Management:

  • Data Processing Agreements (DPAs) with all processors
  • Standard Contractual Clauses (SCCs) for non-EU transfers

Breach Notification:

  • Notify supervisory authority within 72 hours of awareness
  • Notify affected individuals if high risk to their rights and freedoms

GDPR Compliance Timeline

Phase Duration Activities
Data mapping 36 weeks Map all personal data flows: collect, store, process, share, delete
Legal basis review 24 weeks Assign legal basis to each processing activity
Policy updates 46 weeks Privacy policy, cookie policy, employee data notices
DPA execution 24 weeks Execute DPAs with all processors (SaaS vendors, cloud providers)
Technical controls 412 weeks Consent management, data subject rights automation, retention
Staff training 24 weeks GDPR awareness for all staff
Total 36 months

GDPR Fines

  • Standard violations: Up to €10M or 2% of global annual revenue
  • Major violations (basic principles, consent, data subject rights): Up to €20M or 4% of global annual revenue
  • Highest ever fine: Meta, €1.2B (2023, data transfers to US)

5. Multi-Framework Efficiency

Control Overlap Analysis

The same underlying controls satisfy multiple frameworks. Build once, certify multiple times.

Core Control Domain Overlap:

Control Domain SOC 2 ISO 27001 HIPAA GDPR
Access control / IAM CC6 A.5.15A.5.18 §164.312(a) Art. 32
Encryption at rest/transit CC6.7 A.8.24 §164.312(a)(2)(iv) Art. 32
Audit logging CC7.2 A.8.15, A.8.17 §164.312(b) Art. 32
Incident response CC7.3CC7.5 A.5.24A.5.28 §164.308(a)(6) Art. 3334
Vendor/third-party mgmt CC9 A.5.19A.5.22 §164.308(b) Art. 28
Risk assessment CC3 Clause 6.1 §164.308(a)(1) Art. 32
Security training CC1.4 A.6.3, A.6.8 §164.308(a)(5) Art. 39
Business continuity A1 A.5.29A.5.30 §164.308(a)(7) Art. 32
Data classification CC6.1 A.5.9A.5.13 §164.514 Art. 5(1)(c)
Change management CC8 A.8.32 §164.312(c) Art. 25

Efficiency Rule: If you build SOC 2 controls correctly, you're ~6575% of the way to ISO 27001 and ~70% of the way to HIPAA. Don't rebuild — extend.

B2B SaaS (US-focused):

Month 06:   SOC 2 Type I → unblocks early enterprise deals
Month 618:  SOC 2 Type II → enterprise table stakes
Month 1830: ISO 27001 → EU market expansion
             (GDPR should be woven in from month 0 if any EU data)

HealthTech (US):

Month 08:   HIPAA compliance + BAA readiness → enables healthcare customers
Month 618:  SOC 2 Type II → enterprise IT requirements on top of HIPAA
Month 18+:   ISO 27001 if entering European market

EU-founded SaaS:

Month 03:   GDPR compliance → legal requirement, not optional
Month 312:  ISO 27001 → EU enterprise default expectation
Month 1224: SOC 2 → US market expansion

HealthTech (EU):

Concurrent:  GDPR + ISO 27001 (strong overlap with MDR/IVDR security requirements)
Month 12+:   HIPAA if entering US market

Shared Evidence Model

Build your evidence library once. Tag each piece of evidence by framework:

evidence/
├── access_control/
│   ├── iam_policy.pdf          [SOC2:CC6, ISO:A5.15, HIPAA:164.312a]
│   ├── mfa_screenshot_Q1.png   [SOC2:CC6, ISO:A8.5, HIPAA:164.312d]
│   └── access_review_log.xlsx  [SOC2:CC6, ISO:A5.18, HIPAA:164.308a]
├── encryption/
│   ├── kms_config.png          [SOC2:CC6.7, ISO:A8.24, HIPAA:164.312e]
│   └── tls_policy.md           [SOC2:CC6.7, ISO:A8.24, HIPAA:164.312e]
└── incident_response/
    ├── ir_plan.pdf             [SOC2:CC7, ISO:A5.24, HIPAA:164.308a6]
    └── tabletop_log.pdf        [SOC2:CC7, ISO:A5.26, HIPAA:164.308a6]

GRC Platform Comparison

Platform Best For Price/yr SOC 2 ISO 27001 HIPAA GDPR
Vanta Fast SOC 2, US startups $1530K
Drata Automation depth $1835K
Secureframe Cost-effective $1020K
Sprinto SMB, global $1225K
Tugboat Logic Mid-market $2040K
Manual Budget-constrained $0 + time

Recommendation: For Series A startups, Vanta or Drata pays for itself in reduced auditor fees and internal time savings. Budget $1525K/year.

Compliance Maintenance Annual Budget

Item SOC 2 ISO 27001 HIPAA GDPR
Annual audit / surveillance $2560K $820K n/a (self-assessed) n/a (self-assessed)
GRC platform $1530K Shared Shared Shared
Annual training $38K Shared Shared Shared
Policy review $25K $25K $25K $25K
Total ongoing $45103K/yr +$1025K/yr +$515K/yr +$515K/yr