AirWatch and VMware Carbon Black: endpoint detection and response
Endpoint security in an Australian business has to cover managed laptops, company phones, personal tablets and field equipment operating from metropolitan offices to regional sites. AirWatch, now associated with VMware, and VMware Carbon Black address different parts of that problem: AirWatch provides enterprise mobility management and device control, while VMware Carbon Black centres on endpoint detection and response (EDR).
Combined with compatible licences, deployment design and security policies, the platforms can give IT teams a clearer view of device trust, security teams stronger behavioural signals, and leaders a more defensible basis for access and investment decisions. The distinction between management and detection matters when assessing coverage, ownership and response speed.
How the Platforms Divide the Work
The useful starting point is to treat each product according to its operational purpose rather than assume that one replaces the other.
| Area | AirWatch | VMware Carbon Black |
|---|---|---|
| Main purpose | Enterprise mobility management, endpoint configuration and device support | Endpoint detection and response for supported endpoints |
| Core visibility | Enrolment, inventory, operating-system and application configuration, device health and compliance | Process, file and network telemetry, behavioural detections and threat hunting |
| Everyday control | Deploy applications, enforce settings, manage access and apply remote configuration | Investigate suspicious activity, block malicious behaviour and respond to incidents |
| Typical owner | IT operations, mobility teams and service desks | Security operations, threat hunting and incident response teams |
| Main business value | Consistent access, manageable support and policy enforcement across managed devices | Faster investigation, targeted containment and a record of endpoint activity |
| Coverage considerations | Mobile, desktop and operating-system capabilities depend on the selected features and architecture | Prevention, isolation and telemetry options depend on the subscription, endpoint type and deployment |
AirWatch establishes the administrative baseline. It records enrolled equipment, applies application and configuration policies, checks device health, and helps support teams manage access to business resources. Its controls are strongest when the endpoint is enrolled and the organisation has defined which settings indicate an acceptable security posture.
Carbon Black observes activity within supported endpoints and applies detection logic to identify suspicious behaviour. Security teams can investigate an alert, trace activity and use available response actions such as process termination or endpoint isolation, depending on the subscription. Management shows what an endpoint should be doing; EDR helps reveal what it is actually doing.
AirWatch in Everyday Australian Operations
AirWatch is particularly relevant to organisations running structured bring-your-own-device (BYOD) programmes. A sales employee may move between an office in Melbourne, a home workspace and a client site in Brisbane, alternating between a company laptop and a personal phone. Consistent application access, passcode requirements and enrolment policies can keep this mixed environment usable without exposing business data unnecessarily.
The platform supports device inventory, application deployment, software updates, remote configuration and policy enforcement. Teams can control access to selected business applications according to device posture, encryption, operating-system version and other checks. For personal devices, clear enrolment rules, user consent and separation of work from personal data remain important; a management profile should not imply ownership of every item a person carries.
Australian IT teams also work with mixed estates. Microsoft 365 is common on Windows in professional services, government and enterprise offices, while macOS, iOS and Android devices add different management requirements. AirWatch helps organise that variety, but administrators still need to confirm which features support each operating system and how policy conflicts will be handled across a large fleet.
Mobility management also supports the service-desk side of operations. Remote configuration, device information and policy visibility can shorten troubleshooting when staff work from home or travel. This matters for distributed teams and field personnel in agriculture, mining and utilities, where a managed re-enrolment may be more practical than returning equipment to a central office.
How Carbon Black Detects and Contains Threats
Carbon Black brings the security team’s investigative layer. Supported endpoints generate telemetry about processes, files, network connections and behavioural patterns. Detection models can surface activity associated with malware, ransomware, credential theft or unauthorised remote access, helping analysts move beyond a simple antivirus match to a more complete account of an incident.
That visibility supports two distinct jobs: prevention and detection. Preventive controls can block known malicious files or scripts, while EDR detections identify suspicious sequences that deserve attention. Analysts can examine a process tree, search for related artefacts and determine whether an alert represents isolated noise or a wider compromise.
Response controls can include terminating a process, blocking a hash, denying an application or isolating a host. Availability differs by licence and endpoint type, so those capabilities should be matched to the risk of business interruption. Carbon Black should be seen as a computer and server endpoint capability, not as automatic equivalent protection for every managed mobile phone; mobile controls need separate evaluation.
Security teams should also test how prevention policies, detection updates and remote response behave when cloud connectivity is interrupted. Regional sites and long-distance field operations can experience patchy network coverage, making local procedures and cached controls important parts of the response plan.
Connecting Management and Security Context
The strongest operational case for using both is shared context. AirWatch can show whether an endpoint is encrypted, correctly configured, up to date or compliant with corporate policy. Carbon Black can reveal signs of compromise on that same asset. Joined through approved connectors and identity records, those signals can help a responder judge urgency before deciding whether to revoke access, isolate the device or request re-enrolment.
A practical workflow might start when a Carbon Black detection raises an endpoint’s risk. The security team confirms the evidence, isolates the host where appropriate and records the affected user and device. AirWatch then provides the management path for remediation, such as enforcing a compliant configuration or beginning a clean re-enrolment. Access to business applications can be adjusted through the relevant identity and access controls.
Automation needs restraint. An integration that blocks every device during a false positive can disrupt payroll, logistics or clinical work, while overly broad telemetry collection can create privacy and retention issues. Security architects should verify supported APIs, permission boundaries and action sequencing, and establish human approval for disruptive containment. Shared information does not necessarily mean a single console, and teams should not promise a direct technical integration until they have confirmed it for their chosen editions and deployment model.
Ownership should be explicit. Service desks usually own device support, security operations owns detection and containment, and identity administrators enforce access restrictions. Shared dashboards and escalation rules help prevent these teams acting on conflicting signals, while recorded decisions support governance and audit expectations across a larger Australian organisation.
Start With a Measured Australian Trial
An Australian deployment should be assessed against the obligations and operating realities that shape the organisation. The Australian Signals Directorate’s Essential Eight provides a useful risk-based reference for endpoint controls. Organisations in critical infrastructure, finance, health and government may also face sector requirements, and entities covered by the Security of Critical Assets Act 2018 have obligations that vary by industry and role. EDR contributes to detection and response, but it does not replace patching, application allow-listing, multifactor authentication and other foundational safeguards.
Privacy is equally important. The Privacy Act 1988 and the Australian Privacy Principles can apply to endpoint telemetry and user activity collected by security tools. Under the Notifiable Data Breaches scheme, qualifying breaches must be assessed and notified through the Office of the Australian Information Commissioner. Configure collection, access, retention and deletion deliberately, and align alerts with incident response procedures rather than treating monitoring as unlimited data collection.
A structured evaluation can measure time to enrol a device, inventory accuracy, policy exceptions, detection usefulness, investigation effort and containment recovery. Test Windows laptops used by hybrid teams, mobile access for field personnel and any critical systems in scope. Australian buyers often assess implementation through local managed service providers and resellers, so operational support and delivery capacity matter alongside licence features. Compare pricing and package options against measured outcomes, review customer stories for comparable environments, and use a pilot that can be rolled back.
Start with the fully functional 30-day free trial offered by AirWatch, then use the evaluation to define which endpoint roles, licences and integrations are justified. Contact the sales team with a concise Australian use-case brief covering industries, locations, device types and security obligations, and request a deployment proposal that includes support arrangements, implementation milestones and measurable security outcomes.