Preview draft · Pending review by the publication’s editor.
Use a repeatable structure
We suggest five fields for a client alert: what happened, whether the client is affected, what is being done, what the client must do and when the next update will arrive. Link the original advisory.
Separate unknowns from reassurance
If inventory matching is incomplete, say so. Avoid saying a client is unaffected until the relevant systems and versions have been checked. Keep speculation out of the opening summary.
Close the loop
Name the service owner and record verification. A later update should explain what changed and any remaining exception. The NIST framework provides a broader context for assigning responsibilities across response and recovery.
Sources & further reading
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
