What a policy applies to
Policy Protection lets your team compare current and proposed protection for selected traffic, along with status and policy hits. Active policies apply to new matching connections only.
Review the selected path
Confirm the target and traffic selection before interpreting policy status. Check whether the workload created new connections that match the policy during the period you are reviewing.
Keep the boundary clear
A traffic policy does not upgrade cryptography inside a process or library. Policy status alone does not prove an entire application, every connection, or an end-to-end path is post-quantum secure.
Interpret policy hits
A hit is evidence to review within the selected policy and observation window. Missing hits may require checking selection, connection timing, and captured activity. They do not establish that the workload has no relevant traffic.
Decide with a human review
Laviq supports the migration decision and keeps policy evidence visible. Review deployment and workload implications with the responsible team before making a change. See the evidence model for the wider workflow.
Compare the three remediation paths
Native upgrade: your team changes an application, library, or configuration based on the evaluated options. Define compatibility, deployment, validation, and recovery arrangements for that change. Laviq does not automatically execute every native upgrade.
Proxy protection: selected supported connections can be steered through a PQC-capable proxy to a compatible destination without changing application source. Protection applies to the configured, evaluated connection segment. Confirm routing, destination compatibility, trust, and certificate requirements; source changes being unnecessary does not remove these deployment prerequisites.
OpenSSL implementation redirection: supported operations can use runtime implementation redirection without changing application source, while preserving expected output and application behavior. Confirm operation and version support with the Laviq team. Do not infer an operation or version is supported because another one is.
Implementation substitution is different from algorithm substitution. This redirection is not a demonstrated native post-quantum algorithm upgrade. Transparent substitution of a different algorithm remains future research.
Validate the evaluated path
Compare before-and-after crypto behavior or negotiation and measured costs under documented conditions. Keep application observations, proxy results, and simulation separate. Record what the change establishes and what remains outside its scope.