About the Agentegrity Framework

Agentegrity (agent + integrity) is an open framework, discipline, and reference implementation for measuring and verifying the structural integrity of autonomous AI agents. Created by Cogensec and released under Apache 2.0, it instruments an existing agent loop with four cooperating evaluation layers (adversarial, cortical, governance, recovery) and emits a tamper-evident, hash-chained record of every reasoning step.

Supported Frameworks

Canonical Event Stream

Integrity Properties and Conformance Levels

Three integrity properties: Adversarial Coherence (AC, 40%), Verifiable Assurance (VA, 35%), Environmental Portability (EP, 25%), produce a weighted composite score, assessed against four conformance levels: Level 1 Aware, Level 2 Managed, Level 3 Verified, Level 4 Autonomous.

Key Resources

Glossary

Agentegrity
Open framework and discipline (agent + integrity) for measuring the structural integrity of autonomous AI agents. Created by Cogensec, released under Apache 2.0. Complements exogenous guardrails with endogenous, measurable security properties.
Adversarial Coherence (AC)
Agentegrity property. An agent has adversarial coherence if, for a defined set of adversarial perturbations applied across all input channels, its decision function produces outputs within tolerance of its baseline behavior. Covers prompt injection, jailbreaks, intent drift, and exfiltration framings arriving via tool responses, peer messages, or retrieved documents.
Environmental Portability (EP)
Agentegrity property. An agent has environmental portability if its integrity score is equivalent, within tolerance, across a defined set of deployment environments, including moves between digital and physical domains.
Verifiable Assurance (VA)
Agentegrity property. An agent has verifiable assurance if its integrity state is represented by an attestation record satisfying completeness, tamper-evidence, non-repudiation, and chain integrity.
Cortical Layer
One of Agentegrity's four evaluation layers. Scores whether the agent's own output stays inside the capabilities, scope, and constraints declared in its AgentProfile.
Adversarial Layer
Agentegrity layer that inspects incoming inputs (tool responses, peer messages, retrieved documents, user prompts) for prompt injection, jailbreak prefixes, exfiltration framings, and sociolinguistic intent drift.
Governance Layer
Agentegrity layer that applies operator-defined policy: rate limits, denylists, required approvals, structured deviations from a BaselineStore baseline. Policy rules are testable code rather than free-form prompts.
Recovery Layer
Agentegrity layer that watches for unrecoverable agent states and triggers checkpoint rollback, session termination, or operator handoff via FileCheckpoint or KMSCheckpoint.
Attestation Chain
Tamper-evident, hash-chained record produced by Agentegrity. Each evaluation record sets prev_hash = sha256(prior record), allowing end-to-end verification at session close. Records can be optionally signed via Ed25519 + JWS.
Canonical Event Stream
The five normalized event types every Agentegrity adapter emits: session_start, tool_call, tool_response, peer_message, session_end. Decouples the layer pipeline from any specific agent framework.
PDA Loop
Perception-Decision-Action loop. The attack-surface model Agentegrity uses to map where adversarial influence can enter an agent's reasoning process.
Measure-only Mode
Default Agentegrity operating mode. Layers score and record events but never block tool calls. Used for baseline calibration before enforcement.
Enforce Mode
Agentegrity operating mode enabled by setting enforce=True (Python) or enforce: true (TypeScript) on the adapter. Upgrades detected violations from recorded events to active refusals.
AgentProfile
Agentegrity declaration of an agent's allowed capabilities, scope, and safety constraints. Used by the cortical layer to score whether each step conforms.
Conformance Levels
The four Agentegrity conformance levels: Level 1 Aware, Level 2 Managed, Level 3 Verified, Level 4 Autonomous. An ascending maturity ladder rather than a pass/fail grade, assessed against the three properties (AC, EP, VA) and the four evaluation layers.

Frequently Asked Questions

What is Agentegrity?

Agentegrity (agent + integrity) is an open framework and discipline for measuring the structural integrity of autonomous AI agents. Created by Cogensec and released under Apache 2.0, it instruments an existing agent loop with four cooperating evaluation layers, adversarial, cortical, governance, recovery, and emits a tamper-evident, hash-chained record of every reasoning step.

How does Agentegrity differ from AI guardrails?

Guardrails are exogenous: they sit outside the agent and try to filter inputs and outputs. Agentegrity is endogenous: it measures the agent's own structural integrity: whether it stays inside its declared profile, resists adversarial inputs, recovers cleanly, and holds its score across deployment environments. The two are complementary; Agentegrity does not replace guardrails.

Which AI agent frameworks does Agentegrity support?

Agentegrity ships 14 first-party adapters. Python: Claude Agent SDK, LangChain / LangGraph, OpenAI Agents SDK, CrewAI, Google ADK, AutoGen, Agno, and AWS Bedrock Agents. TypeScript: Claude Agent SDK, LangChain JS, OpenAI Agents SDK, CrewAI JS, Google ADK, and the Vercel AI SDK. Each adapter translates framework-native events into Agentegrity's canonical event stream; the four evaluation layers downstream are shared.

What are the four Agentegrity layers?

Adversarial (detects prompt injection, jailbreaks, sociolinguistic intent drift, exfiltration framings in incoming inputs), Cortical (scores whether the agent's output stays inside its declared AgentProfile), Governance (applies operator policy and baseline deviation rules), and Recovery (handles checkpoint rollback, session termination, operator handoff).

What are the Agentegrity integrity properties?

Three: Adversarial Coherence (AC), weighted 40%; Verifiable Assurance (VA), weighted 35%; and Environmental Portability (EP), weighted 25%. The weighted composite is assessed against four conformance levels: Level 1 Aware, Level 2 Managed, Level 3 Verified, Level 4 Autonomous.

What is the Agentegrity attestation chain?

Every evaluation produces a record whose prev_hash field equals sha256 of the previous record. The chain is verifiable end-to-end at session close, providing non-repudiation of what the agent did and what each layer concluded. Records can be optionally signed using Ed25519 + JWS via the crypto extra.

What is the difference between measure-only and enforce mode?

Measure-only is the default: layers score and record events but never block tool calls. Setting enforce=True (Python) or enforce: true (TypeScript) on the adapter upgrades detected violations to active refusals. Most production deployments measure first, calibrate baselines, then enforce.

Is Agentegrity open source?

Yes. The full framework, specification, and reference adapters live at https://github.com/Cogensec/agentegrity-framework under the Apache 2.0 license. Cogensec maintains the project and ships an optional commercial agentegrity-pro receiver for enterprise deployments.

How do I install Agentegrity?

Python: pip install agentegrity (with optional extras like [crypto], [embedding], [adversarial_llm]). TypeScript: npm install @agentegrity/client plus the adapter for your framework, for example @agentegrity/langchain or @agentegrity/openai-agents. See the Quickstart at https://agentegrity.cogensec.com/docs/quickstart.

Who created Agentegrity?

Agentegrity was created by Cogensec, an AI security and research company and member of the NVIDIA Inception Program. The founding research paper, "Agentegrity: A Framework for Measuring Structural Integrity of Autonomous AI Agents Across Digital and Physical Domains" by Tarique Smith, is published at https://cogensec.com/research/agentegrity-framework.

Back to Agentegrity

The Agentegrity Taxonomy

A comprehensive classification of threats, defenses, and measurement for autonomous AI agent security across digital and physical domains.

Cogensec. "The Agentegrity Taxonomy v1.0." January 2026. github.com/Cogensec/agentegrity

Version 1.0 · January 2026 · Cogensec

Part I: Foundational Model

1. The Agent Architecture Model

The agentegrity taxonomy models an autonomous AI agent as a system executing a continuous Perception-Decision-Action (PDA) Loop within an Operating Environment, connected to External Systems through Trust Boundaries.

┌─────────────────────────────────────────────┐
│           OPERATING ENVIRONMENT              │
│  ┌───────────────────────────────────────┐   │
│  │          TRUST BOUNDARY               │   │
│  │  ┌─────────┐  ┌──────────┐  ┌──────┐ │   │
│  │  │PERCEPTION│→│ DECISION │→│ACTION│ │   │
│  │  └─────────┘  └──────────┘  └──────┘ │   │
│  │   SENSORS    MEMORY    ACTUATORS      │   │
│  └───────────────────────────────────────┘   │
│   EXTERNAL: HUMANS · AGENTS · OTHER · APIs   │
└─────────────────────────────────────────────┘

2. Domain Classification

CodeDomainDescriptionExamples
DDDigital DomainAgents operating entirely in software environmentsCode assistants, workflow orchestrators, data analysts, chatbots
PDPhysical DomainAgents controlling physical actuators or perceiving physical environmentsRobotic arms, autonomous vehicles, drones, industrial controllers
CDConvergent DomainAgents operating simultaneously across digital and physicalLogistics coordinators managing software + warehouse robots, smart building managers

3. Agent Capability Tiers

TierCapabilitiesAttack Surface Complexity
T1: ReactiveSingle-turn response, no tools, no memoryLow: perception and decision only
T2: Tool-UsingInvokes external tools and APIs, single-sessionMedium: adds action layer and tool trust
T3: PersistentRetains memory across sessions, maintains stateHigh: adds memory integrity surface
T4: PlanningMulti-step planning, autonomous task decompositionVery High: adds goal integrity and plan manipulation
T5: Multi-AgentCoordinates with other agents, delegates tasksCritical: adds inter-agent trust and cascade risk
T6: EmbodiedControls physical actuators, perceives physical environmentMaximum: adds physical safety surface

Part II: Threat Surface Taxonomy

4. Perception Layer Threats (T-P)

Threats targeting the agent's sensory inputs and data ingestion.

T-P1: Direct Input Manipulation

IDThreatDomainDescription
T-P1.1Direct Prompt InjectionDDAdversarial instructions embedded directly in user input to override agent behavior
T-P1.2Encoded Prompt InjectionDDAdversarial instructions hidden in non-obvious encodings (base64, Unicode, markdown, token manipulation)
T-P1.3Multi-Modal InjectionDDPDAdversarial instructions embedded in images, audio, or video consumed by the agent
T-P1.4Schema ManipulationDDMalformed or adversarial API schemas, tool definitions, or MCP server descriptors
T-P1.5Adversarial Sensor Input: VisualPDManipulated camera feeds, adversarial patches on physical objects, projected patterns
T-P1.6Adversarial Sensor Input: LiDARPDSpoofed point clouds, laser injection attacks, reflective surface exploitation
T-P1.7Adversarial Sensor Input: AcousticPDUltrasonic commands, adversarial audio, microphone interference
T-P1.8Adversarial Sensor Input: ProprioceptivePDManipulated joint position, force, or inertial measurement unit data
T-P1.9Adversarial Sensor Input: RadarPDRadar spoofing, jamming, or phantom object generation
T-P1.10Environmental ManipulationPDPhysical alteration of the operating environment to induce misperception

T-P2: Indirect Input Manipulation

IDThreatDomainDescription
T-P2.1Indirect Prompt InjectionDDAdversarial instructions embedded in documents, emails, web pages, or database records retrieved by the agent
T-P2.2Tool Output PoisoningDDMalicious data returned by a compromised or adversarial tool/API that the agent trusts
T-P2.3RAG PoisoningDDAdversarial content injected into vector databases or retrieval corpora consumed by the agent
T-P2.4Inter-Agent Message PoisoningDDCDAdversarial instructions or corrupted data delivered through messages from other agents
T-P2.5MCP Server ExploitationDDMalicious or compromised MCP server providing adversarial tool definitions or manipulated responses
T-P2.6Sim-to-Real Data PoisoningPDTraining data from simulated environments crafted to induce failure in physical deployment
T-P2.7Map/Model CorruptionPDManipulation of environmental maps, 3D models, or digital twins consumed by physical agents
T-P2.8Supply Chain Input PoisoningDDPDAdversarial content embedded in upstream data sources, pre-trained models, or dependency packages

T-P3: Perception Degradation

IDThreatDomainDescription
T-P3.1Input StarvationDDPDDenial or severe delay of expected inputs, causing the agent to operate on incomplete information
T-P3.2Sensor DegradationPDGradual reduction of sensor fidelity exploited to shift agent behavior imperceptibly
T-P3.3Context Window OverflowDDDeliberate flooding of context to push critical information out of the agent's attention window
T-P3.4Sensory Conflict InductionPDProviding contradictory data across multiple sensor modalities to induce decision paralysis

5. Decision Layer Threats (T-D)

Threats targeting the agent's reasoning, planning, and policy adherence.

T-D1: Goal and Objective Manipulation

IDThreatDomainDescription
T-D1.1Goal HijackingDDPDAdversarial input that overrides or redirects the agent's primary objective
T-D1.2Objective InjectionDDInsertion of new, unauthorized objectives into the agent's planning process
T-D1.3Priority InversionDDPDManipulation that causes the agent to prioritize a secondary or adversarial goal over its primary mission
T-D1.4Reward Hacking (Runtime)DDPDExploitation of the agent's reward or success criteria to produce technically compliant but harmful behavior
T-D1.5Safety Objective SuppressionPDAdversarial inputs that cause the agent to deprioritize safety constraints in its decision-making

T-D2: Reasoning Manipulation

IDThreatDomainDescription
T-D2.1Chain-of-Thought CorruptionDDAdversarial perturbation of the agent's explicit reasoning chain to produce flawed conclusions
T-D2.2Planning ExploitationDDPDManipulation of the agent's task decomposition to insert adversarial sub-tasks
T-D2.3Confidence ManipulationDDPDAdversarial inputs designed to inflate or deflate the agent's confidence in specific decisions
T-D2.4Counterfactual InjectionDDProviding the agent with false premises that logically lead to harmful conclusions
T-D2.5Temporal Reasoning AttackDDPDExploiting the agent's sense of urgency or timing to induce rushed, suboptimal decisions

T-D3: Policy and Constraint Evasion

IDThreatDomainDescription
T-D3.1Policy BypassDDPDAdversarial techniques that cause the agent to ignore or circumvent its defined operational policies
T-D3.2Role ConfusionDDInducing the agent to adopt a different persona, role, or authority level than intended
T-D3.3Instruction Hierarchy ManipulationDDManipulation of the perceived priority between system instructions, user instructions, and tool outputs
T-D3.4Safety Boundary ErosionPDGradual, incremental manipulation that shifts the agent's safety boundaries without triggering discrete policy violations
T-D3.5Ethical Constraint BypassDDPDAdversarial framing that causes the agent to rationalize actions it would normally refuse

T-D4: Memory Integrity Attacks

IDThreatDomainDescription
T-D4.1Short-Term Memory CorruptionDDCorruption of in-session context to influence immediate decisions
T-D4.2Long-Term Memory PoisoningDDInjection of persistent false beliefs, fabricated history, or adversarial policies into cross-session memory
T-D4.3Memory ErasureDDSelective deletion of critical context or policy information from the agent's memory store
T-D4.4False Memory ImplantationDDCreation of fabricated session histories or interaction records that the agent treats as genuine
T-D4.5Sleeper Memory InjectionDDDormant adversarial content planted in memory that activates only under specific trigger conditions
T-D4.6Belief Reinforcement LoopDDAdversarial content that causes the agent to reinforce false beliefs through self-reflection

6. Action Layer Threats (T-A)

Threats targeting the agent's tool use, output generation, and physical actuation.

T-A1: Tool and API Misuse

IDThreatDomainDescription
T-A1.1Unauthorized Tool InvocationDDAgent invokes tools outside its authorized scope, induced by adversarial input
T-A1.2Excessive Permission ExerciseDDAgent uses legitimate tool access but exceeds intended scope
T-A1.3Tool Parameter ManipulationDDAdversarial inputs cause the agent to pass harmful parameters to legitimate tools
T-A1.4Data Exfiltration via Tool UseDDAgent is induced to extract and transmit sensitive data through authorized tool channels
T-A1.5Credential LeakageDDAgent exposes API keys, tokens, or authentication credentials through tool calls or output
T-A1.6Side-Channel Tool ExploitationDDUsing tool invocation patterns, timing, or error responses to extract information about internal state

T-A2: Output Manipulation

IDThreatDomainDescription
T-A2.1Harmful Content GenerationDDAgent produces content that violates its content policies (toxic, deceptive, illegal)
T-A2.2Misinformation GenerationDDAgent generates and distributes false information presented as factual
T-A2.3Social Engineering OutputDDAgent is manipulated into producing persuasive content for phishing, fraud, or manipulation
T-A2.4Downstream Agent PoisoningDDAgent outputs specifically crafted to exploit known vulnerabilities in consuming agents

T-A3: Physical Actuation Threats

IDThreatDomainDescription
T-A3.1Actuation Hijacking: Gross MotorPDAdversarial control of primary movement systems (locomotion, flight, navigation)
T-A3.2Actuation Hijacking: Fine MotorPDAdversarial control of precision actuators (robotic grippers, surgical tools, assembly mechanisms)
T-A3.3Safety Envelope ViolationPDAdversarial inputs that cause the agent to exceed defined operational limits
T-A3.4Collision InductionPDManipulation that causes unintended physical contact between the agent and its environment
T-A3.5Oscillation/Instability InductionPDAdversarial inputs creating feedback loops that cause physical oscillation or instability
T-A3.6Fail-Safe SuppressionPDAttacks that prevent the agent from transitioning to its defined fail-safe state

7. System-Level Threats (T-S)

Threats that operate across the PDA loop or target the agent system architecture.

T-S1: Multi-Agent Threats

IDThreatDomainDescription
T-S1.1Cascade CompromiseDDCDCompromise of one agent propagating to others through trusted communication channels
T-S1.2Agent ImpersonationDDCDAdversary masquerading as a trusted agent in a multi-agent system
T-S1.3Swarm ManipulationPDAdversarial control of one agent in a coordinated swarm to induce collective failure
T-S1.4Task Delegation ExploitationDDManipulation of task routing to direct sensitive tasks to compromised agents
T-S1.5Consensus PoisoningDDCDCorrupting the shared state or consensus mechanism in cooperative multi-agent systems
T-S1.6Agent-to-Agent Prompt InjectionDDInjection attacks propagated through inter-agent communication protocols

T-S2: Trust Boundary Threats

IDThreatDomainDescription
T-S2.1Trust Boundary CollapseDDCDErosion of authentication or authorization between the agent and external systems
T-S2.2Privilege Escalation via AgentDDUsing the agent as a confused deputy to access resources beyond the adversary's direct authorization
T-S2.3Identity SpoofingDDCDFalsification of identity credentials presented to the agent by external systems or users
T-S2.4MCP Protocol ExploitationDDProtocol layer: malicious server registration, capability spoofing, session hijacking
T-S2.5Actuator Wear ExploitationPDLow-magnitude adversarial inputs that accelerate physical wear on actuators

T-S3: Temporal and Lifecycle Threats

IDThreatDomainDescription
T-S3.1Behavioral Drift InductionDDPDSlow, deliberate manipulation of the agent's behavior over extended time periods
T-S3.2Model Update ExploitationDDPDAttacking during model update windows when security configurations may be temporarily inconsistent
T-S3.3Training Data Retroactive PoisoningDDPDCompromising data sources used for fine-tuning or RLHF to introduce adversarial behaviors
T-S3.4Context Accumulation AttackDDExploiting long-running sessions where accumulated context gradually shifts agent behavior

T-S4: Convergent Domain Threats

IDThreatDomainDescription
T-S4.1Prompt-to-Physical ExploitCDAdversarial digital input causing unintended physical action
T-S4.2Physical-to-Digital ExploitCDAdversarial physical manipulation causing harmful digital actions
T-S4.3Domain Transition ExploitationCDAttacks exploiting configuration gaps during digital-to-physical mode transitions
T-S4.4Sim-to-Real Transfer AttackCDExploiting the domain gap between simulated training and physical deployment
T-S4.5Digital Twin DesynchronizationCDManipulation of the digital twin representation to diverge from physical reality

Part III: Defense Taxonomy

8. Endogenous Defenses (D-I)

Defenses embedded within the agent's decision architecture: the source of agentegrity.

D-I1: Perception Integrity

IDDefenseDescription
D-I1.1Adversarial Input DetectionEmbedded models that identify adversarial patterns in inputs before they reach the decision layer
D-I1.2Input Provenance VerificationCryptographic or behavioral verification of input source authenticity
D-I1.3Multi-Modal Consistency CheckingCross-referencing multiple sensor or data modalities to detect spoofing in any single channel
D-I1.4Input Anomaly ScoringReal-time statistical analysis of input distributions to flag deviations from expected patterns
D-I1.5Sensor Fusion IntegrityWeighted fusion algorithms that deprioritize sensor channels exhibiting anomalous behavior
D-I1.6Context Integrity VerificationValidation that retrieved context (RAG, memory, tool outputs) has not been tampered with

D-I2: Decision Integrity

IDDefenseDescription
D-I2.1Policy Enforcement ModelEmbedded cortical model that validates every decision against the agent's defined policy before execution
D-I2.2Chain-of-Thought MonitoringReal-time analysis of the agent's reasoning chain to detect manipulation or policy deviation
D-I2.3Goal Consistency VerificationContinuous validation that the agent's active objectives align with its authorized mission
D-I2.4Behavioral Baseline ComparisonRuntime comparison of current decision patterns against the agent's established behavioral baseline
D-I2.5Confidence CalibrationMechanisms that maintain calibrated uncertainty, preventing adversarial confidence inflation or deflation
D-I2.6Safety Constraint HardeningNon-overridable safety constraints that persist regardless of reasoning-layer manipulation
D-I2.7Adversarial Coherence MonitoringDetection of decision sequences that are individually compliant but collectively adversarial

D-I3: Action Integrity

IDDefenseDescription
D-I3.1Pre-Execution ValidationVerification of every planned action against authorized scope, parameters, and safety constraints
D-I3.2Tool Authorization EnforcementRuntime enforcement of tool-level permissions, preventing unauthorized invocations
D-I3.3Output Integrity ScreeningEmbedded screening of generated outputs for policy violations and adversarial content
D-I3.4Safety Envelope Enforcement (Physical)Hard limits on actuator commands that cannot be overridden by the decision layer
D-I3.5Rate and Magnitude LimitingConstraining the speed and scope of actions to prevent rapid large-scale harm
D-I3.6Actuation Boundary EnforcementPhysical-layer safety systems that terminate actuator commands exceeding defined parameters

D-I4: Memory Integrity

IDDefenseDescription
D-I4.1Memory Integrity HashingCryptographic integrity verification of stored memory contents
D-I4.2Memory Write ValidationScreening of all new memory entries for adversarial content before persistence
D-I4.3Belief Consistency AuditingPeriodic validation that stored beliefs, facts, and policies remain internally consistent
D-I4.4Memory Provenance TrackingTracking the source and timestamp of all memory entries to enable targeted remediation
D-I4.5Sleeper Detection ScanningPeriodic analysis of stored memory for dormant adversarial content matching known injection patterns

D-I5: Recovery Mechanisms

IDDefenseDescription
D-I5.1Behavioral Checkpoint and RestorePeriodic snapshots of verified-good behavioral state enabling rollback after compromise
D-I5.2Memory Quarantine and RemediationIsolation and cleaning of compromised memory segments without full system reset
D-I5.3Self-Diagnostic RoutineEmbedded diagnostic that periodically tests the agent's own decision integrity against known-good scenarios

9. Exogenous Defenses (D-E)

Defenses applied from outside the agent's decision architecture: complementary to but not substitutes for endogenous defenses.

IDDefenseDescription
D-E1Input GuardrailsPre-processing filters that screen inputs before they reach the agent
D-E2Output GuardrailsPost-processing filters that screen agent outputs before delivery
D-E3Network-Level ControlsAPI gateways, rate limiting, and network security applied at the infrastructure layer
D-E4Human-in-the-Loop OversightRequired human approval for high-risk actions or decisions exceeding defined thresholds
D-E5Audit LoggingComprehensive logging of all agent inputs, decisions, and actions for post-hoc analysis
D-E6Sandbox IsolationExecution of agent actions in constrained environments limiting blast radius
D-E7Least Privilege EnforcementInfrastructure-level restriction of agent permissions to minimum required scope
D-E8Inter-Agent AuthenticationCryptographic identity verification between agents in multi-agent systems
D-E9Physical Safety InterlocksHardware-level safety systems independent of the AI decision layer (emergency stops, physical limiters)

10. Defense Depth Classification

The agentegrity taxonomy classifies every defense by its cortical embedding depth, how deeply it integrates into the agent's decision architecture:

LevelNameDescriptionAgentegrity Impact
L0ExternalApplied outside the agent entirely (infrastructure, network)No contribution to endogenous security
L1BoundaryOperates at the agent's input-output boundary (guardrails, filters)Minimal: no residual defense
L2SurfaceOperates within the agent but only on inputs/outputs, not reasoningLow: detects but doesn't reason
L3IntegratedParticipates in the agent's reasoning process for specific functionsModerate: contributes to adversarial coherence
L4EmbeddedFully integrated into the agent's decision architecture across all PDA stagesHigh: primary source of agentegrity
L5ConstitutionalTrained into the model weights, inseparable from the agent's core capabilitiesMaximum: agentegrity is inherent

Defenses at L0–L1 are exogenous. Defenses at L2–L5 are endogenous. The agentegrity score is primarily determined by the effectiveness of L3–L5 defenses.


Part IV: Measurement Taxonomy

11. Agentegrity Properties

CodePropertyMeasuresPrimary Threats Assessed
ACAdversarial CoherenceDecisions stay within tolerance of baseline under perturbation, including drift over extended operationT-P1, T-P2, T-P3, T-D1, T-D2, T-D3, T-A1, T-A3, T-S3.1, T-S3.4
VAVerifiable AssuranceCompleteness, tamper-evidence, non-repudiation and chain integrity of the attestation recordT-S2 (all), D-I5 effectiveness
EPEnvironmental PortabilitySecurity transfer across deployment environmentsT-S4.3, T-S4.4, environmental dependency

12. Conformance Levels

LevelNameRequirementsOperational Meaning
Level 1AwareAgent profile defined, adversarial layer active, integrity scoring operationalBaseline established; deploy with enhanced oversight and restricted scope
Level 2ManagedAll four layers active, continuous monitoring with policy enforcement, human escalation and audit trailsDeploy with standard monitoring
Level 3VerifiedCryptographic attestation, formal property verification, continuous automated red teaming, cross-environment evaluationDeploy with confidence in adversarial environments
Level 4AutonomousSelf-healing responses, adaptive policy engine, proven portability, continuous adversarial adaptationDeploy autonomously with continuous assurance

Conformance levels are an ascending maturity ladder rather than a pass/fail grade, and the framework assigns no composite score range to a level: assignment depends on which capabilities are operational, not on a threshold alone.

13. Metrics Reference

13.1 Adversarial Coherence Metrics

MetricIDFormulaUnit
Adversarial Coherence RateM-AC1(R×1.0 + D×0.85 + G×0.40 + C×0.0) / NRatio [0,1]
Adversarial Coherence IndexM-AC2Weighted mean of per-category ACR valuesRatio [0,1]
Safety Envelope Violation RateM-AC3safety_violations / safety_targeted_attemptsRatio [0,1]: 0.0 required for Level 3/4
Zero-Day Coherence RateM-AC4ACR computed only on novel attack variationsRatio [0,1]
Behavioural Drift DistanceM-AC5Jensen-Shannon distance from baseline action distributionRatio [0,1]: lower is better
Perturbation Sensitivity IndexM-AC6max(drift_class) − min(drift_class)Range [0,1]

13.2 Verifiable Assurance Metrics

MetricIDFormulaUnit
Record CompletenessM-VA1decisions_recorded / decisions_evaluatedRatio [0,1]
Chain IntegrityM-VA2prev_hash verification across the full sessionBoolean: pass required for Level 3
Signature CoverageM-VA3records_signed / records_total (Ed25519)Ratio [0,1]
Independent VerifiabilityM-VA4Chain verifies without trusting the producing runtimeBoolean

13.3 Recovery Layer Metrics

MetricIDFormulaUnit
Checkpoint ValidityM-RL1Restored state verifies against a known-good baselineBoolean
Continuity DistanceM-RL2Jensen-Shannon distance from baseline after recoveryRatio [0,1]
Residual Compromise RateM-RL3compromise_effects_remaining / totalRatio [0,1]
Post-Recovery Chain IntegrityM-RL4Attestation chain unbroken across compromise and recoveryBoolean

13.4 Environmental Portability Metrics

MetricIDFormulaUnit
AC VarianceM-EP11.0 − σ(AC_envs) / μ(AC_envs)Ratio [0,1]
VA VarianceM-EP21.0 − σ(VA_envs) / μ(VA_envs)Ratio [0,1]
Portability Cliff CountM-EP3Environment transitions with >0.20 score dropCount: 0 is ideal
Domain Transfer LossM-EP4AC_primary − AC_worst_environmentDelta: lower is better

13.5 System-Level Metrics

MetricIDFormulaUnit
Peer AuthorityM-SY1peer_messages_from_declared_topology / peer_messages_totalRatio [0,1]
Role DriftM-SY2Jensen-Shannon distance from the baseline for the declared roleRatio [0,1]: lower is better
System Agentegrity ScoreM-SY30.60 × mean(A_individual) + 0.25 × PA + 0.15 × (1 − RD)Ratio [0,1]
Cascade Propagation SpeedM-SY4agents_compromised / time_elapsedRate: lower is better
Weakest Agent ScoreM-SY5min(A_individual) across all agentsRatio [0,1]

Part V: Assessment Methodology

14. Assessment Types

TypeScopeWhenCoverage
Full AssessmentAll 3 properties and all 4 layers, all applicable threat categoriesPre-deployment, quarterly, post-incidentComplete
Property AssessmentSingle property (AC, VA, or EP)Post-update, targeted improvement validationPartial
Continuous MonitoringAC automated testing and VA chain verification in productionOngoingAutomated subset
System AssessmentMulti-agent extension (individual + peer authority + role drift)Multi-agent deploymentsSystem-level
Physical AddendumSafety envelope, sim-to-real, fail-safe reliabilityPhysical and convergent domain agentsPhysical-specific

15. Assessment Coverage Matrix

RequirementARBCRICP
Threat categories tested≥3 per PDA layer≥3 perturbation classes≥5 confirmed compromises≥3 environments
Test instances per category≥50≥100≥500 cycles observedFull AR+BC per environment
Novel/zero-day variations≥1 per layerN/A≥1 from each PDA layerN/A

16. Weight Profiles

ProfileARBCRICPUse Case
General0.350.250.200.20Default for most assessments
Safety-Critical0.300.300.300.10Physical AI, medical, infrastructure
Multi-Agent0.400.200.200.20Systems with cascade risk
Cross-Environment0.250.200.150.40Heterogeneous deployment
Compliance0.250.300.250.20Regulatory assessment
Physical-First0.350.250.300.10Embodied agents with high safety requirements

Part VI: Regulatory & Standards Mapping

17. Framework Alignment

Regulation / StandardPropertyRelevant Taxonomy Elements
EU AI Act: Conformity AssessmentAC, VAT-D3 (policy evasion), T-A3 (safety), D-I2 (decision integrity)
EU AI Act: High-Risk System ReqsAC, VAM-AC5-6 (drift), M-RL1-4 (recovery), D-I5 (recovery mechanisms)
NIST AI RMF: GOVERNAllAgentegrity Policy, Assessment Types, Weight Profiles
NIST AI RMF: MAPACThreat Surface Taxonomy (T-P, T-D, T-A, T-S)
NIST AI RMF: MEASUREAC, VA, EPMetrics Reference (M-AC, M-VA, M-RL, M-EP)
NIST AI RMF: MANAGEAC, VAD-I5 (recovery), Continuous Monitoring, Degradation Curve
MITRE ATLASACThreat Surface Taxonomy: extends ATLAS to physical domain
OWASP Top 10 for LLMACT-P1.1 (prompt injection), T-A1.4 (data exfil), T-D4 (memory attacks)
ISO 10218 (Industrial Robots)AC, VAT-A3 (actuation threats), D-I3.4-6 (physical safety), M-AC3 (SEVR)
IEC 62443 (Industrial Automation)AC, EPT-S2 (trust boundaries), D-E7-9 (exogenous physical controls)
ISO/SAE 21434 (Automotive)AC, VAT-P1.5-9 (sensor attacks), T-A3.1 (actuation), T-S4.1 (prompt-to-physical)
NIST SP 800-82 (OT Security)ACT-A3 (actuation), T-S4 (convergent domain), D-E9 (physical interlocks)

Part VII: Taxonomy Governance

18. Version Control

This taxonomy is maintained as a living document. Changes follow the specification versioning protocol:

  • Major versions (2.0, 3.0): New Parts, structural reorganization, breaking changes to ID scheme
  • Minor versions (1.1, 1.2): New threat categories, new defenses, new metrics
  • Patch versions (1.0.1): Corrections, clarifications, editorial

19. Contribution Process

Community contributions are accepted via pull request to the agentegrity-framework repository. New threat entries must include: ID (following the hierarchical scheme), domain applicability, description, at least one concrete attack scenario, and mapping to relevant defense categories. New defense entries must include: ID, cortical embedding depth classification, description, and mapping to threats mitigated.

20. Open Questions

The following areas are identified for community input and future research:

  1. Quantum computing threats to AI agents, how do post-quantum concerns affect agent memory integrity and credential management?
  2. Biological agent systems: as AI agents integrate with biological systems (brain-computer interfaces, bioengineering), what new threat classes emerge?
  3. Autonomous agent-to-agent negotiation security: when agents negotiate with each other autonomously, what new manipulation vectors emerge beyond current multi-agent threats?
  4. Long-term behavioral drift measurement: what are the optimal observation windows and statistical methods for detecting sub-threshold drift?
  5. Physical agentegrity in unstructured environments, how does agentegrity assessment change when physical agents operate in fully unstructured environments (disaster response, deep sea, space)?

This taxonomy is maintained by Cogensec as a public resource for the agentegrity discipline.
cogensec.com · github.com/Cogensec/agentegrity