AgentReadyHomeAgent ListingPricing

← Abridge

Abridge — agentic threat model

7.0AIVSS 7.0 · High

Abridge presents a high-impact risk profile due to its handling of highly sensitive Protected Health Information (PHI) and integration with Electronic Health Records (EHR). While its agentic autonomy is constrained by required clinician sign-off, vulnerabilities like prompt injection via patient dialogue or data breaches pose severe compliance and patient safety risks.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 8.2AARS uplift 0.54Factor sum 3.0/10Threat ×1.0Mitigation ×0.8
Autonomy of Action
0.30
Goal-Driven Planning
0.20
Self-Modification
0.00
Dynamic Tool Use
0.40
Persistent Memory
0.20
Contextual Awareness
0.70
Dynamic Identity
0.10
Multi-Agent Interactions
0.10
Non-Determinism
0.50
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 specialized automatic speech recognition (ASR) and clinical LLMs. Primary threats include clinical hallucinations, adversarial audio injection, and model bias leading to inaccurate medical summaries.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — processes highly sensitive audio recordings and patient-clinician dialogue. Primary threats include unauthorized retention of PHI, lack of secure data lineage, and data exfiltration of patient records.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — likely uses a structured pipeline (audio processing to EHR-compatible note generation) rather than an open-ended agentic framework. A key threat is indirect prompt injection, where a patient's spoken words maliciously manipulate the generated clinical note.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — requires highly secure, HIPAA-compliant cloud hosting with strict network isolation. Threats include container compromise or misconfigured cloud storage exposing sensitive clinical audio files.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — requires rigorous clinical validation, drift monitoring, and audit logging of clinician edits. Threats include silent degradation of transcription accuracy over time and insufficient logging of note modifications.

L6 · Security & Compliance (cross-cutting)✓ mapped

As an 'enterprise-grade' clinical tool, it must strictly align with HIPAA, HITECH, and SOC 2 Type II standards, integrating with EHR identity providers. Threats include unauthorized access to PHI, privilege escalation within the EHR, and regulatory compliance failures.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — likely operates as a downstream integration within EHR marketplaces (e.g., Epic App Orchard). Threats include API vulnerabilities in EHR integrations and cascading failures if the EHR schema changes.

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

These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology. Are you the vendor? Factual corrections are free.