AgentReadyHomeAgent Listing

← Document Intelligence Agent

Document Intelligence Agent — agentic threat model

6.4AIVSS 6.4 · Medium

The Document Intelligence Agent presents a low agentic risk profile due to its narrow, utility-focused scope of transforming documents into structured text. Its primary security risks are data-centric, specifically indirect prompt injection via malicious documents and the exposure of sensitive data processed by the system.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 5.8AARS uplift 0.63Factor sum 1.5/10Threat ×1.0Mitigation ×1.0
Autonomy of Action
0.20
Goal-Driven Planning
0.10
Self-Modification
0.00
Dynamic Tool Use
0.10
Persistent Memory
0.10
Contextual Awareness
0.30
Dynamic Identity
0.00
Multi-Agent Interactions
0.00
Non-Determinism
0.40
Opacity & Reflexivity
0.30

Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.

MAESTRO 7-layer threat model

Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.

L1 · Foundation Models⚠ not certain from listing

Not certain from the listing — likely uses a vision-language model or standard LLM for OCR and extraction. It is highly vulnerable to indirect prompt injection embedded within uploaded documents, which could manipulate the structured output.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — processes uploaded documents which may contain highly sensitive PII, financial, or proprietary data. Risks include data leakage, unauthorized access to document stores, and lack of secure data deletion policies.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — likely uses a basic orchestration pipeline to ingest, chunk, and parse documents. Vulnerabilities include insecure handling of malformed files and lack of input validation before passing content to the LLM.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — requires secure hosting to process user files. Vulnerable to server-side request forgery (SSRF) or remote code execution (RCE) if underlying document parsing libraries (e.g., PDF/image parsers) contain unpatched vulnerabilities.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — requires schema validation and drift detection to ensure extraction accuracy. Lack of observability could lead to silent failures where corrupted or hallucinated data is ingested into downstream databases.

L6 · Security & Compliance (cross-cutting)⚠ not certain from listing

Not certain from the listing — handling user documents necessitates strict compliance with data privacy regulations (e.g., GDPR, HIPAA). The listing does not specify encryption standards, access controls, or data retention policies.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — appears to operate as a standalone utility with no multi-agent coordination or ecosystem integration described.

MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).