Sound familiar?
Secure today, open again after the next release
You know what needs fixing, from an audit, a scanner or a question from your client. But knowing isn't the same as closed:
The findings are on a list, and nobody has time to work through them.
A Content Security Policy was switched on once, broke a form, and was switched off again.
Marketing adds a new script, and nobody checks what it is allowed to load.
Someone sends e-mail in your domain's name, and your customers can't tell it isn't you.
A certificate expires, and visitors get a warning before you do.
A security audit tells you where you stand. Hardening closes the gaps, and monitoring keeps them closed.
What you get
Security that keeps up with your website
The gaps are closed, not just listed.
We make the changes in your platform. For what sits with your IT or hosting partner, we work with them, or take it over.
Your site stays as it should.
Releases, new scripts and new integrations are checked against the policy you have, so a fix doesn't quietly disappear.
You hear it from us first.
Blocked scripts, a header that changed or a certificate that is about to expire reach us, not your visitors.
Your domain is harder to misuse.
With SPF, DKIM and DMARC, receiving mail servers can check whether e-mail in your name is authorised, which makes spoofing your domain harder.
Hardening
What we set up
Security headers. HSTS, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, plus the CSP directive frame-ancestors against clickjacking, with X-Frame-Options for older browsers. Set in your platform, your CDN or your server.
Content Security Policy. A policy that lists which scripts, styles and frames your pages may load, with a fresh nonce on every response instead of unsafe-inline. We start in report-only, so nothing breaks, and enforce it once the reports are clean.
TLS and HTTPS. Current protocol versions, one redirect to https and to your canonical host, and HSTS, rolled out in steps. Preload is optional: we only consider it once every subdomain supports HTTPS for good.
Domain and e-mail. CAA records for your certificates, and SPF, DKIM and DMARC for your e-mail. We tighten DMARC step by step, so legitimate mail keeps arriving.
Platform security patches. Security patches and updates of your CMS, its packages and your front end, only the HTTP methods your site needs, access to the admin area restricted, and no server versions on display.
Repository and pipeline. Repository hardening on GitHub: branch protection with required reviews and checks, secret scanning that stops passwords and keys from being pushed, Dependabot alerts and security updates for vulnerable packages, and GitHub Actions workflows that only get the rights they need.
We do this on the platforms we build on, such as Umbraco, Sitecore, Kentico and headless front ends.
Monitoring
What we keep an eye on
CSP reports. When CSP reporting is set up, the browser can send a report every time it blocks something. If you want, those reports come in on our own CSP reporting endpoint, so you don't need a separate reporting service. We only keep the CSP data: which page, which rule, what was blocked and which browser. No IP addresses, no other visitor data. We follow them up: a new script that belongs on the site gets a place in the policy, anything else stays blocked.
Headers. A release or a change at your hosting can remove a header. We watch that they stay in place.
Certificate. We watch the expiry date and the set-up of your certificate, so it is renewed in time.
Vulnerabilities and patches. We keep you informed when new vulnerabilities appear in your platform, and plan the security patch with you, tested before it goes live.
Monitoring is part of hosting and support. What we watch, and how we report to you, is agreed in that agreement.
Who follows up the reports?
“A breach costs far more than preventing it: downtime, recovery and the damage to your reputation. That's why we close the weak spots before they become costly problems, and keep following up the reports.”
Tim Vermaelen
Front-end developer, Blastic
Our own site
Check it yourself on this page
We apply on blastic.com what we set up for you: a Content Security Policy with a nonce per request and reports to our own collection point, HSTS with preload, one redirect to https and www, and only the HTTP methods the site needs.
Open the developer tools of your browser and look at the response headers of this page.
Scope
What this is, and what it isn't
Hardening and monitoring are about the settings around your code: headers, CSP, TLS, domain, e-mail and platform updates. We don't do penetration tests, malware scans or round-the-clock security operations. If you need those, we tell you, and we work with the party that does them.
Price
What does hardening and monitoring cost?
That depends on the number of domains and environments, your platform, what sits in front of your site and how much is already in place. Start with the free quickscan from our security audit: it shows where you stand today, and you get a proposal for the hardening and the monitoring. The quickscan shows the gaps, hardening closes them, and monitoring keeps them closed.
Frequently asked questions
What is security hardening?
Hardening means removing what an attacker could use: settings that are too open, information that is shown for no reason, and missing protections. For a website that is mostly headers, CSP, TLS, domain settings and keeping the platform up to date.
What is a CSP report?
When a Content Security Policy blocks something, the browser can send a short report: which page, which rule and what was blocked. In report-only mode nothing is blocked yet, but the reports still arrive. That's how you test a policy without breaking the site.
What is the difference between report-uri and report-to?
Both tell the browser where to send CSP reports. report-uri is the older directive and still the most widely supported. report-to is the newer one and works with the Reporting API. Many sites set both. We can point both to our own reporting endpoint.
What happens when an SSL certificate expires?
Browsers show a full-page warning and most visitors leave. Forms and integrations that call your site can stop working. That's why the expiry date is something to monitor, not to remember.
What are SPF, DKIM and DMARC?
SPF lists which servers may send e-mail for your domain, DKIM signs your e-mail, and DMARC tells receiving mail servers what to do when a message fails those checks. Together they make spoofing of your domain much harder.
What is repository hardening?
Securing the place where your code lives and is built: who may change what, which checks must pass before a change goes live, and making sure no passwords or keys end up in the code. On GitHub, part of it, such as secret scanning for private repositories, depends on your GitHub plan.
What does HSTS preload mean?
HSTS tells browsers to only visit your site over HTTPS. With preload, your domain is on a list that is built into browsers, so even the very first visit goes over HTTPS. It's hard to undo, so we only add it when every subdomain supports HTTPS.
At a glance
Hardening: headers, CSP, TLS, domain and e-mail, platform security patches, repository
Monitoring: CSP reports, headers, certificate, new vulnerabilities and patches
Not: pentests, malware scans or a 24/7 SOC
Start: a free quickscan
Free quickscan
We check one URL for headers, CSP and TLS, you get the result as a PDF, and we show you what to close first.
Close the gaps, and keep them closed
Request a free quickscan. You see what is open today, and we tell you how we close it and keep it that way.