Security Architecture

How ERPUX keeps your Oracle data secure. Designed for a 10-minute CISO review.

Architecture Overview

ERPUX is a UI-only layer. It renders data but never stores it. All queries flow directly to your Oracle ERP Cloud instance via Oracle REST APIs.

Browser

↔

ERPUX (UI Only)

↔

Oracle REST APIs

No data is stored at the ERPUX layer. All responses are streamed directly from Oracle to the browser.

Zero Data Storage

ERPUX never stores your ERP data. Every query is executed in real-time against your Oracle instance. Results are rendered in the browser and discarded when the session ends.

No caching of financial data, PII, or transactional records
No database tables for customer ERP data
No server-side session storage of query results
What we store: company configuration, JWT certificates, user preferences (favorites, recent reports)

Authentication

ERPUX uses bidirectional JWT authentication with RS256 signing. No passwords are stored or transmitted.

Inbound (Oracle to ERPUX)

Oracle sends a signed JWT via Page Integration (Secure Destination). ERPUX verifies the token using Oracle's public certificate. Token contains user identity, roles, and data security context.

Outbound (ERPUX to Oracle)

ERPUX creates a JWT signed with the customer-specific private key, asserting the authenticated user. Oracle validates this token and executes API calls as that user, enforcing all security policies.

RS256 (RSA + SHA-256) signing algorithm
30-minute token expiry with automatic refresh
Certificate-based — no passwords stored or transmitted

Oracle Security Enforced

ERPUX does not implement its own authorization layer. All data access is controlled by Oracle.

Oracle roles determine which menus and features a user can access
Data access sets control which ledgers, business units, and segments a user can see
Business unit security restricts transactional data to authorized organizations
API calls execute as the authenticated user — ERPUX cannot elevate privileges
If a user cannot see data in Oracle, they cannot see it in ERPUX

Credential Management

Optional BI Publisher credentials (used for report deployment, not end-user access) are stored securely.

OCI Vault — Oracle Cloud Infrastructure's HSM-backed secret management
AES-256-GCM encryption at rest
IAM-controlled access with full audit logging
Customer-owned vault option: keep credentials in your infrastructure
End users never need or see admin credentials

Hosting

Application hosted on Vercel (edge network) and Oracle Cloud Infrastructure
TLS 1.3 enforced on all connections
HTTPS only — no HTTP fallback
Automatic certificate rotation via Vercel
No SSH access, no server management — serverless architecture

Compliance

Because ERPUX stores no customer ERP data, your existing Oracle compliance certifications cover your data at rest and in transit.

Inherits Oracle's SOC 2 Type 2 and ISO 27001 certifications for data
OCI Vault is SOC 2 Type 2 and ISO 27001 certified for credential storage
No PII stored beyond contact information (name, email)
All Oracle audit trails preserved — ERPUX does not bypass Oracle logging

Have security questions? We're happy to walk your security team through the architecture.