AI security where work actually happens.

Aona observes workforce AI activity through an installed and configured browser plugin or native application. It is not an agentless network scanner or an identity-log discovery service. The 10,000+ tool catalogue describes risk-catalogue breadth; observed coverage depends on the deployed client and collection settings.

Yes, on supported application and input paths. Policies can use data, application and employee-group context to redact sensitive content or block a submission. Prompt and file handling differ by client and application, so validate the exact rule and path. A hard-block response does not offer an acknowledge-and-continue option.

Chrome, Edge, Firefox and Safari are production browser paths. Native Windows and macOS coverage varies by application, operating system and input path. Native AI-agent inspection is in limited rollout; it is not universal agent coverage or a remote agent kill switch. Use the coverage reference to define the path you want to validate.

Aona provides a live Microsoft Sentinel integration, an event API and signed outbound webhooks with OCSF-aligned event data. Confirm event scope, collection, delivery timing and ingestion configuration for your environment. Other SIEMs can consume the feed through a customer-managed integration; a packaged connector is not implied.

The Aona backend can run in your cloud, on-premises or on Aona-managed servers. Prompt processing is a separate choice: on the user device at the edge, in your cloud or on-premises, or on Aona-managed servers. Confirm the supported combination and responsibilities during deployment planning.

Bring an AI application, the browser or native client and operating system, a synthetic prompt or file, and the policy response you want to test. Include your preferred hosting and processing locations and any SIEM requirement. The session can then focus on the supported path and evidence needed for your evaluation.