Trust Center
Security at CYBERWARE
How we protect the Virtual SOC platform and cwAWARE Academy. We document real practices — no certifications we do not have yet.
Encryption in transit and at rest
All platform traffic is served over HTTPS/TLS. Data in PostgreSQL (Neon) and objects in AWS are encrypted at rest. Connector secrets and sensitive tokens are hashed or encrypted with managed keys before they are stored.
Multi-tenant isolation
Each organization runs on its own tenant identifier (socId / organization id). Application queries filter by organization; superadmin/org_admin/analyst roles are segregated by RBAC. Internal isolation tests cover cross-tenant leaks.
Authentication
SOC uses Better Auth with httpOnly sessions, mandatory email verification for new accounts, enterprise SSO (Google Workspace and Microsoft Entra ID), and optional TOTP 2FA. Administrative roles (superadmin and org_admin) must enable 2FA before accessing admin panels. Academy keeps its own session system with SHA-256 hashed tokens in the database.
AWS infrastructure
The app is deployed with SST on AWS (Lambda/OpenNext, S3 storage, SES email, and Amazon Bedrock for AI-assisted recommendations). We do not send customer data to third-party models outside the configured AWS perimeter.
Retention and deletion
Findings, campaigns, and training data are kept while the account or organization is active, except for customer deletion requests or legal requirements. After offboarding we can delete or anonymize tenant data on written request.
Report a vulnerability
If you find a security issue, email security@cyberwarelab.com. We welcome responsible disclosure: describe the impact, reproduction steps, and avoid accessing other customers’ data. We will reply as soon as we can.