GOVERNATLAS / PRODUCT DOSSIER

Proofpoint AI Security

Proofpoint describes AI security for people and agents, including visibility and controls for AI use and MCP connections.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Use the current Proofpoint offering as the product boundary; the Acuvity redirect is an identity transition, not another profile. Distinguish employee AI use, agent tool activity and MCP authorization. Confirm which product components are in the contract and how they share policy and identity context.

What this record does not establish

Acuvity redirects to this current Proofpoint offering and is not separately counted. Current Proofpoint product scope does not establish parity with every historical Acuvity capability.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

Model a synthetic employee-to-agent handoff and a mock MCP connection. Observe a permitted operation, a deliberately disallowed operation and the audit event for each. Re-run after changing the acting identity, preserving the current integration and source permissions.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A current Proofpoint component and legacy-transition scope statement.
An identity-aware handoff trace separating alerts from enforced outcomes.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

Proofpoint describes AI security for people and agents, including visibility and controls for AI use and MCP connections. Scope: primary documentation only; no independent product test or compliance determination.

Source, dates & preserved provenance

Proofpoint AI Security — current primary product documentation ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: c127a64c04e17162a389417a574f040ce1761da1659257ae7484a2e1569794d5

The hash identifies the preserved capture. The live source may have changed.

Source register

Proofpoint AI Security — current primary product documentation ↗vendor owned · captured 2026-10-16

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Can you provide a current Proofpoint component and legacy-transition scope statement for the selected configuration?

Can you provide an identity-aware handoff trace separating alerts from enforced outcomes for the selected configuration?

Which exact version, entitlements, data paths and responsible roles apply?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗