Keep control of what leaves.
The default Airlock workflow sends signed, policy-filtered evidence from a customer-controlled collector. Optional integrations have their own explicitly approved scopes.
How evidence crosses the boundary
Evidence that may leave
Algorithm families, TLS versions, certificate hashes, finding summaries, and configured policy results.
Salted component identifiers, CBOM counts, firmware hashes, and ledger roots. Privacy settings determine whether approved identifiers are retained or fingerprinted.
Ownership, remediation state, validation results, audit references, and signed proof events.
Excluded from the default Airlock workflow
Source code, private keys, passwords, tokens, raw firmware binaries, packet payloads, customer production records, and broad filesystem images. Review the generated collector configuration before running it.
Platform traffic metadata
Authorized platform administrators can inspect source IP, route template, HTTP method, status, duration and verified identity. The retained database stores a browser category; the recent bounded buffer includes a truncated user agent. Queries, bodies, cookies and authorization headers are excluded. Actual password/SAML outcomes, refreshes and supplied refresh-token revocations are separate from request history. Failed credentials are not trusted user identities. Defaults: 90 days for the new authentication journal and 7 days for retained request metadata, with configurable limits. Historical audit records and exported backups have separate retention. This is not session replay or a record of everything a visitor does; external IdP events require the provider's own logs.
Optional integrations
Repository scanning, remediation, proxies, and third-party integrations may require broader permissions than Airlock collection. Authorize these separately; the Airlock boundary does not describe every optional workflow.
Privacy policy Security reviewCustomer-controlled AI
AI is off until an organization admin approves a Data Control policy. Review the local filtering kit, read-only assistant, support permission and signed gateway receipts, with their explicit limitations.
AI data controls