Acuvity (now Proofpoint)

https://acuvity.ai/ai-runtime-security/

Runtime enforcement targeting memory poisoning, unauthorised execution, identity spoofing per the OWASP LLM threat list. Visibility/control over MCP servers and locally-installed AI tools — the infrastructure layer where memory is most exposed.

At a glance

Type
MCP / Shadow-AI runtime enforcement
Tier
T1
Created
2023 (founded by cybersecurity veterans; acquired by Proofpoint Feb 12 2026)
Latest release
not applicable — not OSS
License
not applicable — not OSS
GitHub
not applicable — no GitHub repo
Pricing
enterprise pricing via Proofpoint (not public); contact sales
Funding
no public funding data found — pre-acquisition private company; acquired by Proofpoint for undisclosed amount

Taxonomy

storage
n/a
retrieval
agentic
persistence
session
update
read-only
unit
prompt
governance
auditable
conflict
n/a

When to use

Optimised for: governance + compliance + audit + adversarial hardening

Anti-fit: not for hobbyist / non-production use cases

Pros & cons

Pros

Enterprise DLP for AI products — protects against data exfiltration via memory writes/reads; backed by Proofpoint's enterprise channel.

Cons

Enterprise-tier pricing and complexity; smaller mind-share than Lakera or Microsoft Defender for AI.

Claims & capabilities

Acquired by Proofpoint Feb 2026 for integration into enterprise DLP / governance.

Technical surface

API surface
REST (typical SaaS REST + first-party SDK pattern; see vendor docs for language coverage)
Backend storage
custom
Deployment
on-prem or cloud (Proofpoint enterprise deployment); agentless approach
Embedding model
locked
Multi-tenancy
hard-isolation
MCP
Yes — Secure MCP servers (Model Context Protocol) is a core capability; protects MCP-based agent integrations
A2A
no data — searched proofpoint.com/us/platform/ai-security, acuvity.ai/, acuvity.ai/integrations/, acuvity.ai/blog/; A2A protocol not advertised
OpenTelemetry
no data — searched acuvity.ai, proofpoint.com/us/platform/ai-security, docs.acuvity.ai; OpenTelemetry export not advertised

Compare Acuvity (now Proofpoint) with…

Similar systems

Other memory governance, privacy & safety in the catalog, ranked by inbound references.

  • Enkrypt AI T1

    Applies guardrails at three points: (1) before write to vector DB, (2) before query reaches embedding model, (3) before response. Detects malicious instructions in stored memory before retrieval; scans for PII/PHI in/out. Text + image + voice modalities.

  • HiddenLayer AISec Platform 2.0 T1

    Targets the supply-chain / lineage layer rather than runtime memory writes. Model Genealogy tracks training/fine-tuning/modification history — catches poisoning baked in during training. AIBOM generates auditable inventory of model components + datasets. Runtime layer also monitors agentic workflows.

  • Lakera Guard / Lakera Red T1

    Screens every prompt, response, and retrieved document for indirect prompt injection — primary vector for memory poisoning. Treats memory as untrusted: anything written to or read from memory is adversarial until proven clean. Lakera Red provides "Agent Breaker" gamified red-teaming.

  • Mem0 Security / OpenMemory T1

    Commercial Mem0 ships SOC 2 / HIPAA, zero-trust access controls, BYOK encryption, real-time monitoring, audit logs, workspace governance as defaults. OpenMemory is the local self-hosted variant (Docker + FastAPI + Postgres + Qdrant) for privacy-first deployments.

  • Microsoft Agent Governance Toolkit T2

    Cross-Model Verification Kernel (CMVK) requires majority-voting agreement across multiple model calls before a memory-influenced action. Agent OS package intercepts every action (memory included) at sub-millisecond latency. MIT licensed.

  • OWASP Agent Memory Guard T3

    Open-source runtime defense. Enforces YAML policies on every memory read/write. SHA-256 baselines detect tampering, injection, sensitive-data leakage, protected-key modification, rapid-change anomalies. Forensic snapshots + rollback. Reference impl for OWASP ASI06 (Memory Poisoning).

Row last verified 2026-05-14. Catalog data is CC-BY-4.0 — see how to read this.