Exposure starts now
Encrypted data can be collected today for future decryption. The information may still be sensitive when its current protection can be broken.
Products / Assessment
AlphaQuantumSentinel
A starting point for PQC migration.
QuantumSentinel provides a starting point for your organization's PQC migration that is backed up by your own network data and topology.
Quantum risk
Know your exposure
Migration decisions depend on where cryptography is used, what it protects, and how long that information must stay confidential.
A sufficiently capable quantum computer could break widely used public-key encryption and digital signatures.
Source: NIST
Priorities need evidence
Cryptography can sit across application code, public connections, and internal services. An initial scan helps identify what is visible and where a wider assessment is needed.
QuantumSentinel
Scan coverage
Start with one asset and review the cryptographic evidence it exposes. Use the findings to identify what needs further review, who owns it, and the next action.
Website
Review observed TLS versions, cipher settings, key exchange, and certificate algorithms. The scan reports whether it observed post-quantum key exchange. It does not crawl pages or inspect the application.
Repository
Review cryptographic references in supported text files in a public GitHub repository. Findings include file and line evidence. Pattern matching does not execute code or prove how the application uses it.
File
Inspect one supported text file up to 512 KB. Use source or configuration content without secrets.
Network
Run the local connector on an approved computer. It uploads the scan scope, responding addresses, service observations, and summary to the service. The browser cannot inspect a private network.
How it works
Scan process
- 01
Select the asset and scan type. Confirm authorization.
- 02
Run the checks available for that type.
- 03
Review findings against the observed evidence and coverage limits.
- 04
Assign an owner and next action for findings that need follow-up.
Example finding
- Asset
- Public website connection
- Finding
- No post-quantum key exchange observed.
- Impact
- Recorded traffic may face future decryption risk.
- Next action
- Review the hosting provider’s key exchange support.
This example is not a scan result.
Inputs and results
Start with one asset you own or have permission to assess. Keep the target and scan type with the result.
- You provide
- The target address or supported file, scan type, and authorization.
- You receive
- On-page findings, observed evidence, recommended actions, and scope limits. Website, repository, and file scans include readiness scores. The hosted tool does not provide a downloadable cryptographic bill of materials or report export.
- You review
- False positives, system ownership, dependencies, and the priority of each next action.
Limits
A scan covers the evidence it observes. It is not a certification or a complete system assessment. Do not submit passwords, private keys, customer records, or other sensitive data.
Individual use cases
PQC leads
Give your migration program an initial evidence base. Use findings to identify the questions, systems, and owners that need a wider assessment.
Security teams
Focus follow-up work on observed cryptographic exposure. Check the evidence and scope before deciding which findings need action.
Developers
Locate cryptographic code that needs review in a public repository or supported file. Use the findings to plan changes with your team.
IT administrators
Compare responding services with your network inventory. Identify gaps in visibility and decide where a closer review is needed.
Website owners
Get a starting point for a discussion with your hosting provider. Review what the public connection reveals about its cryptography.
Independent consultants
Use an authorized initial scan to define follow-up questions with a client. Keep the observed findings separate from the wider assessment.