AgentReadyHomeAgent ListingPricing

← Louisa AI

Louisa AI — agentic threat model

7.7AIVSS 7.7 · High

Louisa AI presents a high-risk profile primarily due to its deep integration with sensitive internal corporate data sources (such as emails and CRMs) to map organizational relationships. While its autonomous action capabilities are limited, a compromise could lead to severe confidentiality breaches of proprietary business networks and deal pipelines.

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.6Factor sum 3.8/10Threat ×1.05Mitigation ×0.85
Autonomy of Action
0.30
Goal-Driven Planning
0.20
Self-Modification
0.10
Dynamic Tool Use
0.50
Persistent Memory
0.70
Contextual Awareness
0.80
Dynamic Identity
0.20
Multi-Agent Interactions
0.10
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 or fine-tuned proprietary LLMs to parse unstructured communication data and extract relationship entities. Threats include prompt injection that could bypass output filters to leak sensitive relationship metadata.

L2 · Data Operations✓ mapped

Louisa AI heavily ingests and processes highly sensitive internal data sources (emails, calendars, CRMs) to construct an enterprise relationship graph. This creates a high-value target for data exfiltration, unauthorized relationship mapping, and knowledge-base poisoning.

L3 · Agent Frameworks⚠ not certain from listing

Not certain from the listing — likely uses a proprietary orchestration framework to query internal databases and generate relationship recommendations. Vulnerabilities could include insecure tool integration with internal enterprise APIs.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — given its origin within Goldman Sachs, it likely supports secure VPC or enterprise cloud deployments. Threats include container compromise or unauthorized access to the underlying graph database hosting the relationship intelligence.

L5 · Evaluation & Observability⚠ not certain from listing

Not certain from the listing — no details are provided regarding real-time monitoring, drift detection, or guardrails. Gaps here could lead to undetected data access anomalies or silent failures in relationship mapping logic.

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

As an enterprise platform born out of a major financial institution, it must align with strict compliance standards (e.g., SOC 2, GDPR). However, robust access control is critical to prevent horizontal privilege escalation, ensuring users cannot view relationship maps they are not authorized to see.

L7 · Agent Ecosystem⚠ not certain from listing

Not certain from the listing — the platform appears to operate as a standalone enterprise intelligence system with no explicit multi-agent or external marketplace interactions described.

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.