Skip to main content
Vallum Threat Modelmanifest-tampering-evidence-provenance-certificationLast reviewed: 2026-07-01

Manifest Tampering in Evidence provenance certification

Analysis of manifest tampering when operating in the context of evidence provenance certification. Covers mechanism, preconditions, Vallum detection and prevention capabilities, limitations, and residual risk.

Attack Mechanism

In the context of evidence and certification: Attacker modifies an agent or tool manifest to alter declared capabilities, permissions, or identity without detection

Preconditions

Active evidence or certification workflow, accessible signing or verification endpoints, and existing evidence packages or certificates in the system

Observable Indicators

Evidence integrity failures, signature validation errors, unexpected certificate state changes, and provenance-chain discontinuities

Affected Assets

Evidence packages, certificates, signing keys, verification endpoints, and audit records

Enterprise Impact

Evidence integrity compromise, false certification claims, audit trail corruption, and regulatory compliance failures

Vallum Containment Strategy

Prevention Capability

Vallum provides authorization-layer controls that reduce attack surface but cannot prevent all variants of this threat without complementary infrastructure and application controls

Detection Capability

Vallum generates receipts and evidence records for authorization decisions that can be analyzed for anomalous patterns. Detection effectiveness depends on integration with customer monitoring infrastructure.

Evidence Produced

Evidence-integrity verification records, signature-validation receipts, and provenance-chain audit trails

Evidence NOT Produced

Network-level intrusion detection data, application-level business logic logs, model inference internals, or infrastructure security monitoring events

Known Limitations

Detection and evidence capabilities are limited to Vallum-managed authorization and evidence boundaries. Attacks that occur entirely within customer application logic, at the infrastructure level, or through social engineering channels are outside Vallum's detection scope.

Your Responsibilities

Implement application-level input validation, deploy infrastructure security monitoring, maintain incident response procedures, conduct regular security assessments, and integrate Vallum detection events with organizational SIEM

Residual Risk

Novel attack variants not covered by current detection patterns, attacks that bypass Vallum's authorization layer entirely, and time-of-check to time-of-use windows between detection and response

Relevant Titan Components

Titan VerifyTitan Sign

Need a threat assessment for your specific AI deployment?

Request a Vallum Threat Assessment

Legal boundary: This threat model is technical reference documentation. It does not constitute a penetration test, vulnerability assessment, or security certification. Threat descriptions are based on publicly documented attack patterns. Consult qualified security professionals for your specific threat landscape.