What a Cybersecurity Audit Actually Is (and Isn’t)
A cybersecurity audit is a structured review of your business’s security controls against a defined standard — identifying what’s in place, what’s missing, and what needs improvement. For a small business, it doesn’t require an external auditor, a specialist tool, or a week of downtime. It requires honest answers to specific questions, and a commitment to addressing what you find.
What a cybersecurity audit is not: it is not a penetration test (where someone attempts to actively break into your systems), not a vulnerability scan (automated scanning of systems for known weaknesses), and not a one-time exercise. An audit reviews your programme — your policies, your controls, your processes — and assesses whether they meet an acceptable standard. Penetration testing and vulnerability scanning are components that a more advanced programme adds alongside the audit.
Who should use this checklist:
- Business owners who have never formally reviewed their security posture
- IT administrators conducting their first structured security review
- Businesses preparing for cyber insurance underwriting or renewal
- Businesses preparing for a client security questionnaire or vendor assessment
- Any business that has implemented security controls and wants to verify they’re complete
How long it takes: Allow 2–4 hours for a small business with 5–25 employees. Larger environments or businesses with more complex IT infrastructure should allow 4–8 hours. The output is a gap list with prioritised remediation actions.
How to use the scoring: Each item has three possible statuses:
- ✅ In place — control is implemented and operating effectively
- ⚠️ Partial — control exists but has gaps (not fully implemented, not consistently applied, or not documented)
- ❌ Not in place — control is missing
At the end of each section, count your statuses. A section with mostly ❌ is a priority area. A section with mostly ⚠️ needs tightening. A section with mostly ✅ is your current strength baseline.
Section 1: Identity and Access Management
Access control failures — shared passwords, lingering accounts for departed staff, no MFA — are present in the majority of small business breaches. This section is typically the highest-impact area for improvement.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 1.1 | Every employee has a unique account on every business system — no shared credentials | ✅ / ⚠️ / ❌ | |
| 1.2 | MFA is enabled on all cloud services (email, cloud storage, CRM, accounting software) | ✅ / ⚠️ / ❌ | |
| 1.3 | MFA is enabled on all remote access systems (VPN, RDP, remote management tools) | ✅ / ⚠️ / ❌ | |
| 1.4 | A password manager is in use and all business account passwords are stored in it | ✅ / ⚠️ / ❌ | |
| 1.5 | Passwords meet minimum length requirements (12+ characters) | ✅ / ⚠️ / ❌ | |
| 1.6 | Default passwords have been changed on all routers, firewalls, and network devices | ✅ / ⚠️ / ❌ | |
| 1.7 | Access is granted on a need-to-know basis — employees have only the access their role requires | ✅ / ⚠️ / ❌ | |
| 1.8 | Administrative accounts are separate from standard user accounts | ✅ / ⚠️ / ❌ | |
| 1.9 | A formal offboarding process revokes all system access within 24 hours of departure | ✅ / ⚠️ / ❌ | |
| 1.10 | Access to all key systems was reviewed in the past 12 months and unnecessary access removed | ✅ / ⚠️ / ❌ | |
| 1.11 | No former employees have active accounts on any business system | ✅ / ⚠️ / ❌ | |
| 1.12 | Guest Wi-Fi is segmented from the business network | ✅ / ⚠️ / ❌ |
Section 1 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 2: Endpoint Security
Every device that accesses business data is a potential attack entry point. This section covers the security of those devices.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 2.1 | Business-grade endpoint protection (antivirus/EDR) is installed on all employee devices | ✅ / ⚠️ / ❌ | |
| 2.2 | Endpoint protection is centrally managed — not just installed locally on individual devices | ✅ / ⚠️ / ❌ | |
| 2.3 | Real-time protection and automatic definition updates are enabled on all devices | ✅ / ⚠️ / ❌ | |
| 2.4 | Full-disk encryption is enabled on all laptops and mobile devices | ✅ / ⚠️ / ❌ | |
| 2.5 | Screen lock activates automatically after a defined period of inactivity on all devices | ✅ / ⚠️ / ❌ | |
| 2.6 | All devices run supported operating systems (no Windows 10 post-October 2025 EOL, no macOS past Apple support end) | ✅ / ⚠️ / ❌ | |
| 2.7 | All devices are enrolled in device management (MDM/Intune/Jamf) or equivalent | ✅ / ⚠️ / ❌ | |
| 2.8 | A process exists to remotely wipe devices that are lost or stolen | ✅ / ⚠️ / ❌ | |
| 2.9 | USB and removable storage use is controlled (restricted or monitored) | ✅ / ⚠️ / ❌ | |
| 2.10 | Personal devices accessing business data meet minimum security requirements (screen lock, encryption, current OS) | ✅ / ⚠️ / ❌ |
Section 2 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 3: Patch Management and Software Currency
The majority of successful exploits in 2026 target known vulnerabilities with available patches. Unpatched software is the path of least resistance for attackers.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 3.1 | All operating systems on all devices are current and receiving security updates | ✅ / ⚠️ / ❌ | |
| 3.2 | All applications are current — no software running past its end-of-support date | ✅ / ⚠️ / ❌ | |
| 3.3 | Critical security patches are applied within 14 days of release | ✅ / ⚠️ / ❌ | |
| 3.4 | High-severity patches are applied within 30 days of release | ✅ / ⚠️ / ❌ | |
| 3.5 | A patch management tool or process tracks patch status across all devices | ✅ / ⚠️ / ❌ | |
| 3.6 | Router and firewall firmware is current and on a supported version | ✅ / ⚠️ / ❌ | |
| 3.7 | Automatic updates are enabled where possible (browsers, operating systems) | ✅ / ⚠️ / ❌ | |
| 3.8 | A software inventory exists listing all applications in use across the business | ✅ / ⚠️ / ❌ |
Section 3 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 4: Network Security
Network security controls protect the infrastructure that all devices and systems rely on.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 4.1 | A business-grade firewall (not a consumer router) protects the network boundary | ✅ / ⚠️ / ❌ | |
| 4.2 | The firewall’s default admin password has been changed | ✅ / ⚠️ / ❌ | |
| 4.3 | Firewall rules are documented and reviewed at least annually | ✅ / ⚠️ / ❌ | |
| 4.4 | Remote management of the firewall is not accessible from the internet | ✅ / ⚠️ / ❌ | |
| 4.5 | DNS filtering (e.g. Cloudflare Gateway, Cisco Umbrella) is in place for all network devices | ✅ / ⚠️ / ❌ | |
| 4.6 | SSL/TLS inspection is enabled on the firewall (or documented reason it is not) | ✅ / ⚠️ / ❌ | |
| 4.7 | Guest Wi-Fi is on a separate VLAN with no access to business systems | ✅ / ⚠️ / ❌ | |
| 4.8 | IoT devices (smart TVs, cameras, printers, environmental controls) are on a separate network | ✅ / ⚠️ / ❌ | |
| 4.9 | VPN is required for all remote access to internal business systems | ✅ / ⚠️ / ❌ | |
| 4.10 | RDP and other remote access services are not directly exposed to the internet without a VPN or Zero Trust gateway | ✅ / ⚠️ / ❌ |
Section 4 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 5: Data Protection and Backup
Data loss and ransomware are the highest-impact incident types for small businesses. This section covers the controls that determine whether a business survives one.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 5.1 | All business-critical data is backed up at least daily | ✅ / ⚠️ / ❌ | |
| 5.2 | Backups follow the 3-2-1 rule (3 copies, 2 media types, 1 off-site) | ✅ / ⚠️ / ❌ | |
| 5.3 | At least one backup copy is stored off-site or in a cloud service separate from primary systems | ✅ / ⚠️ / ❌ | |
| 5.4 | At least one backup is stored in a location not continuously connected to the business network (ransomware-resistant backup) | ✅ / ⚠️ / ❌ | |
| 5.5 | All backup copies are encrypted | ✅ / ⚠️ / ❌ | |
| 5.6 | Backup restoration has been tested in the past 12 months — data was verified as actually recoverable | ✅ / ⚠️ / ❌ | |
| 5.7 | Recovery time has been measured and meets the business’s recovery time objective | ✅ / ⚠️ / ❌ | |
| 5.8 | Microsoft 365 or Google Workspace data is backed up by a third-party backup service (not relying on Microsoft/Google retention alone) | ✅ / ⚠️ / ❌ | |
| 5.9 | Data is classified by sensitivity (confidential, internal, public) and handled accordingly | ✅ / ⚠️ / ❌ | |
| 5.10 | Sensitive data is not stored on personal devices or personal cloud accounts | ✅ / ⚠️ / ❌ | |
| 5.11 | A data retention schedule defines how long different types of data are kept and how they are deleted | ✅ / ⚠️ / ❌ |
Section 5 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 6: Email and Phishing Protection
Over 90% of successful cyberattacks begin with a phishing email. Email security controls and employee awareness are the primary defence.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 6.1 | Business email is hosted on a business email platform — not free consumer email (Gmail personal, Hotmail, Yahoo) | ✅ / ⚠️ / ❌ | |
| 6.2 | SPF, DKIM, and DMARC records are configured correctly for the business email domain | ✅ / ⚠️ / ❌ | |
| 6.3 | Email security filtering (antispam, anti-phishing, malicious link scanning) is active | ✅ / ⚠️ / ❌ | |
| 6.4 | Employees can report suspicious emails using a report button or designated process | ✅ / ⚠️ / ❌ | |
| 6.5 | Employees have received phishing awareness training in the past 12 months | ✅ / ⚠️ / ❌ | |
| 6.6 | Phishing simulations have been conducted in the past 12 months and results reviewed | ✅ / ⚠️ / ❌ | |
| 6.7 | Business email accounts are protected with MFA (not just a password) | ✅ / ⚠️ / ❌ | |
| 6.8 | External email is labelled as external in the inbox (banner or subject tag) to help identify impersonation | ✅ / ⚠️ / ❌ | |
| 6.9 | A process exists to verify unusual financial requests received by email (e.g. payment instruction changes) before acting | ✅ / ⚠️ / ❌ | |
| 6.10 | Business email continuity is available if the primary email system is unavailable | ✅ / ⚠️ / ❌ |
Section 6 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 7: Vendor and Third-Party Security
Third-party breaches cause 29% of business security incidents. Every vendor with access to your systems or data is a potential entry point.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 7.1 | A current inventory of all vendors and service providers with access to business data exists | ✅ / ⚠️ / ❌ | |
| 7.2 | Data Processing Agreements (or equivalent) are signed with all vendors that process personal data | ✅ / ⚠️ / ❌ | |
| 7.3 | Vendor agreements include security obligations, incident notification requirements, and data deletion terms | ✅ / ⚠️ / ❌ | |
| 7.4 | Vendors are assessed for security posture before being granted access to business systems or data | ✅ / ⚠️ / ❌ | |
| 7.5 | New software and cloud services require approval before business data is entered | ✅ / ⚠️ / ❌ | |
| 7.6 | Shadow IT (employees using unapproved tools for business work) is actively identified and addressed | ✅ / ⚠️ / ❌ | |
| 7.7 | AI tools used in the business are assessed for what data they process and whether appropriate agreements are in place | ✅ / ⚠️ / ❌ | |
| 7.8 | Vendor access is reviewed annually and access is removed from vendors no longer actively used | ✅ / ⚠️ / ❌ | |
| 7.9 | IT support providers and MSPs with privileged access to business systems are subject to formal agreements with security obligations | ✅ / ⚠️ / ❌ |
Section 7 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 8: Incident Response Readiness
When a breach happens, the quality of your response in the first 24–72 hours determines the outcome. This section assesses whether you’re ready.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 8.1 | A documented incident response plan exists | ✅ / ⚠️ / ❌ | |
| 8.2 | All employees know how to report a suspected security incident and who to contact | ✅ / ⚠️ / ❌ | |
| 8.3 | A specific individual (or role) is designated as incident response lead | ✅ / ⚠️ / ❌ | |
| 8.4 | The incident response plan has been tested (e.g. a tabletop exercise) in the past 12 months | ✅ / ⚠️ / ❌ | |
| 8.5 | An incident log or register exists, and minor incidents are documented even if they don’t require regulatory notification | ✅ / ⚠️ / ❌ | |
| 8.6 | The business knows which regulatory authorities to notify in the event of a breach (ICO, relevant DPA, HHS if applicable) and how | ✅ / ⚠️ / ❌ | |
| 8.7 | Notification templates for regulatory authorities and affected individuals are prepared in advance | ✅ / ⚠️ / ❌ | |
| 8.8 | A breach response firm or privacy attorney is on retainer or identifiable to contact within the first 24 hours | ✅ / ⚠️ / ❌ | |
| 8.9 | Cyber insurance coverage is in place and the policy terms are understood (what’s covered, what conditions apply) | ✅ / ⚠️ / ❌ | |
| 8.10 | Business continuity arrangements exist for operating while systems are unavailable | ✅ / ⚠️ / ❌ |
Section 8 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 9: Security Awareness and Training
The human layer is both the largest vulnerability and the most cost-effective control to improve. This section assesses the training programme.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 9.1 | All employees received security awareness training on joining the business | ✅ / ⚠️ / ❌ | |
| 9.2 | All employees receive security awareness training at least annually, and completion is documented | ✅ / ⚠️ / ❌ | |
| 9.3 | Training covers phishing recognition, password hygiene, incident reporting, and data handling | ✅ / ⚠️ / ❌ | |
| 9.4 | Training content is updated annually to reflect current threats | ✅ / ⚠️ / ❌ | |
| 9.5 | Employees know not to use personal AI tools (ChatGPT, etc.) for work tasks involving confidential business data | ✅ / ⚠️ / ❌ | |
| 9.6 | A clear policy exists on acceptable use of AI tools for business purposes | ✅ / ⚠️ / ❌ | |
| 9.7 | Training completion is tracked and staff who haven’t completed training are followed up | ✅ / ⚠️ / ❌ | |
| 9.8 | Leadership and management have completed the same security training as other staff | ✅ / ⚠️ / ❌ |
Section 9 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Section 10: Governance, Policies, and Compliance
Policies, documentation, and governance create the structure that makes all other controls sustainable. Without them, controls are implemented inconsistently and fail under scrutiny.
| # | Audit Item | Status | Notes |
|---|---|---|---|
| 10.1 | A written information security policy exists and has been reviewed in the past 12 months | ✅ / ⚠️ / ❌ | |
| 10.2 | An acceptable use policy exists and all employees have acknowledged it | ✅ / ⚠️ / ❌ | |
| 10.3 | An access control policy exists defining how access is granted, reviewed, and revoked | ✅ / ⚠️ / ❌ | |
| 10.4 | A password policy exists setting minimum requirements for business accounts | ✅ / ⚠️ / ❌ | |
| 10.5 | A data retention policy defines how long different types of data are kept | ✅ / ⚠️ / ❌ | |
| 10.6 | A privacy notice is published, accurate, and reviewed at least annually | ✅ / ⚠️ / ❌ | |
| 10.7 | A named individual is responsible for security and privacy compliance | ✅ / ⚠️ / ❌ | |
| 10.8 | A cybersecurity risk assessment has been conducted in the past 12 months identifying key threats and vulnerabilities | ✅ / ⚠️ / ❌ | |
| 10.9 | Cybersecurity is reviewed at the management or board level at least annually | ✅ / ⚠️ / ❌ | |
| 10.10 | Cyber insurance requirements (MFA, endpoint protection, backup, patching) are understood and actively maintained | ✅ / ⚠️ / ❌ | |
| 10.11 | If subject to regulatory requirements (GDPR, HIPAA, PCI DSS), compliance status has been formally reviewed in the past 12 months | ✅ / ⚠️ / ❌ | |
| 10.12 | This cybersecurity audit (or equivalent) has been completed in the past 12 months | ✅ / ⚠️ / ❌ |
Section 10 score: _____ in place / _____ partial / _____ not in place
Highest priority gaps identified:
Scoring Summary and Action Plan Template
After completing all 10 sections, summarise your findings here.
Overall Score Summary
| Section | In place (✅) | Partial (⚠️) | Not in place (❌) |
|---|---|---|---|
| 1. Identity and Access Management | |||
| 2. Endpoint Security | |||
| 3. Patch Management | |||
| 4. Network Security | |||
| 5. Data Protection and Backup | |||
| 6. Email and Phishing | |||
| 7. Vendor Security | |||
| 8. Incident Response | |||
| 9. Security Awareness | |||
| 10. Governance and Policies | |||
| Total |
Priority Interpretation
Sections with 3 or more ❌: Critical gaps — address within 30 days. These represent fundamental controls that leave your business materially exposed to common attack types.
Sections with 3 or more ⚠️: Significant gaps — address within 90 days. Controls exist but are inconsistent, undocumented, or partially implemented. These will typically fail during a genuine incident or insurance/compliance review.
Sections with mostly ✅: Maintain and document. These are your security strengths. Ensure they remain current through annual reviews.
Action Plan Template
Complete this for each gap identified during the audit.
| Item # | Gap description | Priority (High/Medium/Low) | Owner | Target completion date | Status |
|---|---|---|---|---|---|
Priority guidance:
- High: Any ❌ in Section 1 (Access), Section 5 (Backup), or any control directly required by your cyber insurance policy
- Medium: Any ❌ in Sections 2, 4, 6, 8 / Any ⚠️ in Sections 1 and 5
- Low: ⚠️ items in Sections 3, 7, 9, 10
How to Run This Audit: Practical Guidance
Who should complete it
The person completing this audit needs to know your IT environment well enough to answer accurately. For a very small business where the owner manages everything: the owner completes it. For a business with an IT administrator: the IT administrator completes it. For a business managed by an MSP: the MSP completes it and reviews findings with the owner.
The most common audit failure is providing aspirational answers — “we probably do this” or “we should be doing this” scored as ✅. The purpose of the audit is to find the honest gaps, not to produce a clean score. An audit that finds no gaps in a business without a documented security programme is not a clean audit — it’s an inaccurate one.
Gathering evidence
For each item you score ✅, you should be able to point to evidence that it’s actually in place:
- MFA is enabled: a screenshot of the MFA configuration in your email provider
- Backup restoration was tested: a record of the test date and what was restored
- Policies are reviewed annually: a document with a revision date
- Former employee accounts are removed: an offboarding checklist with completion dates
Evidence doesn’t need to be elaborate. A dated email confirming an action was completed, a screenshot of a configuration screen, or a brief note in a shared document is sufficient. Evidence is what protects you when an insurer, auditor, or regulator asks whether a control was actually in place.
Common honest findings
The gaps most commonly found in small business cybersecurity audits — the items businesses think they have but actually don’t:
Backup restoration has been tested. Most businesses back up. Far fewer have tested restoration. The backup process running doesn’t mean the backup is restorable. Schedule a test.
No former employees have active accounts. Almost every business finds at least one departed employee’s account still active on at least one system during their first audit. Run through the list of leavers from the past two years and verify access removal on every system.
MFA is enabled on all cloud services. Businesses enable MFA on their primary email but forget the CRM, the accounting software, the cloud backup, the payroll system, the social media business accounts, or the various SaaS tools added over time. Audit every cloud service against MFA status.
The incident response plan has been tested. Writing a plan is not the same as testing it. A 30-minute tabletop exercise walkthrough is sufficient for a first test. Without testing, nobody knows whether the plan actually works.
Shadow IT has been addressed. Employees use tools for work that IT doesn’t know about. Ask employees directly what tools they use daily. Every unapproved tool that touches business data is a gap.
What to do with the gap list
After completing the audit, you have a gap list. The next step is prioritisation and an action plan:
- Identify the highest-risk gaps — anything that would cause significant harm in a breach scenario or that fails a cyber insurance requirement
- Assign an owner to each gap — a named person responsible for closing it
- Set a target date — realistic but time-bound
- Revisit the action plan monthly until all high-priority gaps are closed
- Schedule the next audit — annual is the minimum; semi-annual is better for rapidly changing environments
What the Audit Doesn’t Cover
This checklist covers the broad landscape of small business cybersecurity controls. It does not replace:
Vulnerability scanning: Automated scanning of your systems and network for known vulnerabilities and misconfigurations. Tools like Tenable.io, Qualys, or even free options like OpenVAS provide this. PCI DSS compliance requires quarterly external vulnerability scans from an Approved Scanning Vendor.
Penetration testing: Active testing by a specialist who attempts to find and exploit vulnerabilities in your environment. Typically costs $5,000–$15,000 for a small business scope. SOC 2, ISO 27001, and NIS2 all expect penetration testing on at least an annual basis.
Dark web monitoring: Checking whether your employees’ credentials have appeared in breach dumps or stealer logs. Our dark web monitoring article covers the tools available for this.
Full compliance audit: This checklist covers security controls that underpin compliance with GDPR, HIPAA, PCI DSS, Cyber Essentials, and other frameworks. A formal compliance audit for any of those frameworks requires additional framework-specific evidence and typically involves an external assessor.
How Often to Run This Audit
Annual minimum: At minimum, run this audit once per year. Security posture changes as you add staff, adopt new tools, change cloud services, and expand or contract operations. An annual audit catches drift.
After significant changes: Any of the following should trigger a mid-cycle audit review:
- Adding a new major cloud service or IT platform
- Significant staff changes (large new hire cohort, senior departures)
- Moving to a new office or significant infrastructure change
- Experiencing a security incident
- Receiving a new cyber insurance policy or renewing an existing one
Before a security questionnaire or compliance review: If a client, partner, or insurer asks about your security posture, run this audit first. Completing it honestly gives you an accurate picture of what you can attest to and what needs addressing before you respond.
Final Verdict
A cybersecurity audit is not a compliance exercise — it’s a gap-finding exercise. Its value is in the honest gaps it reveals, not in the score it produces. A business that completes this checklist honestly and acts on what it finds is meaningfully more secure than one that produces a clean-looking score that doesn’t reflect reality.
The 10 sections cover the foundational security domains that determine whether a small business can withstand and recover from the most common attack types in 2026. Completing all 10 sections takes a few hours. Acting on the gap list takes weeks to months. The protection it provides lasts for the year before the next audit.
Start with Section 1 (Identity and Access Management) — it’s the highest-impact area for most small businesses and the controls are primarily free to implement. Enable MFA on everything, remove former employees’ accounts, deploy a password manager. Those three actions close the most common breach vectors before you’ve spent a penny on security tools.
Frequently Asked Questions
How much does a cybersecurity audit cost for a small business?
A self-conducted audit using this checklist costs only staff time — typically 2–4 hours for a business with 5–25 employees. A professionally conducted external cybersecurity audit by a specialist firm typically costs $7,500–$40,000 depending on scope, company size, and whether it maps to a specific compliance framework. External audits provide independent assessment and are appropriate when preparing for SOC 2, ISO 27001, or client due diligence that requires third-party attestation. For most small businesses, a rigorous self-assessment using this checklist, followed by an annual review with your IT provider or MSP, is the appropriate starting point.
How is a cybersecurity audit different from a penetration test?
A cybersecurity audit reviews your security programme — the policies, controls, and processes you have in place — and assesses whether they meet an acceptable standard. It’s a documentation and process review. A penetration test involves a specialist actively attempting to exploit vulnerabilities in your systems to find weaknesses that automated scanning and documentation review wouldn’t reveal. Audits assess what you have; penetration tests try to break what you have. Both are valuable; the audit typically comes first because it reveals control gaps that should be addressed before a penetration test makes them visible to an external party.
What should I do if I find a lot of gaps?
Prioritise ruthlessly. A business that tries to close all gaps simultaneously typically closes none — the scope is too broad and nothing gets finished. Pick the three to five highest-risk gaps — typically items in Identity and Access Management, Backup, and Endpoint Security — and close those first. Set a 30-day deadline for the highest-priority items. Then move to the next tier. Progress is better than perfection, and closing five critical gaps in a month is significantly more valuable than attempting all twenty and completing none.
Can I use this checklist for cyber insurance purposes?
This checklist helps you understand your security posture and prepare for cyber insurance underwriting. Most cyber insurance questionnaires ask about specific controls — MFA on all accounts, endpoint protection, backup, patch management — that map directly to the items in this checklist. Completing this audit honestly will identify gaps that might affect your insurability or your premium, giving you the opportunity to address them before or during the renewal process. However, this checklist does not produce the formal documentation that insurers request; that typically requires completing the insurer’s own questionnaire and, in some cases, providing evidence of specific controls.
How do I know if my current security is adequate?
“Adequate” security is a function of your risk profile, not an absolute standard. A medical practice handling patient records faces higher risk than a landscaping company’s admin system. A business with significant remote access, cloud infrastructure, and sensitive customer data faces higher risk than one with a few in-office devices and no sensitive data. This audit covers the foundational controls appropriate for most small businesses. For a specific regulated industry (healthcare, financial services) or a business subject to specific frameworks (PCI DSS, GDPR, NIS2), additional framework-specific requirements apply on top of this baseline. If in doubt about adequacy for your specific risk profile, consult an IT security specialist or managed security service provider.
For free cybersecurity audit resources, see CISA’s Cybersecurity Assessment resources and the NCSC’s Cyber Essentials guidance for UK businesses. For a full set of cybersecurity policies to support this audit, see our guide to writing a cybersecurity policy for small business.
Related reading on SmallBiz Defense:

2 thoughts on “Cybersecurity Audit Checklist for Small Business (Free Template)”