48: IGEL Weekly: How to Use IGEL OS Drive Encryption

मई 2, 2022

IGEL’s Sebastian Perusat teaches you to use IGEL OS drive encryption. You will learn how to obfuscate the corporate identity, hide AD login info, manage lost devices, enhance the chain of trust, and deal with legal compliance. 

होस्ट: एंडी व्हाइटसाइड
सह-मेजबान: पैट्रिक टोनर
सह-मेजबान: सेबेस्टियन पेरुसैट

Why Encrypt an Endpoint That Holds Little Data

IGEL OS is a read-only operating system with very little data on it, so disk encryption may seem unnecessary. Even so, it matters for several reasons. A lost or stolen device can reveal corporate identity items such as wallpapers, logos, and session names. It can also expose Active Directory login information. Beyond that, encryption strengthens the chain of trust on the device and limits extraction of local data.

For some organizations, it is simply a compliance requirement. Security checklists and cyber insurance questionnaires increasingly ask about it, and a missing control can stand in the way of coverage. Windows administrators already know this kind of feature from BitLocker, and IGEL takes the Linux capability underneath and makes it easy to manage.

What Is Encrypted

The feature encrypts the operating system partition, not an entire disk. IGEL OS is small, using roughly 1.5 to 4 gigabytes of space, so the partition involved is only a few gigabytes. That keeps the process quick on typical hardware.

The capability arrived after customers repeatedly asked what happens to a device that is stolen, whether the operating system partition could be encrypted, and which kind of encryption is used locally. One local encryption requirement from a project made it mandatory, which helped push it onto the roadmap.

Configuring It in the UMS

As with other IGEL settings, configuration is done through a profile in the Universal Management Suite. There is a device encryption setting with a few options. The default value keeps whatever is already configured locally, while other options enable or require encryption. To make users encrypt their devices, the setting has to be deployed through the profile.

One caution applies to any new feature: if a setting does not appear in a profile, the profile may be built on older firmware, or the management server may not support it yet. Using the latest public versions avoids the problem.

The User Experience

After the profile reaches an endpoint, a device encryption window appears on the next reboot. The user enters and confirms a password that meets the rules set in the profile, such as length and character requirements, with a strength bar that moves from red to yellow to green. Once the user applies it, encryption begins.

The device should not be rebooted or powered off during that time. Depending on the hardware, the process takes from about two minutes to 15 or 20 minutes. Users can start a session while it runs, but laptop users should confirm they have enough power. After encryption, a user logs in to the device with the encryption password and then signs in with their usual Active Directory or Citrix credentials, so there are two logins.

A First Version With More to Come

This is the first release of the feature, and for now it is entirely user based. The user sets the password. Gaps remain, such as remote recovery for a device whose user forgets the password after it sat unused, and a shared or resettable password. Further changes are expected in future releases, including behavior closer to what Windows and macOS administrators already know.

A device with a forgotten password can still be reflashed and recovered, and there is a switch to keep or discard the old settings when that happens. IGEL weighs customer requests by the size of the project, but it also gathers feedback from the community, where people can suggest features without a formal request process.

hi_INHindi