ciso

Classifies security risks and governs GDPR, LGPD, and PCI-DSS compliance decisions.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/beelabstudio/ai --skill ciso-beelabstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ciso
Source: https://github.com/beelabstudio/ai/tree/main/skills/c-level/ciso
Command: npx skills add https://github.com/beelabstudio/ai --skill ciso-beelabstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security findings, compliance obligations, and vendor risks often lack a clear decision owner, leaving teams unsure whether a vulnerability blocks a release or goes to the backlog. This Skill provides CISO-level risk governance: severity classification, compliance obligation mapping, and structured security decision records. ## Core Features & Use Cases - Risk Classification: Categorizes vulnerabilities into P0–P3 severity levels with defined response timelines and release-blocking criteria. - Compliance Management: Maps GDPR, CNPD, LGPD, PCI-DSS, and ePrivacy obligations to jurisdictions and data processing activities. - Security Review Gates: Provides pre-release checklists for features touching auth, payments, PII, or multi-tenant data, plus vendor security approval criteria. - Use Case: A penetration test reveals a privilege escalation flaw before launch. Use this Skill to classify it as P1, feature-flag the affected surface, define the 24-hour remediation plan, and document the compliance impact. ## Quick Start Ask the AI to act as the CISO and classify the severity of a discovered vulnerability, then produce a security decision record with remediation steps.

Frequently Asked Questions about ciso

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify the severity of a security vulnerability?▼

Use the P0–P3 risk classification matrix: P0 covers data breaches and auth bypasses requiring immediate release blocks, P1 covers privilege escalation needing 24-hour fixes, P2 covers issues like missing rate limiting fixed within a sprint, and P3 covers low-severity findings added to the backlog.

How do I decide if a security issue should block a release?▼

P0 issues such as data breaches or multi-tenant isolation failures always block releases, while P1 issues require feature-flagging the affected surface and fixing within 24 hours. P2 and P3 findings go to the sprint or maintenance backlog unless they amplify a higher-severity risk.

What compliance obligations apply when handling EU or Brazilian user data?▼

EU user data triggers GDPR obligations including consent, right to erasure, DPAs, and 72-hour breach notification, with CNPD registration for Portuguese subjects. Brazilian data triggers LGPD with similar data subject rights and a DPO requirement at scale.

What should a security review checklist include before shipping a feature?▼

The review gate requires a threat model, verified authentication and RBAC enforcement, multi-tenant isolation testing, input validation, encryption at rest and in transit, audit logging for sensitive operations, and a feature flag for instant rollback.

How do I evaluate a third-party vendor for security and privacy?▼

Check for SOC 2 Type II certification, an available Data Processing Agreement, data storage location meeting EU residency requirements, a defined breach notification SLA, and the ability to limit shared data to the minimum necessary.

When should I use a dedicated security skill instead of this one?▼

Use this Skill for risk governance and compliance decisions, not technical implementation. For hands-on security controls, auth/RBAC coding, or infrastructure hardening, consult the software-engineer, devops-engineer, or a project-specific security skill instead.