Web server TLS and security header baseline
Set safe transport and browser policies, but verify application compatibility and avoid treating headers as a substitute for secure code.
Scope
For teams operating public websites and reverse proxies.
Start with the situation, not the slogan
Hardening is the practice of making the safe path ordinary and the dangerous path conspicuous. Web server TLS and security header baseline is not a demand to enable every severe-looking setting. It is a measured baseline: understand the service, reduce unnecessary exposure, protect privileged changes and prove that the business function still works.
Begin with inventory and ownership. A control applied to an unknown dependency is not defence in depth; it is surprise as a service. Record the current state, define the rollback condition and change one coherent control group at a time. The result should be supportable by the people who will receive the telephone call six months later.
TLS protects transport; browser security headers constrain selected client behaviours. Both need current configuration, but neither repairs broken access control, injection, or insecure application logic.
Composite scenario
How this usually reaches the desk
Assume a routine review records the following condition: “HTTP remains reachable without a clear redirect or HSTS deployment plan.” The appropriate response is not a mass edit copied from a checklist. Establish which systems share the condition, which legitimate workflow depends on it, and how a safe pilot will demonstrate improvement. A baseline earns trust by surviving both an attack-shaped test and an ordinary Monday.
This scenario combines common operational patterns; it is not presented as a report of one named incident.
What to look for
Begin with preserved, comparable evidence. One signal is rarely proof; use independent observations and a reliable timeline before declaring scope or intent.
HTTP remains reachable without a clear redirect or HSTS deployment plan.
Measure the current state and identify the owner before proposing a target. Configuration without ownership quietly returns to folklore after the next upgrade.
Obsolete protocol or cipher support, certificate-chain errors, and inconsistent virtual-host configuration.
Separate necessary exceptions from historical accidents. An exception needs a reason, compensating control, approver and review date; otherwise it is merely a setting wearing formal clothes.
Content Security Policy, framing, MIME sniffing, referrer, and permissions policies are absent or copied without testing.
Look for enforcement and telemetry together. A blocked action should leave a useful record, while an allowed action should remain understandable to support staff and service owners.
Working examples
Run it, read it, decide what changes
These examples use documentation addresses, test identities and bounded targets. Replace placeholders only inside systems you own or are explicitly authorised to operate. Read the expected result and next action before running the command; a successful command is evidence, not yet a conclusion.
Record HTTP security headers
- Prerequisites
- An owned HTTPS endpoint.
curl -sS -D headers.txt -o /dev/null https://www.example.com/
grep -Ei '^(strict-transport-security|content-security-policy|x-content-type-options|referrer-policy|permissions-policy):' headers.txtThe live response headers are saved and selected security controls are printed.
Header presence is not proof of a safe value. CSP report-only does not enforce, and HSTS on HTTP is ignored.
Compare values with the application design, add one header at a time in staging, and retest affected user flows.
Inspect TLS protocol and certificate
- Prerequisites
- An owned hostname.
host=www.example.com
openssl s_client -connect "$host:443" -servername "$host" -tls1_2 </dev/null
openssl s_client -connect "$host:443" -servername "$host" -tls1_3 </dev/nullEach supported handshake prints certificate and negotiated cipher information; unsupported versions fail.
Handshake failure can be a network or client issue. Supporting TLS 1.2 is not inherently weak; cipher and application context matter.
Test from a second current client, remove obsolete protocols in staging, and monitor compatibility during rollout.
Run a passive web baseline
- Prerequisites
- Written authorisation for the target URL.
docker run --rm -t -v "$PWD:/zap/wrk/:rw" ghcr.io/zaproxy/zaproxy:stable zap-baseline.py -t https://www.example.com -r zap-report.htmlA local HTML report lists passive alerts from the short spider and response analysis.
It does not prove absence of application vulnerabilities and may not reach authenticated routes.
Triage findings, arrange authenticated testing separately, fix confirmed headers or content issues, and repeat the same baseline.
What to do
Read the whole sequence before starting. Several workstreams may run in parallel, but their evidence, authority and expected outcomes still need to be explicit. Every step below points back to a concrete example; use the example as implementation evidence, not as permission to operate outside the stated scope.
Operational judgement
Controls age. Products change defaults, licences move features, teams replace applications and carefully written exceptions outlive the systems that inspired them. Review the baseline for TLS, HTTP headers and Web after material upgrades and incidents, and on a scheduled cadence. The review should remove obsolete rules as readily as it adds new ones.
Measure outcomes rather than configuration volume. Useful evidence includes reduced exposed services, stronger authentication coverage, tested recovery, fewer standing privileges and alerts that an operator can act upon. A longer policy is not automatically a safer policy; sometimes it is merely more difficult to print.
Handover
Make the result useful to the next person
Publish the baseline with its purpose, scope, authoritative management path, minimum supported versions, dependencies, allowed exceptions, monitoring, rollback and review date. Show the delta from the previous state rather than distributing a mysterious final configuration. Service owners should know which user-visible behaviour may change and where to report a legitimate failure. Security owners should know what event proves that the control blocked or detected the intended case.
The implementation record should connect “Inventory every hostname, certificate, proxy, CDN, origin, redirect, and non-browser client before changing policy.” to the verification required after “Test redirects, subdomains, APIs, downloads, framing, third-party resources, and error pages across browsers.” Include pilot population, success measures, support findings and every approved exception. If the control cannot be continuously measured, schedule a repeatable audit. A baseline is healthy when operators can explain it, new systems inherit it, exceptions remain scarce and visible, and removal of an obsolete rule is treated as maintenance rather than heresy.
Validate before you close
Use an independent configuration check and application tests to prove transport, renewal, policy enforcement, and required user flows across every hostname.
Capture the test, the expected result and the observed result. Where a person or business owner must accept restored service, name them in the record. A green dashboard can confirm that a component is answering; it cannot confirm that invoices, identities or restored data are trustworthy.
Finish with a compact closure note: the original trigger, confirmed scope, evidence retained, controls changed, tests passed, known gaps, residual risk, and the people responsible for the remaining work. Schedule a review while the timeline is still fresh enough to challenge. The purpose is not to find a person to blame; computers already perform blame with admirable efficiency. The purpose is to make the next response faster, safer and less dependent on one person remembering where the useful log was hidden.
Common mistakes
- Changing many controls at once without a rollback path.
- Applying a generic baseline without documenting business exceptions.
- Assuming a setting is effective without testing both normal use and a blocked case.
These errors usually come from haste, unclear ownership or misplaced confidence. Build the safeguard into the runbook: a required evidence field, a second-person review, a rollback test or a specific exit criterion.
Questions people ask when the clock is running
Should we apply every recommendation at once?
No. Group related controls, pilot them, define rollback and expand only after verification. Large undifferentiated changes make both outages and security improvements difficult to attribute.
What makes an exception acceptable?
A business reason, narrow scope, accountable approver, compensating control, expiry or review date, and evidence that the residual risk is understood. “It broke once in 2019” is useful history, not permanent governance.
How is the baseline verified?
Use an independent configuration check and application tests to prove transport, renewal, policy enforcement, and required user flows across every hostname. Re-test after significant platform changes and keep the result with the control record.
Safety boundary
Use these steps only on systems you own or are explicitly authorised to assess. Preserve evidence, follow your organisation’s legal and regulatory obligations, and prefer reversible actions when the situation is not yet understood.
Primary references
- HTTP Headers Cheat SheetOWASP
- Cryptographic Storage Cheat SheetOWASP
- Authorization Cheat SheetOWASP
- ZAP Baseline ScanOWASP ZAP
Editorial status: first edition. Review the linked vendor documentation for product- and version-specific changes before acting.