What Is Vulnerability Remediation?
Vulnerability remediation is the work of eliminating a security vulnerability, usually by changing code, upgrading a dependency, applying a patch or fixing a configuration. It differs from mitigation, which reduces the risk without removing the underlying flaw.
Also known as:
Remediation vs Mitigation vs Risk Acceptance
- Remediation. Removes the vulnerability, for example by fixing the code or upgrading the package.
- Mitigation. Reduces the chance or impact of exploitation without removing the flaw, such as a WAF rule, a feature flag or network isolation.
- Risk acceptance. A documented decision to leave the vulnerability in place, with an owner, a reason and a review date.
Mitigation buys time; remediation closes the finding. Most programs use mitigation when a fix cannot ship within the SLA, then follow up with a permanent fix.
The Remediation Workflow
Remediation starts after triage has confirmed a finding is real and urgent. Someone has to own it, write the fix, test that it does not break the build or change behavior, get it reviewed and deploy it, then confirm the vulnerability is gone. Each handoff adds delay, which is why mean time to remediate (MTTR) is usually measured across the whole workflow rather than the coding step alone.
Common Types of Remediation
- Code fixes. Changing application code to remove an injection, authorization or logic flaw.
- Dependency upgrades. Moving to a patched version of an open source package, which may involve breaking changes.
- Configuration changes. Fixing cloud or infrastructure settings at the source, such as Terraform, so they do not reappear.
- Secret rotation. Revoking and replacing a leaked credential, not only deleting it from the code.
Remediating at Scale
Fixing findings one ticket at a time does not keep up with a large backlog. Teams get further by grouping similar work into campaigns, such as one dependency upgrade across many repositories, and by pacing fixes so reviewers are not flooded.
How Nullify Remediates Vulnerabilities
Nullify writes a minimal, root-cause fix, validates it against the build before the pull request opens and then manages the PR through review, reading CI output and fixing failures. It caps open fix PRs at 3 per repository, runs remediation campaigns across teams and never auto-merges. Across customers, 89% of fix PRs merge without a developer rewriting them. See how Nullify fixes and routes findings.
Key Takeaways
- Vulnerability remediation removes the flaw; mitigation only reduces its risk.
- The workflow covers ownership, the fix, testing, review, deployment and verification.
- Fixes include code changes, dependency upgrades, configuration changes and secret rotation.
- Campaigns and paced fixes help teams remediate at backlog scale.
Read More About Vulnerability Remediation
Triage & Remediation
See Nullify in Action
Nullify writes the fix, gets it through CI and hands it to the owner to merge.