Skip to main content

Behavry — Compliance & Regulatory Mapping

Informational only. This document is provided for reference purposes. It does not constitute legal or compliance advice. Consult your compliance team, legal counsel, and qualified assessors for formal certifications, audits, or regulatory filings.


Overview

Behavry provides technical controls that map to requirements across multiple compliance frameworks, including SOC 2 Type II, ISO/IEC 27001:2022, NIST AI Risk Management Framework (AI RMF), the EU AI Act, GDPR, and HIPAA. The table below summarizes these mappings.


Control Mapping

Audit Logging & Monitoring

Control DescriptionFrameworkClause / ControlBehavry Feature
Log all AI system activitySOC 2CC7.2 — System MonitoringImmutable audit log (TimescaleDB hypertable) captures every tool call, policy decision, DLP finding, and latency measurement
Maintain audit trail integritySOC 2CC7.2 — Log IntegritySHA-256 hash chain across all audit events; tampering detectable by hash verification
Log and monitor user and system activityISO 27001A.8.15 Logging / A.8.16 MonitoringStructured JSON logs with agent_id, session_id, tool_name, policy_result, timestamp
Monitor AI-specific behaviorsNIST AI RMFMG-2.2 — Monitor AI System BehaviorBehavioral Monitor tracks per-agent rolling statistics; anomaly score calculated continuously
Detect behavioral anomaliesSOC 2CC7.3 — Anomaly DetectionBehavioral Monitor detects statistical deviations; raises ALERT events when thresholds exceeded
Monitor for security eventsISO 27001A.8.16 MonitoringEventBus publishes all events to real-time dashboard SSE stream and configurable webhooks

Access Control & Identity

Control DescriptionFrameworkClause / ControlBehavry Feature
Authenticate all AI agent requestsSOC 2CC6.1 — Logical AccessEvery proxy request requires a valid RS256 JWT issued via OAuth 2.1 client credentials flow
Enforce least-privilege accessSOC 2CC6.1 — Least PrivilegeRole-based permissions (e.g., filesystem:read) enforced at the proxy layer before any tool call reaches the target server
Verify agent identityNIST AI RMFMG-2.1 — AI Actor AuthenticationAgent identity bound to client_id + client_secret; session tracked by JWT jti claim
Revoke access on terminationSOC 2CC6.2 — RevocationAgent suspension and deprovisioning immediately invalidate issued tokens
Rotate credentialsSOC 2CC6.1Credential rotation endpoint (POST /api/v1/agents/{id}/rotate) replaces client_secret without downtime
Separate admin and agent identitiesISO 27001A.8.2 Privileged Access ManagementAdmin JWT (RS256, separate signing flow) and agent JWT are issued via different endpoints and carry different claims

Policy Enforcement

Control DescriptionFrameworkClause / ControlBehavry Feature
Enforce technical controls on AI actionsSOC 2CC6.6 — Boundary ProtectionOPA policy engine evaluates every tool call before forwarding; deny results in immediate rejection
Define and enforce acceptable use policiesNIST AI RMFGV-1.2 — Policies and ProceduresRego policies define allow/deny/escalate rules per agent type, tool, resource, and action
Maintain policy versioningSOC 2CC8.1 — Change ManagementPolicy version number incremented on each update; history maintained in DB
Test policies before activationISO 27001A.8.8 Management of Technical VulnerabilitiesPolicy evaluate endpoint (POST /api/v1/policies/{id}/evaluate) enables pre-activation testing against sample inputs
Prevent unauthorized AI model accessNIST AI RMFMG-2.2OpenAI and Anthropic API proxies gate all programmatic model access behind Behavry JWT + OPA policy check

Sensitive Data Controls (DLP)

Control DescriptionFrameworkClause / ControlBehavry Feature
Protect sensitive data from unauthorized disclosureSOC 2CC6.7 — Data Protection in TransitDLP scanner inspects all tool inputs and outputs; 12 built-in patterns (SSN, credit card, PII, keys, etc.)
Prevent exfiltration of PII and sensitive dataGDPRArt. 32 — Security of ProcessingDLP auto-blocks tool calls rated critical; lower severities raise alerts
Protect PHI / ePHIHIPAA§164.312(a)(1) — Access ControlDLP patterns include medical record number and HIPAA-relevant identifiers; critical findings are blocked
Log DLP findingsSOC 2CC7.2dlp_findings field in every audit event records all matched patterns with severity
Block outbound data to unauthorized endpointsSOC 2CC6.7OPA policies can deny web write operations to external domains; demonstrated in threat exfiltration demo

Human Oversight of AI

Control DescriptionFrameworkClause / ControlBehavry Feature
Maintain meaningful human oversight of AI systemsEU AI ActArt. 14 — Human OversightHuman-in-the-loop (HITL) escalation queue holds sensitive operations pending human approval
Ensure humans can override AI decisionsNIST AI RMFGO-1.7 — Human OverrideEscalation approve/deny endpoints allow human operators to permit or block held requests in real time
Log human oversight decisionsSOC 2CC7.2Escalation resolution (approver identity, timestamp, decision) recorded in audit log
Define escalation timeout policiesEU AI ActArt. 14Escalations automatically expire after configurable timeout; timed-out requests are treated as denied
Track escalation audit trailNIST AI RMFMG-4.2 — Risk MonitoringFull escalation lifecycle (created → pending → resolved) emits audit events visible in dashboard

Incident Response

Control DescriptionFrameworkClause / ControlBehavry Feature
Detect and alert on security incidentsSOC 2CC7.4 — Incident ResponseAlert system raises ALERT events for anomalies, DLP violations, and policy breaches
Notify stakeholders of high-severity eventsSOC 2CC7.4Webhook delivery module sends signed HTTP POST to Slack, PagerDuty, or custom SIEM endpoints for high/critical alerts
Maintain incident audit trailISO 27001A.5.24 — Information Security Incident ManagementAll alert events stored with full context (agent_id, session_id, tool_name, details)
Classify alert severitySOC 2CC7.4Alerts are classified as low, medium, high, or critical; webhooks filter by configurable minimum severity
Support threat hunting and forensicsISO 27001A.8.15Audit log queryable by agent, action, policy_result, time range; SSE stream for real-time investigation

Risk Assessment

Control DescriptionFrameworkClause / ControlBehavry Feature
Assess and score AI agent riskNIST AI RMFMG-2.2 — Risk AssessmentBehavry Risk Framework (BRF) risk scorer evaluates 6 dimensions: access, action, decision_scope, oversight, intent_drift, observability
Classify agents by risk tierNIST AI RMFGV-6.2 — AI Risk TiersRisk tiers (low / medium / high / critical) determine escalation thresholds and policy behavior
Recalculate risk on behavioral changeNIST AI RMFMG-2.2Risk score recalculated on demand and after behavioral anomaly alerts
Document AI system capabilities and risksEU AI ActArt. 11 — Technical DocumentationAgent registry captures agent_type, owner, assigned roles, and current risk tier

Encryption & Cryptographic Controls

Control DescriptionFrameworkClause / ControlBehavry Feature
Use strong cryptography for authentication tokensSOC 2CC6.1RS256 (RSA 2048+) JWT signing for all agent and admin tokens
Sign outbound webhook payloadsISO 27001A.8.24 — Use of CryptographyX-Behavry-Signature: sha256=<hmac> on all webhook deliveries; recipients should verify before processing
Never log sensitive credentialsSOC 2CC6.1API proxy (X-OpenAI-Key, X-Anthropic-Key) strips and never logs upstream API keys; client_secret stored as bcrypt hash

Framework Quick Reference

SOC 2 Type II (Trust Services Criteria)

Behavry primarily addresses the Security trust service category (CC6–CC8) with supporting controls in Availability (CC9) through its reliability design.

CC CategoryDescriptionCoverage
CC6.1Logical and physical access controlsIdentity Service, RBAC, JWT
CC6.2Account provisioning and revocationAgent lifecycle APIs
CC6.6Boundary protectionMCP Proxy, OPA policy enforcement
CC6.7Data protection in transitDLP scanner, TLS in production
CC7.2System monitoring and loggingAudit Logger, hash chaining
CC7.3Anomaly detectionBehavioral Monitor
CC7.4Incident responseAlerts, webhooks
CC8.1Change managementPolicy versioning

ISO/IEC 27001:2022

ControlDescriptionCoverage
A.5.24Information security incident managementAlert system
A.8.2Privileged access managementSeparate admin/agent identity flows
A.8.15LoggingStructured audit log
A.8.16Monitoring activitiesSSE dashboard, behavioral monitor
A.8.24Use of cryptographyRS256 JWT, HMAC webhook signing

NIST AI Risk Management Framework (AI RMF 1.0)

FunctionSub-categoryCoverage
GOVERNGV-1.2 — PoliciesRego policy management
GOVERNGV-6.2 — Risk TiersBehavry Risk Framework risk scoring
MAPMP-2.3 — Impact AssessmentDLP + alert severity classification
MEASUREMG-2.1 — AuthenticationAgent identity + JWT
MEASUREMG-2.2 — Monitor BehaviorBehavioral Monitor, anomaly detection
MEASUREMG-4.2 — Risk MonitoringEscalation audit trail
MANAGEGO-1.7 — Human OverrideHITL escalation queue

EU AI Act (High-Risk AI Systems)

ArticleRequirementCoverage
Art. 11Technical documentationAgent registry with type, owner, risk tier
Art. 14Human oversightHITL escalation with approve/deny/timeout
Art. 17Quality management systemPolicy versioning, audit trail, incident response

GDPR

ArticleRequirementCoverage
Art. 5(1)(f)Integrity and confidentialityDLP scanner, audit log, access controls
Art. 25Data protection by designDLP auto-block on critical findings
Art. 32Security of processingEncryption (JWT RS256), DLP, access controls

HIPAA

SectionRequirementCoverage
§164.312(a)(1)Access controlIdentity Service + RBAC
§164.312(b)Audit controlsImmutable audit log
§164.312(c)(1)IntegrityHash-chained audit events
§164.312(e)(2)EncryptionTLS in production (infra-level)

Evidence Collection Guide

For auditors and compliance teams: the following Behavry artifacts can serve as evidence for the controls listed above.

Evidence ArtifactLocation / APIRelevant Controls
Audit log exportGET /api/v1/audit/events (filterable by time range)CC7.2, A.8.15, Art. 32
Agent registryGET /api/v1/agentsCC6.1, GV-6.2
Policy definitionsGET /api/v1/policiesCC6.6, GV-1.2
Policy historyGET /api/v1/policies/{id} (version field)CC8.1
Alert logGET /api/v1/alertsCC7.3, CC7.4, A.5.24
Escalation logGET /api/v1/escalationsArt. 14, GO-1.7
Agent risk scoresGET /api/v1/agents/{id}/riskMG-2.2, GV-6.2
Behavioral baselinesGET /api/v1/agents/{id}/behaviorMG-2.2

Last updated: February 2026