HomeGuide

Security readiness guide

What to check before you launch a web app, and how to prepare for a penetration test so you get the most out of it.

Ten checks before launch.

These are the issues we find most often in real projects. None of them need a big budget, only attention before go-live.

  1. Every route checks who is asking

    Access control is enforced on the server for every record, not only hidden in the UI. Changing an ID in a URL or API call must return 403 or 404.

  2. Sessions are locked down

    Session cookies are HttpOnly, Secure and SameSite. Sessions expire, are rotated on login, and are revoked on logout and password change.

  3. Passwords are hashed properly

    bcrypt or Argon2 with a sensible cost. Login and reset endpoints are rate limited, and error messages do not reveal which accounts exist.

  4. Input is validated, output is encoded

    Validate on the server against a schema. Use parameterised queries. Render user content as text, never as HTML.

  5. Secrets live outside the code

    No keys or passwords in the repository or its history. Use environment variables or a secret manager, and rotate anything that leaked.

  6. Security headers are set

    Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy and frame-ancestors are configured and tested.

  7. Dependencies are current

    Lockfiles are committed, known-vulnerable packages are updated, and you know who is responsible for patching.

  8. Backups are tested

    Backups run automatically, are stored separately, and you have restored one at least once.

  9. Logs answer questions

    Logins, permission failures and admin actions are logged with time and user, without logging passwords or personal data you do not need.

  10. Errors stay quiet

    Production returns generic errors. Stack traces, debug pages and directory listings are off.

Preparing for a penetration test.

A little preparation turns a test from a scan of the front door into a real look at how your application can be abused.

What the report looks like

  1. Confirm ownership and scope

    List the domains, apps and APIs in scope, and get written authorisation from whoever owns them, including hosting or third-party providers if required.

  2. Pick the environment

    Staging that mirrors production is ideal. If production is in scope, agree a test window and what is off limits.

  3. Create test accounts

    One account per role, plus a second account in the same role so access between users can be tested.

  4. Share what helps

    API documentation or an OpenAPI file, a short description of the business logic, and anything you are already worried about.

  5. Name a contact

    Someone who can answer questions during the test and can be reached quickly if a critical issue turns up.

  6. Plan time to fix

    Book developer time after the report lands, so fixes and the retest happen while everything is still fresh.

Got something to build, or something to break?

Tell us what it is. A few lines are enough to start.