Use Case

Vulnerability To Remediation

A scanner finding and a completed remediation are different records. GAEZLA exposes managed scanner assets, scan state, findings, and provenance, alongside supported hardening checks and remediation workflows.

Scanner record

The vulnerability surfaces show what the configured scanner reported and where that data came from.

Review managed assets, scan runs, status, and findings.
Retain scanner identity and source provenance with the finding data.
Use reporting views while keeping ownership and due-date decisions explicit.

Supported hardening work

Hardening profiles provide a separate path for assessment, evidence, and remediation on supported benchmarks.

Select a supported profile and scoped target.
Review check results and collected evidence before deciding on remediation.
Retain remediation execution state and output in its own operational record.

Value over time

How the product path is separated.

Observe

Read the finding

Inspect the configured scanner’s assets, run state, findings, and provenance.

Assess

Choose a supported path

Use hardening checks where an applicable supported profile exists.

Act

Run scoped remediation

Execute supported remediation and review the returned status, evidence, and output.

Related workflows.

Next step

Want to see this on your stack?

Book a walkthrough and I will show how this workflow maps to the tools you already run.

Book a walkthrough