Not sure where to start?

Start with free introductory courses

Create account
All security guides

AICI · Free practical security guides · 10 min read

A website security baseline that a small business can actually maintain

A repeatable baseline for inventory, authentication, software updates, backups, logging and validation without intrusive scans.

A security snapshot is useful only when someone can act on its findings. Start with a documented asset inventory and ownership; a random automated scanner cannot tell you whether an application is in scope, whether a business rule is safe, or whether a backup can be restored. This baseline is a governance and verification checklist — not a penetration test or a certification.

Who this guide is for

CTOs, website owners, SaaS teams and business operators responsible for production websites.

1. Build a real inventory and assign owners

Write down your production domains, hosting providers, admin consoles, public APIs, third-party scripts, DNS/CDN ownership and deployment process. Identify where secrets live and who can modify production. A forgotten staging subdomain or unused privileged account can weaken security regardless of the main site's design. Avoid publishing internal system details in the inventory.

  • List each service, its purpose, owner, environment, data sensitivity and public exposure.
  • Confirm HTTPS, domain renewal, access to DNS and least-privilege admin roles.
  • Record where patches and infrastructure changes are approved, tested and rolled back.

2. Check the controls that break most often

Review authentication and authorization separately; MFA on administrator accounts does not replace object-level access control. Check that dependencies are supported and updates are tracked, configuration secrets are not exposed, input is validated and error messages do not disclose sensitive information. Review the application against relevant OWASP ASVS controls rather than claiming a single scanner proves safety.

  • Verify privileged account MFA, account recovery, revoked session behavior and authorization of API operations.
  • Track updates for the runtime, dependencies and hosted services with owners and deadlines.
  • Review browser headers, application logging and privacy-safe alerting; test backups by actually restoring a nonproduction copy.

3. Prioritize fixes by exposure and verify them

A severity score alone does not prove a breach or predict business impact. Rank by internet exposure, exploitability, data sensitivity and operational consequence. A critical issue on an unreachable lab asset and a medium issue on a sensitive public API may need different priorities. Capture evidence for authorized findings, map each fix to an owner, and schedule a retest.

  • Create a risk register with issue, affected asset, scope, evidence, owner, target date and status.
  • Fix high-impact access-control and actively exposed issues first; document temporary mitigations when patches are delayed.
  • Retest changed behavior and monitor for regressions after deployment.

Worked prioritization — hypothetical e-commerce site

The team discovers an old staging admin account without MFA, a missing non-critical browser header on the marketing site, and customer order access that relies only on a client-provided identifier.

What the response should show

Check exposure and access authorization immediately. Disable or secure the stale admin account, verify server-side order ownership and add regression tests; prioritize the header improvement appropriately. Document a real owner and retest evidence for each item.

Deliverable: a maintained inventory, control checklist, risk register and scheduled retest. For assurance about specific vulnerabilities, commission an authorized scoped assessment by qualified professionals.

A website security baseline that a small business can actually maintain | AICI