Capture & Ingest
Records land in CEDX Access already linked to the canonical customer, employee, or vendor ID.
CEDX Access scores every grant for risk, ages every standing privilege, and puts a decision on every review row: keep, revoke, or convert to just-in-time, with an AI recommendation you can overturn.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."
| Security Control / Asset ID | Principal / Endpoint Scope | SOC Owner & Policy | Telemetry / Grant Age | Enforcement Action | Posture Score |
|---|---|---|---|---|---|
| PAM Just-in-Time Grant #481CEDX Access · Record #1040 | Prod DB Read · Exp in 45m | SecOps Auto-Reaper | 64 Stale Grants Revoked | ● Zero Standing Privilege | 99.4 / 100 |
| SIEM Correlation Rule #109CEDX Access · Record #1041 | 2.4M Events -> 12 Actionable | CISO Incident Pod | 0.3s Detection Latency | ● Session Quarantined | 100% Audited |
| Fleet Endpoint Posture · 344 Mac/WinCEDX Access · Record #1042 | FileVault + Crowd/EDR + Patch v26 | IT Security Ops | 342 Compliant · 2 Quarantined | ● Auto-Patch Scheduled | 99.1 / 100 |
| Vault Secret Rotation EngineCEDX Access · Record #1043 | 184 Production Keys & Certs | Platform Crypto Bus | Max Secret Age: 14 Days | ● Zero Plaintext Env Vars | FIPS Verified |
The riskiest grant in the demo is a break-glass account at 94, used this morning with no ticket claim attached. The root-caused alert names it. That is the point of a risk score.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The grant table carries principal, resource, role, level, type and risk: the break-glass account on the ledger at 94, a service account approving finance at 92, a contractor's deploy grant at 91. Unused for 90 days is a counted state: 64 grants.
The review board is 95 items with a decision per row: revoke the break-glass, keep the app-admin, convert the vault grant to just-in-time. The AI recommendation sits next to the decision (deny 97%), so agreement and disagreement are both recorded.
43 open requests, 9 of them high risk. Each shows requester, resource, role, duration and the AI recommendation: deny the standing payroll admin at 95, convert the deploy grant to 24 hours, approve the scoped one at 74% confidence.
Every figure below is directly inspectable in the running CEDX Access application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Access moves from initial intake to verified cross-estate completion.
281 standing grants, 43 requests awaiting decision, 9 high-risk, an access-health ring at 49. The root-caused alerts are the week's arguments: a contractor keeping deploy-operator unused since May, an SoD conflict where one person holds approver and deployer.
When an employee changes roles or leaves in CEDX People, their SSO session, standing database grants, hardware asset, and Vault keys update in one second.
Records land in CEDX Access already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Owns the break-glass accounts and the JIT sessions. A 94-risk grant used without a ticket is their first conversation of the day.
Runs the quarterly recerts: 95 items, decisions per row, and the 29 pending attests chased before the campaign closes.
Decides the 43 open requests with the risk score and the AI recommendation on the same row, and their overturns are counted, not judged.
CEDX Access is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.
The 22 grants against prod/payments are this ledger's rows: Vault counts what they can read, Access counts whether they should exist.
Logical-access controls test against this ledger: review completion, stale standing grants and the break-glass log are dated evidence.
Break-glass use and role grants land in the event stream. The 08:53 ledger access with no ticket is an alert there and a finding here.
Privilege follows the person to the device: a 94-risk grant on a 95-exposure laptop is the compound number both products show.
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
Drag the seat slider to compare your current stitched stack (CrowdStrike + Datadog SIEM + CyberArk + HashiCorp Vault + Jamf + Kandji) against running CEDX Access natively on the unified CEDX estate.
Explore the live CEDX Access workspace on canonical demo data at /app/access, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Access pre-loaded with canonical demo records and connected across the 132-application CEDX estate.