Author: GDanu
-
WordPress Hosting Pre-Launch Checklist (The One Most Sites Skip)
Most WordPress problems appear after launch, not before. Slow performance, security incidents, SEO indexing issues — all because basic hosting checks were skipped. This checklist is designed to be used before any WordPress site goes live, regardless of hosting provider. Table of Contents Hosting & Server Checks PHP & Environment Security Hardening Performance & Caching…
-
Secure a WordPress Hosting Account in 30 Minutes: cPanel Checklist
Most WordPress hacks are caused by weak defaults. This checklist focuses on actions you can complete in under 30 minutes to significantly increase security. 1. cPanel Security Settings Enable immediately: Two-Factor Authentication Change cPanel password Enable Hotlink Protection Disable: Unused FTP accounts Old email accounts 2. WordPress Hardening Checklist: Change admin username Enforce strong passwords…
-
CloudLinux LVE Limits Explained: How to Stop WordPress Throttling
CloudLinux is designed to protect shared hosting environments. When your site exceeds limits, it gets throttled. This article explains how to identify the problem and reduce resource usage from the client side. 1. Signs of LVE Throttling Typical symptoms: Error 508 Resource Limit Is Reached Site loads slowly only sometimes wp-admin becomes unresponsive Spikes during…
-
WordPress on Shared Hosting: Practical Performance Checklist
Shared hosting is not slow by default. Most WordPress performance issues come from incorrect settings, not from the hosting itself. This checklist focuses on actions you can actually take inside cPanel and WordPress to get the best possible performance without changing the hosting plan. Table of Contents PHP Configuration WordPress Caching Database Optimization Media and…
-
Linux Server Hardening Checklist for Production Environments (2026 Edition)
Linux servers are rarely compromised through advanced exploits. Most breaches occur because of weak configurations, exposed services, or poor access control. A hardening checklist provides a repeatable baseline that improves security while maintaining operational stability. Operating System Baseline Systems must be fully patched and supported. Unused packages and services should be removed to minimize attack…
-
How to Build a Practical Incident Response Runbook for SMB Environments
Small and medium-sized businesses are frequent targets of cyberattacks, yet most of them lack a clear and usable incident response process. In many environments, incident response exists only as a policy document or not at all. When an actual incident occurs, teams improvise, leading to delayed containment and unnecessary damage. A practical incident response runbook…
-
Incident Response – First 30 Minutes Checklist
Purpose This checklist provides a structured guide for the first 30 minutes of any security incident, reducing panic-driven decisions and ensuring consistent response. Phase 1: Situation Control (0–10 minutes) Identify incident type (access, malware, DoS, data exposure) Identify affected systems Assign incident lead Start activity log (who/what/when) Phase 2: Containment (10–20 minutes) Block malicious IPs…
-
Windows Privilege Escalation Suspicion – Incident Response Guide
Privilege escalation often follows an initial foothold. Early identification and controlled response are critical to limit damage while preserving evidence. Detection Indicators New local admin accounts Event ID 4672 (special privileges assigned) Unexpected group membership changes Suspicious scheduled tasks or services Scope Windows endpoints and servers Local and domain-joined systems Phase 1: Evidence Collection (READ-ONLY)…
-
Suspected RDP Brute Force Attack – Incident Response Runbook
RDP brute force attacks are among the most common intrusion attempts against Windows systems. This runbook provides a structured response workflow focused on containment, evidence preservation, and recovery without disrupting production unnecessarily. Detection Triggers Repeated Event ID 4625 (failed logon) Login attempts from multiple IPs Security alerts from SIEM or firewall Unexpected account lockouts Scope…
-
Patch Management Without Downtime
Applying patches reduces risk, but unplanned outages often come from missing validation and rollback planning. This runbook outlines a conservative, production-safe patching workflow. Scope Windows and Linux servers Security and stability patches Production and pre-production environments Common Failure Points Patching without dependency awareness No baseline or pre-change snapshot Missing service validation Incomplete rollback procedures Patch…