Provenance Verification

​

Policy JSON

{
  "registry": {
    "verify_provenance": true,
    "require_hash": true,
    "models": [
      { "id": "gpt-4o", "version": "2024-08-06", "hash": "sha256:..." },
      { "id": "claude-3-sonnet", "version": "20240229" }
    ]
  }
}

policy = {
    "registry": {
        "verify_provenance": True,
        "require_hash": True,
        "models": [
            {"id": "gpt-4o", "version": "2024-08-06", "hash": "sha256:..."},
            {"id": "claude-3-sonnet", "version": "20240229"},
        ],
    }
}

​

What It Does

• Verifies model identity — confirms the model ID matches an approved entry
• Checks version strings — ensures the model version matches what was tested
• Validates hashes (when available) — SHA-256 hash verification for model integrity
• Denies requests if the model version doesn’t match or the hash fails verification
• Protects against model swaps, silent updates, and supply chain attacks

​

Example

{
  "action": "DENY",
  "risk_score": 0.9,
  "reasons": ["provenance_verification_failed"],
  "evidence": {
    "model_id": "gpt-4o",
    "expected_version": "2024-08-06",
    "actual_version": "2024-11-20",
    "hash_verified": false,
    "verification_type": "version_mismatch"
  }
}

​

Install

# Install via CLI
tealtiger policy install provenance-verification

# Or copy the JSON above into your tealtiger.config.json

​

Customize

​

Related

• Model Allowlist — Combine allowlisting with provenance verification
• Tool Allowlist — Basic — Control tool access alongside model verification
• EU AI Act — High Risk — Requires provenance tracking for high-risk AI
• TealRegistry Documentation — Full API reference