Preparing for PQC readiness: is TLS crypto visibility the right starting point?

I’m launching CryptView in a couple of weeks and would value early feedback from security, PKI, infrastructure, compliance, and SOC teams.

The idea behind CryptView is simple: before organisations can prepare for post-quantum cryptography, they first need visibility into where cryptography is exposed.

The first version focuses on TLS-facing assets and helps teams review:

• visible TLS endpoints

• certificate expiry pressure

• classical-only cryptographic posture

• priority/risk findings

• CBOM-style inventory

• executive reporting

• Splunk workflow support

Access is currently private beta so scans can stay controlled, safe, and useful for early feedback.

I’d love input on three things:

1. Would TLS cryptographic visibility be a useful starting point for PQC readiness?

2. What would you expect in a first useful PQC readiness report?

3. Would you rather see this as a standalone dashboard, a Splunk workflow, or both?

Open to blunt feedback before launch.