\u201cAny email containing sensitive customer data or PII that is addressed to an external domain must trigger a \u2018confirm recipient\u2019 prompt. Matching of outgoing domain vs organisational domain must be verified. Common misspellings (e.g., .con vs .com) should cause anomaly alert.\u201d<\/p><\/blockquote>\n
<\/span>Incident response steps when a mis-sent email occurs<\/span><\/h3>\n\n- Immediately identify the email and recipient, and evaluate what data was sent.<\/li>\n
- Attempt retrieval\/recall if possible, or initiate contact with the unintended recipient asking deletion.<\/li>\n
- Perform root-cause: Was it autocomplete error? Typo domain? Wrong attachment?<\/li>\n
- Adjust controls: autocomplete filters, DLP rules, training for involved staff.<\/li>\n
- If data breach thresholds met (sensitive data, regulatory obligations), notify proper authorities\/affected parties.<\/li>\n
- Monitor for follow-on exploitation (e.g., credential compromise, spoofing using leaked data).<\/li>\n<\/ul>\n
\n