AgileSec 3.5 and 3.5.1 released

We are pleased to announce the general availability of AgileSec 3.5.0 (March 31, 2026) and AgileSec 3.5.1 (April 15, 2026).

What's new in AgileSec 3.5

AgileSec 3.5 is a significant platform release introducing a new data model, a dedicated web UI, and expanded enterprise deployment capabilities.

Platform and architecture:

• New web-based UI replacing manual configuration file management with guided dashboards and workflows

• Scalable event-driven architecture supporting high-volume cryptographic discovery across large enterprise environments

• Kubernetes deployment support alongside the existing VM-based model

• Multitenancy support with isolated datasets, users, and policies per tenant

• FedRAMP certification achieved

Integrations:

• ServiceNow Vulnerability Response connector for automated cryptographic finding workflows

• CrowdStrike-orchestrated host scanning with centralized sensor deployment via Falcon

• Qualys integration for network cryptographic finding ingestion via API

• AWS KMS and Thales CTM sensors for managed key store visibility

Upgrade path:

• In-place upgrade supported from existing AgileSec 3.x environments

• No reinstall or cluster rebuild required

• Existing sensors continue operating after upgrade

• New 3.5 sensor data is visible immediately after upgrade

What's new in AgileSec 3.5.1

AgileSec 3.5.1 is a focused follow-on release with one primary addition: automated data migration from pre-3.5 versions.

• Automated legacy data migration tooling replaces the manual CLI script approach from 3.5.0

• Backward compatibility for migrated data is finalized

• No new platform or sensor features beyond migration automation

There is no need to repeat any manual migration steps already completed under 3.5.0. Customers upgrading directly from 3.x to 3.5.1 can use the automated migration path without the manual steps.

Understanding the data migration

This is the most common source of questions on this release and worth addressing clearly.

When upgrading from 3.x to 3.5.0, your existing data is not deleted. It remains stored in the backend. However, legacy data is not visible in the UI until a migration is run. New 3.5 sensor data appears immediately after upgrade.

In 3.5.0, migration was performed using manual CLI scripts with Keyfactor engineering assistance. In 3.5.1, this is fully automated. The recommended upgrade path for customers who have not yet migrated is to upgrade directly to 3.5.1 and use the automated tooling.

Customers with API-based integrations consuming AgileSec data programmatically should review the Data Migration Guide before upgrading, as the new data model affects API response structure.

Recommended upgrade path

For customers on AgileSec 3.x:

1. Upgrade to AgileSec 3.5.1 directly

2. New 3.5 sensor data is immediately visible

3. Run automated migration to surface legacy data

4. No data is lost at any point in this process

For customers on AgileSec 2.x or earlier, please contact your Keyfactor account team before upgrading as additional steps apply.

Documentation

Full documentation for AgileSec 3.5 and 3.5.1 is available at: https://docs.keyfactor.com/agilesec/latest 

Including:

• AgileSec 3.5.1 Release Notes

• On-Premises Multi-Node Installation Guide

• AgileSec 3.5 In-Place Upgrade and Data Migration Guide

• Sensor Deployment Documentation

Support

If you have questions about this release or need assistance with your upgrade, open a ticket at Keyfactor Support or contact your Keyfactor account team.