1. Inventory systems and owners
List the domain registrar, hosting, CMS, form recipients, external scripts and integrations. Name an owner or function and show where changes are approved.
Review accounts with administrator permissions and how access is removed. Enable multifactor authentication where accounts support it and document a safe recovery method.
2. Make updates and forms testable
Record who assesses and applies updates and how changes are tested before release. A current version does not prove a separate integration works.
Send a fictional test inquiry through the form. Check validation, recipient, confirmation and what is stored. Do not collect more information than the task requires.
3. Review headers in the context of the site
Capture HTTP responses for representative pages and record the security headers actually present. OWASP explains common headers and their limits; choose settings that fit the site’s resources and integration needs.
Test changes in staging or another safe environment. A Content Security Policy or embedding rule can block scripts, payments, video or tools if allowed sources are unknown.
4. Rehearse one recovery task
Follow the organization’s documented process to restore a bounded page or content change. Check what can be recovered, who has access and how the restored result is verified.
Keep conclusions within the test’s scope. Restoring one page does not prove recovery of a database, accounts or the entire operating environment.
| Question | Evidence to collect |
|---|---|
| Who owns access? | Current account and owner register |
| Does contact work? | Fictional test with confirmed receipt |
| What does the server send? | Saved header responses for tested URLs |
| Can a change be reversed? | Bounded exercise and recorded result |