Custom Software · Security · Build vs Buy · Performance

Inspectable is not hardened: what an SME can verify from the outside

Published · Updated

Headers and response times can be checked by anyone with a browser. Access control cannot. When the verifiable surface drives the comparison, the expensive layers go unpriced.

Two things about a platform can be checked by anyone with a browser and a terminal: the headers it returns, and how long the first byte takes to arrive. Both are real signals. Neither tells you whether one account can read another account's records. When a smaller company compares a custom build with an off-the-shelf product, the inspectable surface tends to dominate the comparison, because it is the part that can be shown in a screenshot.

The part a response can prove

A Content Security Policy is delivered to the browser in the Content-Security-Policy response header, and it should be set on all responses to all requests, not just the main document. That is a verifiable claim: fetch an endpoint, read the header, repeat. Time to first byte is observable in the same way, measuring the gap between starting navigation and the first byte of a response arriving. Abbys Consult launched with a time to first byte below 200 ms and 0 technical SEO issues.

The header that is not the fix

Presence is not enforcement. To ease deployment, a policy can be delivered in report-only mode: it is not enforced, but violations are sent to the reporting endpoint named in the policy. A report-only policy looks identical to a strict one in a slide. Recommended practice for mitigating cross-site scripting is nonce- or hash-based fetch directives, and setting a policy is explicitly not an alternative to sanitising input. One header, two unrelated pieces of work.

The risks with no observable surface

Broken Access Control maintains its position at #1 in the 2025 OWASP Top 10, and the contributed data indicates that, on average, 3.73% of applications tested had one or more of the 40 Common Weakness Enumerations in that category. Security Misconfiguration moved up from #5 in 2021 to #2 in 2025. Mishandling of Exceptional Conditions is a new category for 2025. None of the three produces a header a buyer can read.

Observable does not mean measured

The inspectable numbers are also easy to misread. Good time to first byte values are 0.8 seconds or less, and poor values are greater than 1.8 seconds, but it is not a Core Web Vitals metric, so meeting that threshold is not absolutely necessary provided it does not impede the metrics that matter. A server-rendered site may show a higher time to first byte and still deliver better first contentful paint and largest contentful paint than a client-rendered one.

Write the unverifiable items into the brief

Since the costly layers leave no external trace, name them. Ask which responses carry the policy, not whether the home page does. Ask whether it is enforced or report-only, and on which date enforcement starts. Ask who reads the reporting endpoint, because great logging with no alerting is of minimal value in identifying security incidents. Ask for access control test cases by name: a category spanning 40 weaknesses is not covered by one check.

Repeat the check per surface

A header check is per response, so verification is per domain and per route, not per project. Tatano Energy runs four country domains indexed separately and seven languages from one codebase. One repository does not collapse into one verification pass; each deploy target answers requests on its own. The same applies to the invisible layers, which are configured where the application runs rather than where it is written.

Split the acceptance criteria into two columns before signing anything. The left column holds what a response can prove: headers on every response, first-byte timing, launch-time search signals. The right column holds what only a test or a review can prove: access control cases, input sanitisation, behaviour on the failure path, and someone receiving the alert. Platforms get bought on the left column and breached through the right one, so price both.

Sources

OWASP — Top 10:2025 Introduction — https://top10.owasp.org/2025/0x00_2025-Introduction/

MDN Web Docs — Content Security Policy (CSP) — https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP

web.dev (Google Chrome) — Time to First Byte (TTFB) — https://web.dev/articles/ttfb

Neurolinks case study — Four markets, one codebase — https://neurolinks.be/work/tatano-energy

Neurolinks case study — A consulting firm, dressed for trust — https://neurolinks.be/work/abbys-consult

Working on a project where these methods apply?