Encrypted on the wire
All traffic between your endpoints, browsers, identity sources, and Atomburst is encrypted in transit using TLS. Version & cipher details coming soon
A detection and response platform only works if you trust it with sensitive signal. Here's exactly how Atomburst handles, protects, and retains your data — and where we are on formal compliance.
The defaults below reflect how a cloud-native, multi-tenant platform should treat customer signal. Confirm each against production before relying on it.
All traffic between your endpoints, browsers, identity sources, and Atomburst is encrypted in transit using TLS. Version & cipher details coming soon
Stored data is encrypted at rest. Key-management details coming soon
Multi-tenant by design, with each client's data logically separated so one tenant can never read another's. Isolation model details coming soon
Role-based access, MFA for internal access, and audit logging on administrative actions. Full details coming soon
Hosting region and EU/UK data-residency options. Coming soon
Telemetry and event data is retained for a configurable window, then deleted. Exact window coming soon
We publish status, not aspiration dressed as fact. "In progress" means underway and not yet certified.
If you believe you've found a security vulnerability in any Atomburst or NSCA product, we want to hear from you. Report it privately and give us reasonable time to remediate before any public disclosure. We won't pursue legal action against good-faith research that respects user privacy and avoids service disruption.
Report to [email protected]. PGP key coming soon