Tenant isolation
Stateful queries carry an organization boundary. Server-side authorization protects decisions, policies, approvals, exports, connections, and administration.
Agent authorization security a buyer can inspect.
Review how Adranum isolates organizations, encrypts SAP artifacts, rejects unsafe archives, preserves validation and approval history, brokers integrations, and restores durable state.
Identity
Sessions are hashed, HTTP-only, SameSite, expiring, and revocable. Google OAuth tokens are verified against issuer signing keys.
Enterprise access
OIDC supports Authorization Code with PKCE, signed identity-token validation, domain restriction, and encrypted client secrets. SCIM supports provisioning.
Evidence history
Source hashes, rules, analysis, proposals, approvals, workflows, and exports are appended to a tenant-scoped hash chain.
Input safety
Uploads are size-bounded. ZIP paths, expansion size, file types, and malformed supported formats are checked before analysis.
Billing and OAuth
Stripe webhooks are signature-verified and replay-protected. Managed OAuth providers hold authorization while Adranum stores workspace-scoped connection identifiers.
Recovery
SQLite runs in WAL mode with integrity checks. Backups support independent encryption, off-box storage, and restore verification.
Runtime hardening
The deployment supports a non-root container behind TLS, read-only filesystems, dropped capabilities, health checks, and resource limits.
Honest assurance
Adranum never presents LLM output as validated code, never claims official SAP clean-core certification, and does not claim independent security certification without current evidence.
Verify before enforcement.
Start in shadow mode, review the decision record, and publish a policy only when its effects are understood. Procurement reviewers can use the linked trust and legal documents.