Short answer. Three services have similar names. A scan is a program that looks for known weaknesses. A penetration test is an authorised simulated attack on a precise target. A security audit assesses the security level of the whole organisation: what is exposed to the internet, the accounts, the PCs and servers, the data, the organisation. For a company that has never done one, you start with the audit. What you should receive: every finding with its severity on a 0 to 10 scale, the proposed fix, the estimated effort, and an order. In the example, fourteen findings, five of them serious and quick, fixed in one week.
This guide is for the manager of a company with ten to two hundred workstations whom a customer, a bank or a principal asks for an audit, for the one who wants to know where they stand before spending, and for the founder based in France who runs a company in Algeria. The notions quoted come from public sources: the definitions of the penetration test, the vulnerability scanner and the security audit, the CVSS severity scale, and the CIS, NIST and ISO/IEC 27001 frameworks. The company, the findings and their scores are a constructed example. This guide gives no prices and does not cover legal or sector obligations: those are matters for your adviser.
Audit, penetration test, scan: three services, three questions
The figure compares the audit and the penetration test on six points; the scan is a tool both of them use.
The scan. A vulnerability scanner is a computer program designed to assess computers, networks or applications for known weaknesses. It produces a list, a long one, without saying what matters in your case. It is a tool, not a service. The penetration test. It is an authorised simulated cyberattack on a system, carried out to evaluate its security: a target is chosen, a website, an application, a network, and the tester sees how far they get. It proves; it does not take stock. The audit. It is the assessment of the level of information security in an organisation: it looks at everything, from settings to ways of working, and it ranks.
In what order. Having a system that has never been tidied tested by intrusion amounts to paying someone to find the door left open that the audit would have flagged in an hour. You audit, you fix, then you test what has to resist: the online shop, the application open to customers. Comparing three quotations. Ask each one for the scope, the days spent on your premises, a sample report, and whether the second check is included. Two offers with the same title can describe a one-hour scan or ten days of work.
«You audit, you fix, then you test what has to resist.»
What a stranger sees of you from the internet
The figure shows an audit's first look: six doors visible from outside, and the severity of what is found there.
Without a password. The auditor starts outside, with what anyone can see: the services that answer at your address, your website, your mail, your domain name. In the example, six doors: a remote desktop port opened on the router, twelve mailboxes without two-step verification, a website with a plugin not updated for fourteen months, an administration page open to everyone, a domain name with no protection against spoofing, a guest Wi-Fi on the same network as the workstations.
Severity. Each finding gets a score. The most widely used scale, CVSS, runs from 0 to 10: low from 0.1 to 3.9, medium from 4.0 to 6.9, high from 7.0 to 8.9, critical from 9.0 to 10. It was designed for software flaws; for a setting or a habit, the auditor gives a score of the same kind, and must say how it was arrived at. The open port is described in the guide to remote access, address spoofing in the guide to professional mail. The written agreement. None of this is done without a signed document setting the scope, the dates and the people to warn: that is what separates an audit from an intrusion.
A security audit, in six steps
The first step is accented: without a scope and a written agreement, there is no audit.
Scope it: what is in scope, what is not, the dates, who is warned. Take stock: workstations, servers, accounts, online services; you cannot protect what you do not know, and surprises often come from a service nobody had listed. Look from outside, then check inside: who is an administrator, which accounts stay open after someone leaves, how long the servers have gone without updates, and whether a backup has ever been restored, following the guide to backups.
Rank: by severity, then by effort. Fix and check again: emergencies within the week, the rest according to a plan, and a second check at three months. An audit with no second check is a photograph; what you are buying is the fix.
Fourteen findings, five to fix this week
The figure places the fourteen findings of the example by severity and by the effort needed to fix them.
How to read it. Top left, what is serious and quick: five findings, everything critical and everything high. Closing the remote desktop port takes an hour. Turning on two-step verification for mail, a day. Updating the website, half a day. Closing former employees' accounts, an hour. Trying to restore the backup, a day. In one week the heaviest risk is gone, without buying anything.
The rest. Eight medium findings, one low: removing administrator rights from the PCs, updating a server, separating the guest Wi-Fi, keeping an inventory, training the teams. They take days or weeks and are planned, with an owner and a date. What the report must contain. For each finding: what was seen, the proof, the severity, the fix, the effort, the owner. And a first page the manager reads in five minutes. If an attacker has already used one of these doors, what to do is in the guide to ransomware and in the guide to hacking.
«An audit report is not worth its number of pages: it is worth the order in which it tells you to fix things.»
What an audit examines, in five layers
The accented layer is exposure: that is where it starts.
Exposure, identities, PCs and servers, data, organisation. These five layers match the public frameworks. The CIS Controls are a publication of best practice guidelines for computer security, organised in eighteen key actions. The NIST Cybersecurity Framework is a set of guidelines for assessing and improving preparedness, around six functions: govern, identify, protect, detect, respond, recover. The ISO/IEC 27001 standard sets the requirements for an information security management system. For an application open to the internet, the OWASP Top Ten lists the most critical application security risks.
What is done with them. A company with forty workstations does not have to choose a framework before starting: the auditor uses it as a checklist so that nothing is forgotten, and tells you which one was followed. For the management application, the question of who sees what and who changed what belongs to the guide to roles and the audit log. After the audit, keeping the fixes in place over time is upkeep work, described in the guide to managed IT.
An audit in 2027, in weeks
Four weeks in the example, one of them to fix the emergencies.
- What the manager receives: one page with the ranked findings, the first five to fix, the effort for each, and the date of the second check.
- What the company no longer does: buy a penetration test before tidying up, receive a report nobody reads, fix what is easy rather than what is serious, answer “I think so” to the customer who asks.
- What is measured: open findings by severity, days since the servers were last updated, accounts without two-step verification, date of the last successful restore.
- What Symloop does: the audit with a written agreement, the ranked report, fixing the emergencies with your team, the second check, then upkeep; and, for the applications we build, security taken into account from the design stage.
Week 1, scoping and stock-take. Week 2, measurements and checks: the look from outside, accounts and rights, updates, the trial restore. Order of magnitude in the example, for forty workstations: five auditor days spread over those two weeks, and a few hours of your IT person's time.
Week 3, report and emergencies: debrief with the manager, the first five findings fixed. Week 4, follow-up and second check: plan for the remaining fixes, verification that the emergencies are really closed, meeting at three months.
- What is an IT security audit?
- It is the assessment of an organisation's level of information security: what is visible from the internet, accounts and rights, PCs and servers, data and backups, the organisation. It ends with ranked findings and a remediation plan.
- What is the difference between an audit and a penetration test?
- The audit looks for all the weaknesses and ranks them. The penetration test is an authorised simulated attack on a precise target, to see how far it gets. You audit and fix first; then you test what has to resist.
- Is a vulnerability scan enough?
- No. A scanner is a program that looks for known weaknesses; it sees neither former employees' accounts, nor the backup never restored, nor the lack of two-step verification. It is a useful tool for the auditor, not an audit.
- How long does an audit take for a small company?
- In our example, for forty workstations: about five auditor days over two weeks, then a week for the report and the emergencies, and a second check. The duration depends on the number of sites, servers and applications in scope.
- What must the audit report contain?
- For each finding: what was observed, the proof, the severity on an explained scale, the fix, the estimated effort and an owner. And a first page the manager can read, with the fixes in order. Ask for a sample report before signing.
- Where do you start to secure a company?
- With what is serious and quick. Most often: close what is exposed to the internet for no reason, turn on two-step verification for mail, close former employees' accounts, update, and try restoring a backup.
- Should we aim for a certification such as ISO 27001?
- Only if a customer or a market requires it. The standard sets the requirements for a security management system; it is an organisational project of several months. An audit and its fixes are the first step, useful with or without certification.
- Can an audit disrupt our business?
- Properly scoped, no. Most of it is done in read-only mode, and the checks that might get in the way are planned outside working hours, with the people concerned warned. That is the role of the written agreement at the start.
- How often should an audit be repeated?
- A second check three months later, to verify the fixes; then an audit at every significant change, new site, new application, change of provider, and at a regular interval that you set according to what is at stake.
- How do you choose a cybersecurity provider?
- Ask for the proposed scope, the number of days, a sample report, the scoring method, and whether fixing the emergencies and the second check are included. A provider who starts with a written agreement and ends with an order of fixes is doing the job properly.