A website scan can return a long list of warnings. Before turning it into a backlog, check which findings expose sensitive data or support an actual attack and which are configuration improvements. The labels help, but the evidence and affected function should determine the order of work.

Start with what the scanner observed, then review severity in the context of your site.

Severity ratings exist for a reason, and they're not interchangeable

Read the provider’s severity definitions. Critical and high findings generally need prompt review because of their potential impact. Medium and low findings may cover narrower exposures or additional protections. Informational entries usually describe configuration rather than a confirmed vulnerability. A label should be accompanied by evidence and an explanation of the consequence.

Do not assign the same urgency to every failed check. Review the demonstrated impact before scheduling fixes, especially when a report mixes application vulnerabilities with missing headers.

Security headers: context decides the severity

A missing Content-Security-Policy isn't automatically critical. It depends entirely on what else is true about the site. On a page that loads inline scripts from multiple third-party sources, a missing CSP means there's effectively nothing stopping an injected script from executing with full access to the page, which pushes that finding toward high or critical. On a simple, mostly static site with a minimal script footprint, the same missing header is a real gap worth closing, but the immediate exploitability is lower.

Missing X-Content-Type-Options or Permissions-Policy headers typically land as low severity. They close off narrower, less commonly exploited attack paths, and their absence rarely represents a direct route to compromise on its own. Worth fixing, not worth an emergency deploy.

Review framing restrictions against the page’s function. Clickjacking on an account-settings page can cause an unauthorized action; framing a public marketing page may have a smaller consequence. Test what a user can be induced to do.

Not every cookie on your site carries the same risk if misconfigured. A session cookie missing protection against client-side script access, combined with any script injection path elsewhere on the site, is a critical finding, because that combination is a direct route to session hijacking. The same missing protection on a non-sensitive preference cookie, like a theme setting, is low severity, because there's nothing meaningful to steal.

Same-site protection follows a similar pattern. Missing it on an authentication cookie meaningfully raises cross-site request forgery risk and should be treated as high priority. Missing it on a cookie that just tracks whether a user dismissed a banner is close to informational.

Assess cookies individually. An authentication token and a banner preference can have the same missing attribute but very different consequences.

CORS: this is where severity jumps fast

An API that reflects arbitrary origins and permits credentialed requests needs careful validation. Test whether another origin can read sensitive responses using a test user’s session. That demonstrated access is stronger evidence than the header values alone.

A broad non-credentialed CORS policy may be intentional for public data. Check the endpoint’s purpose and the information it returns before deciding whether to restrict it or assign severity.

Transport and redirects: mostly foundational, occasionally severe

Missing HSTS or an incomplete preload configuration is usually a lower severity finding, a hardening gap rather than an active exposure, since most traffic still gets upgraded to HTTPS through standard redirect behavior. Where transport findings jump to critical is when HTTPS isn't properly enforced on pages handling credentials or payment data, or when mixed content is loading active resources like scripts over an unencrypted connection on an otherwise secure page. That combination undermines the encryption protecting the rest of the page and deserves immediate attention, not a backlog ticket.

Reading a report the right way

Review critical and high findings first, confirm their impact, and assign owners. Schedule the remaining work according to exposure, effort, and the application’s release cycle. Keep lower-severity improvements in a visible backlog.

Ask for evidence and an explanation when a report contains only failed checks. Engineers need to know which request or configuration produced the finding and what should change.

Ceron Check reports the observed headers, cookie flags, CORS behavior, and redirects with explanations and suggested fixes. Findings are ordered by severity. The check is free and requires no login; use its results as a starting point for reviewing the affected pages and endpoints.

Back to the blogExplore Ceron