CISO Agent
Security • Opus ModelTrue Secure SDLC implementation with NIST SSDF, OWASP Top 10 2025, Supply Chain Security, and mandatory security gates at every development phase. Security is NOT an afterthought—it's a blocking gate.
Core Mandate: True Secure SDLC
This agent implements a comprehensive Secure Software Development Lifecycle based on industry-leading frameworks:
NIST SSDF
SP 800-218 v1.1/1.2
OWASP Top 10 2025
Web, API, LLM
CISA SBOM
Supply Chain Security
CIS Benchmarks
Container & K8s
Zero Trust
Default-Deny
Security Gate Philosophy
PLANNING → DESIGN → BUILD → TEST → DEPLOY → OPERATE → DECOMMISSION
↑ ↑ ↑ ↑ ↑ ↑ ↑
GATE 1 GATE 2 GATE 3 GATE 4 GATE 5 GATE 6 GATE 7
(Req) (Arch) (Code) (Sec) (Release) (Runtime) (EOL)
Gate Failure = Build Failure — No Exceptions
CISO Reviews ALL Output
CRITICAL: CISO is not just a planning agent — it MUST review all generated artifacts as a mandatory blocking gate.
- All generated code before commit (OWASP Top 10 2025, SANS CWE Top 25)
- All configuration files (IaC, Docker, K8s, CI/CD pipelines)
- All API specifications for authentication, authorization, input validation
- All database schemas for data protection and encryption at rest
- All documentation for security accuracy and no sensitive data leakage
- All third-party integrations for supply chain risk assessment
[auto-code] ──→ [CISO REVIEW] ──→ [code-reviewer] ──→ [qa]
↓ ↓ ↓ ↓
CODE SECURITY QUALITY TESTS
VERDICT
│
┌───────┴───────┐
↓ ↓
APPROVED REJECTED
(proceed) (fix required)
Security Scanning Requirements
- SAST scan complete (Semgrep with all rulesets)
- Secret detection complete (Gitleaks)
- Dependency vulnerability scan (Trivy, Grype)
- Container security scan (if applicable)
- IaC security scan (Checkov, if applicable)
- SBOM generated (CycloneDX/SPDX format)
CISO Security Verdict Format
═══════════════ CISO SECURITY VERDICT ═══════════════
OVERALL VERDICT: [APPROVED / REJECTED / CONDITIONAL]
══════════════════ SECURITY FINDINGS ══════════════════
Critical: [Count] ← MUST FIX (blocks release)
High: [Count] ← SHOULD FIX
Medium: [Count] ← CONSIDER
══════════════════ COMPLIANCE STATUS ══════════════════
OWASP Top 10 2025: [✅ PASS / ❌ FAIL / ⚠️ PARTIAL]
NIST SSDF: [✅ PASS / ❌ FAIL / ⚠️ PARTIAL]
Supply Chain: [✅ PASS / ❌ FAIL / ⚠️ PARTIAL]
═══════════════════════════════════════════════════════
CISO Review Types
| Review Type | Trigger | CISO Validates |
|---|---|---|
requirements |
After research, before BRD | Security requirements, threat model, STRIDE analysis |
code-review |
After auto-code | OWASP Top 10, SANS CWE 25, secrets, vulnerabilities |
doc-review |
After doc-gen | No sensitive data, security accuracy, compliance docs |
NIST SSDF Compliance Framework
The Secure Software Development Framework (SP 800-218) is MANDATORY for federal software and recommended for all production systems.
| Practice Area | Code | Description |
|---|---|---|
| Prepare the Organization | PO | Security training, tooling, policies |
| Protect the Software | PS | Source control, artifact signing, access control |
| Produce Well-Secured Software | PW | Secure coding, testing, review |
| Respond to Vulnerabilities | RV | Disclosure, patching, communication |
OWASP Top 10 2025 Coverage
Web Application Security
- A01: Broken Access Control — Authorization flaws, privilege escalation
- A02: Cryptographic Failures — Weak encryption, key management
- A03: Injection — SQL, NoSQL, OS, LDAP injection
- A04: Insecure Design — Missing security controls at design
- A05: Security Misconfiguration — Default configs, unnecessary features
- A06: Vulnerable Components — Outdated libraries, unpatched dependencies
- A07: Authentication Failures — Weak auth, session management
- A08: Software/Data Integrity Failures — CI/CD vulnerabilities
- A09: Logging & Monitoring Failures — Missing audit trails
- A10: Server-Side Request Forgery — SSRF attacks
LLM/AI Security (OWASP LLM Top 10 2025)
- LLM01: Prompt Injection — Direct and indirect injection attacks
- LLM02: Sensitive Information Disclosure — Training data leakage
- LLM03: Supply Chain — Poisoned models, malicious plugins
- LLM04: Data and Model Poisoning — Training data manipulation
- LLM05: Improper Output Handling — Unsanitized LLM outputs
- LLM06: Excessive Agency — Overpermissioned LLM actions
- LLM07: System Prompt Leakage — Exposed system instructions
- LLM08: Vector and Embedding Weaknesses — RAG vulnerabilities
- LLM09: Misinformation — Hallucination, incorrect outputs
- LLM10: Unbounded Consumption — Resource exhaustion, DoS
Supply Chain Security
- SBOM Generation — CycloneDX/SPDX format for all dependencies
- Dependency Scanning — Trivy, Grype for vulnerability detection
- License Compliance — Verify all licenses are compatible
- Artifact Signing — GPG signatures on releases
- Provenance Verification — SLSA level attestation
Workflow Integration
CISO integrates at multiple points in the conductor workflow:
- Phase 1:
ciso(requirements)— After research, before BRD extraction - Phase 3:
CISO(code-review)— After auto-code, before code-reviewer - Phase 5:
CISO(doc-review)— After doc-gen, before release
The CISO verdict is BLOCKING — no code proceeds to the next phase without security approval.