Security

Security-first architecture, explained

We describe concrete architectural decisions rather than slogans. Here is what ATLASOPS actually implements — and why each choice matters.

Authentication & Access

Enterprise SSO

Sign-in is organization-first: enter your work email and ATLASOPS routes you to your company's identity provider (Okta, Entra ID, Google Workspace, and more). Sessions use httpOnly cookies — not localStorage JWTs — so the browser never exposes long-lived bearer tokens to XSS.

Role-based access control

A permission catalog maps system and custom roles to fine-grained actions. Every write endpoint checks membership permissions; viewers cannot mutate operational data.

Encrypted connector credentials

Integration credentials are encrypted before they are stored.

Server-side sessions

Sessions are stored server-side with hashed tokens, expiry, revocation, and concurrent-session limits.

Data & Tenancy

PostgreSQL row-level security

Tenant-owned tables carry organization_id and are protected with FORCE ROW LEVEL SECURITY policies keyed to app.current_org_id. Application queries also filter by organization so isolation is enforced in both layers.

Audit logging

Sensitive actions are recorded to an org-scoped audit log, creating a traceable history of who did what and when across the platform.

Input validation

Every request and ingestion row is validated with Pydantic schemas before it reaches business logic, rejecting malformed or unexpected data early.

API & Network

Secure API design

Thin controllers delegate to well-defined services. Schemas constrain inputs and outputs, reducing the surface area for injection and over-posting.

Encrypted communication

The platform is designed to run behind TLS so traffic between clients, the API and external systems is encrypted in transit.

Security headers & rate limits

Responses include CSP, X-Frame-Options, and HSTS (in production). Auth routes are rate-limited per IP to slow credential stuffing.

Deployment & Operations

Containerized deployment

The backend and frontend ship as Docker images orchestrated with Docker Compose, giving reproducible, isolated runtime environments.

Configuration management

Configuration is driven by environment variables through pydantic-settings, keeping secrets out of source control.

Structured logging

JSON structured logs plus optional OpenTelemetry and Prometheus metrics make operational and security-relevant events observable.

See your entire operation in one place

Explore a sample operational workspace with your reviewer login, or talk with our team about connecting your systems.