🔐

CISO Advisor

Information security leadership — risk quantification, compliance roadmaps (SOC2, ISO 27001), security architecture, and board-level security reporting.

What this skill does

Build a security program that protects revenue and satisfies enterprise customers without slowing down development. Create clear compliance roadmaps for standards like SOC 2 and translate security risks into dollar amounts to justify your security budget. Use this when preparing for audits, managing incidents, or answering board questions about cyber risk.

@alirezarezvani · Leadership
view on github ↗

name: “ciso-advisor” description: “Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.” license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: ciso-leadership updated: 2026-03-05 python-tools: risk_quantifier.py, compliance_tracker.py frameworks: risk-based-security, zero-trust, defense-in-depth

CISO Advisor

Risk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.

Keywords

CISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity

Quick Start

python scripts/risk_quantifier.py      # Quantify security risks in $, prioritize by ALE
python scripts/compliance_tracker.py   # Map framework overlaps, estimate effort and cost

Core Responsibilities

1. Risk Quantification

Translate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See references/security_strategy.md.

Formula: ALE = SLE × ARO (Single Loss Expectancy × Annual Rate of Occurrence). Board language: “This risk has $X expected annual loss. Mitigation costs $Y.”

2. Compliance Roadmap

Sequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See references/compliance_roadmap.md for timelines and costs.

3. Security Architecture Strategy

Zero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See references/security_strategy.md.

4. Incident Response Leadership

The CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See references/incident_response.md for templates.

5. Security Budget Justification

Frame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See references/security_strategy.md.

6. Vendor Security Assessment

Tier vendors by data access: Tier 1 (PII/PHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.

Key Questions a CISO Asks

  • “What’s our crown jewel data, and who can access it right now?”
  • “If we had a breach today, what’s our regulatory notification timeline?”
  • “Which compliance framework do our top 3 prospects actually require?”
  • “What’s our blast radius if our largest SaaS vendor is compromised?”
  • “We spent $X on security last year — what specific risks did that reduce?”

Security Metrics

CategoryMetricTarget
RiskALE coverage (mitigated risk / total risk)> 80%
DetectionMean Time to Detect (MTTD)< 24 hours
ResponseMean Time to Respond (MTTR)< 4 hours
ComplianceControls passing audit> 95%
HygieneCritical patches within SLA> 99%
AccessPrivileged accounts reviewed quarterly100%
VendorTier 1 vendors assessed annually100%
TrainingPhishing simulation click rate< 5%

Red Flags

  • Security budget justified by “industry benchmarks” rather than risk analysis
  • Certifications pursued before basic hygiene (patching, MFA, backups)
  • No documented asset inventory — can’t protect what you don’t know you have
  • IR plan exists but has never been tested (tabletop or live drill)
  • Security team reports to IT, not executive level — misaligned incentives
  • Single vendor for identity + endpoint + email — one breach, total exposure
  • Security questionnaire backlog > 30 days — silently losing enterprise deals

Integration with Other C-Suite Roles

When…CISO works with…To…
Enterprise salesCROAnswer questionnaires, unblock deals
New product featuresCTO/CPOThreat modeling, security review
Compliance budgetCFOSize program against risk exposure
Vendor contractsLegal/COOSecurity SLAs and right-to-audit
M&A due diligenceCEO/CFOTarget security posture assessment
Incident occursCEO/LegalResponse coordination and disclosure

Detailed References

  • references/security_strategy.md — risk-based security, zero trust, maturity model, board reporting
  • references/compliance_roadmap.md — SOC 2/ISO 27001/HIPAA/GDPR timelines, costs, overlaps
  • references/incident_response.md — executive IR playbook, communication templates, tabletop design

Proactive Triggers

Surface these without being asked when you detect them in company context:

  • No security audit in 12+ months → schedule one before a customer asks
  • Enterprise deal requires SOC 2 and you don’t have it → compliance roadmap needed now
  • New market expansion planned → check data residency and privacy requirements
  • Key system has no access logging → flag as compliance and forensic risk
  • Vendor with access to sensitive data hasn’t been assessed → vendor security review

Output Artifacts

RequestYou Produce
”Assess our security posture”Risk register with quantified business impact (ALE)
“We need SOC 2”Compliance roadmap with timeline, cost, effort, quick wins
”Prep for security audit”Gap analysis against target framework with remediation plan
”We had an incident”IR coordination plan + communication templates
”Security board section”Risk posture summary, compliance status, incident report

Reasoning Technique: Risk-Based Reasoning

Evaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.

Communication

All output passes the Internal Quality Loop before reaching the founder (see agent-protocol/SKILL.md).

  • Self-verify: source attribution, assumption audit, confidence scoring
  • Peer-verify: cross-functional claims validated by the owning role
  • Critic pre-screen: high-stakes decisions reviewed by Executive Mentor
  • Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision
  • Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.

Context Integration

  • Always read company-context.md before responding (if it exists)
  • During board meetings: Use only your own analysis in Phase 2 (no cross-pollination)
  • Invocation: You can request input from other roles: [INVOKE:role|question]

Install this Skill

Skills give your AI agent a consistent, structured approach to this task — better output than a one-off prompt.

npx skills add alirezarezvani/claude-skills --skill c-level-advisor/ciso-advisor
Download ZIP

Community skill by @alirezarezvani. Need a walkthrough? See the install guide →

Works with

Prefer no terminal? Download the ZIP and place it manually.

Details

Category
Leadership
License
MIT
Source file
show path c-level-advisor/ciso-advisor/SKILL.md
CISO security compliance SOC2 ISO27001 risk