15 of 15 requirements
Export view:Audit & Evidence
AUD · 1Restrict and audit access to raw prompt content
Provide RBAC controls over who can read full prompt content, and record each access to it.
- Why it matters
- Raw prompts are among the most sensitive data the control holds, so access must be limited and logged.
- How to verify
- Only an authorized role can open full prompt content, and each access is recorded.
Area: Audit & Evidence
Platform, Privacy & Assurance
PLT · 14- PLT-001Documentation
Minimize endpoint and network architecture risk
Support agentless and optional-agent patterns, and avoid kernel mode, reverse proxy and major network changes unless justified and tested.
- Why it matters
- Kernel components, proxies and network changes add operational risk that should be justified.
- How to verify
- The vendor documents the deployment architecture and justifies any privileged component.
Area: Platform, Privacy & Assurance
Disclose where decisions are enforced and how the control fails
Enforce before submission, so a blocked payload is never sent and a denied tool call never runs. State where each decision is evaluated (device, browser or cloud), whether TLS interception, a forward proxy or a managed certificate is required, and whether each surface fails open or fails closed.
- Why it matters
- Where a decision runs and how it fails decide whether data is actually stopped.
- How to verify
- The vendor documents enforcement points and failure modes per surface, and the pilot confirms them.
Area: Platform, Privacy & Assurance
- PLT-003Proof of value
Deploy silently through endpoint management with release controls
Deploy and update every component silently through the buyer's endpoint management tools on Windows, macOS and Linux and all major browsers, with release rings, version pinning, rollback and a central view of deployment health by device.
- Why it matters
- Deployment is where enterprise controls most often fail.
- How to verify
- Pilot devices are deployed silently through your endpoint management, with deployment health visible.
Area: Platform, Privacy & Assurance
- PLT-004Live test
Support Linux endpoints
Provide Linux visibility or document an equivalent coverage method.
- Why it matters
- Engineering teams on Linux are often the heaviest AI users.
- How to verify
- AI use on a pilot Linux endpoint is visible, or an equivalent method is shown.
Area: Platform, Privacy & Assurance
- PLT-005Walkthrough + Documentation
Support network-based AI traffic detection where the architecture requires it
Integrate with SASE or network controls, identify AI hosts and protocols, and state whether the implementation is passive or inline.
- Why it matters
- Some architectures need network-level coverage, and the difference between passive and inline matters.
- How to verify
- The vendor shows the network integration and states whether it is passive or inline.
Area: Platform, Privacy & Assurance
- PLT-006Documentation + Proof of value
Scale enforcement and telemetry to the full population
Demonstrate capacity, latency and availability, and dashboard, drill-down, search and export performance, at the target scale.
- Why it matters
- A control proven at a few thousand users can behave like a different product at full scale.
- How to verify
- The vendor provides a reference at your scale and demonstrates console performance on pilot data.
Area: Platform, Privacy & Assurance
Resist common circumvention paths
Test disabling the extension, switching browser or private mode, personal accounts and desktop or CLI routes; document residual gaps.
- Why it matters
- A control that is easy to bypass gives false assurance.
- How to verify
- Pilot testers try disabling the extension, switching browser and using CLI routes; record residual gaps.
Area: Platform, Privacy & Assurance
Separate administrative roles, and authenticate them through enterprise SSO
Separate policy, approval, administration, investigation and exception duties; authenticate administrators through enterprise SSO; apply least-privilege roles over policy, alerts, raw prompts, exports and dashboards; and record administrative and investigative actions.
- Why it matters
- Whoever can change policy or read prompts holds a lot of power, so roles must be separated and every action recorded.
- How to verify
- Show separate policy, investigation and exception roles, SSO login and the record of an admin action.
Area: Platform, Privacy & Assurance
- PLT-009Documentation + Walkthrough
Control telemetry residency, retention, encryption, deletion and masking
Validate region, retention period, encryption, deletion behavior, identity masking and exclusions with Legal and Privacy.
- Why it matters
- Residency, retention and masking are the first questions privacy and legal teams ask.
- How to verify
- The vendor documents region, retention, encryption, deletion and masking, and shows the settings.
Area: Platform, Privacy & Assurance
- PLT-010Documentation
Offer required hosting regions
Document processing and storage locations, regional failover, subprocessor boundaries and tenant residency enforcement.
- Why it matters
- Where data is processed and stored is often a contractual and legal requirement.
- How to verify
- The vendor documents processing and storage locations, failover and subprocessor boundaries.
Area: Platform, Privacy & Assurance
- PLT-011Documentation + Walkthrough
Inspect uploaded content without permanent file retention
Webhook, pointer or in-place inspection so source files stay in enterprise-controlled storage.
- Why it matters
- Copying every uploaded file into another vendor's storage creates a second copy to protect.
- How to verify
- The vendor documents and shows how uploads are inspected without permanent retention.
Area: Platform, Privacy & Assurance
- PLT-012Walkthrough
Support pseudonymized and aggregate-only views where required
Provide role-scoped views that withhold individual identity while preserving team, department and tool-level analysis, so monitoring can proceed where works councils, unions or local law restrict individual attribution.
- Why it matters
- Where works councils or local law restrict individual attribution, monitoring still has to be possible.
- How to verify
- Pilot data viewed at team level with individual identity withheld.
Area: Platform, Privacy & Assurance
- PLT-013Walkthrough + Documentation
Limit monitoring scope by design
Monitor AI destinations and agent activity only, not general browsing. Minimize captured content and allow full capture to be switched off, ring-fence named individuals such as executives, exclude personal conversations from analytics, and document the configuration for privacy, legal and workforce review.
- Why it matters
- Works councils and privacy teams judge the architecture, not the policy document.
- How to verify
- Show that non-AI browsing is not captured, a ring-fenced user is excluded, and the configuration is documented.
Area: Platform, Privacy & Assurance
- Why it matters
- Standard assurance should be evidenced, not assumed.
- How to verify
- Current SOC 2 Type II report, ISO 27001 certificate and privacy terms are provided.
Area: Platform, Privacy & Assurance