Capture & Ingest
Records land in CEDX Compliance already linked to the canonical customer, employee, or vendor ID.
CEDX Compliance keeps a library of 320 controls mapped to eight frameworks, scores each one, ages the evidence behind it, and puts the gaps in a queue with owners, so an audit is a query, not a project.
"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 Compliance · 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 Compliance · Record #1041 | 2.4M Events -> 12 Actionable | CISO Incident Pod | 0.3s Detection Latency | ● Session Quarantined | 100% Audited |
| Fleet Endpoint Posture · 344 Mac/WinCEDX Compliance · Record #1042 | FileVault + Crowd/EDR + Patch v26 | IT Security Ops | 342 Compliant · 2 Quarantined | ● Auto-Patch Scheduled | 99.1 / 100 |
| Vault Secret Rotation EngineCEDX Compliance · Record #1043 | 184 Production Keys & Certs | Platform Crypto Bus | Max Secret Age: 14 Days | ● Zero Plaintext Env Vars | FIPS Verified |
The framework cards are honest about the shape of the work: SOC 2 at 84% with 11 gaps, PCI DSS at 68% with 12. Zero frameworks are near-ready, and the card says zero.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
The library lists code, control, domain, status, the frameworks it maps to, owner and evidence age: a break-glass procedure passing with 95-day-old evidence, a code-review control failing, an encryption-in-transit control never tested.
Each program shows readiness, control count, gaps and the next audit date: SOC 2 Type II at 84% with its audit on 2026-11-01, PCI DSS v4.0 at 68% due 2026-10-20, ISO 27701 not started at 62%.
The compliance agent chased a fresh MFA coverage export (evidence age 112 days, down to 2), nudged an owner on a 34-day-overdue review, and drafted dual-approval enforcement for the change pipeline. Four actions sit pending a human's approval.
Every figure below is directly inspectable in the running CEDX Compliance application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Compliance moves from initial intake to verified cross-estate completion.
173 of 320 controls ready, 18 high-gap controls, 70 failing continuous monitors, 104 fail-or-partial with 43 never tested. The readiness bars per framework carry their gap counts: 84% SOC 2 means 11 gaps, not a grade.
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 Compliance 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 framework packs and the audit dates. The 77% weighted readiness and the zero near-ready card are theirs to move.
Keeps their controls' evidence fresh. A 34-day-overdue review is a nudge from the agent, not an audit finding.
Reads the failing tests on the change pipeline and approves, or dismisses, the agent's drafted remediation.
CEDX Compliance 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.
Logical-access controls test against the same grant and review records Access keeps. The MFA coverage export the agent chased is one of them.
Rotation SLAs and never-rotated keys are control evidence with dates. The 134 past-SLA secrets are gaps in both products, once.
Restore-test freshness is a dated artefact the recovery controls cite. The 45-day-stale test is the evidence, not a story.
Patch lag and sensor coverage feed configuration and vulnerability controls from the scored fleet, row for row.
"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 Compliance natively on the unified CEDX estate.
Explore the live CEDX Compliance workspace on canonical demo data at /app/compliance, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Compliance pre-loaded with canonical demo records and connected across the 132-application CEDX estate.