A website security audit should define the assets and controls it tests. The scope may include public applications and APIs, authorized cloud configuration, and authenticated account roles. Ask for the methods, evidence, and exclusions before work begins.
How the process runs
Agree the assets, permitted access, testing window, and engagement depth first. Identify public checks and authenticated tests separately so both sides understand what the report will cover.
Ceron uses its Agent Harness for AI-assisted investigation of configuration, services, and permissions. Suspected issues are validated against evidence before reporting. The finding should show what was attempted and what happened in the assessed environment.
At handover, review the findings and limitations with the relevant owners. Leadership needs the risk and decisions; engineering needs the reproduction evidence and remediation steps.
What gets checked
Confirm which of these three areas are included and what access each requires.
Internet-facing assets are the baseline layer, and the one that requires no internal access to test: approved websites, APIs, and exposed services, evaluated the way an unauthenticated attacker on the open internet would encounter them. This is where most vulnerability assessments start, because it maps directly to your actual external exposure without requiring credentials or internal network access to begin.
Cloud and infrastructure coverage goes a layer deeper, evaluating configuration and permissions inside the cloud accounts you authorize. Overly permissive IAM roles, exposed storage, and misconfigured network rules live here, the kind of exposure that doesn't show up in application code but sits directly in an attacker's path once they're inside.
Identity and access testing uses provided accounts to compare authentication, roles, and permissions. Include the relevant customer and staff functions so the report can establish which attempted actions were permitted or denied.
Verified findings, not raw output
Each reported vulnerability needs evidence and a severity rationale tied to the affected function. An account-takeover or cross-customer data finding should show the tested account, request, and result. Keep configuration observations distinct from demonstrated exploitation.
What you receive
The report includes a risk summary and technical findings with affected assets, evidence, and prioritized remediation guidance. It should also list tested roles and environments and explain anything excluded or incomplete.
Two tiers, matched to depth of testing
The core audit starts at $1,500 with coverage for up to three web applications or APIs, fifty internet-facing assets, and three cloud accounts, with no fee if no verified finding qualifies. Public testing needs no internal credentials; cloud configuration review requires the authorized account access agreed in scope.
An extended audit adds penetration testing and deeper coverage: authenticated access, additional environments, and the kind of manual-augmented, exploitation-focused testing that identity and access review requires. Because the scope varies so much between organizations, extended audits are quoted individually rather than sold as a flat product, priced around your actual attack surface rather than a generic tier.
Why this shouldn't be a once-a-year exercise
Keep the assessment’s date and tested version visible. New code, subdomains, and cloud changes may introduce paths the earlier review did not examine.
Set recurring reviews and targeted retests around significant changes. Track the results with the original findings so owners can see what remains resolved and what needs another check.
Getting started
Start with an asset list and the questions you need the audit to answer. Agree the scope and access, then include remediation and retest time in the plan. Expand testing as the application and its requirements grow.