AgentReadyHomeAgent Listing

← AutoX

AutoX — agentic threat model

9.0AIVSS 9.0 · Critical

AutoX represents an extreme-risk profile due to its Level 4 physical autonomy, where software compromise directly translates to real-world physical harm, vehicle collisions, or fleet-wide disruption.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 10.0AARS uplift 0.0Factor sum 6.3/10Threat ×1.1Mitigation ×0.9
Autonomy of Action
1.00
Goal-Driven Planning
0.90
Self-Modification
0.10
Dynamic Tool Use
0.80
Persistent Memory
0.40
Contextual Awareness
1.00
Dynamic Identity
0.20
Multi-Agent Interactions
0.50
Non-Determinism
0.60
Opacity & Reflexivity
0.80

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 — The listing mentions 'AI driving systems' but does not specify the exact foundation models or neural network architectures used. Threats include adversarial physical attacks (e.g., adversarial stickers on road signs) and model evasion.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — The listing details sensor modalities (cameras, LiDAR, radar, IMUs, GPS) but does not describe the data operations, training pipelines, or local data storage. Threats include sensor data spoofing and training data poisoning.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — The proprietary orchestration and decision-making framework for Level 4 autonomy is not detailed. Threats include exploitation of the path-planning logic or hijacking of the vehicle control commands.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — The physical vehicle hosting environment and onboard edge-compute infrastructure are not specified. Threats include physical access to the vehicle's internal networks (e.g., CAN bus) and remote exploitation of wireless interfaces.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — Real-time safety guardrails, logging, and observability systems are not detailed in the public listing. Threats include silent perception failures, sensor drift, and lack of out-of-distribution detection in novel driving environments.

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

Not certain from the listing — The listing does not mention specific automotive cybersecurity standards (such as ISO/SAE 21434) or functional safety standards (ISO 26262). Threats include regulatory non-compliance and lack of standardized AI safety audits.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — While a 'robotaxi service' implies a centralized dispatch or fleet management system, specific multi-agent coordination or V2X protocols are not detailed. Threats include fleet-wide compromise via a single compromised dispatch agent.

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