AGENT SKILL

ciso-advisor

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
最近更新
2026-07-29
Stars
★ 0
Forks
1

01 前言 Front Matter

name
ciso-advisor
license
MIT
metadata
{ "author": "Alireza Rezvani", "domain": "ciso-leadership", "updated": 1772668800000, "version": "1.0.0", "category": "c-level", "frameworks": "risk-based-security, zero-trust, defense-in-depth", "python-tools": "risk_quantifier.py, compliance_tracker.py" }
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.

02 资源文件 5

03 SKILL.md 正文

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

Category Metric Target
Risk ALE coverage (mitigated risk / total risk) > 80%
Detection Mean Time to Detect (MTTD) < 24 hours
Response Mean Time to Respond (MTTR) < 4 hours
Compliance Controls passing audit > 95%
Hygiene Critical patches within SLA > 99%
Access Privileged accounts reviewed quarterly 100%
Vendor Tier 1 vendors assessed annually 100%
Training Phishing 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 sales CRO Answer questionnaires, unblock deals
New product features CTO/CPO Threat modeling, security review
Compliance budget CFO Size program against risk exposure
Vendor contracts Legal/COO Security SLAs and right-to-audit
M&A due diligence CEO/CFO Target security posture assessment
Incident occurs CEO/Legal Response 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

Request You 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]

04 同仓库更多 Skills

Heverton-web
Heverton-web/proj_livros

youtube-full

Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.

★ 0
Heverton-web
Heverton-web/proj_livros

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 0
Heverton-web
Heverton-web/proj_livros

write-a-skill

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.

★ 0
Heverton-web
Heverton-web/proj_livros

workflow-builder

Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.

★ 0
Heverton-web
Heverton-web/proj_livros

weekly-review

Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.

★ 0
Heverton-web
Heverton-web/proj_livros

webinar-marketing

When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).

★ 0