What Orthalon can and cannot see
Coverage boundaries for each protected environment, so an unprotected path is never mistaken for a protected one.
Orthalon inspects AI interactions where one of its sensors sits in the path. Anything outside those paths is not observed, and the console says so rather than reporting it as safe. Use this page to decide which device and network controls you need alongside Orthalon.
Browser extension
| Path | Coverage | What closes the gap |
|---|---|---|
| Chrome and Edge, managed profile with the extension force-installed | Prompts, paste, file upload, copy and download on supported AI sites | — |
| Private / InPrivate / Incognito windows | Covered only when the extension is allowed in private windows. Otherwise the sensor reports private-window coverage as unsupported | Chrome: turn Incognito off with IncognitoModeAvailability; admins cannot switch an extension on in Incognito by policy, only the user can. Edge: require the extension in InPrivate with MandatoryExtensionsForInPrivateNavigation, or turn InPrivate off with InPrivateModeAvailability |
| A second, unmanaged browser profile | Not observed | Restrict sign-in to managed accounts with BrowserSignin and RestrictSigninToPattern (Chrome) or Edge's equivalent |
| Firefox | Pilot; not covered by release testing | Treat as unsupported until it is listed as supported |
| Safari and other browsers | Not observed | Restrict installation with device management |
| Extension disabled or removed | Not prevented unless force-installed; the sensor stops reporting and the fleet view marks it stale or uninstalled | Force-install the extension through policy |
Model API gateway
The gateway inspects only traffic sent through it: tools and SDKs whose base URL points at the gateway. A direct call to a model provider with a personal API key, or from a tool that ignores the configured base URL, is not observed. Close this with egress controls on your network or secure web gateway that allow model API hosts only through the gateway.
Desktop app
The distributed desktop build is for Windows 10 and 11. It inspects local model traffic it is configured to route and inventories MCP configurations. Native AI apps that do not use the routed path are not inspected; application blocking depends on the desktop app running and on the device's own application controls. Mobile devices are not covered.
MCP
Policy is enforced only for allowlisted stdio MCP servers launched through the Orthalon MCP agent. HTTP and SSE servers are inventoried but not mediated. Actions taken by an agent that Orthalon cannot see are labelled not observed, never safe.
Account identity
An AI account counts as corporate only when its sign-in domain is one of your organization's domains. Consumer domains count as personal, and anything else as external or unknown. Unknown accounts follow your unknown-account rule. They are never promoted to corporate.
Content Orthalon does not keep
Orthalon sends and stores metadata only: categories, decisions and salted hashes. It never sends prompts, file contents or matched values unless an administrator turns on encrypted evidence capture. Exports and SIEM events follow the same rule.