Plan a defensive security check of my own site
Plans a defensive security check of a site you own, with scope, safe tests, a fix order and when to bring in a professional.
Task:
Plan a defensive security check for my own website that I can finish in [available time].
Context:
The site is [site description] built with [tech stack] and hosted on [hosting]. It handles [kinds of user data]. I own the site, or I have written permission from the owner to test it.
Rules:
- Cover only my own site and its components. Do not include steps aimed at other people's systems.
- Order the checks by risk: login and sessions, input handling, outdated components, security headers, backups and access rights.
- For each check give what to look at, the safe way to do it on a staging copy, and what a good result looks like.
- This is general information and not professional advice. Say which findings should go to a qualified security professional.
- Never ask me to paste passwords, keys or tokens into this chat.
Result:
A table with the columns order, check, safe method and good result, at most ten rows, then a list of three signs that I should hire a security professional.