Added DDNS client for manual configuration

Added ability to set system time when NTP is disabled and improved time synchronization during adoption

Added additional security protections for Virtual Key requiring rekey of older deployed clients

Updated Angular framework to version 19.2 and fixed UI issues for: Remote burn, Footer, Onboarding pages

Fixed audit log issues for destination pools

Added cloud integration work related to AWS AMI image and WIC configuration

Added preliminary containerization support

Enhanced Virtual Key logging, auditing, and revocation capabilities

Enhanced audit and logging when deleting clients or devices

Fixed Virtual Key issues when LGX pools are in use

Fixed onboarding issue caused by invalid network data that forced factory reset

New filesystem layout making use of LVM to adapt better to storage changes in the future. Upgrade from prior release is not supported - new installs are required.

Add ability to supply a file to auto-configure the initial setup of the LGX, removing the need to interact with the Onboarding screens on initial setup

Add ability to use Cognito accounts for user authentication

Adjust startup ordering to interact better with cloud-init

Enable VRF kernel support to isolate completely Enclave networks and interfaces from external and management networks and interfaces

Add initial ability to define routing and a DHCP server on the Enclave networks

Update MongoDB to v8.0.x

Add BRN Licensing code to ensure license compliance

Add services to enable specific Cloud Provider integrations

AWS: Add integration to ensure all traffic presented to the enclave interface is delivered (disable source/dest check)

AWS: Add integration to publish and adjust routing table entries for networks available across the CyberCloak enclave

AWS: Enable access to the Management UI on the primary network interface. In AWS deployments, this interface is protected by the load balancer and is not directly available to the Internet. Access to this UI is required by the Load Balancer to detect availability.

AWS: Add CloudFormation template to deploy LGX into AWS with associated AWS services installed and configured. Launch LGX instance with configuration file detailing those AWS interfaces.