Skip to main content
reopt Handbook
reopt Handbook
AI Security and Compliance Operations

Strategy and Governance

Risk GovernanceData ProtectionSecure Architecture

Security Controls

Prompt Injection DefenseAccess Control and SecretsAudit Readiness

Operations and Leadership

Incident ResponseBoard Reporting

Appendix

GlossaryVerificationUpdates
Handbook›AI Security and Compliance
한국어KOEnglishEN

AI Security and Compliance Operations

A practical CISO and CTO framework for operating AI products securely and auditably.

Written and reviewed by Eric Han · Co-founder & CTO, reopt

Recently Updated Chapters

  • Access Control and Secrets2026-10-23

    Govern human, service, and agent permissions with least privilege and rotation.

  • Audit Readiness2026-10-23

    Build evidence pipelines for AI controls before formal audits begin.

  • Prompt Injection Defense2026-10-23

    Defend AI systems against malicious instructions in user input, retrieved content, and tool output.

  • Risk Governance2026-10-23

    Create an AI risk governance loop with ownership, scoring, approval, and review.

  • Secure Architecture2026-10-23

    Design AI systems with policy boundaries, isolation, logging, and safe tool access.

October 23, 2026 review

Updated high-risk timelines and literacy changes after the AI Omnibus entered into force, while keeping Article 50's active obligations separate. Connected September's OWASP Agent Control Standard and the October 20 GenAI Red Teaming Manual 1.0 to runtime controls and reproducible checks. Legal classification, internal risk scores, and security frameworks remain separate records.

AI Omnibus entry into force · Article 50 FAQ

AI security cannot be solved by a checklist at release time. Teams need to design data boundaries, permission models, controls, and evidence paths from the beginning.

This handbook gives engineering and security leaders a shared operating model for AI risk, controls, audit readiness, incident response, and executive reporting.

Core View

AI compliance is an evidence system. The question is not only whether a control exists, but whether the organization can prove it worked when auditors or executives ask.

Operating Chain

Security Maturity

LevelStateOperating signalPromotion condition
L1 InitialReactive after incidentsPolicies and evidence are scatteredCommon risk register
L2 ManagedCore controls existAccess, approval, and logs are standardizedControl effectiveness is measured
L3 QuantifiedMetrics drive reviewResidual risk and coverage are visibleExecutive reporting is routine
L4 AssuredEvidence and detection are continuousTeams improve controls quarterlyRisk appetite guides investment

Contents

Ch1. Risk Governance

Identify, score, own, approve, and review AI risks.

Ch2. Data Protection

Classify data and design retention, encryption, and movement controls.

Ch3. Secure Architecture

Build policy-driven boundaries for AI systems and tools.

Ch4. Prompt Injection

Defend input, retrieval, and tool-calling surfaces.

Ch5. Access Control

Separate human, service, and agent permissions.

Ch6. Audit Readiness

Map controls to evidence before auditors ask.

Ch7. Incident Response

Prepare detection, containment, recovery, and communication.

Ch8. Board Reporting

Translate technical AI risk into executive decisions.

Glossary

Align terminology across engineering, security, and leadership.

Risk Governance

Create an AI risk governance loop with ownership, scoring, approval, and review.

On this page

October 23, 2026 reviewOperating ChainSecurity MaturityContents