Security audit services that end in a fix list, not a shelf report
Our security audit services check how your IT environment, cloud accounts, web applications and mobile apps are actually set up, against a named standard such as the CIS Controls, OWASP or the NIS2 measures. You get a ranked list of what to fix first, the evidence behind every finding, help with the fixes if you want it, and a retest that proves each one was closed.
- Fixed price, agreed before work starts
- A one-off job with no follow-on contract
- Logins stay in your company's name
Who asks for a security audit
Most companies that come to us for a security audit have one of four reasons. A large customer has sent a supplier security questionnaire and the answers need evidence, not optimism. The company falls under NIS2, or sells to companies that do, and management wants to know where it stands; energy companies, for example, are in the NIS2 sectors of high criticality, as our page on energy software development explains. A new web application or app is about to launch and someone should look at it before attackers do. Or something has already happened, a phishing incident or a lost laptop, and the question is what else is open.
In each case the useful result is the same: a short list of the gaps that matter most, in the order to close them, with the proof a customer, an auditor or a board can read.
What we audit
| Audit | What it covers | Checked against |
|---|---|---|
| IT environment | Microsoft 365 or Google Workspace, accounts and admin rights, multi-factor sign-in, laptops and phones, patching, backups, email security | CIS Controls v8.1, NIS2 Article 21 measures |
| Cloud accounts | AWS, Azure or Google Cloud: identity and access, public storage, network exposure, logging, keys and secrets, billing alerts | The provider's own security benchmark, CIS Controls |
| Web application or API | Sign-in, sessions, access control, input handling, data exposure, dependencies, configuration | OWASP ASVS 5.0.0 |
| Mobile app | Data stored on the device, network traffic, authentication, platform permissions, code and privacy | OWASP MASVS |
| External attack surface | Domains, open services, forgotten test sites, certificates, email spoofing protection | Public exposure from the outside |
| Processes and suppliers | Starters and leavers, incident handling, backup restore tests, supplier access, policies that exist only on paper | NIS2 Article 21, ISO/IEC 27001 controls |
One audit can combine several rows. A typical first audit for a company of twenty to two hundred people covers the IT environment, the external attack surface and the processes, and adds the web application when the company sells software.
Audit, vulnerability scan, penetration test or certification?
These words are often used as if they meant the same thing. They do not, and buying the wrong one wastes money.
- Vulnerability scan. An automated tool lists known weaknesses on systems it can reach. Useful, quick and repeatable, but it cannot tell whether a former employee still has access or whether backups would actually restore.
- Security audit. A structured review of settings, processes and evidence against a standard. It finds the open doors, explains why they matter and ranks them. This is where most companies should start.
- Penetration test. A tester tries to break in, within agreed rules, and shows how far an attacker gets. It is most useful after the obvious gaps from an audit are closed, and for applications before launch.
- Certification audit. An accredited certification body checks an information security management system against ISO/IEC 27001 and issues a certificate. Our part is the readiness audit that tells you what the certification audit will find.
What a penetration test costs depends on its scope, tester days and retesting; our guide to penetration testing cost shows how to compare quotes on the same basis.
The standards we audit against
An audit is only as good as the yardstick. We use public, recognised standards, so the findings mean the same thing to your customer's security team as they do to us. (All sources below read on 11 November 2026.) For the EU laws that often trigger an audit, see our guides to NIS2 compliance and the Cyber Resilience Act; for websites and apps used by people with disabilities, see our accessibility audit.
NIS2. Article 21(2) of Directive (EU) 2022/2555 lists the minimum measures covered entities must take, including risk analysis and security policies, incident handling, business continuity and backup management, supply chain security, security in development and maintenance, policies to assess whether the measures work, basic cyber hygiene and training, cryptography, access control and asset management, and multi-factor authentication. Article 32 lets the authorities subject essential entities to regular and targeted security audits carried out by an independent body, with the cost of a targeted audit paid by the audited entity. Our NIS2 audit maps every finding to the point of Article 21(2) it belongs to.
CIS Controls. The Center for Internet Security states that CIS Controls v8 and v8.1 contain 153 safeguards in total, and that every enterprise should start with Implementation Group 1, which it defines as essential cyber hygiene. For most small and midsize companies, IG1 is the right first audit scope: it is concrete, it can be checked, and it closes the gaps behind the most common attacks.
OWASP ASVS and MASVS. For web applications we test against the OWASP Application Security Verification Standard, whose version 5.0.0 was published on 30 May 2025. For mobile apps we use the OWASP Mobile Application Security Verification Standard, which groups its controls into storage, cryptography, authentication, network, platform, code, resilience and privacy.
We do not give legal advice. Whether NIS2 applies to your company is decided by national law and your own advisers; the audit gives them the technical facts.
If you do not yet have written rules to audit against, start with our information security policy guide.
How a security audit runs
- Scope and rules in writing. Which systems, which standard, what we may test actively and when, who to contact if we find something urgent, and a fixed price for that scope.
- Access in your name. You create read-only accounts for us in your own tenant and cloud accounts. We never ask for a shared password, and active tests on applications run against a test environment or in an agreed window.
- Evidence collection. Settings exports, admin interviews, sample checks such as one leaver and one restored backup, and testing of the applications in scope.
- Urgent findings at once. If we find something open to the internet right now, such as a public storage bucket with customer data, you hear about it the same day, not in the final report.
- Report and fix list. Each finding has a severity, the evidence, the standard it maps to, the fix in plain steps and a rough effort, ranked so the first five items close most of the risk.
- Retest. When you have fixed the items, we check them again and update the report, so the evidence shows the closed state, not only the problem.
What you get
- A one-page summary for management: where you stand, the top risks in plain words and what closing them involves.
- The full findings list, each with evidence, severity, the mapped control and the fix.
- A mapping table to the standard you chose, ready to attach to a customer questionnaire or a NIS2 self-assessment.
- A retest note per finding, with the date it was confirmed closed.
- If you want it, the fixes themselves, done by our team under a separate written scope, or handed to your own IT team or provider.
Why the fix list matters more than the report
Many audits end as a long document that nobody acts on. A list of eighty findings, all marked important, gives no one a place to start. We rank on two questions: how likely is this to be used against you, and how much damage would it do. In practice the top of the list is usually familiar: admin accounts without multi-factor sign-in, backups that have never been restored, old accounts of people who left, a test site still online, and email without spoofing protection. Closing those first changes your real risk within weeks.
The rest of the list becomes a plan with owners and dates, and a repeat audit a year later shows the progress in the same format.
Independence, said plainly
An auditor should not audit their own work. If we already build or run part of your systems, through managed IT services or co-managed IT, we can still review that part, but the report says so. When you need an audit that a supervisor or a large customer will treat as independent, we keep to systems another team built or runs, or we tell you to use a separate auditor for that part. We also earn nothing from security products: if a finding needs a tool, we name the options and you buy in your company's name.
Yours, and then gone
The report, the findings and the evidence belong to your company. Our access accounts are removed on the last day of the audit, evidence is stored in an EU location only for the period the agreement sets, then deleted, and everything we learn about your systems is covered by a confidentiality and data processing agreement signed before we start.
An audit is a snapshot. To keep the fixes in place month after month, with multi-factor sign-in, patching, backups and access reviews run and recorded as routine, see our managed IT security services. For day-to-day help after the audit, see IT support for small business. If the audit is part of a wider plan for your systems, see IT consulting. Before a new app goes to the stores, pair the audit with mobile app testing. For connected products under the Cyber Resilience Act, see IoT software development, and for recurring release testing, software testing outsourcing. What a website gives away about its software versions is explained in our guide to the version number on a website. See prices.
Questions we get
What is the difference between a security audit and a penetration test?
An audit checks how your systems are set up and run against a known standard: accounts, settings, backups, patching, suppliers and the evidence behind each. A penetration test tries to break in and shows what an attacker could reach. Many companies need the audit first, because it finds the open doors a test would only confirm one at a time.
Will the audit disrupt our work?
No. The audit uses read-only access in your own accounts, agreed in writing, and active testing of a web or mobile app runs against a test environment or in an agreed time window. Nothing is changed in your systems without your approval.
Can you certify us for ISO 27001?
No. Certification is issued by an accredited certification body. We run a readiness audit against the standard's controls, so you know the gaps before the certification audit, and we help you close them if you want.
Does NIS2 require a security audit?
NIS2 requires covered entities to have policies and procedures to assess whether their security measures work, and lets authorities order regular and targeted security audits of essential entities by an independent body. National law decides the details. Even when you are not covered, customers who are covered increasingly ask their suppliers for this evidence.
Can you audit systems you built or run for us?
We can review them, but we say so in the report, because an audit of our own work is not independent. When you need an independent audit, for example for a supervisor or a large customer, we tell you that and keep to the systems another team built or runs.
What happens to our data after the audit?
Access accounts are removed on the last day, and the evidence is kept in an EU location only as long as the agreement says, then deleted. The report and every finding belong to your company.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.