Findings
Prioritized concerns that give your team a place to start.
Product
A migration path
that fits your workload.
Laviq helps enterprises plan and execute post-quantum migration by discovering active cryptography, evaluating workload-specific upgrade options, and protecting supported connections without changing application code.
Discover → Plan → Remediate → Validate
Discover. Plan. Remediate. Validate.
Move from observed activity to an evaluated change. Current comparisons are operator-assisted; your team reviews requirements, evidence, and deployment prerequisites.
- 01 / DISCOVER
Discover active cryptography
A scan captures cryptographic activity with the process, implementation, library, and network details available for the workload.
What is active, and where? - 02 / PLAN
Compare paths for this workload
Compare upgrade options against security requirements, dependencies, and measured or simulated costs. Trace the potential impact of a change.
Which acceptable path fits? - 03 / REMEDIATE
Apply a supported change
Choose a customer-executed native upgrade, supported proxy protection, or supported OpenSSL implementation redirection. Each path has its own prerequisites.
What can we change now? - 04 / VALIDATE
Check behavior and cost
Compare before-and-after cryptographic behavior or negotiation and measured costs under relevant workload conditions. Keep the evaluated path and remaining gaps visible.
Did the change meet the goal?
01 / Discover
Start with what your workload actually used.
Raw Evidence shows the cryptography Laviq captured in the workload, with the process and implementation details your team needs to investigate it.
what happened / runtime evidence
What you can see
See the event before deciding what to change.
- Crypto operations and implementation identity.
- The process and library behind the activity.
- Network negotiation details when captured.
- Measurements and call-stack detail when collected.
02 / Plan · Compare options
See what needs attention first.
Use workload context and dependencies to compare acceptable upgrade paths. Security requirements constrain the options; measurements and simulation help assess their operational cost.
Inventory
The workloads, libraries, and endpoints seen in the run.
Correlations
Connections between a concern and the workload or network path behind it.
Performance
Measured behavior from the workload.
Evidence
The records behind each review.
Experiments
Catalog-backed controlled experiments to investigate acceptable alternatives.
02 / Plan · Priorities
See what needs attention first.
The dashboard brings active findings, exposure, coverage, owner gaps, and migration progress together so your team can focus the next review.
migration priorities / dashboard
trace the workload / connected evidence
02 / Plan · Trace the workload
See how a concern connects to the workload.
This view links the concern to the target, process, network path, implementation, and crypto activity so your team can see what is behind it.
02 / Plan · Performance Lab
Measure the behavior behind the decision.
Performance Lab shows measured samples and related operations from the workload. Combine measurements with simulation and controlled experiments where applicable. Record test conditions and distinguish simulated estimates from measurements of an actual change.
measured behavior / performance
selected traffic / protection
03 / Remediate · Selected traffic
Protect selected traffic while the migration progresses.
Steer selected supported connections through a PQC-capable proxy to a compatible destination. This protects the configured, evaluated connection segment. Review routing, trust, and certificate requirements. Active policies apply to new matching connections only.
03 / Remediate
Choose the change your environment supports.
No single remediation path fits every workload. Confirm operation, connection, version, and deployment compatibility before selecting one.
Native upgrade
Change the application or library.
Your team executes an application, library, or configuration upgrade using the evidence and evaluated options. Laviq does not automatically perform every native upgrade.
Connection protection
Protect a supported segment.
A PQC-capable proxy can protect selected connections to compatible destinations without source changes. Application-internal cryptography and other segments retain their own scope.
OpenSSL redirection
Redirect a supported implementation.
Supported OpenSSL operations can use runtime implementation redirection without source changes, preserving expected output and application behavior. Confirm operation and version support with the team.
Implementation substitution is different from algorithm substitution. OpenSSL redirection is not a demonstrated native post-quantum algorithm upgrade. Automated workload-specific recommendations are planned; transparent algorithm substitution remains future research.
04 / Validate
Check the change against the goal.
Compare before-and-after crypto behavior or negotiation and measured costs for the evaluated environment and path.
- Behavior: verify the operation or negotiated protection actually observed after the change.
- Cost: compare relevant measurements under documented workload and test conditions.
- Boundary: distinguish original application behavior, proxy measurements, and simulated results.
- Decision: record remaining coverage gaps, prerequisites, and the next owner or test.
Deployment & coverage
Understand the scope
of the evidence.
Results depend on what ran, the collection window, and the supported observation path. Review deployment requirements and coverage with your team.
- Environment: representative, supported Linux workloads.
- Evidence: activity captured during the run, with context when available.
- Protection: selected new matching connections within supported paths.
- Decision: keep application, connection-segment, and full-path claims distinct.