AgentReadyHomeAgent Listing

← Apollo

Apollo — agentic threat model

8.6AIVSS 8.6 · High

Apollo presents a high-risk profile due to its background activity-tracking capabilities and direct integration with corporate billing systems, which could lead to sensitive data exposure or financial fraud if compromised.

OWASP AIVSS score rationale

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

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 utilizes commercial LLMs to generate compliant narratives. Threats include prompt injection that could manipulate billing descriptions or leak sensitive background activity data.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — requires continuous ingestion of background activity data (e.g., active windows, calendar events). Threats include data exfiltration of highly sensitive corporate/client data and poisoning of client/matter mapping databases.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — orchestrates background activity capture, narrative generation, and dispatching. Threats include insecure tool integration with local OS tracking APIs and downstream billing systems.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — likely deploys as a local background daemon or cloud-connected agent. Threats include local privilege escalation via the activity tracker or unauthorized access to stored API credentials.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — no explicit mention of guardrails or drift monitoring for narrative generation. Threats include silent failures in activity tracking or undetected drift in narrative compliance.

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

Not certain from the listing — mentions 'compliant' narratives and '20+ configurable settings' but lacks details on encryption, OAuth, or SOC2 compliance. Threats include unauthorized access to billing systems and credential theft.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — operates as a standalone digital worker. Threats include cascading failures if the target timekeeping system APIs change or are compromised.

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