Security · 4 min read
Protect secrets and administrator routes
API keys, private service credentials and privileged database operations belong on trusted servers, not in browser bundles or public repositories. Use environment-specific credentials and rotate keys that might have been exposed.
Protect administrative routes at the server boundary. A hidden navigation link is not access control. Use authentication, authorization and least-privilege roles with meaningful audit trails.
Treat integrations as untrusted input
Validate form fields, API parameters and external responses. Add limits for public endpoints and clearly communicate uncertain outcomes. A domain lookup returning no registration record, for example, does not prove that a name is available to purchase.
Review dependency updates and automated changes before release. Use protected branches and CI checks for regressions, but remember that a passing build does not establish that a site is secure.
Plan for recovery
Keep recoverable backups of content and configurations, document who can roll back a deployment, and rehearse restoring essential services. For a website moving between hosting providers, maintain the working production setup until staging has passed functional and security checks.
Write down incident contacts and escalation steps. Operational preparedness often matters more than adding another security badge to a website.