Security is built into the platform architecture.
ThreatLens is designed for security investigation training using synthetic telemetry rather than real customer security data. The platform architecture follows the same principles of isolation, access control, data protection, and operational security expected from modern enterprise software.
This page describes the platform's security architecture and engineering practices. It is not a compliance certification or security certification.
What the architecture is built around.
Authentication
Secure authentication for individuals and organizations, with support for password-based authentication and enterprise SSO where enabled. Sessions use short-lived access credentials and rotating refresh tokens, with sensitive authentication material protected from client-side storage.
Role-based access control
Access is governed by explicit roles and permissions — student, instructor, organization administrator, platform administrator. Capabilities are enforced centrally through shared authorization controls rather than scattered application-level checks.
Tenant isolation
Organization data is logically isolated at the data-access layer. Tenant-scoped queries are required to include the appropriate organization boundary, reducing the risk of accidental cross-tenant access.
Ground-truth protection
Scenario ground truth is protected from normal learner-facing APIs. Scoring infrastructure accesses answer keys through controlled internal paths, while learner-facing endpoints expose only the data required to conduct the investigation.
Rate limiting
API rate limits protect authentication, investigation, evidence, and other sensitive endpoints against automated abuse and excessive request activity.
Audit logging
Security-relevant and administrative actions are recorded through audit logging to provide traceability across the platform.
Secrets are kept outside the source repository and rotated when exposure is suspected. Data in transit is protected using TLS, while sensitive configuration data receives additional protection at rest. Requests are validated at application boundaries, and dependencies are continuously monitored for known security vulnerabilities.
Have a security question? Contact us at info@useclickbox.com.