Skip to main content

Security Hardening

Closing the routes that actually get used. Almost every compromise at this size starts with a credential or an unpatched component, not a sophisticated attack.

What Actually Happens To Businesses Your Size

Not targeted attacks. Automated ones.

Scanners sweep the internet continuously for known flaws in common software, find them indiscriminately, and exploit them without anyone deciding you were interesting. Being small offers no protection whatsoever.

The good news is the corollary: these attacks are almost entirely against known vulnerabilities with available fixes, and against reused credentials. Which means the defences that matter are unglamorous and cheap, and the expensive products mostly address threats you do not have.

The Order That Actually Reduces Risk

Roughly this, and it is not the order most security proposals follow.

Second factors everywhere, starting with email. Credential reuse is the most common single route in, and a stolen password stops being sufficient. Free.

Patching on a cadence. Most vulnerabilities are in dependencies rather than your own code, they are published, and exploitation attempts begin within days of the fix being available.

Access review. Who can reach what, and removing what accumulated. Former contractors, old keys, permissions granted for a project that ended.

Check what is exposed to the internet. Administrative interfaces, database ports, staging environments. This one regularly finds something.

Verified backups. Not whether they run. Whether a restore has been performed.

Those five remove the overwhelming majority of realistic risk and none requires a product.

The Flaw Worth Testing Yourself

Open one of your own records and change the identifier in the address. If you see somebody else’s data, the system checks that you are logged in and never checks whose data you asked for.

Automated scanners rarely find this because nothing about the request is malformed. Only the business rule is missing. It is the most common serious flaw in business applications and you can test it in a minute, including on exports and reports where the check is most often forgotten.

What Moves The Price

Whether it is a review or remediation. Finding problems is quick; fixing them across a codebase is not.

How much is unpatched. A system two years behind is a project rather than a task.

Whether there are tests. Changing security-relevant code without them is slow because everything needs manual verification.

Compliance requirements, which add evidence and documentation to the work.

Where This Goes Wrong

Buying a product instead of doing the basics. A firewall in front of an unpatched system with shared logins and no second factors is comfort rather than security.

Penetration testing too early. A test on a system with obvious gaps produces an expensive report confirming what was already knowable. Do the cheap things first.

A report with no remediation. Findings nobody fixes.

Treating it as a project. Patching and access review are continuous. A one-off hardening decays from the day it finishes.

Questions To Ask Whoever Quotes For This

  • What are the five cheapest things we should do first? If the answer starts with a product, be sceptical.
  • Is second-factor authentication enforced everywhere, including admin?
  • What is exposed to the internet that does not need to be?
  • When did we last verify a restore?
  • Does the quote include fixing, or only finding?

A Brief You Can Send Anyone

What we run: [systems, and what data they hold]
What worries us: [the specific concern, or a customer asking]
Who has access: [including former staff and suppliers]
When it was last patched: [honestly, including “we do not know”]
Compliance obligations: [if any]
What a breach would cost us: [reputation, contracts, regulatory]

How We Work

The cheap things first, because they remove most of the risk and make anything afterwards worth doing. Then remediation of what is actually reachable, prioritised by what an attacker gains rather than by a generic severity rating. Where the system was built with AI and nobody has read the code yet, we usually start with an AI Sign-Off instead, which takes in these checks as part of a review against what the software is meant to do.

Ongoing patching belongs in a support arrangement rather than a project, because it is the part that decays.

Get in touch and we will start with what is exposed.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.