SOLUTIONS · USE CASE
Automated Cryptographic Discovery and Inventory
Automated cryptography discovery and inventory (ACDI) is the use of tooling, rather than spreadsheets and interviews, to find the cryptography an organisation runs and keep that record current. CISA introduced the term in a 2024 strategy for federal agencies. Quantum Sentinel performs scheduled, credentialed discovery across network, file system and database estates and writes every finding into one Cryptography Bill of Materials.
Where the term comes from
ACDI is CISA’s vocabulary. Its Strategy for Migrating to Automated Post-Quantum Cryptography Discovery and Inventory Tools, dated 15 August 2024, was written because OMB Memorandum M-23-02 directed CISA to produce one, in consultation with NIST and NSA. Its stated purpose is "to support the assessment of FCEB progress towards PQC adoption using automated cryptography discovery and inventory (ACDI) tools".
The strategy’s scope is United States federal civilian agencies, and it covers both cloud-based and on-premises systems. The vocabulary has travelled well beyond that scope, because the underlying problem is the same everywhere: an inventory compiled by hand is out of date by the time it is finished.
CISA names four cryptographic discovery types. In its own words, ACDI tools "either individually or in combination, provide the following cryptographic discovery types: network, file system, database system, or software package", the combination of which covers encryption for data in transit and data at rest. The strategy does not define what each type covers, and it sets no performance requirements for tools.
What automation can and cannot collect
The most useful thing in CISA’s strategy is how candid it is about the limits. Of the nine inventory data items M-23-02 asks for, CISA says three can be collected by automation: the algorithm, key length and service provided; the software package type and vendor; and the operating system and version. Of the rest it says plainly that "most of the nine data items cannot be detected or collected using currently available automated tools, and therefore, are manually collected".
It is equally direct about coverage gaps, warning that "software packages with embedded cryptography, customized applications, or certain operating systems may not be discoverable using automated tools".
That is the honest frame for any ACDI tool, this one included. Automated discovery removes the largest and most repetitive part of the work, the part no team can sustain by hand across a changing estate. It does not remove the need for people to classify systems, decide what matters and ask vendors the questions a scanner cannot.
Quantum Sentinel against CISA's four discovery types
| CISA discovery type | Quantum Sentinel |
|---|---|
| Network | Covered. TLS directly and through STARTTLS, SSH, RDP, SMB, DNS-over-TLS, DNS-over-HTTPS and DNS-over-QUIC across 55 crypto-relevant ports by default; IKEv2 discovery that never establishes a security association; and read-only collection from F5 BIG-IP, FortiGate, Palo Alto PAN-OS and Cisco ASA. |
| File system | Covered. SMB dialects 2.0.2 through 3.1.1 and NFS v3, identifying encrypted files, keystores and key containers by content signature rather than file extension. |
| Database system | Covered. PostgreSQL, MariaDB, MSSQL, Oracle, MongoDB, CockroachDB, ClickHouse, Neo4j and Cassandra, recording the encryption actually negotiated on the scanner’s own session plus transparent data and column encryption. |
| Software package | Not covered. Quantum Sentinel does not inspect operating system packages, language dependencies or SBOMs. Repository scanning reads source code, which answers a different question: what your own code calls, not what a shipped package contains. |
Three of four, stated plainly, because a capability table that claims everything is worth nothing to somebody running an evaluation. Software package discovery is exactly the type CISA itself flags as hardest, and where it expects vendor engagement and manual tracking to remain necessary.
Automated means scheduled, not occasional
A discovery exercise that runs once is a consulting engagement. Automation is what makes it an inventory.
Scans run on standard five-field cron expressions in a timezone you choose, or as one-time runs, and can be started on demand through the REST API. Each schedule carries blackout windows, so scanning never runs during a change freeze or a trading window, and a maximum runtime, so a scan cannot overrun into one. Schedules can notify by email, syslog, Slack or Teams when a scan starts, finishes or pauses.
Scan profiles control pacing and how assertive a scan is allowed to be, and disruptive checks are withheld unless explicitly enabled, which matters when the estate includes embedded and operational technology that does not enjoy being probed.
What changes between one scan and the next
Every entry in the inventory carries first seen and last seen timestamps, and a rescan updates the entry it matches rather than creating a second one. That is what makes comparison across scans possible at all.
When a rescan finds that an entry has got worse, a crypto drift event is recorded: a weaker algorithm, a lower TLS version, a changed cipher suite, a smaller key, or a higher quantum risk score, with the old and new values kept side by side. Alert rules can watch for drift and for policy violations, scoped to an asset or asset group with a minimum severity, and deliver to Slack, Teams, email or a SIEM over syslog. Alongside that, daily snapshots of the risk-tier distribution give a real trend line rather than a single reading.
Two boundaries worth knowing. Drift is recorded for degradation, so a remediation that improves an entry updates the inventory but does not raise a drift event. And there is no new-versus-removed delta report between two scans: entries absent from a complete rescan are removed from the inventory rather than reported as departures.
What the automation produces
Discovery that does not produce something a governance process can consume is just a scan log. Every finding lands in the CBOM with a 0 to 100 quantum risk score, a harvest-now-decrypt-later flag and NIST and CNSA status, weighted by the environment and exposure of the asset it sits on, and aggregated into a single weighted index for the estate.
From there it comes out as CycloneDX 1.7 JSON, plain JSON or CSV for tooling; as reports in PDF, CSV or DOCX across report types that include quantum readiness, NIST IR 8547, DORA, NIS2 and PCI DSS; and through a REST API. An MCP server exposes the inventory to AI assistants as read-only tools unless writes are deliberately enabled. Policies can ban named algorithms, TLS versions and cipher suites and set minimum key sizes, evaluated across the whole inventory, and every action is written to a hash-chained audit trail that can be forwarded to a SIEM.
All of it installs and runs offline: the platform deploys on-premises and in air-gapped environments from a signed, checksum-verified bundle, which is what makes automated discovery usable in the estates that need it most.
Frequently asked questions
What is automated cryptographic discovery and inventory (ACDI)?
ACDI is the use of tooling to discover the cryptography an organisation runs and maintain a current inventory of it, rather than compiling that inventory by hand. CISA introduced the term in its August 2024 strategy for federal civilian agencies, where ACDI tools are described as providing four cryptographic discovery types: network, file system, database system and software package.
Which of CISA’s four discovery types does Quantum Sentinel cover?
Three of the four. Network discovery, file system discovery across SMB and NFS shares, and database system discovery across nine engines are all covered. Software package discovery is not: Quantum Sentinel does not inspect operating system packages, language dependencies or SBOMs. Its repository scanning reads source code, which answers a different question.
Does CISA’s strategy apply to organisations outside the US government?
Its scope is United States federal civilian agencies, excluding national security systems. The vocabulary and the method are useful to anyone building a cryptographic inventory, and the discovery types it names map cleanly onto a commercial estate, but it is not a regulation that applies to private companies.
How often can scans run?
On any schedule a standard five-field cron expression can express, in a timezone you choose, with blackout windows and a maximum runtime per schedule. Scans can also be run once, or started on demand through the API. The scheduler works to a one-minute resolution; this is scheduled scanning, not continuous real-time monitoring.
Does it detect changes between scans?
Yes. Entries carry first seen and last seen timestamps, and a rescan that finds a weaker algorithm, a lower TLS version, a changed cipher suite, a smaller key or a higher risk score records a crypto drift event with the old and new values. Alert rules can watch drift and policy violations and deliver to Slack, Teams, email or a SIEM. Drift is recorded for degradation, not for improvement.
Is discovery agentless?
Network, file share, database, network device, key manager and cloud discovery are all agentless and use each system’s own protocol or API with read-only credentials. Kubernetes discovery is the exception: it injects a read-only sidecar into the pod, because nothing outside a pod can see what is mounted inside it.
What does the inventory export as?
CycloneDX 1.7 JSON, plain JSON or CSV, plus reports in PDF, CSV or DOCX across report types including quantum readiness, NIST IR 8547, DORA, NIS2 and PCI DSS. A REST API and an MCP server provide programmatic access.
Can it run in an air-gapped environment?
Yes. Quantum Sentinel installs offline from a signed, checksum-verified bundle and runs on-premises and in air-gapped environments, including offline scan workers and signed offline updates.
Related: Cryptographic Discovery & CBOM · File shares · Code repositories · All use cases
Automate the inventory, not the guesswork.
See what a scheduled discovery run finds across your estate. Request a demo.