Modernize IP Manager configuration encryption to AES-256-GCM

Summary:
Replace the legacy 3DES-based encryption used for IP Manager configuration artifacts (.ipimp, .ipexp, .binx) with AES-256-GCM using a stronger key-derivation scheme (PBKDF2-HMAC-SHA256, 100,000 iterations). Implement a versioned file format (e.g., IPC2 prefix) that allows upgraded installations to transparently read legacy 3DES-encrypted files and automatically re-save them in the new AES-256 format without manual migration.

Problem Statement:
IP Manager currently encrypts configuration file artifacts using 3DES in ECB mode with a single-iteration PBKDF2-SHA1 key derivation. 3DES is now disallowed under NIST SP 800-131A Rev. 2 as of December 31, 2023, and the existing configuration does not meet modern cryptographic best practices. Customers undergoing cybersecurity audits are being blocked from audit sign-off because this legacy encryption scheme is out of compliance with current NIST requirements. At the same time, customers must retain access to existing configuration files without taking on a complex, manual migration process.

Proposed Solution:

• Replace the current 3DES (ECB mode, 1-iteration PBKDF2-SHA1) scheme with AES-256-GCM authenticated encryption for all IP Manager configuration artifacts (.ipimp, .ipexp, .binx).

• Use PBKDF2-HMAC-SHA256 with 100,000 iterations for key derivation to align with modern security recommendations.

• Introduce a versioned magic prefix (e.g., IPC2) in the file format to distinguish AES-256-GCM–encrypted files from legacy 3DES-encrypted files.

• Allow upgraded installations to:

  • Detect and decrypt existing 3DES-encrypted configuration files using the legacy format.

  • Transparently re-encrypt and save those files in the new AES-256-GCM format on the next save operation, with no manual migration steps required from the customer.

• Ensure that files written with the new AES-256-GCM format are not readable by older IP Manager versions, and clearly document this behavior and version-compatibility impact in the release notes.

• Provide internal testing and validation artifacts (e.g., sample encrypted files, automated tests) to verify compatibility and correctness across upgrade paths.

Benefits:

• Restores compliance with NIST SP 800-131A Rev. 2 by moving away from disallowed 3DES encryption to AES-256-GCM.

• Unblocks customers’ cybersecurity audits and approvals that currently fail due to the legacy encryption scheme.

• Improves overall security posture through stronger encryption and key derivation practices.

• Preserves access to existing configuration files, avoiding disruptive or error-prone manual migration steps for customers.

• Provides a clear, well-documented compatibility model between old and new versions, reducing support burden and confusion during upgrades.