Authentication
Credential-backed sign-in with server-side sessions and per-organization roles. Every request is bound to an identity and an organization before anything else runs.
SECURITY / POSTURE
Built for infrastructure where the blast radius is real.
ByDevopsify TeamRead~8 min
TL;DRKey takeaways
• Server-side authorization on every operation; AI never authorizes.
• AES-256-GCM encryption at rest, TLS 1.2+ at edge, tenant isolation.
• Every record filtered by organization id; no cross-tenant path.
• Immutable audit trail with signed envelopes for compliance.
The security model lands on server-side authorization, encrypted isolation, deeply scoped service accounts, and an immutable audit trail. This is the marketing-level snapshot; the operational details live in the docs' security boundaries.
Devopsify is a tenant-scoped infrastructure control plane that unifies multi-cloud inventory, topology, governed provisioning, delivery operations, audit, and AI-assisted investigation under one declarative graph. Security is enforced server-side: deny-by-default RBAC, per-tenant encryption, and an audit trail that records every proposal, approval, and apply. The AI reads the graph and proposes (it never executes), so the authorization boundary stays with policy and human review.
REQUEST / 0xA1ENFORCED SERVER-SIDE
01
Browser & clientsSession-bound, never trusted
✓02
AuthenticationCredentials, sessions, tokens
✓03
Authorization boundaryRBAC + entitlements + policy
✓04
Control planeScoped capabilities, audit, apply
✓05
Encrypted at restAES-256-GCM, tenant-isolated
✓Deny by defaultAuditedNever delegated to AI
How does Devopsify stay secure by default?
| Pillar | Devopsify | Common gap |
|---|---|---|
| Authorization | ✓ Server-side, deny-by-default | ✗ Client-side |
| Encryption | ✓ AES-256-GCM + TLS 1.2+ | ✗ Plaintext |
| Isolation | ✓ Org-id filtered | ✗ Shared |
- Authenticate every request bound to identity and organization.
- Authorize deny-by-default RBAC + policy evaluation server-side.
- Encrypt secrets at rest (AES-256-GCM) and in transit (TLS).
- Audit every action as a signed envelope, no gaps.
Common Questions
How is tenant isolation enforced?
Every record, query, job, and audit entry carries an organization id and is filtered server-side. There is no cross-tenant query path.
Does AI have access to secrets?
No. Secrets are excluded from model context entirely and never logged. AI reads the graph and proposes; it never executes.
What compliance is targeted?
SOC 2 Type II and ISO/IEC 27001 targeted for Q4 2026, with GDPR alignment today and HIPAA/PCI-DSS scoped as products.
THE TRUST MODEL
Four pillars hold the boundary.
Every pillar is enforced server-side and verified by the audit trail, the same record that keeps operational decisions honest.
Authorization
Deny by default. RBAC permission sets, organization entitlements, and the policy engine are evaluated server-side on every operation, never in the browser or the model.
Encryption
TLS 1.2+ enforced at the edge with HSTS. Tenant secrets encrypted under AES-256-GCM with per-key identifiers; master keys never leave the control plane.
Isolation
Every record, query, job, webhook, and audit entry carries an organization id and is filtered server-side. There is no cross-tenant query path.
AI WITH OPERATIONAL BOUNDARIES
The assistant reads and plans. It never becomes the authorization boundary.
Devopsify AI can investigate infrastructure context and propose a next step. Authorization remains with server-side controls, policy, scoped capabilities, approval, and audit.
- Reads and plans only: the AI proposes next steps, it never executes.
- Actions stay scoped to approved capabilities and human review.
- Every proposal is recorded in the audit trail as a signed envelope.
- Secrets are excluded from model context entirely and never logged.
COMPLIANCE ROADMAP
Posture first, certifications on a clock.
This page describes posture, not a certification. Certifications are targeted after live-execution surfaces reach GA in lock step with legal review.
SOC 2 Type II & ISO/IEC 27001
Scoped toward certification in Q4 2026. Control evidence is gathered from the audit trail and signed envelopes throughout the current hardening period.
GDPR, HIPAA, PCI-DSS
GDPR alignment for stored personal data today. HIPAA and PCI-DSS are scoped as products and hosting requirements surface with customer demand.
Least-privilege operations
Least-privilege service accounts, key rotation, dependency auditing, and 90-day certificate auto-renewal via ACME on every deployed surface.
Real connections, labeled fallbacks.
AWS, Azure, and GCP are reachable through real SDK connections when credentials are present; without credentials the connectors fall back to labeled demo data. Long on-premises and CI/CD channels are scoped with sales.
Demo never masquerades as production.
Any surface running on demo data is marked Demo. Demo mode never presents itself as production evidence and cannot apply real infrastructure changes.
RESPONSIBLE DISCLOSURE
Found something? Tell us first.
If you believe you have found a weakness, report it through the contact and support flow, table the minimum reproducible steps with mock data, and stop at the first sign of another tenant's data. The reported surface is the demo deployments; a production program will publish its own scope and commitments.