Capture & Ingest
Records land in CEDX Backup already linked to the canonical customer, employee, or vendor ID.
CEDX Backup tracks the jobs, but it scores the restores. Every asset carries a readiness score, every restore point is checked for infection, and the gaps board sizes what is not protected at all, in terabytes.
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective i..."
| Security Control / Asset ID | Principal / Endpoint Scope | SOC Owner & Policy | Telemetry / Grant Age | Enforcement Action | Posture Score |
|---|---|---|---|---|---|
| PAM Just-in-Time Grant #481CEDX Backup · 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 Backup · Record #1041 | 2.4M Events -> 12 Actionable | CISO Incident Pod | 0.3s Detection Latency | ● Session Quarantined | 100% Audited |
| Fleet Endpoint Posture · 344 Mac/WinCEDX Backup · Record #1042 | FileVault + Crowd/EDR + Patch v26 | IT Security Ops | 342 Compliant · 2 Quarantined | ● Auto-Patch Scheduled | 99.1 / 100 |
| Vault Secret Rotation EngineCEDX Backup · Record #1043 | 184 Production Keys & Certs | Platform Crypto Bus | Max Secret Age: 14 Days | ● Zero Plaintext Env Vars | FIPS Verified |
The demo's primary database has a point 6.0 hours old, and a restore test 45 days stale that failed. The product's advice, on screen: restore to an isolated cleanroom, not prod.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
64 assets on the readiness model, 21 not ready at score ≥70. The heat grid names them (a finance file share at 98 whose last success is past the RPO window) and infected restore points feed the score at +15 weight each, so a poisoned backup makes you less ready, not more.
48 coverage gaps, 101 TB uncovered. Reasons are explicit: orphaned chain 40 days, no policy for 55 days, never backed up. Each row carries blast score, tier, days exposed and size. A legacy archive at 7.8 TB does not hide behind a percentage.
320 jobs in the demo corpus: 47 failed, 85 warning or failed, 85 past their RPO window. Age in hours is on the row: a database catalog job at 668 hours is a finding, not a footnote.
Every figure below is directly inspectable in the running CEDX Backup application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Backup moves from initial intake to verified cross-estate completion.
Job health is 62.8%, and the screen says the harder things too: 85 jobs past their RPO window, 13 high-blast assets unprotected, a 439 TB corpus. The analyst bar answers the question you actually have: can I restore this database to before Sunday?
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 Backup 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 job stream and the RPO breaches: the 85 jobs past window are theirs to clear, oldest first.
Works the gaps board: every uncovered asset gets a policy, a chain, or a decision, with the size of the exposure on the row.
Runs the restore tests and the cleanroom restores. The 45-day-stale failed test on the primary database is the kind of finding they exist to close.
CEDX Backup 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 344-asset estate Inventory IT keeps is what the gaps board reconciles against. Uncovered assets are a join away, not a discovery project.
Endpoint-class assets carry an exposure score; backup readiness sits next to it, so a device can be both exposed and unrestorable, and you can see it.
The secrets infrastructure on the gaps board (ops-secrets, 18 days orphaned) is the same namespace Vault ages. One record, two risks.
Backup and recovery controls are rows in the controls library; the restore-test log is the evidence they point at.
"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."
"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."
"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."
Drag the seat slider to compare your current stitched stack (CrowdStrike + Datadog SIEM + CyberArk + HashiCorp Vault + Jamf + Kandji) against running CEDX Backup natively on the unified CEDX estate.
Explore the live CEDX Backup workspace on canonical demo data at /app/backup, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Backup pre-loaded with canonical demo records and connected across the 132-application CEDX estate.