Customer Security Explanation (Equifax 2017 Incident (2020 oversight))¶
Use this to explain a security topic or incident to customers in clear, non-technical language; supports notification obligations and trust.
Purpose¶
This explanation translates technical and legal context from Equifax 2017 Incident (2020 oversight) into clear customer-facing language, focusing on what happened, what protections are in place, and what customers should do. It supports transparent communication while remaining aligned with counsel-reviewed facts.
Hallucinated writing examples¶
Scenario: In an illustrative period following federal Equifax enforcement orders and ongoing MDL settlement administration (time), the Security Director (role) prepares a customer security explanation (type) for leadership stakeholders (audience).
CUSTOMER NOTICE — DATA SECURITY INCIDENT
What Happened: The 2017 incident involved unauthorized access to systems containing consumer credit-file information. Equifax remediated the vulnerability, supported law enforcement and regulators, and has continued long-term control improvements under ongoing oversight.
What Information Was Involved: Affected information included personal information associated with credit-file services, as described in prior notices. Equifax continues to provide customer resources consistent with settlement and regulatory obligations.
What We Are Doing: We are strengthening vulnerability management, access controls, monitoring, and governance reporting, and we continue independent validation of control effectiveness across in-scope systems.
What You Can Do: Monitor account and credit activity and use available identity-protection resources. Use official Equifax channels for updates and support and avoid unsolicited requests for sensitive credentials. Additional information is available at [URL].
Document-type guide: Customer Security Explanation
Writing tips: Writing best practices — Customer Security Explanation