- Public admin login
- PHP application runtime
- MySQL database
- Theme and plugin chain
- Continuous patch pressure
EPIC IT / SECURITY MODEL
NO GHOSTS
IN THE
MACHINE.
The safest unnecessary component is the one that does not exist.
01 / ATTACK SURFACE
WHAT WE
TOOK AWAY.
- Pre-built public files
- No production CMS login
- No public database
- Versioned source changes
- Explicit security controls
02 / DEFENSE IN DEPTH
SURFACE
Remove public admin tools, unused runtimes, plugins, and database access from the marketing site.
+BROWSER
Enforce HTTPS, strict content rules, clickjacking protection, and restrained browser permissions.
+RELEASE
Build from reviewed source, verify the output, and deploy a known version instead of editing production.
+OPERATIONS
Keep access narrow, patch dependencies, retain clean backups, and monitor the endpoints that matter.
+03 / CLEAN BREAK
DO NOT CARRY THE
INCIDENT FORWARD.
The new release is built independently from clean source. The old WordPress web root should be isolated, preserved only for investigation, and never copied into the replacement environment.
NEED A PRACTICAL SECURITY REVIEW?
REDUCE THE RISK ↗