Insights:Pre-Launch Checklist for Website Security and Account Permissions
I. Password Inspection
- Default passwords for the admin panel, database, server, and email have been changed.
- No shared accounts (multiple users on the same login).
- Password strength meets requirements (length, complexity).
- No plaintext passwords in code or configuration files.
- Accounts for departed employees have been disabled.
II. Attack Surface
| Item | Standard |
|---|---|
| Admin panel path | Not easily guessable; non-default |
| Ports | Only required ports open |
| Debug mode | Disabled in production |
| Error details | Stack traces not exposed externally |
| Directory listing | Disabled |
III. Roles & Permissions
- Every account has an assigned role.
- Number of admin accounts is controlled (no more than 3).
- Editors cannot modify permissions; reviewers cannot publish directly.
- Front-end user accounts are separated from back-end accounts.
- Permission changes are logged.
IV. Sessions & Transmission
- Full-site HTTPS; HTTP automatically redirects.
- Cookies set with
HttpOnly,Secure, andSameSite. - Session ID is regenerated after login.
- Idle timeout enforced (e.g., 30 minutes).
- Sessions are destroyed on logout.
V. Logging & Auditing
- Successful and failed logins are recorded.
- Critical operations (publish, delete, modify permissions) are logged.
- The log includes timestamp, account, IP, and object.
- Logs cannot be deleted by regular accounts.
- The retention period is at least 90 days.
6. Backup and Recovery
- Backups are stored on a different machine and in a separate directory from the site.
- The backup account is independent.
- The most recent recovery drill was successful.
- Critical data has an offline copy.
7. Dependencies and Vulnerabilities
- Frameworks and plugins are not excessively outdated.
- No components with known high-risk vulnerabilities.
- The upload function enforces file-type and size limits.
- Forms have anti-duplicate-submission and rate-limiting measures.
Additional Checks on Launch Day
- Were any unauthenticated endpoints added?
- Are test accounts present in production?
- Has test data been written to the live database?
- Have temporary debug switches been disabled?
Acceptance Criteria
- No high-risk ports exposed per external scan.
- 100% of default passwords have been changed.
- Logs can show the most recent login and publish operations.
- Backups can be restored to the test environment.
Common Oversights
- Only the admin password was changed; the database still uses defaults.
- Debug mode from the test environment carried over to production.
- Log tables were accidentally cleared alongside business data.
- Backups reside on the same disk as the site.
Scope
This checklist covers baseline protections and does not replace professional penetration testing. Sites handling payments or personal information should undergo a dedicated security assessment before going live.
Related reading: