GOVERNATLAS / PRODUCT DOSSIER

Virtue AI

Virtue AI describes an enterprise AI safety platform with evaluation and runtime guardrail capabilities.

THE DOCUMENTED SCOPE

What the current evidence describes.

Source-attributed capabilities and limits. Inspect the full record before drawing a conclusion.

vendor asserted

VirtueGuard is described as a family of policy and modality-specific guardrails. The current site announces Fortinet’s acquisition; contracting and module continuity require confirmation.

Inspect the evidence ↘
vendor asserted

AgentSuite-Blue is described as covering MCP tool inspection, action monitoring, shadow AI discovery and runtime trajectory visibility.

Inspect the evidence ↘
vendor asserted

Virtue AI describes AgentSuite-Red as agent red-teaming using sandboxed environments and reusable attack skills.

Inspect the evidence ↘

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Reconcile current contracting and module availability alongside the technical trial. The preserved site announces a Fortinet acquisition while describing AgentSuite and Virtue guardrail/testing products. Do not infer unchanged licenses or automatic integration with other Fortinet services. Identify the component that observes an agent trajectory and the component authorized to block a tool call.

What this record does not establish

The current acquisition banner is a corporate transition, not evidence of universal feature or license continuity. Advertised speed, accuracy, prevention and compliance outcomes are excluded from independent claims.

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

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

In an authorized synthetic agent sandbox, pair an allowed action with a prohibited mock call. Review any red-team finding separately from the runtime action trace, then interrupt the guardrail dependency and preserve the configured behavior. No production tools, live targets or customer data are used in this proposed exercise.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A current module/contract/deployment responsibility statement.
  2. A paired benign/prohibited-action trace and unavailable-dependency observation.

THE OPERATING DETAIL

Keep module scope and action evidence precise.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Identify the purchased boundary

Ask which named module, release, deployment option and support arrangement would cover the intended use. Keep that answer with the trial manifest. The acquisition announcement should prompt confirmation of the current service and agreement; it does not establish that every previously advertised integration or entitlement continues unchanged.

Separate sandbox and runtime

Run an authorized fictional tool-use scenario in a disposable environment. Preserve the attack input, agent trajectory and actual mock action. Compare what an offline adversarial exercise reveals with the observation available at the runtime enforcement point. Success in one path should not silently become evidence for the other.

Test an allowed exception

Include a benign case that resembles a prohibited action and define an escalation route. Inspect whether the reviewer can explain the decision using the effective policy and observed context. Keep false blocks, missed detections and inconclusive results separate; an advertised latency or coverage claim does not settle those trade-offs.

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.

01
vendor asserted

VirtueGuard is described as a family of policy and modality-specific guardrails. The current site announces Fortinet’s acquisition; contracting and module continuity require confirmation.

Source, dates & preserved provenanceVirtue AI — primary scope and current identity ↗

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

Artifact SHA-256: b5fd3bb59a93764a20ee33a1df8a9a8ff582ec4f2ac99b7f560db36e2d8be4c5

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

02
vendor asserted

AgentSuite-Blue is described as covering MCP tool inspection, action monitoring, shadow AI discovery and runtime trajectory visibility.

Source, dates & preserved provenanceVirtue AI — primary scope and current identity ↗

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

Artifact SHA-256: b5fd3bb59a93764a20ee33a1df8a9a8ff582ec4f2ac99b7f560db36e2d8be4c5

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

03
vendor asserted

Virtue AI describes AgentSuite-Red as agent red-teaming using sandboxed environments and reusable attack skills.

Source, dates & preserved provenanceVirtue AI — primary scope and current identity ↗

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

Artifact SHA-256: b5fd3bb59a93764a20ee33a1df8a9a8ff582ec4f2ac99b7f560db36e2d8be4c5

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

04
vendor asserted

Virtue AI describes an enterprise AI safety platform with evaluation and runtime guardrail capabilities. Scope: primary documentation only; no independent model test, fairness determination, causal finding or compliance approval.

Source, dates & preserved provenanceVirtue AI — primary scope and current identity ↗

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

Artifact SHA-256: b5fd3bb59a93764a20ee33a1df8a9a8ff582ec4f2ac99b7f560db36e2d8be4c5

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

Source register

Virtue AI — primary scope and current identity ↗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.

01

Can you provide a current module/contract/deployment responsibility statement for the selected configuration?

02

Can you provide a paired benign/prohibited-action trace and unavailable-dependency observation for the selected configuration?

03

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 ↗