A remediation plan is an agreed set of actions, owners and deadlines for closing the gaps found in a vendor assessment, such as missing controls, contract terms or evidence, tracked until each item is closed or formally accepted.
What Remediation plan means
Findings that are not accepted need treatment. Some sit with the vendor: fix a control, issue an updated policy, sign a contract amendment. Others sit with you: add monitoring, restrict the data shared, operate a complementary control. Both need owners.
Each item should name the finding, the action, the owner on each side, the due date and the evidence that will close it. Dates should reflect severity. A critical gap on a critical vendor may justify conditional approval or a delayed go-live.
Track remediation where the work actually happens. If engineering and legal work in a ticketing system, put the tasks there with the evidence attached, so nobody has to re-read the original report. Close each item only when the evidence arrives, not when someone says the work is done.
What to check in vendor documents
- A clear link from each action to the finding and its evidence.
- Owners on both the vendor's side and yours.
- Due dates in proportion to severity.
- The evidence that will show the item is closed.
- Escalation for overdue items.
In ProcureCortex
Findings can be sent to Jira as tasks with the evidence attached, so remediation is tracked where the work happens.
How an assessment worksRelated terms
- Risk acceptanceRisk acceptance is a documented decision by an authorised person to proceed with a known risk without further treatment, recording the risk, the reason, any conditions and when the decision will be reviewed.
- Compensating controlA compensating control is an alternative control that meets the intent of a requirement when the primary control cannot be implemented, giving a similar level of protection against the same risk.
- Residual riskResidual risk is the risk that remains after controls, contract terms and other treatments have been applied. In vendor review, it is the risk the organisation actually accepts when it approves the vendor.
- Continuous vendor monitoringContinuous vendor monitoring is the ongoing tracking of a vendor's risk between formal assessments, using triggers such as new reports, incidents, contract or sub-processor changes, financial events and external signals, so reviews happen when risk changes.
- Penetration test reportA penetration test report is the written result of an authorised simulated attack on a system, documenting the scope, method, findings with severity and recommendations. Vendors usually share a summary or a letter from the tester rather than the full report.
Sources
- Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920 (June 2023)www.govinfo.gov/content/pkg/FR-2023-06-09/html/2023-12340.htm
- NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0doi.org/10.6028/NIST.CSWP.29
Summarised for practitioners, not legal advice. Check the source text for your own obligations.