Discover: establish the evidence
Identify the target, collection window, workload activity, and scan status. Confirm that relevant paths executed. Use Raw Evidence and Execution Match to connect a concern to the process, implementation, and available network observations. Record coverage and missing observations alongside the finding.
Plan: compare acceptable options
Agree on security requirements and compatibility constraints with the migration lead and application or infrastructure owner. Trace dependencies and use blast-radius analysis to identify relationships that need review. Treat these as observed impacts, not a guarantee of complete dependency coverage.
Compare measurements, simulation, or catalog-backed controlled experiments where applicable. Record the option, operation, implementation, workload conditions, and test path. Label simulated estimates separately from observed costs of an actual change. Performance helps choose among acceptable alternatives; it does not override security requirements.
Remediate: choose and scope the action
Record whether the action is a customer-executed native upgrade, a supported proxy path, or supported OpenSSL implementation redirection. Confirm compatibility and deployment prerequisites with the responsible owner before changing the environment.
Document the selected action, evidence, remaining uncertainty, approvals required by your team, and recovery arrangements appropriate to the change. Do not assume a complete rollback workflow is provided by the product. See remediation scope.
Validate: compare before and after
Collect relevant evidence again under documented workload conditions. Compare observed crypto behavior or negotiation and measured costs against the agreed goal. Distinguish the original application, protected connection segment, proxy measurements, and simulated results.
For traffic policies, review new matching connections, negotiated settings when captured, and policy hits. Active status alone does not prove end-to-end protection. Record remaining gaps and assign the next action or test to an owner.
Package the assessment outcome
Agree on a scoped application migration evidence report with the Laviq team. The proposed deliverable includes scope and coverage, supporting evidence, constraints and dependencies, options and tests evaluated, costs, the selected action and prerequisites, and before-and-after results where a change is evaluated.
The report is prepared through an operator-assisted assessment with your team. Keep observations, estimates, and assumptions distinguishable so another reviewer can revisit the decision.