Securing Telework PCs

Many firewalls require the user to manually select the appropriate policy or environment from a list, but some personal firewalls can be configured to "auto-sense" the network they are on and choose a security policy based on that information.

Although auto-sensing helps to automate the security process, it may not always work correctly and could apply the wrong policy at times, making the computer insecure or blocking needed functionality.

Thus, organizations that want to use auto-sensing features should test them thoroughly before relying on them, as well as educating users on how they work and how users can override them if the wrong policy has been selected. Auto-sensing features should only be used if they notify the teleworker what environment the feature thinks the user is in so that the user can override it if the auto-sensing feature has misidentified the environment.

Another important consideration for telework PCs is applying OS and application security updates.

For personally-owned telework PCs, this generally involves configuring the OS and applications to automatically contact the vendors' online services frequently to check for updates and download and install them.

Determining how to configure organization-controlled telework PCs to acquire updates can be significantly more complicated. An organization might wish to use a centralized patch management system for all its PCs, but if telework PCs rely on such a system, they may not receive updates promptly if they are configured to get updates only from the organization's centralized patch management system.

For example, a user might connect a telework PC to an external network but not establish a remote access connection to the organization.

The PC may be exposed to threats that could exploit its unpatched vulnerabilities, and patches would not be available until some time after the user established a remote access session.

Another potential problem with keeping software updated is that remote access sessions downloaded if the software performing the updates does not permit updates to be downloaded in pieces.

Organizations should carefully consider these issues when planning how their telework PCs will be kept current with OS and application updates. Organizations should also encourage users to fully update their telework PCs before taking them on travel or to other third-party environments, which are generally more likely to contain new threats than home networks.

Other security measures that are particularly important for telework include the following:

-Have a separate user account with limited privileges for each person that will use the telework PC. Teleworkers should use their limited privilege accounts for regular work and use a separate administrative account only for tasks that require administrator-level access, such as some software updates. This reduces the likelihood of an attacker gaining administrator-level access to the PC.

-Enforce session locking, which prevents access to the PC after it has been idle for a period of time (such as 15 minutes) or permits the user to lock a session upon demand. After a session is locked, access to the PC can only be restored through authentication. Session locking is often part of screen-saver software. This prevents an attacker within physical proximity of a PC from easily gaining access to the current session. However, it does not thwart an attacker who steals a PC or has access to it for an extended period of time; session locking can be circumvented through various techniques.

In cases where organizations are concerned about risk from inadequate telework PC security, particularly from PCs that are not organization-controlled or are otherwise at higher risk of compromise, organizations may want to consider different security controls in addition to or instead of those described above.

For example, some vendors offer solutions that provide a bootable OS on read-only removable media with pre-configured remote access client software. A user can insert this media into a PC and reboot the computer; this bypasses the PC's OS, which may be compromised, and loads the known-good OS and remote access client software from the removable media.

In most cases, these solutions can be configured to prevent users from storing files on the local hard drive, saving files to removable media, and otherwise transferring information from the known-good OS to another location.

Bootable OS solutions make the logical security of the telework PC much less important, although they do not prevent all compromises (for example, vulnerabilities in the removable media's OS could be exploited, or malicious code may be present in the PC's BIOS, firmware, or hardware). Another caveat with these solutions is that they require the PC to support booting the removable media before the hard drive, which may require the user to reconfigure the PC's BIOS settings.

Another option is to provide teleworkers with flash drives that are specifically configured for telework use. These drives hold organization-approved applications that are executed from a read-only portion of the drives, which protects them from unauthorized modification. Temporary files from these applications are stored in another portion of the flash drives, which reduces the likelihood of data leakage onto the PC.

Computer Security - Cryptography
Development of a Cryptographic Module
Cryptographic Module Guidance
Cryptography - Security Levels
Cryptographic Module Finite State Model
Cryptographic Modules - Design
Configuration Management
Conditional Self-Tests
Pre-Operational Self-Test
SSP Zeroization
SSP Entry and Output
Environmental Failure Testing Procedures
Single-Chip Cryptographic Modules
Multiple-Chip Standalone and Embeded Cryptographic Modules
Cryptographic Module Specification
Software and Services
Operator Authentication & Logical Interfaces
Cryptography - Acronyms