Discovery
Find services in the evidence you supply.
Public DNS detection and IdP audit tools inspect customer-supplied files. Discovery can surface services for review; it does not block employee access or prove complete coverage.
AI security / Staff. Spend. Security.
Give Security and IT a clearer route from finding AI services to deciding what deserves inspection or control. Discovery, data inspection and runtime enforcement are separate tasks with separate prerequisites.
Executive report · October 2026 public edition
A practical security brief for executives
Four pages · PDF for download or a mobile-friendly reading version. Research findings are not proof of AInforce outcomes; product access depends on your configuration.
A practical working session
A domain scan, an identity review and a configured runtime control answer different questions. Treating them as interchangeable leaves important gaps in the review.
Discovery
Public DNS detection and IdP audit tools inspect customer-supplied files. Discovery can surface services for review; it does not block employee access or prove complete coverage.
Data inspection
Data inspection depends on supported inputs and the product area selected. Confirm data types, source permissions and configuration before treating a finding as a control.
Runtime controls
Runtime checks and policy enforcement require the relevant application traffic to connect to and use the configured control. A marketing page or inventory does not establish deployment coverage.
Scope matters
The public DNS detection and IdP audit workspaces are discovery tools, not inline enforcement. Runtime controls have a different setup and operate only within their connected, configured scope. No universal claim is made about every employee, browser, model or AI request.
Evidence and access
The DNS and identity audit tools accept customer-supplied files. Do not upload sensitive material unless your organization has approved that use. For a runtime discussion, bring an architecture and traffic-flow overview so the required connection and policy scope can be established.
Before you evaluate
No. DNS detection is a discovery workspace. A finding is a prompt for review, not a network block or proof that all AI services were found.
They use customer-supplied files. Review the file contents and your organization's handling requirements before upload.
No universal inspection claim is made here. Data inspection depends on the supported product area, source and configured connection.
The relevant application traffic must connect to a runtime control that is configured for the intended policy. Scope and prerequisites should be confirmed for each environment.
Staff. Spend. Security.
We can walk through the relevant product areas and name the data, access and configuration needed for each one.