menu_open Columnists
We use cookies to provide some features and experiences in QOSHE

More information  .  Close

A 10-step response plan for when a website you use is hacked

1 0
yesterday

Get Quartz in your inbox

Free daily briefing on global business news.

A 10-step response plan for when a website you use is hacked

Knowing what to do after a data breach limits the damage, from changing reused passwords to freezing your credit, plus how AO3 users can protect a pen name

A breach notice usually arrives after the damage on the company's side is already done. The data has been copied, and nothing a customer does can pull it back. What a person controls is the window that follows. The hours and days after a leak decide whether a stolen email address and password stay a single problem or become a key to many other accounts.

That is the core of knowing what to do after a data breach. The main danger to other accounts does not come from the hacked website itself. It comes from credential stuffing. This is the practice of taking leaked email and password pairs and trying them automatically on other sites. Banks, email providers, shopping accounts and streaming services all become targets if the same password protected them. A breach at a small hobby forum can end with someone inside a person's main inbox.

The right response also depends on what was exposed. A leaked email address alone calls for caution about scam messages. A leaked password calls for changes across every account that shared it. A leaked Social Security number, card number or date of birth raises the stakes to fraud and identity theft. The tools for those problems are different.

Some exposures are personal rather than financial. Archive of Our Own, the fan fiction archive known as AO3, is run by the nonprofit Organization for Transformative Works. Its accounts are tied to a username and an email address. Many writers there publish under pen names. On any site built around pseudonyms, the most sensitive piece of data may be the email address. That address can connect a pen name to a real person. The same risk applies to other fan archives, gaming communities and anonymous forums, whether or not a given site has ever been breached.

The 10 steps that follow move in a deliberate order. They start with confirming that a breach actually happened and finding out what it covered. They then turn to securing accounts with new passwords and two-factor authentication. Next come monitoring tools, including breach-lookup services, credit freezes and credit reports. The list closes with reporting identity theft if it occurs and reducing how much any single site knows about you. Each step works on its own. Readers can start with the one that matches what leaked.

Confirm a data breach through the company's official notice

Before changing anything, confirm the breach on the company's own website, its official social media accounts or in a notice it sent you directly. A verified announcement tells you what was exposed, and that detail decides which later steps you actually need.

News of a breach often arrives secondhand. A screenshot circulates on social media, a forum thread claims a database is for sale, or an email warns that your account is at risk. Some of these reports turn out to be accurate. Others are exaggerated, recycled from an older incident or written by scammers hoping to catch people in a panic.

The safest route is to type the site's address into your browser yourself rather than following a link. Companies typically post breach information in a press release, a blog post, a help center article or a status page. Many also email affected users. If the only evidence is a message you cannot match to anything on the company's own channels, treat it with suspicion.

A site going offline is not proof of a breach either. Archive of Our Own, the fan fiction archive known as AO3, has had outages caused by distributed denial-of-service attacks. Those attacks flood a site with traffic to knock it offline. That is a different problem from attackers stealing account records.

A useful notice explains what happened and roughly when it was discovered. It lists the categories of data involved, such as email addresses, usernames, passwords, payment card numbers or Social Security numbers. It should say whether stored passwords were hashed. Hashing makes passwords harder to recover, but it does not make them safe to keep using. The notice should also describe what the company is doing and what it wants users to do.

That list of exposed data shapes your response. A leak limited to email addresses mainly raises the risk of targeted scam messages. Exposed passwords mean resetting credentials. Leaked financial or government ID numbers call for stronger protections against fraud.

Legal rules push many companies toward disclosure. Every U.S. state has a breach notification law. In the European Union, the General Data Protection Regulation requires organizations to report qualifying breaches to regulators within 72 hours of becoming aware of them, where feasible. The U.K. applies the same deadline under its own version of the regulation. Timing and detail still vary from company to company. Check back for updated notices as an investigation continues. Early announcements are sometimes revised as more is learned.

Change your password on the breached account

Reset the password on the affected account as soon as the company confirms the breach. Make the change by typing the site's address into your browser or opening its official app, not by following a link in an email or text.

A new password matters even if the company says stored passwords were hashed or encrypted. Hashing makes stolen passwords harder to read. Weak or common passwords can still be cracked, though. Changing yours closes that gap regardless of how the site stored it.

The replacement should be long, random and used nowhere else. Length does more work than a scattering of symbols. The U.S. National Institute of Standards and Technology takes that position in its digital identity guidelines, published as Special Publication 800-63B. Those guidelines favor longer passwords over complicated composition rules. A passphrase built from several unrelated words is one way to get length that is still practical to type.

Avoid small edits to the old password. Adding a digit at the end or capitalizing a different letter produces something an attacker holding the leaked version can guess. The new password should share nothing with the one that was exposed.

After the reset, look for a setting that signs you out of other devices or ends active sessions. Many services place it near the password option in their security settings. Ending old sessions cuts off anyone who logged in with the stolen password........

© Quartz