Website Maintenance After a Data Breach: What to Check First

Isolate the hacked site, preserve logs, remove backdoors, and restore clean backups in the right order.

After a data breach, check containment first: isolate the affected website hosts and stop further data loss. Then preserve logs and system images before you wipe, repair, or restore anything. Website maintenance here means incident recovery for the live site, not routine updates. For WordPress, Drupal, or custom sites, the order matters because cleaning too fast destroys proof and leaves backdoors in place.

Table of Contents

How do you contain the site safely?

Disconnect impacted hosts from the network at once. If several subnets show signs of compromise, take the network offline at the switch level. CISA advises isolating impacted hosts and using out-of-band phone calls during multi-subnet incidents in its StopRansomware response guide. Use phone or a separate channel for response talk.

Attackers with mail, chat, or ticket access can watch remediation. Keep hosting, DNS, and ad accounts in this isolation check when shared logins exist. Do not power down servers unless disconnection is impossible. Memory evidence disappears on shutdown. Keep one person recording every action, time, and system touched.

What evidence should you save before cleaning?

Save cloud volume snapshots, firewall logs, endpoint detection logs, VPN logs, and full disk and memory images. Preserve access logs, error logs, file-change records, and backup catalogs from before and after the suspected breach. These records show entry, movement, and which customer data was exposed. Treat the site as read-only during collection.

Avoid installing cleaners, restoring files, or changing passwords before images and logs are secured. Each change overwrites traces investigators need. Store copies off the affected network. Label each item with source, date range, and collector. That order prevents a second loss when systems are rebuilt.

Who should act in the first hours?

Bring forensics, legal, IT, and management together at once. The Federal Trade Commission directs businesses to form that team to stop further loss and identify affected data in its breach response guide for business. Assign one lead for technical containment and one for records. Document hosting access, admin roles, API access, and network segmentation.

For agencies, include the client owner and ad-account holder so tracking pixels and integrations are covered. Map which system held which data. List contact forms, checkout records, member tables, email lists, and connected CRMs. That inventory decides notification and restoration priority.

How do you remove access and close the entry point?

After containment, delete malware and backdoors, disable breached accounts, and revoke API keys and sessions. Reset all affected system passwords only after malicious code is removed. Otherwise attackers reuse saved access and undo the reset. Then patch the exploited software, CMS core, themes, plugins, and credentials.

Prioritize flaws in CISA's Known Exploited Vulnerabilities catalog, which carries binding federal remediation deadlines. Check these common persistence points: Confirm the fix before reconnecting services. Rescan files, review outbound traffic, and watch for reinfection. Record what was found and changed.

  • hidden admin users, SSH keys, cron jobs, and scheduled tasks
  • unknown plugins, mu-plugins, themes, file-manager scripts, and redirects
  • OAuth grants, API tokens, webhooks, and payment or email integrations

How do you restore and meet notification duties?

Rebuild affected systems on a clean network. Restore data from offline encrypted backups, with critical services first. Confirm what each system held before restoring so checkout, login, and lead capture return in the right order.

Notify local law enforcement and affected businesses and individuals as state breach laws require. For health-site protected health information, notify affected individuals, HHS and, if more than 500 residents in one state are affected, prominent media within 60 days of discovery. Because the FTC guide is nonbinding and state deadlines vary, confirm duties with counsel.


You Might Also Like