How to Create an AirWatch Compliance Policy That Blocks Unpatched Devices
An effective endpoint compliance policy should do more than report missing updates. It must identify devices that fall below the organisation’s patching standard, restrict access before they create risk, and give users a practical path back to compliance. AirWatch, now associated with VMware and commonly delivered through Workspace ONE UEM, provides the controls needed to make that process consistent across corporate-owned, personally owned and specialised devices.
The central idea is simple: define the minimum acceptable operating system and security posture, connect that standard to access rules, then test the response before applying it broadly. A Windows laptop with an outdated security update may need a short grace period, while a rooted Android phone or a device missing several critical patches may need immediate blocking.
Australian organisations also need to account for local privacy and operational requirements. A policy may cover staff in Sydney and Melbourne offices, remote workers in Brisbane, and employees connecting from mining or construction sites with intermittent links. The controls should protect company data without making legitimate work impossible when a device is temporarily offline.
AirWatch compliance rules work best when they are specific, measurable and tied to business risk. Rather than blocking every device that is not perfectly current, security teams can distinguish between critical and routine updates, set deadlines, and combine patch status with encryption, passcode and threat-detection requirements.
| Policy approach | Best use | Access result | Main consideration |
|---|---|---|---|
| Minimum OS version | Enforcing supported platforms | Blocks devices below the approved version | Does not prove every security patch is installed |
| Patch age threshold | Controlling update freshness | Restricts devices with updates older than a set age | Requires reliable device reporting |
| Compliance grace period | Allowing users time to remediate | Warns first, then blocks after the deadline | Needs clear user communication |
| Conditional access | Protecting sensitive apps and data | Limits email, VPN or SaaS access | Must be integrated with identity services |
| Full device quarantine | Responding to high-risk endpoints | Denies corporate access until fixed | Can interrupt field operations |
Define The Compliance Baseline
Start by writing the rule in operational terms. For example, Windows 11 devices may be required to run a supported build and install critical security updates within 14 days of release. Android and iOS devices can use a minimum operating system version, while macOS endpoints may be assessed against both the approved version and recent security update status.
Avoid relying on a single condition if the business handles sensitive information. A device that has a recent operating system but lacks encryption, screen locking or endpoint threat protection should not receive unrestricted access. Combine patch compliance with device ownership, platform, risk level and the applications being requested.
Useful baseline conditions include:
- Supported operating system and approved build
- Critical patch installed within a defined age
- Encryption enabled on corporate storage
- Passcode, biometric and lockout controls active
The threshold should reflect the risk of the data involved. A retail tablet used for stock checks may have a different access profile from a finance laptop handling payroll records. Australian organisations should also map the policy to the Australian Privacy Principles and, where relevant, the ACSC Essential Eight mitigation strategies.
Configure Detection In AirWatch
In the AirWatch console, create separate smart groups for platforms, ownership models and business functions before assigning the compliance policy. This makes it possible to apply stricter rules to administrator laptops or privileged accounts without forcing the same settings onto every enrolled endpoint.
Set the operating system minimum and patch-age condition in the compliance rules for each platform. For Windows, use a supported build requirement and a security update condition where the available device inventory provides dependable patch data. For Apple and Android fleets, use the latest supported OS baseline and include indicators such as jailbreak or root detection.
The policy should specify how often the device checks in and what happens when it stops reporting. A corporate laptop that has not checked in for several days may simply be travelling, while a lost phone that remains connected to business services presents a different concern. Use a shorter tolerance for high-risk devices and avoid treating every offline period as a patch failure.
When configuring device groups, account for Australian connectivity patterns. Staff in central Sydney may check in continuously, while a worker travelling between Perth and a remote Western Australian site may experience long gaps. A sensible design can require compliance before access resumes, rather than blocking a device solely because it could not report during a period without coverage.
Apply Blocking And Remediation Actions
A blocked endpoint should receive a clear remediation path. AirWatch can send a notification, mark the device non-compliant, restrict selected applications, or trigger enterprise wipe and quarantine actions depending on the severity of the failure. For an unpatched device, staged enforcement is usually easier to manage than an immediate, universal lockout.
A practical sequence is to notify the user when an update is required, provide a deadline, and show the exact action needed. After the deadline, restrict access to corporate email, VPN and managed applications. If the device remains vulnerable or shows signs of tampering, move it into quarantine until the service desk verifies remediation.
Consider conditional access for cloud services used by distributed teams. Blocking Microsoft 365, Salesforce or internal applications can be more precise than disabling the entire device. Privileged administrators and users accessing personal, health or financial information may require an immediate deny rule when critical patches are missing.
Good remediation messaging usually includes:
- The missing update or minimum version
- The deadline and business impact
- A link to the approved update process
- A service desk contact for failed installations
Do not rely on users to interpret a generic “device non-compliant” message. In Australia, support teams may need to assist employees across multiple time zones, including staff working early shifts or on rotating rosters. Give them a clear procedure for temporary access, identity verification and escalation.
Test The Policy Before Broad Deployment
Use a pilot smart group containing representative devices from Windows, macOS, iOS and Android. Include corporate-owned and BYOD endpoints, older hardware, devices with limited storage, and users who work away from metropolitan networks. Deliberately introduce test conditions, such as an overdue patch, an unsupported build or a device that has stopped checking in.
Verify that AirWatch detects the correct state and that enforcement reaches the intended services. A device should be blocked from the defined corporate resource, while emergency contact methods and approved recovery tools remain available. Check whether an update changes the compliance state automatically or whether the user must restart, open the agent, or trigger a manual check-in.
Specialised equipment deserves its own test plan. Kiosks, point-of-sale systems, scanners and operational technology may not support the same update schedule as office computers. For organisations managing connected equipment, this discussion of IoT gateway management is useful when deciding how edge devices should be monitored and governed alongside standard endpoints.
Record false positives and missed detections during the pilot. A patch policy that blocks a required application after an operating system update may create more operational risk than the original vulnerability. Use the results to adjust thresholds, exclusions and maintenance windows before enrolling the full workforce.
Monitor Compliance And Maintain Exceptions
After rollout, review compliance dashboards regularly rather than treating the policy as a set-and-forget control. Track the percentage of devices that are compliant, approaching a deadline, blocked, or unable to report. Segment the results by operating system, location, ownership and business unit so recurring problems are visible.
Exceptions should be limited, documented and time-bound. A medical device, warehouse scanner or production controller may need a vendor-approved patch window, but it should not receive a permanent exemption. Record the owner, reason, compensating controls and expiry date, then require a new review before the exception continues.
Useful maintenance checks include:
- Retiring inactive or duplicated device records
- Reviewing unsupported operating system versions
- Checking whether blocked users can self-remediate
- Comparing AirWatch data with vulnerability reports
Keep the policy aligned with the organisation’s patch management process. If updates are released on a predictable monthly schedule, set notification and enforcement dates around that cycle. Critical vulnerabilities may require an accelerated deadline, while routine feature updates can use a longer window to reduce disruption.
Review the rule after major platform changes, acquisitions or new software deployments. Australian businesses often operate mixed environments because of BYOD, contractors and regional offices. A quarterly review can identify whether the original policy still reflects the devices, applications and data flows the organisation actually uses.
Start with a small pilot, define the blocking threshold clearly, and connect every failure to a workable recovery path. Then deploy the AirWatch compliance policy through controlled groups, monitor the results and tighten enforcement as the data supports it. A well-maintained rule can keep unpatched devices away from corporate systems while giving Australian teams the visibility and support needed to stay productive.