Tablet Computer

What a tablet computer is

A tablet computer is a portable computing device built around a touchscreen interface, battery power, and mobile-friendly software. It sits between a phone and a laptop in everyday use, so the security model is shaped by portability, app ecosystems, wireless connectivity, and the fact that it is often carried outside controlled office environments.

How tablets differ from other personal computers

The key difference is the primary interface: a tablet is designed to be used directly through touch, with an operating model that usually assumes a lighter accessory set than a traditional laptop. That affects how users authenticate, how data is entered, and how organisations should think about loss, theft, and unsanctioned use. In practice, the device class is defined as much by mobility and user experience as by hardware.

Security characteristics of tablet computers

Tablets inherit many of the same risks as other endpoint devices, but the combination of constant mobility, consumer app stores, and personal use makes control harder. They may store email, documents, tokens, cached sessions, or app data, and they often connect through public Wi-Fi or unmanaged networks. That makes device posture, encryption, screen locking, and app permissions central to reducing exposure.

Because tablets are frequently used for both work and personal tasks, organisations need to assume that trust boundaries can blur. A corporate tablet enrolled in mobile device management can enforce app control, data separation, and remote wipe, but those safeguards only work if enrollment is maintained and policies are not bypassed by sideloading, jailbreaking, or poor configuration.

Why tablet management matters

For security teams, a tablet is not just a small computer, it is an endpoint with a highly mobile threat profile. Its value lies in access to accounts, business applications, and stored data rather than in raw processing power. That means exposure management should focus on who can use it, what data it can reach, and whether the device remains compliant throughout its lifecycle.

In enterprise settings, the practical question is usually not whether tablets can be secured, but whether they are consistently governed at scale. Shared tablets, contractor devices, and personally owned devices used for work all create different control expectations, especially when the device is a gateway to sensitive systems or regulated information.

Risk and Threat Considerations

Tablets create meaningful exposure because they are easy to lose, easy to carry into untrusted environments, and often rich in cached business data and active sessions. The main risk is not the hardware itself, but the combination of physical portability, weak local controls, and broad app access that can turn a lost or misconfigured device into an account and data exposure event.

Failure mechanism: If screen locks, encryption, enrollment, or remote management are weak or inconsistent, an attacker or opportunistic finder may gain access to apps, tokens, synced files, or authenticated sessions already present on the device.

Impact: That can lead to data disclosure, account misuse, lateral access into business systems, or persistence through trusted mobile access paths until the device is revoked or wiped.

Practitioner Guidance

Why practitioners should care: Tablets should be managed as enterprise endpoints, not as simple consumer devices with a larger screen. The important operational question is whether the organisation can control software, data, and access consistently across owned, shared, and personally used devices.

Governance implication: Establish a clear policy for ownership, enrollment, app installation, and data separation so that tablets used for work are covered by the same minimum security expectations as other managed endpoints. Where a tablet can access sensitive resources, its lifecycle should include onboarding, compliance checks, and revocation.

Practitioner takeaway: Treat the tablet’s portability as a security requirement, not just a usability feature, and design controls around loss, session exposure, and long-lived access.

Related resources from NHI Mgmt Group

• How do you know if computer-use governance is actually working?
• How should security teams govern computer-use models that change access inside enterprise systems?
• How can organisations decide whether a computer-use model belongs in production IAM?
• How should organisations handle digital identity proofing when a tablet cannot read IC cards directly?