COBO

What COBO Means in Device Governance

COBO, or Company Owned, Business Only, is a device ownership and usage model in which the organisation provides the hardware and limits it to work purposes. That makes the device easier to standardise, monitor, and secure than a mixed-use endpoint, because policy, configuration, and data handling expectations are set by the business rather than the individual user.

In practice, COBO is less about the label itself and more about control boundaries. The organisation can define which applications are allowed, how storage is protected, what telemetry is collected, and how quickly a device can be quarantined or wiped if it is lost, retired, or suspected of compromise.

Why Organisations Use COBO

COBO is attractive when the business needs predictable control over endpoint posture. A company-owned, business-only device can be built around a known baseline, which reduces variation across the fleet and makes patching, configuration enforcement, and support more consistent.

The model also supports tighter data separation. When the device is reserved for business use, organisations can more confidently apply device encryption, mobile device management, conditional access, and application restrictions without needing to balance those controls against personal-use exceptions.

For regulated environments or roles that handle sensitive systems, COBO often fits better than bring-your-own-device approaches because it gives the organisation clearer operational authority over monitoring, investigation, and removal from service.

How COBO Shapes Security Control

COBO changes how endpoint security is implemented, not just how the device is issued. Because the hardware is corporate property, the organisation can enforce stronger baselines, standard image builds, and a narrower software allowlist. That helps reduce drift, shadow IT, and unsupported configurations.

The model is also useful for visibility. A business-only device gives security teams a cleaner picture of installed software, device health, OS version, encryption status, and policy compliance. That visibility is often what makes COBO valuable in the first place, especially where data loss prevention, auditability, or incident response depends on reliable endpoint telemetry.

COBO works best when joined to policy that is explicit about acceptable use, administrative rights, update enforcement, and the handling of removable media or local storage. Without those rules, the ownership model alone does not guarantee strong protection.

COBO Compared with Other Endpoint Models

COBO sits in the same family as other enterprise endpoint models, but its defining feature is that the device is owned by the company and dedicated to work. That is different from patterns where a personal device is merely managed, partially containerised, or allowed limited access to corporate apps.

The practical difference is control depth. In COBO, the organisation can usually apply more aggressive management because it controls the entire device lifecycle, from enrolment through retirement. That typically makes COBO the preferred choice for high-trust roles, shared devices, frontline environments, and situations where supportability matters as much as usability.

It is also the model most likely to be paired with strict identity and access policy, since the organisation is trying to keep both the device and the work activity inside a controlled boundary. In that sense, COBO is not just an ownership model, it is a governance choice about how much trust to place in the endpoint itself.

Risk and Threat Considerations

COBO reduces some endpoint risk, but it also concentrates trust in a managed fleet. If the management plane, policy baseline, or device build is weak, the organisation can scale the problem across every corporate device at once. Misconfiguration, delayed patching, or excessive administrative access can turn a well-controlled model into a highly consistent failure mode.

Failure mechanism: Attackers and insiders benefit when a business-only fleet has uniform weaknesses, weak monitoring, or broad administrative privileges, because compromise can spread through the same controls that are meant to provide consistency.

Impact: A compromised COBO device can expose corporate data, authenticated sessions, local secrets, and managed applications, and it can also provide a reliable foothold for lateral movement or policy abuse if recovery and revocation are slow.

Practitioner Guidance

Why practitioners should care: COBO is most effective when device ownership, configuration control, and response authority are clearly assigned. Treat it as an endpoint governance model, not just a procurement label, because its value depends on how consistently the fleet is managed.

Governance implication: Define who owns the baseline, who can approve exceptions, and what triggers remote lock, selective wipe, or full retirement. That clarity matters most where the device is used for sensitive business workflows or highly regulated data handling.

Practitioner takeaway: COBO delivers the most value when organisations keep the fleet standardised and resist exception creep, because every unmanaged exception weakens the security and compliance advantage the model is meant to provide.

Related resources from NHI Mgmt Group

• What is the difference between CYOD, COPE, and COBO in a device strategy?