Use this index to evaluate architecture, identity, governance, interoperability and assurance boundaries before a pilot or commercial commitment.
Control plane, detection plane, persistence, identity and deployment boundaries are documented in the architecture material.
OIDC is implemented through the existing NextAuth/engine identity boundary. SAML is not represented as generally available.
Organization-scoped access and analyst boundaries are enforced through the existing authenticated product surface.
The product separates public marketing surfaces from authenticated/customer workflows and applies server-side input validation.
Health/version boundaries and failure-safe API behavior are part of the web-to-engine integration contract.
SIEM, SOAR, webhook and STIX adapter contracts are documented without claiming undeployed connectors.
The public security policy provides the responsible disclosure path; incident handling remains deployment-specific.
No independent certification is claimed by this release.
Confirm deployment topology, environment ownership, network boundaries and operational responsibilities during technical evaluation.
Commercial support and SLA terms are scoped during contracting rather than represented as a universal technical guarantee.
A subprocessors list should be supplied for the actual customer deployment; this page does not invent a universal list.