Glossary
Remediation
Definition
Remediation is the work done to correct a security weakness and check that the fix has addressed the problem.
It turns a finding into a verified corrective change. Temporary safeguards may reduce exposure while a permanent fix waits, but the remaining risk still needs an owner.
A customer may include “Remediation” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Remediation moves a security finding from diagnosis to corrective action. It may mean installing an update, removing an exposed account or changing a procedure that repeatedly fails. NIST's remediation definition centres on correcting known weaknesses or reducing the likelihood that they can be exploited.
The finding needs a person responsible for fixing it and a way to verify the result. Record which systems are affected, what was changed and whether the same weakness appears elsewhere. Closing a ticket should follow that verification rather than simply recording that someone attempted a fix.
For example, a small online retailer might learn that a former contractor still has an active administrator account. Deleting that account fixes the immediate exposure. Checking other former contractors and correcting the departure process addresses the reason it happened, so the problem is less likely to return.
Some fixes need testing, planned downtime or a replacement system. Prioritise according to the exposed service and potential harm, and record any temporary safeguards while the permanent work waits. An accepted delay should have an owner and review point. Verify a reported fix by checking the affected system again, then look for the same weakness elsewhere. A ticket marked complete is not evidence that the problem is gone.