CryptView for Splunk (package id: TA-cryptview) provides visibility in Splunk into CryptView-generated cryptographic asset inventory, certificate lifecycle risk, and post-quantum cryptography readiness evidence.
The app helps security, PKI, identity, infrastructure, and SIEM teams review Cryptographic Bill of Materials (CBOM) data directly in Splunk. It visualizes TLS endpoints, certificate expiry pressure, key type and key size signals, issuer concentration, migration priorities, filesystem crypto inventory, and layered Post-Quantum Cryptography (PQC) readiness evidence.
CryptView separates certificate identity, transport/key-exchange evidence, and evidence confidence so standard TLS-only scans do not overclaim PQC readiness. Where active PQC transport evidence is not available, the dashboard reports transport status as “not tested” rather than assuming support or lack of support.
This beta/community preview does not perform active scanning from Splunk. CryptView Collector, CryptView CLI, or external CryptView workflows generate normalized NDJSON data separately, and this Splunk app ingests and visualizes that output. Optional CycloneDX CBOM JSON can also be indexed as a standards/audit artifact.
For endpoint filesystem certificate, private-key-file indicator, and keystore inventory, install the companion CryptView Collector app from Splunkbase:
https://splunkbase.splunk.com/app/9012
The collector is metadata-only and is designed to work with this CryptView dashboard app.
For managed assessments, executive reporting, connector onboarding, PQC migration prioritization, support, feedback, or pilot participation, complete the feedback form or contact hello@qwocks.com.
Beta feedback, pilot access, and product enquiries:
https://forms.gle/qJRaDb1sXaMo2yqA7
Compatibility: Splunk Enterprise 9.x. Splunk Cloud deployment may require separate validation/review.
License: Beta/community preview license. See LICENSE included in the package.