Windows servers collect years of small changes. Permissions get widened to fix a problem on a busy day, services are switched on for convenience, and old roles stay running long after anyone needed them. None of it is visible until someone takes advantage of it.
Windows is our specialism. We have built and run systems on Windows Server and SQL Server for many years.
How we work
We start by understanding how the server is really used: which software runs on it, who logs in, what it shares. Then we reduce what an attacker could use, without breaking the work.
What hardening usually involves
Tightening file and share permissions so people reach what they need and no more. Separating everyday accounts from admin accounts. Removing old user accounts, including people who have left. Switching off services and roles nobody uses. Reviewing scheduled tasks and what they run as. Making sure updates are installed and that the server isn't running an unsupported version of Windows. Checking IIS and SQL Server settings where they are installed. Checking that backups exist and can be restored.
PCs too
The same thinking applies to office PCs: updates, antivirus, who has admin rights, and what happens if a laptop is lost.
Who it suits
Businesses with an office server or a few, a small IT setup that has grown without a plan, or a Cyber Essentials application coming up.
Will hardening stop our software working?
Not if it is done carefully. We find out what the server does first, make changes in small steps, and check with you as we go.
Our server is old. Is it worth hardening?
If its version of Windows is out of support, the honest answer is usually to plan a replacement. We'll tell you, and help keep it as safe as possible in the meantime.
How much does it cost?
It depends on how many servers and PCs you have. You get a price after a short look at your setup.
The aim is not to lock systems down blindly, but to make them predictable, auditable and resilient if a password is ever stolen.