Maintenance

Incident Response Checklist for Linux Web Hosting

Follow a structured response process to scope, contain, investigate, recover from, and learn from Linux hosting incidents.

A server incident may involve an outage, compromised credentials, malicious files, unexpected resource usage, or suspected data exposure. The first objective is to protect users and preserve enough evidence to understand what happened. Unplanned cleanup can destroy logs or timestamps that are needed for investigation.

1. Establish scope and preserve evidence

Record the detection time, affected domains, symptoms, recent deployments, and people involved. Capture service status, active connections, process lists, disk usage, and relevant logs before making disruptive changes where feasible. Store evidence in a protected location and restrict access.

2. Contain the immediate risk

If compromise is suspected, isolate the affected host or service using the provider's network controls where possible. Disable exposed credentials, revoke suspicious sessions, and restrict administrative access. Avoid deleting suspicious files before preserving copies and metadata. If customer data may be affected, follow the organization's legal, contractual, and regulatory notification process.

3. Investigate systematically

Review authentication logs, web access and error logs, PHP application logs, database activity, scheduled tasks, recently modified files, and new accounts or SSH keys. Compare against a known-good deployment artifact. Check whether the issue is limited to one account or affects the shared operating system and other tenants.

4. Eradicate and recover

Do not assume that removing one malicious file removes an attacker's access. Patch the exploited weakness, rotate potentially exposed credentials, rebuild from trusted sources when system integrity is uncertain, and restore data from a verified backup. Reapply least-privilege permissions and validate the application before reopening traffic.

5. Learn and prevent recurrence

Document the timeline, root cause, impact, recovery steps, and unresolved questions. Add monitoring or tests that would have detected the incident earlier. Review backup restore results and update the response contacts and runbooks.

Never promise that a server is clean based only on a quick malware scan. For serious compromise, involve qualified incident-response specialists and the hosting provider. Preserve chain of custody when evidence may be needed for legal or insurance purposes.

Share this page Help other developers discover this resource.