Blog

Summary: Guest Wi-Fi should provide internet access while blocking connections to your internal business network. A different Wi-Fi name and password do not confirm that the networks are separated. The router, access points, and firewall must also be configured to prevent guest devices from reaching internal systems.

Offering Wi-Fi to customers, contractors, and visitors is convenient. But their phones and laptops should not connect to the same network as your business computers, printers, security cameras, servers, and file storage.

Even when you trust the person, you do not control their device. You do not know whether it has current security updates, whether it contains malware, or who else has used it.

A properly configured guest network gives visitors internet access without allowing their devices to communicate with your business systems.

What Separate Guest Wi-Fi Means

When someone connects to your guest Wi-Fi, they should be able to browse the internet, use email, and access online services. They should not be able to connect to anything on your internal network.

That includes:

• Business computers and servers
• Network printers
• File storage and backup devices
• Security cameras
• Building access systems
• Router and network management pages
• Other devices using the guest network

The Australian Cyber Security Centre recommends separating an organization’s internal network from the guest Wi-Fi used by unmanaged devices.

Both networks can use the same internet connection. The settings that separate them are configured in your network equipment, such as the router, firewall, switches, or wireless access points.

Why One Shared Network Creates Unnecessary Risk

Connecting to the same network does not automatically give a visitor access to every business file. Your passwords, device security settings, and user permissions still apply.

However, a device on the same network may be able to find or contact systems that it does not need to use. This could include a printer, shared folder, storage device, camera, or poorly protected management page.

An infected device may also try to connect to other devices on the network. If the network is divided into separate sections, those connections can be blocked before they reach your business systems.

The UK’s National Cyber Security Centre explains that network segmentation restricts movement between systems. If one device is compromised, separating the network reduces the number of other systems it can contact.

Separating the networks reduces risk by blocking access that visitors and unmanaged devices do not need.

A Different Wi-Fi Name May Not Be Enough

Your business Wi-Fi and guest Wi-Fi may appear as two different names when someone opens the Wi-Fi menu on their phone. Those names are called SSIDs.

A second SSID does not confirm that the devices are properly separated. The settings behind it must place guest devices on a separate network and block access to internal systems.

Business networking equipment commonly uses a separate virtual network, known as a VLAN, for guest traffic. Firewall rules then prevent that traffic from reaching private network addresses. Some small-business routers handle this automatically when guest mode is enabled.

Cisco’s current guidance describes guest Wi-Fi as a separate SSID connected to its own VLAN, with guests limited to internet access. Its small-office reference design also uses firewall rules to deny guest access to local networks.

The exact settings depend on your equipment. Look for terms such as:

• Guest network
• Network isolation
• Deny local network access
• Client isolation
• VLAN
• Guest firewall rules

If you only see a second Wi-Fi name and password, ask your IT provider to confirm what guest devices can reach.

Should Guest Devices Be Able to Connect to Each Other?

Guest devices should usually be blocked from communicating with one another.

This setting may be called client isolation, wireless isolation, peer-to-peer blocking, or Layer 2 isolation.

Without it, one visitor’s laptop may be able to contact another visitor’s device on the same guest network. Blocking those connections provides additional protection for everyone using the Wi-Fi.

Client isolation and business-network separation are two different controls. Client isolation blocks communication between guests. Network separation blocks communication between guests and your internal systems. A business guest network should normally use both.

Where Should Employee Phones and Personal Laptops Connect?

A personal phone that only needs internet access can usually use the guest network. The same applies to a personal laptop that does not need to connect to internal business systems.

If employees use personal devices to access company files, applications, or internal systems, the business needs a clear bring-your-own-device policy. Those devices may require security software, device management, encryption, and specific access rules.

An employee-owned device should not receive unrestricted network access unless the work requires it.

Company-owned and managed devices can use the business network if they need access to internal resources. Personal and unmanaged devices should use a restricted network unless there is a business reason to provide additional access.

What About Smart TVs, Cameras, and Other Connected Devices?

Smart TVs, speakers, cameras, thermostats, digital displays, and similar products often need internet access but do not need to communicate with your computers.

These devices can be placed on a separate network for connected devices. Some smaller businesses use the guest network for this purpose, although that may not work if the devices need to communicate with a controller, phone, or local recording system.

The right setup depends on how the devices work. A smart TV or security camera should not be able to reach business computers just because it uses the same router.

CISA’s network-segmentation guidance notes that separate networks can be used for guests, connected devices, personal computers, and work computers.

How to Check Your Guest Wi-Fi

Use these five checks to confirm that the network is set up correctly:

1. Check which devices use each network. Business computers and other managed equipment should use the business network. Visitors and unmanaged devices should use the guest network.
2. Confirm that local network access is blocked. Guest devices should not be able to connect to printers, file storage, cameras, servers, or network management pages.
3. Check whether guest devices are isolated from each other. Enable client isolation or the equivalent setting if your equipment supports it.
4. Review the Wi-Fi security settings. The Australian Cyber Security Centre recommends WPA3, WPA3 transition mode when compatibility is required, or WPA2 when WPA3 is unavailable. Use a guest password that is different from your business Wi-Fi password.
5. Check the router and access points. Install current firmware, enable automatic updates when supported, replace default administrator credentials, and replace equipment that no longer receives security updates.

Test the guest network again whenever the router, firewall, switches, or wireless access points are replaced or reconfigured.

Do You Need a Separate Internet Connection?

Most small businesses do not need to pay for a second internet connection just for visitors.

A suitable business router or firewall can use one internet connection while keeping the internal and guest networks separate. The guest network can also have its own speed limit so that visitor traffic does not use all the available bandwidth.

Very small or older routers may not support proper isolation. Some provide a guest Wi-Fi option but offer limited control over what guests can access. Check the manufacturer’s documentation or ask your IT provider to test the configuration.

Keep the Guest Password Separate

Do not use the same password for your guest and business Wi-Fi networks.

Sharing the business password with visitors makes it harder to control who can reconnect later. It also means changing the password on every company device if the password needs to be replaced.

A separate guest password can be changed without disconnecting business equipment. Change it when too many people know it, after a large event, or when a contractor no longer needs access.

The password protects access to the guest network. It does not replace network separation.

Frequently Asked Questions

Is a guest Wi-Fi password enough to protect my business network?

No. The password controls who can connect to the guest Wi-Fi. Your equipment must also block guest devices from reaching the internal business network.

Can guests use the same internet connection as employees?

Yes. The networks can share one internet connection while remaining separated inside the router, firewall, and wireless equipment.

Should employees connect their personal phones to guest Wi-Fi?

If the phones only need internet access, the guest network is usually the safer option. Devices that need access to company systems should follow your business’s device and access policies.

Can visitors use a network printer?

Guest access to printers should normally be blocked. If visitor printing is necessary, your IT provider can set up a controlled method without giving guests access to the rest of the business network.

Does guest Wi-Fi prevent cyberattacks?

No. It reduces unnecessary access and can limit how far a compromised device can reach. Your business still needs secure passwords, multifactor authentication, software updates, endpoint protection, backups, and appropriate access controls.

Sources and Further Reading

• Secure Your Wi-Fi and Router: Australian Cyber Security Centre
• Risk Management of Enterprise Mobility: Australian Cyber Security Centre
• How to Implement Zero Trust Network Access: UK National Cyber Security Centre
• Cisco Unified Branch Design Guide
• Cisco Meraki Small Office Reference Architecture
• Federal Mobile Workplace Security Guidance: CISA

Ask your IT provider to confirm that your guest Wi-Fi is properly separated from your business network. And if you don’t have an IT provider, feel free to reach out to us and we’ll help you sort it out.

—

Featured Image Credit

This Article has been Republished with Permission from The Technology Press.

Summary: Allow personal devices only for approved work, through approved apps, and when the device meets your security requirements. Use company-owned devices for administration, sensitive work, or jobs that require large amounts of data to be stored locally.

Employees often use personal devices for work before the business has made a decision about it. They add work email to a phone, download a file to a home laptop, or sign into a company app from a computer shared with family.

Once business data is stored on a personal device, you have less control over updates, installed apps, backups, and who else uses the device. You also need a way to remove company data when the employee leaves or the device is lost.

Personal devices can be allowed, but the business should decide which devices, applications, and types of work are permitted.

What BYOD includes

Bring your own device, usually shortened to BYOD, means an employee uses a personally owned phone, tablet, or computer for work.

That can include:

• Adding work email to a personal phone
• Signing into Microsoft 365 or Google Workspace
• Joining online meetings
• Opening customer or company files
• Using a business messaging app
• Accessing accounting, CRM, or project management software
• Downloading documents to a personal computer

Depending on the application, business information may remain in the cloud or be downloaded to the device as messages, attachments, cached data, or files.

What you cannot fully control on a personal device

Your IT team can set and monitor security on company-owned devices. With personal devices, employees choose which apps to install, when to update the operating system, who else uses the device, and where files are backed up.

Management software can enforce some rules, but the available controls depend on the device, operating system, application, and enrollment method.

Other people may use the device

An employee may share a home computer or tablet with a partner, child, or another family member. Separate user accounts can reduce the risk, but many personal devices are used through one shared account.

The UK National Cyber Security Centre says BYOD access should not be permitted when an employee cannot follow the required security rules. Its example includes a device that cannot keep the employee’s work separate from other family users. NCSC BYOD guidance

Updates may be missing

Your IT provider may not be able to confirm whether a personal device runs a supported operating system or has current security updates.

An employee may delay an update because the device lacks storage, an older application might stop working, or the device is rarely restarted.

Business files may enter personal storage

A file downloaded from work email or cloud storage may remain in the Downloads folder, a personal document folder, or a device backup.

A personal cloud backup service could then copy the file to an account the business does not manage. Opening the document in a personal application may create another unmanaged copy.

Other applications may access business information

Personal devices contain applications chosen by the employee. Some may have permission to read files, contacts, browser activity, or information copied to the clipboard.

The business may not know which applications are installed or what those applications can access.

Repairs can expose business data

A broken personal phone or laptop may be taken to a repair shop chosen by the employee. Business email, saved sessions, or downloaded files could still be available on the device.

Your policy should tell employees who to contact before a device is repaired and what to do if the device cannot be opened.

Company data may remain after employment ends

Disabling an employee’s account stops future access to many cloud services. It does not remove copies that were downloaded to personal folders, opened in unmanaged applications, or copied to personal storage.

Managed work profiles and protected applications make it easier to remove company data. They can only remove the information they control.

Decide what work is allowed

Set access based on the work being performed and the information involved.

You might allow employees to read work email through an approved mobile app while requiring a company computer for customer database exports. Staff handling financial records, health information, legal documents, or large amounts of customer data may also need company-owned devices.

Administrative work should be performed from a managed device. Anyone responsible for user accounts, security settings, backups, or business systems should not do that work from an unmanaged personal computer.

Apply the same rules to contractors. Their access should be limited to the applications and information required for their work.

Security requirements for personal devices

A personal device should meet your requirements before it can access company information.

Use a supported operating system

The device should run an operating system that still receives security updates. Block access from devices that can no longer install current updates.

Install security updates

Operating system and application updates should install automatically where possible. Employees should restart their devices when an update requires it.

Require a screen lock

Require a PIN, password, fingerprint, or facial recognition to unlock the device. Configure the screen to lock automatically when the device is not being used.

Require device encryption

Encryption helps protect stored information if a device is lost or stolen. The Australian Cyber Security Centre recommends full-device encryption when personal devices may store business information. Cyber.gov.au BYOD guidance

Encryption must be enabled before the device is lost. It also needs to be supported by a strong device password or PIN.

Require MFA

Require MFA for work email, cloud storage, and other important systems. The NCSC recommends MFA as a minimum for BYOD access.

Use MFA for account sign-ins. Protect downloaded information with encryption and managed applications.

Block rooted or jailbroken devices

Rooting or jailbreaking removes some of the operating system’s built-in restrictions. These devices should not be allowed to access company data.

Detection is not perfect, so it should be used with the other security controls in this article.

Approve the applications used for work

Tell employees which applications they may use for email, messaging, file access, and other work.

Where your management service supports it, prevent business information from being saved to personal storage or copied into unmanaged applications.

Use separate accounts on shared computers

A personal computer used for work should have a separate account for the employee. Other users should have their own accounts and should not know the employee’s password.

Do not allow BYOD access when work cannot be kept separate from other users of the device.

Tell employees how to report problems

Employees need to know who to contact if a device is lost, stolen, repaired, replaced, or infected with malware.

Early reporting gives the business more time to disable access, check account activity, and remove managed data.

Control business data with managed apps or work profiles

Device and application management services can help keep work information separate from personal information.

Mobile device management, or MDM, can apply settings to an enrolled device and report whether it meets company requirements. The amount of control depends on the platform and enrollment method.

Mobile application management, or MAM, applies controls to supported work applications and their data. Depending on the product, it may restrict copying, block saving to personal storage, require another PIN, or remove company information from managed apps.

For example, Microsoft Intune can remove company data from protected applications when a device is lost or an employee leaves. Personal information can remain on the device.

Selective removal only affects data managed by the service. It cannot delete a file copied into an unmanaged application, personal backup, or unsupported storage location.

A factory reset removes personal and business data. Microsoft warns administrators about the risk of applying full device management to computers and phones the business does not own. Configure selective removal where possible and tell employees exactly what your management service can see and do. Microsoft Intune planning guide

What your BYOD policy should cover

Your policy should answer these questions:

• Which employees and contractors may use personal devices?
• Which types of devices are permitted?
• What work can be performed on them?
• Which applications must be used?
• Can company files be downloaded?
• Can the device be shared with other people?
• Which security settings are required?
• What information can the business or IT provider see?
• What settings can the business control?
• Can company information be removed remotely?
• What happens if the device is lost or stolen?
• What must happen before the device is repaired or sold?
• What happens when the employee leaves?
• Who pays for mobile data, repairs, or replacement?

Privacy, employment, and data protection requirements vary between countries. Have the policy reviewed for each location where you employ people.

Employees should read and accept the policy before company access is added to their devices.

What to do when a personal device is lost or stolen

The employee should contact the business or IT provider as soon as possible.

Your response may include:

1. Disabling access if the device cannot be accounted for
2. Revoking active sign-in sessions
3. Removing company data from managed applications
4. Removing the device from approved-device lists
5. Checking account activity for unexpected sign-ins
6. Resetting credentials if they may have been exposed
7. Recording which company files may have been stored on the device

Remote locking and removal commands only work after the device connects to the management service. A device that remains switched off or offline may never receive the command.

Encryption and account controls are still required because remote removal might not run.

What to do when an employee leaves

Disable the employee’s account and revoke active sessions at the agreed time. Remove company data from managed applications or work profiles.

Check whether business files were downloaded to the device and confirm how those copies will be returned or deleted.

Remove the device from your approved-device records. Where your management service supports it, remove business applications, certificates, email profiles, and VPN settings.

When personal devices should not be allowed

Provide a company-owned device when:

• The employee handles sensitive information
• The role requires administrator access
• Large amounts of company data must be stored locally
• The device is shared with other people
• The operating system is no longer supported
• Encryption cannot be enabled
• The business cannot separate or remove its data
• The employee does not accept the required security controls
• The device has been rooted or jailbroken

Company-owned devices are easier for your IT provider to support because their settings and installed software are known.

Frequently asked questions

Can employees use a web browser without enrolling their personal device?

You can allow browser access, but information may still remain in the browser cache, Downloads folder, saved passwords, screenshots, or active sessions.

Access policies can limit the devices and browsers that are permitted. Sensitive work may still require a managed device.

Is MFA enough to secure a personal device?

MFA helps protect the employee’s account. Device encryption protects stored files, while managed applications control how company information is used and copied.

You still need updates, screen locks, approved applications, and a process for lost devices.

Can the business see an employee’s personal information?

It depends on the management method. App management focuses on business applications and their data. Device enrollment can show device details and allow broader control.

Give employees a written explanation of what your IT team can see, change, lock, or remove before they enroll.

Can the business erase a personal phone?

Some enrollment methods support a full factory reset, while app-only management does not. A factory reset deletes personal information as well as company data.

Use selective removal for employee-owned devices where it is available.

Is BYOD cheaper than providing company devices?

BYOD may reduce hardware purchases, but it can add costs for management, support, security, and administration. Whether it saves money depends on the devices, applications, and work you allow.

Sources and further reading

• NCSC: Bring your own device guidance
• NCSC: BYOD costs and security requirements
• Australian Cyber Security Centre: Risk management of enterprise mobility and BYOD
• Australian Cyber Security Centre: Securing customer personal data
• Microsoft Learn: Protect data and devices with Intune
• Microsoft Learn: Remove company data from protected applications
• Microsoft Learn: Intune planning guide

If employees already use personal devices for work, ask your IT provider to check what they can access and whether the required controls are in place.

And if you don’t have an IT provider, feel free to reach out to us and we’ll help you sort it out.

—

Featured Image Credit

This Article has been Republished with Permission from The Technology Press.

Summary: Employees should use standard accounts for email, web browsing, and everyday work. Administrator access should be limited to approved IT tasks and protected with a separate account.

Administrator access often starts with one request. An employee needs to install a printer, update a specialist program, or change a setting on their computer.

Giving them administrator access gets the job done. The problem is that the access usually stays after the request has been completed.

From then on, the employee can approve other software installations and make changes that would normally require help from IT. If they install the wrong program or someone takes control of their account, those permissions can also be used to change the computer.

For everyday work, employees should use standard accounts. Administrator access should be kept for tasks that require it.

What administrator access allows someone to do

An administrator has more control over a computer than a standard user.

On Windows, members of the local Administrators group have full control over the resources on that computer. According to Microsoft’s guidance on local accounts, Microsoft recommends limiting the number of users in that group.

Depending on the computer and how it is managed, an administrator may be able to:

• Install and remove software
• Add drivers for printers and other equipment
• Create, change, or remove user accounts
• Change system settings
• Change permissions on files and folders
• Install services that continue running in the background
• Make changes to some security settings

Mac computers also have standard and administrator accounts. Apple says administrators can install and remove software, manage other users, and change settings. Apple recommends limiting the number of administrative users and using a standard account when administrator rights aren’t required.

Local administrator access applies to the computer itself. It is different from Microsoft 365, Google Workspace, network, or server administrator access. Those accounts may control email, cloud files, user accounts, or several systems at once.

An employee may have local administrator access to a laptop without being a Microsoft 365 administrator. Both types of access should be reviewed separately.

Why permanent administrator access increases your risk

Software launched by an employee normally starts with the permissions available to that employee.

If the software asks for administrator approval and the employee approves it, the program may be able to install system components, change settings, or affect information belonging to other users.

That matters when someone downloads a fake installer, opens a harmful attachment, or installs software from an untrusted website. The employee may think they are approving a legitimate update while giving the program permission to change the computer.

Windows uses User Account Control to ask for approval before many administrative changes. An employee signed in with an administrator account can approve the request themselves. A standard user is normally asked for credentials belonging to an administrator.

Microsoft describes the standard account as the recommended and more secure way to use Windows.

Standard accounts also reduce the number of people who can change security settings without review. Employees cannot approve every installation themselves, so IT has a chance to check the program, where it came from, and what permissions it needs.

CISA advises businesses to control local administrator access and restrict who can install software. The Australian Cyber Security Centre includes restricting administrative privileges in its Essential Eight security measures and recommends creating separate accounts for administrative work. Cyber.gov.au

Standard accounts are suitable for everyday work

A standard account can still be used for normal business tasks, including:

• Reading and sending email
• Using a web browser
• Working in Microsoft 365 or Google Workspace
• Accessing approved business applications
• Joining online meetings
• Printing with an installed printer
• Opening and saving files
• Changing personal settings that do not affect other users

Some applications can be installed for one user without administrator access. Others need administrator approval because they add drivers, services, or files in protected parts of the computer.

An employee should not receive permanent administrator access because one program needs an update. IT can approve the installation, deploy the update remotely, or use a separate administrator account for that task.

Older business applications sometimes expect the user to have administrator rights. Test those applications before changing account permissions. In many cases, IT can update the application, adjust its configuration, or grant access to the specific folders it needs.

How to manage software installations without permanent administrator access

Staff can still get software installed and updated without keeping administrator rights.

Let IT install approved software

Your IT team or provider can install the program remotely. This also gives them a chance to confirm that the installer came from the software company and that the requested version is supported.

Use managed software deployment

Businesses with managed computers can send approved applications and updates to employees without asking each person to run an installer. The available method will depend on the operating system and device management service.

Approve individual requests

An employee can contact IT when an installation requires administrator approval. IT can review the request and enter the required credentials without giving the password to the employee.

Provide time-limited administrator access

Some roles need to install or test software as part of their work. Give those employees a separate administrator account that is enabled only for the approved task, then disable it afterward.

Create a separate administrator account

Employees who regularly perform approved technical work can have a separate administrator account. They should continue using their standard account for email, browsing, and normal work.

The administrator account should only be used when a task requires the extra permissions.

Who should have administrator access?

Administrator access should be limited to people whose work requires it.

That may include:

• Your internal IT staff
• Your IT provider
• An approved technical employee
• A software specialist responsible for a particular system

Business owners should use standard accounts for their normal work too. Ownership of the company does not require permanent administrator access to every computer.

Your IT provider should keep a managed administrator account so they can support each device. The password should be protected and should not be shared with employees.

Using the same local administrator password on every computer creates another problem. If that password is stolen from one device, it may work on the others. Each computer should have a unique administrator password or use a management service that controls those passwords.

How to remove administrator access safely

Do not remove every administrator account at once. Someone still needs a working way to manage and repair each computer.

1. Check which employees have administrator access

Review the local Administrators group on every Windows computer and the administrator users on every Mac. Include old accounts, shared accounts, vendor accounts, and accounts created during the original setup.

2. Confirm why each person has it

Ask what tasks require administrator access. A clear business need should exist for every account that keeps the permission.

Needing to update one application occasionally does not require permanent access.

3. Make sure IT has a working administrator account

Confirm that your IT team or provider can sign in with a protected administrator account before removing permissions from employees.

Test the account on each device. This prevents the business from being locked out of its own computers.

4. Test important software

Check the programs each employee needs for their job. Confirm that they open, update, and work correctly when the employee uses a standard account.

Any application that fails should be reviewed before administrator access is removed permanently.

5. Change the employee’s account to a standard account

Once the computer has been checked, remove the employee from the local administrator group or change the account type.

The employee should then sign out and sign back in so the new permissions apply correctly.

6. Tell staff how to request an installation

Give employees one place to contact when they need software installed or a setting changed. Explain what information to include, such as the program name, the reason it is needed, and the official download page.

7. Review access when roles change

Check administrator access when an employee changes jobs, receives new responsibilities, or leaves the business. Include it in your regular access reviews as well.

Frequently asked questions

Can a standard user install software?

It depends on the software. Programs that only install inside the employee’s user profile may not need administrator approval. Software that changes protected system files, installs drivers, or adds background services usually requires administrator credentials.

Will removing administrator access stop employees from working?

Normal business applications should continue working. Test specialist and older applications before making the change across every computer.

Does removing administrator access stop malware?

It reduces what many harmful programs can change, but it does not prevent every attack. You still need supported software, security updates, endpoint protection, email security, MFA, and tested backups.

Should the business owner keep administrator access?

Use a standard account for everyday work. If you need administrator access for an approved task, use a separate account and keep its password protected.

Is local administrator access the same as Microsoft 365 administrator access?

No. Local administrator access controls one computer. Microsoft 365 administrator roles can control cloud users, email, files, security settings, and other parts of the company’s Microsoft environment.

Both should be limited and reviewed.

Sources and further reading

• Microsoft Learn: Local accounts
• Microsoft Learn: How User Account Control works
• Apple Support: Set up your Mac to be secure
• CISA: StopRansomware Guide
• Australian Cyber Security Centre: Restricting administrative privileges

If you are not sure who has administrator access or whether your employees need it, ask your IT provider to review the accounts on your business computers.

And if you don’t have an IT provider, feel free to reach out to us and we’ll help you sort it out.

—

Featured Image Credit

This Article has been Republished with Permission from The Technology Press.

Summary: Most IT problems don’t appear out of nowhere. Backups quietly stop running, updates sit unfinished for weeks, and old staff accounts stay switched on for months. A short check once a month catches these while they’re still cheap to fix. This post covers the six things to look at.

Most owners only look at their IT when something has already gone wrong. A file won’t open, a laptop won’t start, or an invoice gets paid into a scammer’s account. Fixing it at that point costs more than preventing it would have.

Almost none of it happens without warning. The backup that fails when you finally need it had been failing for weeks. The account a scammer used belonged to someone who left last year. Thirty minutes a month is usually enough to catch that kind of thing.

Why a monthly look is worth the time

Verizon’s 2026 Data Breach Investigations Report found that 31% of breaches started with attackers exploiting software that hadn’t been patched. That makes unpatched software the most common way in, ahead of stolen passwords. The same report found the median time to fully fix a known problem has risen to 43 days.

Most attacks use a problem that was already known, with a fix already available. Nobody had installed it yet.

The check

1. Updates

Check whether Windows updates are installing on your computers, or sitting at “restart required” week after week. Do the same for phones and for the software you use most, like your browser and your accounting app. If people keep clicking “remind me later,” that’s something to fix.

2. Backups

Open your backup tool and look at the last few runs. You want recent successful backups, not a list of errors. Then check when anyone last restored a file from it. If it’s never been tested, you don’t know whether it works.

3. Who has access

Pull up the list of user accounts in Microsoft 365 or Google Workspace and read through it. Every name should be someone who still works for you. Look for people who left, contractors who finished months ago, and shared logins like “office” or “admin” that several people use. Switch off anything you don’t need.

4. Multi-factor authentication

Check that MFA is switched on, and that it’s on for everyone, not just the people who set it up first. Pay closest attention to admin accounts and anyone who handles money. Microsoft’s research shows MFA blocks more than 99.2% of account compromise attacks.

5. Devices

Look at what’s connected to your systems. If there’s a laptop or phone you don’t recognize, find out whose it is. While you’re there, check that laptops are encrypted and that any phone with company email on it has a passcode or fingerprint lock.

6. Subscriptions and licenses

Open your billing page and read what you’re paying for. Businesses regularly pay for licenses belonging to people who left, or for two tools that do the same job. It’s also how you find software somebody signed up for without telling anyone.

Make it a routine

Put it in the calendar on a fixed day, like the first Monday of the month, and give it to the same person each time. That’s you or whoever handles the admin side.

Keep a running note of what you checked and what you found. After a few months you’ll see whether the same problem keeps coming back. If it does, it needs fixing properly instead of clearing each time.

Thirty minutes only works if you don’t stop to fix things along the way. Write down what you find and deal with it afterward.

Who fixes what

Most of it is small, like a laptop that needs restarting, a license to cancel, or an account to switch off. Handle those yourself.

Send the rest to your IT provider: backups that keep failing, MFA that won’t turn on for someone, a device nobody recognizes, or updates that fail on the same machine every month. Those usually mean there’s a bigger problem behind them.

What this check doesn’t do

It isn’t monitoring. A good IT provider has tools watching your systems all day and flagging things you’d never spot from a monthly glance.

The check covers what those tools can’t know. You know who left, which subscriptions you approved, and whose laptop is whose.

Frequently asked questions

How often should a small business check its IT?

Once a month is enough for this list. Backups are worth a quick look more often if losing a day’s work would seriously hurt, since that’s the item most likely to fail quietly.

Who should do it?

You or whoever runs the admin side of the business. Most of the list needs no technical skill, just someone who knows who works there and what the business pays for.

What if I don’t know where to find any of this?

Ask your IT provider to walk you through it once and write down where each thing lives. Many will also send you a monthly summary covering most of it.

Isn’t this my IT provider’s job?

They handle the monitoring, the patching, and the fixing. The check is the part that depends on knowing your business, like who left last month or which subscription nobody approved.

If I only have ten minutes, what matters most?

Backups and updates. Without working backups you can lose everything you’ve stored, and unpatched software is now the most common way attackers get in.

Does this apply if everything we use is in the cloud?

Yes. Cloud tools still need updated devices, working backups, MFA switched on, and access lists that match who actually works for you.

Sources and further reading

• Verizon 2026 Data Breach Investigations Report — the finding that 31% of breaches start with exploitation of unpatched software, and that the median time to fully fix a known problem is 43 days.
• Microsoft: Plan for mandatory Microsoft Entra multifactor authentication — Microsoft’s research that MFA blocks more than 99.2% of account compromise attacks.

If you’d like a hand setting this up, your IT provider can show you where each of these lives in your systems and take the fixing off your plate. And if you don’t have an IT provider, feel free to reach out to us and we’ll help you sort it.

—

Featured Image Credit

This Article has been Republished with Permission from The Technology Press.