Account, privacy and security
Interpret platform vulnerability evidence
Read the matched component, advisory and version limits before deciding on a security response.
Reviewed
Check the finding and its source
Open the platform finding and review the component identity, installed version, advisory references, confidence and observation date. A known advisory match is different from evidence that someone exploited the problem.
External vulnerability intelligence can be delayed or unavailable. A component without a match is not proven secure, especially if its identity or version could not be confirmed.
Plan an appropriate response
Ask the website maintainer to compare the advisory’s affected range and remediation with the actual installed component. Review the vendor guidance and compatibility before an approved update.
For an urgent suspected incident, use your organisation’s incident process and involve the responsible security or hosting team. Do not wait for a monitoring score to establish whether an incident needs attention.
Verify afterwards
After remediation, confirm the installed version and the important customer tasks, then review a later collection. A resolved finding means the relevant evidence changed; it does not certify the entire website.
If the component or version looks wrong, send support the finding reference and component name through the normal support route. Do not send credentials or private incident logs without an appropriate arrangement.
