
IT security assessment: what the report shows, and what it does not
An IT security assessment for a small or mid-sized organisation is not a vulnerability scan with a nicer cover. A scan lists what a machine can see from the network; an assessment also asks who can reach what, whether the backup actually comes back and whether anything is written down. Knowing which one you bought is half its value, and the order in which you act on it is the other half.
A scan finds what a machine can see: missing updates, open ports, expired certificates. An assessment also covers what only a conversation and a look at the settings reveal, such as permissions, backup and documentation.
Read the report on severity and reachability together. A critical finding on a system nobody can reach from outside can wait for a moderate one that faces the internet.
Start with accounts and backup, not with the longest list. Get the admin accounts and a tested restore in order and you survive most of the incidents the rest of the report describes.
What an IT security assessment covers for an SME
For an SME, an IT security assessment is a fixed round past the areas where things go wrong in practice. Seven belong in every one, and a report that skips one says nothing about it.
- Inventory. Which devices, servers, cloud services and licences exist, and who owns them. What is not on the list is not patched and not monitored.
- Network. What is reachable from outside, how the firewall is set, whether guests, tills and cameras sit in their own segment.
- Backup. Not whether a backup runs, but when something was last restored, and whether there is a copy an attacker with admin rights cannot delete.
- Accounts and permissions. Who holds admin rights, whether multi-factor authentication is on everywhere, and how many accounts still belong to people who have left.
- Patching. How long it takes for an update to reach every device, and which systems no longer receive updates at all.
- Protection. Endpoint protection, email filtering, logging, and whether anyone reads those logs.
- Documentation. Whether someone else could take over tomorrow: password vault, network diagram, contracts, a plan for when it goes wrong.
That last one is skipped most often because there is nothing to scan. It is also the first thing an insurer or a large customer asks about.
Assessment, vulnerability scan and pen test: three different questions
The terms get used interchangeably, and then you receive something other than what you thought you ordered.
- A vulnerability scan asks: which known weaknesses are open? Automated, repeatable, and meant to run on a schedule. See our vulnerability scanning.
- A penetration test asks: how far does someone get who really tries? A person who chains weaknesses together and finds what a scanner misses, such as a logic flaw or three small issues that add up.
- An assessment asks: is the set-up as a whole in order, and can you show it? That includes arrangements, permissions, restores and paperwork.
The rule of thumb for the order: assess or at least scan first, fix, and only then test. A pen test on an environment that has never been scanned mostly produces findings a scanner would have found.
What a scan in an IT security assessment shows, and what it does not
What it shows. Missing updates, services that are open for no reason, expired certificates and devices still on a default password. Nearly every first scan also turns up equipment nobody remembered, and that is often the most useful line in the report.
What it does not show. Whether the backup comes back, whether a leaver can still log in, whether permissions fit the role, and whether anyone notices an alert. A scan sees only what is visible over the network, and it measures presence: “antivirus is running” does not mean anyone reads the alerts.
What to check. A clean report on an external scan means the outside looks fine. Always ask what was scanned, from inside or outside, and with or without credentials. A credentialed scan sees missing updates on laptops; an uncredentialed one mostly sees what faces the internet.
Three decisions before you start
- Why you want to know. For yourself, for an insurer, for a customer with a questionnaire, or for a standard. The answer sets the emphasis, and whether you need an internal picture or a report you can show a third party.
- What is in scope. Every site, the home workers too, and Microsoft 365 and the other cloud services. What is out of scope is not in the report either, and you cannot tell by looking at it.
- Who acts on it. Agree beforehand who receives the outcome and who decides per item. A report that stays with the administrator who has to fix it alone becomes a list nobody finishes.
In the UK, the NCSC’s Cyber Essentials scheme is a useful yardstick for exactly this round, and Cyber Essentials Plus adds an independent technical check by a certification body. An assessment is a good way to find out whether you would pass before you apply.
How to read the report
A good report gives four things per finding: what was found, where the evidence is, how severe it is and what is recommended. Without the evidence you cannot check whether the fix worked.
- Sort on severity and reachability. A critical vulnerability on an internal system is less urgent than a moderate one on the VPN or the mail server.
- Look for patterns. Twenty lines of “missing update” on twenty laptops are one finding: the patching process does not work. You fix that once, not twenty times.
- Read the summary last. A score or a traffic light summarises what is in the report and hides what is not. Look at the scope first.
An eighty-item report without an order does not get done. If you do not receive priorities per item, ask for them.
What to do next, in this order
- 1. Admin accounts and multi-factor authentication. Leavers’ accounts removed, admin work on separate accounts, MFA on everywhere. An afternoon’s work that closes the most used way in.
- 2. A tested restore. Restore a file and a whole machine, and note how long it took. Only then do you know what the backup is worth.
- 3. Everything reachable from outside. VPN, firewall, mail, remote desktop: update or close. That is what an attacker sees first too.
- 4. The patching process, not the patches. Make sure updates roll out automatically and verifiably, so the next scan’s list is shorter rather than different.
- 5. Inventory and documentation. Add what the scan found to the list, and write down what a successor needs to know.
- 6. Scan again. Only a second scan shows the fix worked. It is also the evidence you show a customer or insurer.
Give each item an owner and a date. Without those two, the same assessment produces the same result a year later. If you want it to keep running, it belongs in ongoing management rather than a project.
Where our work stops
What we do. The assessment itself: inventory, network, backup, accounts, patching, protection and documentation, with a report in order of priority and an owner per item. We scan on a schedule, run a penetration test as a separate engagement with an agreed scope, and the remediation afterwards is the work we do every day. We hold ISO 9001 and ISO/IEC 27001; that says something about how we work.
What we do not do. We do not certify and we are not an accredited auditor. An ISO 27001 certificate is issued by an accredited certification body, and a Cyber Essentials Plus assessment by a body licensed for that scheme. A statutory audit, such as the one alongside your annual accounts, is carried out by an auditor qualified to do it. Our report is an internal picture and a work list, not an attestation for third parties. We do help you get ready for such an audit.
Questions we get about this
The five that come up most often.
What is an IT security assessment?
It is a structured review of how your IT is set up and protected: inventory, network, backup, accounts, patching, protection and documentation. Unlike a scan it also covers what you cannot see over the network, such as permissions and whether a restore works. The outcome is a list of findings in order of priority.
What is the difference between a vulnerability scan and a penetration test?
A vulnerability scan lists known weaknesses that are open; a penetration test is a person trying to actually get in using them. You scan on a schedule and test after a new application, a major change or when a customer asks. Testing without scanning first mostly produces findings a scanner would have found.
How often should a small business have a security assessment?
A full assessment makes sense when you change supplier, after a major change or when a customer or insurer asks, and otherwise once a year. Scanning should happen more often, because new vulnerabilities appear every week. More important than the frequency is that the items from the last round are finished.
What should you fix first after a security assessment?
Start with admin accounts and multi-factor authentication, then restore something from the backup for real. After that comes everything reachable from outside. Those three cover the most common ways in and take little time compared with the rest of a report.
Can you certify us or carry out an official audit?
No. We are not an accredited auditor and we do not certify; an ISO certificate comes from an accredited certification body and a statutory audit from a qualified auditor. What we do is the assessment, the remediation and the preparation, so you are ready when that audit comes.
Further reading
The three services an assessment points to.
Shall we look at what is open on your side?
Tell us how many workstations and sites you have and why you want to know. You get a proposal for an assessment with the scope spelled out, and a report with an order instead of a long list.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.