Make website security work clear and owned.
Website security is more than a checklist of headers. Accounts, publishing workflows, suppliers, forms and recovery need named owners and checks. ImbaHub can review a defined website scope and recommend actions; this does not replace a penetration test or independent security assessment.
From inventory to verified action
Inventory
Assign each account and system an owner.
Prioritise
Order actions by impact and dependency.
Verify
Test the result and document limitations.
Start with assets and access
List the domain, hosting, CMS, forms, integrations and administrator accounts. Confirm who owns each account, how access is granted and how it is removed when responsibilities change.
Enable multifactor authentication for administrator and supplier accounts where supported. Do not share passwords in briefs or email, and keep secrets out of public content and ordinary project notes.
Review the website’s actual surfaces
Check update ownership, form recipients, dependencies, permission levels and the HTTP response headers the site actually sends. Headers must be considered with the site’s resources and embedded services; a generic strict policy can break working features.
Verify that forms request necessary information, reach the right recipient and do not route sensitive material through an unsuitable channel. Record findings with reproducible steps.
Set a realistic action order
Prioritise recommendations by impact, dependency and owner: resolve exposed access, clarify update responsibilities, test forms and document recovery. Identify work that belongs to a hosting or system provider.
A review is a snapshot and cannot guarantee that a site is secure or incident-free. After changes, an owner should verify behaviour, record results and schedule follow-up.
| Area | Verifiable evidence |
|---|---|
| Accounts | Owners, permissions and removal process |
| Updates | Components, update owner and decision record |
| Website surfaces | Headers, forms and integrations reviewed |
| Recovery | Documented path and bounded test |
Sources and further reading
Questions, answered
Is a review the same as a penetration test?
No. Scope and methods differ. A website review provides prioritised observations and should not be called a penetration test unless one was performed.
Can ImbaHub guarantee the site will never be hacked?
No. Controls can reduce some risks, but no review can guarantee that an incident will never happen.
Who should take part?
The domain and hosting owners, the CMS and form owners, and any supplier responsible for an integration.