Vendor Cybersecurity Reassessment Checklist

An editable 17-page field guide for the analyst reopening a vendor approved two years ago that has since changed hosting, subprocessors and authentication. A reassessment is not the original questionnaire run again: it targets what materially changed, whether the findings accepted last time were ever closed, how controls have actually performed, and what the decision should be now. Every item explains why it matters, the result a good answer should produce, the evidence to request, and the next analyst move.

What’s inside

• A readiness page confirming the vendor entity, product, environment, region and service in scope, business criticality and data sensitivity, the internal owners who can validate each claim, and how restricted evidence will be handled
• 30 numbered items, VCR-01 to VCR-30, grouped into 5 control domains and classified as they are in the guide: 27 marked Core and 3 marked Triggered
• Reassessment Scope and Change; Prior Findings and Assurance; and Current Security Control Evidence
• Resilience Incidents and Dependencies; and Risk Decision and Follow Through
• Response, evidence reference, action owner and due date against every item, so the completed form is the assessment record rather than a questionnaire you transcribe later
• A rapid final checklist that restates all 30 items on one page for the closing challenge

The assessment rule is written into the form: evidence should be current, complete for the service in scope, usable by your organization, tested where capability matters, and linked to a decision. A certificate, policy, screenshot or vendor statement is not enough on its own when it does not prove the specific requirement.