Monitor
Crypto drift: why one scan is not enough
Crypto posture is dynamic. One assessment is a baseline — not a system of record.
What drift looks like
Between audit cycles, teams ship new microservices, rotate certificates, onboard SaaS vendors, and occasionally roll back hybrid TLS experiments. Each change can introduce or resolve quantum-vulnerable exposure. Without scheduled re-scans, you discover drift at the worst time — during an assessor interview.
Monitor tier capabilities
Qtangl Monitor diffs each scan against the prior baseline:
- New findings — endpoints or algorithms that appeared since last scan
- Resolved items — fixes verified with re-scan proof
- Readiness score trends — board-trackable metric over time
- Scheduled alerts — notify owners when drift exceeds thresholds
When to re-scan
Align scan cadence to your change velocity: monthly for fast-moving SaaS, quarterly for stable estates, ad-hoc after major certificate or load-balancer changes.
Honest scope
Monitor tracks external TLS and configured scan scope — not every embedded system in your supply chain. Use Assess for baseline breadth, Monitor for ongoing hygiene.
Continue on the Q-Day hub: Q-Day Monitor tier
References & further reading
Authoritative primary sources cited in this article. Summaries are our own — follow links for full context.
Last verified 2026-06-03
- What Is Post-Quantum Cryptography?NIST · 2024Official overview of NIST's PQC project, finalized standards, and the harvest-now-decrypt-later threat model.
- Cloudflare targets 2029 for full post-quantum securityCloudflare · 2026Cloudflare's accelerated PQ roadmap including post-quantum authentication milestones.
See your exposure with evidence
Run a live PQC inventory scan, export a CBOM, and verify signed reports independently.