Windows 2000 EFS Key Export and Recovery Policies

In Microsoft Windows 2000, the Encrypting File System (EFS) provides file-level encryption using a combination of symmetric and public key cryptography. To safeguard data against loss from hardware failure, profile corruption, or employee turnover, Windows 2000 implements specific procedures for exporting individual user private keys and enforces a mandatory Data Recovery Agent (DRA) policy. This article explains how user encryption keys are exported and how Windows 2000 configures and enforces recovery agent policies.

EFS Architecture and Key Generation

When a user encrypts a file in Windows 2000, EFS generates a pseudo-random, symmetric File Encryption Key (FEK) using the DESX algorithm. The FEK is then encrypted using the user's public key and stored in the file's Data Decryption Field (DDF).

Simultaneously, the FEK is encrypted with the public key of every designated recovery agent and stored in the Data Recovery Field (DRF). This dual-structure ensures that either the original user or an authorized recovery agent can decrypt the file.

Exporting User EFS Keys

Because a user's private key is bound to their profile, losing the profile or reinstalling the operating system renders encrypted data permanently inaccessible unless the key is backed up. Windows 2000 allows users to export their EFS private keys using the Certificates Microsoft Management Console (MMC) snap-in:

  1. Accessing the Certificates Snap-in: The user launches certmgr.msc or opens the MMC, adds the Certificates snap-in targeted at the current user, and navigates to Personal > Certificates.
  2. Export Process: The user right-clicks the certificate designated for Encrypting File System, selects All Tasks > Export, and initiates the Certificate Export Wizard.
  3. Format and Protection: The user must explicitly choose to Export the private key. The wizard exports the certificate and private key together as a Personal Information Exchange format file (.pfx / PKCS #12).
  4. Security Enforcement: The wizard requires password protection for the .pfx file. Once exported, the .pfx file should be stored on external media, and the user can re-import it using the same wizard on another system or after a system restore.

Recovery Agent Policies in Windows 2000

Unlike later versions of Windows where Data Recovery Agents are optional, Windows 2000 operates under a strict, mandatory recovery policy rule: EFS cannot be used unless a valid recovery agent policy exists. If all recovery agents are removed from the policy, EFS is effectively disabled across the scope of that policy.

Default Recovery Agent Configuration

  • Standalone Systems: On a non-domain machine, the local Administrator account is automatically generated as the default DRA during operating system setup, utilizing a self-signed recovery certificate.
  • Domain Environments: On the first domain controller installed in an Active Directory domain, the domain Administrator account is designated as the default DRA for the domain via the Default Domain Policy.

Managing DRA Policies via Group Policy

Administrators configure and enforce DRA policies centrally through Group Policy:

  1. Policy Location: In the Group Policy editor, navigate to: Computer Configuration > Windows Settings > Security Settings > Public Key Policies > Encrypted Data Recovery Agents
  2. Adding Agents: Administrators can right-click the folder and select Add to specify additional recovery agents. This requires importing the public key certificate (.cer) of the designated agent.
  3. Disabling EFS: If an organization wants to prevent EFS usage entirely, an administrator can right-click the policy folder, choose Delete Policy, or leave the folder empty. In Windows 2000, an empty recovery policy produces an error (EFS recovery policy is invalid) whenever users attempt to encrypt files.

Securing the Recovery Agent Key

Because the DRA private key can decrypt any EFS file within its administrative scope, best practices in Windows 2000 dictate that the DRA private key should not remain on production workstations or domain controllers.

Administrators should export the DRA certificate and private key to a .pfx file, store the file securely offline (such as in a physical safe), and delete the private key from the local machine certificate store. The public certificate remains in the Group Policy object to facilitate file encryption, while the private key is only imported temporarily to an isolated, secure machine when recovery operations are required.