The Quantum Command Application Report connects fleet-level posture to the applications responsible for cryptographic activity. It ranks processes by readiness and exposes weak or insecure cipher use, key-exchange prevalence, listening-port resilience, software package information, and certificate characteristics.
Use this dashboard to identify a problematic executable, assess the scope of its exposure across hosts, and then move to Application Detail for process-specific investigation.
Operational guidance: Click a tier in one of the top charts to filter every table on the dashboard. Select a process when you are ready to move from fleet-wide comparison to host- and connection-level detail.
Panels
| Panel | Type | What It Shows |
|---|---|---|
| Navigation Links Bar | Links | Provides cross-dashboard navigation while preserving the investigation workflow. |
| Key Exchange Tier | Interactive Vega chart | Shows key-exchange readiness across observed application executables. |
| Application PQC Compliance | Vega chart | Ranks executables by application-level key-exchange compliance. |
| Certificate Signature Tier | Interactive Vega chart | Shows certificate-signature readiness across application TLS sessions. |
| Web Server Distribution | Vega chart | Compares key-exchange tiers across web server process families such as nginx, Apache, and IIS. |
| Weak Cipher per App | Data table | Ranks weak cipher values by the number of unique application executables using them. |
| Insecure Cipher per App | Data table | Ranks insecure cipher values by unique application count. |
| Port Quantum Resilience | Data table | Shows listening ports and processes with quantum-resilient and non-resilient counts. |
| Software Package | Data table | Ranks observed software packages or process names by occurrence. |
| Key Exchange vs. App Count | Data table | Shows key-exchange algorithms and the number of unique applications associated with each. |
| Signature Algorithm vs. App Count | Data table | Shows certificate-signature algorithms and their unique application counts. |
| Full Application Crypto Inventory | Paginated data table | Provides a 14-column application inventory for audit, export, and remediation tracking. |
| Certificate Inventory | Data table | Lists observed certificates with validity dates, algorithms, key curves, and key sizes. |
| Document Search | Discover panel | Displays raw scan records matching the active dashboard filters. |
Key Data Fields
| Field | Description |
|---|---|
| process.name / process.executable | Identifies the application process and executable observed making TLS connections. |
| omb.kex_tier / omb.kex_primary | Provides the readiness tier and primary key-exchange algorithm. |
| quantum_ready | Indicates whether the process is using a PQC key exchange. |
| tls.weak_ciphers / tls.insecure_ciphers | Lists cipher values classified as weak or insecure. |
| tls.supported_key_exchanges | Lists the key-exchange algorithms supported by the application. |
| x509.* | Provides certificate identity, validity, signature, key algorithm, curve, and size information. |
| omb.software_package_name | Identifies the software package associated with the process. |
Reading the Dashboard
Start with the three posture charts
Use key exchange, application compliance, and certificate signature to determine which cryptographic dimension is driving risk.
Separate weak from insecure
Weak ciphers should be hardened; insecure ciphers represent a higher-priority configuration problem and should be explicitly disabled.
Use the full inventory for scope
The 14-column table shows how an application's crypto configuration varies by port, OS platform, host, protocol, and certificate.
Validate with raw records
Use Document Search when a summarized count needs to be confirmed against the underlying scan documents.
Filtering and Performance
The dashboard opens with a default time range of Last 90 days. Global Elasticsearch dashboard filters apply to the panels unless a panel description states otherwise. Preserve relevant filters when navigating between related dashboards so the investigation remains scoped to the same application, host, tier, or certificate population.