How We Protect Your Data

Security is not a feature we add — it's how we build. Here's an honest, technical overview of the controls in place and what's on our roadmap.

Security Controls In Production

These protections are live and operating now for every Strata Security customer.

🔒
✓ Live

Encryption in Transit

All traffic between your browser and our servers uses HTTPS. Both the website and the API send an HSTS header, so browsers will not connect to them over plain HTTP.

🗄️
✓ Live

Encryption at Rest

Data stored in Supabase and Upstash Redis is encrypted at rest by the underlying cloud infrastructure. OAuth tokens and webhook signing secrets stored in the database are additionally encrypted with Fernet (AES-128 in CBC mode, authenticated with HMAC-SHA256).

🔑
✓ Live

Secure Authentication

Authentication is managed by Supabase Auth with bcrypt-hashed passwords. The signup form requires passwords of at least 10 characters with a letter and a number or symbol. New accounts are sent an email verification link, and unverified accounts are prompted to verify.

👥
✓ Live

Role-Based Access Control

Organizations have owner, admin, and member roles with distinct permission levels. All API endpoints enforce role checks server-side. No one can grant a role higher than their own, and only the owner can change the owner role.

🏗️
✓ Live

Data Isolation (Row-Level Security)

The API enforces organization access in code on every request, so each organization can only reach its own scans, findings, files, members, and settings. Supabase Row-Level Security (RLS) policies add a database-layer guard against direct access from the browser.

📦
✓ Live

Secure File Handling

Uploaded archives are validated before extraction. ZIP bomb protection limits maximum uncompressed size, compression ratio, and entry count. File type and size limits are enforced server-side. Malformed archives are rejected before any processing begins.

🛡️
✓ Live

File Reputation Checks

Uploaded files are optionally checked against VirusTotal's file reputation database using a cryptographic hash. Only the SHA-256 hash is sent — never the file content itself.

⏱️
✓ Live

Rate Limiting

API endpoints are rate-limited per IP address using fixed-window counters, with tighter Redis-backed limits on scan uploads, scan API calls, and public forms. These limits protect against scraping, upload abuse, and form spam.

🌐
✓ Live

CORS and CSP

API CORS headers restrict cross-origin requests to trusted frontend origins. Content Security Policy (CSP) headers restrict what resources the frontend can load, mitigating XSS attacks.

🔐
✓ Live

Secure OAuth Integration

GitHub and GitLab OAuth flows use HMAC-signed, single-use state tokens to prevent CSRF attacks. OAuth access tokens are stored encrypted in the database. GitLab access is read-only; GitHub access uses the repo scope, which GitHub grants as read and write.

🚨
✓ Live

Error Monitoring

Application errors are captured via Sentry in real time. This allows us to detect and respond to unexpected failures, including security-relevant errors, before they affect users broadly.

🔍
✓ Live

Input Validation

All API inputs are validated using Pydantic schemas. SQL injection is prevented through the SQLAlchemy ORM. Webhook URLs are checked against private-network and cloud-metadata blocklists when saved and again before every delivery, to prevent SSRF.

Coming Soon

These capabilities are in progress or planned. We believe in being honest about what isn't finished yet.

🏆
Planned

SOC 2 Type II

We are working toward SOC 2 Type II certification. This involves a formal third-party audit of our security, availability, and confidentiality controls. Target: 2027.

🔎
Planned

Third-Party Penetration Testing

We plan to engage an independent security firm for periodic penetration testing of the platform and its infrastructure. Results will inform ongoing security improvements.

💰
Planned

Bug Bounty Program

We plan to launch a formal bug bounty program with defined scope and rewards. In the meantime, we encourage responsible disclosure via our security email.

🔐
Planned

SSO / SAML

Enterprise SSO via SAML 2.0 or OIDC to support identity providers like Okta, Azure AD, and Google Workspace is on our roadmap.

Responsible Disclosure

We take all security reports seriously. If you discover a vulnerability in Strata Security, please report it responsibly and give us a chance to fix it before public disclosure.

Disclosure Process

Email your report to security@strata-security.com. We will acknowledge receipt within 2 business days and provide a resolution timeline within 7 days. We aim to resolve critical issues within 30 days.

We appreciate the security research community and commit to: not pursuing legal action against good-faith researchers, publicly crediting reporters who wish to be acknowledged, and promptly fixing valid reports.

Report a Vulnerability →

What's in Scope

✓
Authentication and session management vulnerabilities
✓
Authorization bypasses (access to other orgs' data)
✓
Injection attacks (SQL, command, SSRF)
✓
Sensitive data exposure in API responses
✓
XSS vulnerabilities in the web interface
✓
Broken access control on API endpoints
✓
Denial of service via zip bomb or similar
✕
Social engineering or phishing of Strata employees
✕
Findings from automated scanners without proof of exploitability

Our Stack

Full transparency about the providers and technologies underpinning the platform.

🗄️
Auth & Database
Supabase (PostgreSQL + RLS)
📁
File Storage
Supabase Storage (S3-compatible)
💳
Payments
Stripe (PCI-DSS Level 1)
✉️
Email Delivery
Resend (DKIM/SPF/DMARC)
🚨
Error Monitoring
Sentry
⏱️
Rate Limiting
Upstash Redis (TLS)
⚙️
Task Queue
Celery + Redis
🌍
Frontend Hosting
Vercel (Edge Network)
☁️
Backend Hosting
Render (US East)

Have Security Questions?

Our team is happy to answer technical security questions from customers and prospects.