New Features

This section describes the new features in this release.

Automation

  • Dynamic ServiceNow Change Request Integration

    Policy Engine now supports dynamic ServiceNow request forms based on the ServiceNow integration configuration. The new Create Dynamic ServiceNow Request and Update and Close ServiceNow Change Request tasks allow workflows to create and manage ServiceNow tickets based on the configured change requirements.
    • Configure ServiceNow fields directly in the visual workflow by specifying the field ID, display label, field type, values, and mandatory status.
    • Support text area, select box, and date picker field types.
    • Apply field-level fallback actions when a mapped value is unavailable, including using a fixed value, omitting the field, or using the current time with a configured offset.
    • Configure the workflow to wait for a ServiceNow ticket to reach a specified state before continuing certificate operations.
    • Check pending tickets every five minutes in batches of up to 20 through the ServiceNow batch API.
    • Configure API URLs to support ServiceNow tables beyond change requests.
    • Update and close the ServiceNow ticket after the workflow completes.
    • Close tickets for failed workflow executions to prevent unresolved change requests from remaining open.

    Result: Enables organizations to adapt ServiceNow change requests to their existing processes, automate change-state approvals, and keep certificate operations synchronized with ServiceNow workflows.

  • Integrity Hash Fingerprinting

    Added deterministic SHA-256 hash generation for workflow versions during creation and import, enabling cross-environment workflow validation and version tracking via the UI and REST APIs.

  • Enhanced Workflow Import with Dependency Support

    Visual Workflow now supports importing workflows along with their associated dependencies, including hooks, helper scripts, and master variables. When uploading a workflow package, users can review all associated components, view real-time validation messages, and receive a comprehensive status report of imported entities upon completion. All import actions are captured in audit logs for end-to-end traceability.

ADC

  • HA Proxy 3.x Version Compatibility Support

    Adds support for HAProxy community v3 across onboarding, discovery, monitoring, and configuration management, enabling continued management of newer HAProxy environments.

  • F5 BIG-IP V21 Version Compatibility

    Adds support for F5 BIG-IP v21, including parsing and normalization of newly introduced MCP profiles and related entities. Ensures compatibility across discovery, configuration management, monitoring, automation, and lifecycle workflows.

  • F5 Distributed Cloud (XC) – Self Servicing Actions for Distributed App & DNS Management

    Enables self-service management of F5 XC Distributed App and DNS services across SaaS and on-premises deployments. Provides improved visibility, topology awareness, and operational control for distributed application and DNS management.

  • MCP Framework Enablement for ADC Operations & Reporting

    Introduces MCP-based tools for accessing ADC device/application inventory and operational insights, enabling AI agents and external consumers to securely retrieve ADC information and supporting device/application reporting.

    For more information, see AppViewX ADC MCP Server topic.

  • Nginx R36/37 Version Compatibility

    Adds support for newer NGINX versions R36,37 across onboarding, discovery, monitoring, configuration management, and automation workflows, enabling customers to manage updated NGINX environments without disrupting existing operations.

  • AVI v32 Version Compatibility

    Adds support for AVI v32 across onboarding, discovery, monitoring, configuration management, and enabling seamless management of newer AVI environments.

CLM

  • Private Key Encryption for Linux and Enhanced Password Vault
    Private keys can now be encrypted when certificates are pushed to generic Linux devices, helping teams protect sensitive credentials throughout the certificate deployment process. This release also expands Password Vault capabilities with broader credential management, configurable encryption options, and added safety checks.
    • Discover encrypted private keys through Hashicorp credentials stored in the Password Vault for centralized credential management.
    • Associate device onboarding groups and integrate HashiCorp Vault PAM credentials within the Password Vault inventory for streamlined secret management.
    • When pushing PKCS#12, and PFX certificates to Linux servers, choose the encryption standard (AES or 3DES) and fetch keystore passwords directly from the Password Vault or enter them manually.
    • Push PEM private keys in encrypted formats to Linux servers, sourcing encryption passphrases from HashiCorp Vault, AppViewX Password Vault, or manual entry to comply with strict enterprise cryptographic policies.
    • The Password Vault now prevents accidental deletion of credentials actively referenced by Push App Connectors and displays actionable impact warnings prior to credential updates.
  • Enabling ACME ARI support that features certificate renewals to be scheduled dynamically based on server-provided renewal windows rather than fixed intervals. For organizations managing large certificate estates, this distributes renewal activity more evenly over time, reducing the risk of renewal spikes that can strain infrastructure or cause service disruptions.
  • The Linux EST agent now supports downloading PKCS#12 bundles with optional legacy encryption (3DES) and full certificate chain inclusion. This improves compatibility with older applications and simplifies scripted or automated renewal workflows in Linux environments.
  • Discover and manage AWS S3 certificates
    AppViewX now integrates with Amazon S3 to help discover, track, and renew certificate files stored across their AWS environments.
    • Amazon S3 onboarding: Add S3 as part of your existing device onboarding workflow.
    • Certificate discovery: Automatically find certificate files in S3 buckets and bring them into a certificate inventory for lifecycle management.
    • Certificate provisioning: Push renewed certificates back to the appropriate S3 buckets.
  • Certificate group management is now available through documented APIs for headless automation.
    • Create one or more certificate groups and receive the created group identifiers and status in the response.
    • Delete certificate groups with explicit deletion status for each requested group.
    • Use consistent validation and structured error responses for malformed, duplicate, protected, or otherwise invalid group requests.
  • Access to the default onboarding device group can now be managed through access control lists (ACL). Administrators can assign read or read/write permissions, and the group now follows the same access-control behavior as custom onboarding device groups.
  • Query Certificate Inventory via MCP

    AppViewX now supports querying the certificate inventory through the Model Context Protocol (MCP) integration. Users can search and retrieve certificate records at scale directly through MCP-connected tools, enabling AI-assisted workflows and external integrations to access real-time certificate data without requiring manual UI interaction.

  • Renew a Certificate via MCP

    AppViewX now supports certificate renewal through the Model Context Protocol (MCP) integration. Users can initiate renewal for queried certificates directly through MCP-connected tools. Renewal requests are processed asynchronously and return a workflow or operation reference that can be used to monitor progress.

  • Regenerate a Certificate via MCP

    AppViewX now supports certificate regeneration through the Model Context Protocol (MCP) integration. Users can initiate regeneration for queried certificates directly through MCP-connected tools. Regeneration requests are processed asynchronously and return a workflow or operation reference that can be used to monitor progress.

  • Revoke a Certificate via MCP

    AppViewX now supports certificate revocation through the Model Context Protocol (MCP) integration. Users can revoke eligible certificates directly through MCP-connected tools using workflow-based revocation, enabling automated certificate lifecycle operations from external integrations.

Code Signing

  • Usage limits can now be defined for file and hash-based signing operations. Administrators gain real-time visibility into allocated, consumed, and remaining signing capacity, helping with capacity planning, cost control, and policy enforcement.
  • Code Signing Installation can now be dynamically configured within Azure DevOps and GitHub Actions pipelines, with SIGN+ automatically installed on CI/CD runner machines without any manual setup. This reduces the time and effort required to configure consistent signing environments across development teams, ensuring uniform setup across all pipeline runs while supporting faster, more reliable CI/CD workflows.
  • Code signing workflows now support HSM-backed post-quantum algorithms, enabling organizations to future-proof their software signing practices with secure, auditable, end-to-end signing that meets emerging quantum-safe requirements. This is only supported with ML-DSA algorithms using Fortanix HSM for File Based signing currently.

Platform - Cloud Connector

  • Cloud Connector upgrade with new cgroup v2 prerequisite

    As part of our ongoing commitment to security, stability, and performance, we are upgrading the underlying Kubernetes components in an upcoming Cloud Connector release. To support this upgrade, host operating systems must have cgroup v2 enabled. Newer Kubernetes versions need this Linux resource management framework, so it's required before you can upgrade the Cloud Connector from this version onward.

    Before the upgrade starts, the host system is checked. If a mandatory prerequisite isn't met, a Pre-requisite Check Failure dialog appears and the upgrade won't be initiated until prerequisite is met.

    Newly added prerequisite:
    • cgroup v2 enabled (mandatory): cgroup v2 must be enabled on the host operating system. If it isn't, the upgrade won't be initiated.
    Existing validations (no change):
    • Valid Kubernetes cluster certificates (mandatory): The cluster certificates must not be expired. If they are, the upgrade won't be initiated
    • Free memory and disk space (warning): You'll see a warning if resources are low, but the upgrade can still proceed.
  • Automated Creating Helm-Based Cloud Connectors

    Helm-based Cloud Connector deployments can now register automatically with the specified AppViewX datacenter. Provide the datacenter name along with the existing master key during installation to complete registration as part of the deployment process.

    Result: This reduces the manual configuration required after deployment and helps teams onboard Cloud Connectors more consistently across environments.

    Key capabilities:
    • Specify a datacenter name during Helm-based installation
    • Automatically register the Cloud Connector with a validated datacenter
    • Continue using existing master key deployment configuration.
  • Persistent HSM libraries for Helm-based Cloud Connectors

    Cloud Connector deployments using Helm can now persist HSM shared object (.so) library files through pod restarts, redeployments, and Helm upgrades.

    Configure a Persistent Volume Claim (PVC) for HSM library storage, and the Cloud Connector mounts it at startup. This keeps required HSM libraries available after a pod is recreated, reducing manual recovery work and preventing HSM integration interruptions.

  • Non-Interactive Cloud Connector Installation

    Cloud Connectors can now be installed and registered through a non-interactive installer. Provide the required connection and authentication details as command-line arguments to automate deployment without manual prompts or UI-based connector setup.

    Result: This reduces the effort and inconsistency associated with manual installations, helping teams deploy Cloud Connectors more easily through their existing automation workflows.

    Key capabilities:
    • Run Cloud Connector installation without interactive prompts
    • Supply Master Key, Datacenter, Tenant ID and other arguments
    • Validate the provided datacenter before installation and registration
    • Automatically download the required installation files.

Platform - Integration Hub

  • Native Imprivata PAM Integration

    AppViewX integrates natively with Imprivata PAM, allowing teams to securely retrieve and use privileged credentials across onboarding, discovery, monitoring, and operational workflows.

    Customers can use Imprivata as the system of record for privileged access while managing their infrastructure in AppViewX without storing privileged credentials directly in the platform.

    The integration simplifies the adoption of Imprivata-managed privileged access, reduces manual credential handling, improves security by eliminating the need to store privileged credentials directly in AppViewX, and enables scalable use of PAM-backed credentials across onboarding and day-to-day infrastructure operations.

  • Onboarding Group-Based Access Control

    Platform enables administrators to assign devices to groups during onboarding and manage access permissions at the group level.
    • Assign devices to groups during onboarding.
    • Grant read or read/write permissions to onboarding groups.
    • Automatically apply group permissions to all devices in the group.
    • Override group-level permissions for individual devices when required.

    Simplifies access management, improves scalability, and provides consistent visibility and control across devices.

  • Service Account Credential Management

    The Service Account creation API now returns both the Client ID and Client Secret. A new API also enables administrators to regenerate the Client Secret before it expires. These APIs support automated service account provisioning and credential lifecycle management across integrations and workflows.

  • Post-Quantum Cryptography Support Across HSMs

    Platform enables post-quantum cryptography (PQC) support across supported HSMs for key generation, certificate signing request (CSR) creation, code signing, and key protection workflows.

    • Support PQC algorithms across supported HSMs, including Fortanix ML-DSA and Utimaco ML-KEM and ML-DSA.
    • Generate PQC keys.
    • Generate PQC certificate signing requests (CSRs).
    • Support PQC-based code signing.
    • Support PQC master-key encryption and key wrapping.

    Prerequisites: For Utimaco HSMs, enable the Quantum Protect add-on. Configure the latest shared-object (.so) file for Utimaco and Fortanix in AppViewX.

    Improves quantum readiness and provides a unified foundation for PQC-enabled security workflows across downstream products.

  • Delinea Platform PAM Integration

    Platform now integrates natively with Delinea Platform PAM, allowing administrators to securely retrieve and use privileged credentials across onboarding, discovery, monitoring, backup, automation, and operational workflows. The integration extends AppViewX support beyond Delinea Secret Server and enables customers using Delinea Platform PAM to manage privileged credentials without fragmented credential handling.
    • Support Active Directory and domain-based authentication for Delinea credential retrieval.
    • Support domain-qualified usernames, including domain\username and username@domain.com.
    • Maintain compatibility with existing Delinea Secret Server integrations.
  • Future-Dated License Activation

    Platform now supports future-dated license uploads without interrupting the active license. When an uploaded license has a future start date, Platform queues the license and keeps the current license active until the new license becomes effective.
    • Queue future-dated licenses instead of activating them immediately.
    • Display the queued license status and allow tenant administrators to preview its details.
    • Automatically activate the queued license when the earliest product start date is reached.
    • Allow only one queued license file per tenant.
    • Prevent administrators from manually activating a queued license.
    • Notify tenant administrators before the queued license activates and after activation.
  • AI Assistant Integration with AVX Platform

    Teams can now work with the AVX Platform directly from their preferred AI assistant. MCP-compatible assistants and agents, including Claude Desktop, ChatGPT, GitHub Copilot, and Cursor, can query certificate inventory, view certificate details, start renewal, regeneration, or revocation requests, check workflow request status, and retrieve ADC device and object information directly from the conversation.

    An administrator registers the connector once, and each user can connect in under a minute by entering their tenant, signing in with their own login, including single sign-on (SSO), and approving the requested tool scopes. Nothing needs to be installed on the user's machine. Everyday questions about certificate inventory, expiry, ownership, and devices no longer require users to open the AVX Platform console.

    The integration maintains the same access controls and security policies as the AVX Platform. Each session runs as the authenticated platform user and requires dedicated MCP permissions on the user's role. The platform validates every tool call against the user's role and tenant and exposes only the tools that the user is licensed and authorized to use. Write operations follow the same approval controls as the UI, and the platform records every session and tool call in the audit log.

PKI

  • Certificate Revocation Lists (CRLs) can now be published over HTTP on port 80. This improves compatibility with relying parties and network environments that require standard HTTP endpoints, removing a common integration barrier.
  • Administrators can now define reusable configuration policies for Certificate Authorities, making it faster to deploy standardized PKI environments across the organization. This reduces manual effort, improves consistency, and makes it easier to demonstrate compliance with internal and regulatory requirements.

    For more information, see Managing Certificate Authority Policy topic.

  • PQC algorithm names are now consistent across AppViewX PKI and CLM as ML-DSA (Dilithium), SLH-DSA(SPHINCS+), and FN-DSA (FALCON). This eliminates confusion during implementation and migration projects, reducing errors and the time needed for onboarding and troubleshooting.
  • AppViewX CLM can now connect to and manage multiple external PKI Certificate Authority instances from a single deployment. Organizations operating across different environments, regions, or trust boundaries gain centralized visibility and control without needing separate management tools.
  • Certificate Authorities can now be created and certificates issued using post-quantum cryptographic (PQC) algorithms, backed by Hardware Security Modules. This enables organizations to begin a controlled, secure transition toward quantum-safe PKI — including hybrid approaches that maintain compatibility with existing infrastructure. This is only enabled for ML-DSA algorithm with Fortanix HSM currently.

QTH

BOM Upload, Inventory & Crypto Asset Discovery
  • Added support for uploading third-party Cryptography Bill of Materials (CBOM) files and Software Bill of Materials (SBOM) files.
  • Supports import of CycloneDX files generated by third-party tools.
  • Automatically parses uploaded CycloneDX files and extracts available cryptographic metadata, including cryptographic algorithms, key sizes, cryptographic libraries, certificates, keys(when available), hash algorithms, digital signature algorithms.
  • Introduced a dedicated BOM Inventory to view cryptographic assets extracted from uploaded BOM files.
  • Added Post-Quantum Cryptography (PQC) readiness assessment for cryptographic assets imported through CycloneDX BOM uploads, with assessment results displayed in the BOM Inventory.

Benefits:Accelerates PQC readiness assessments and centralizes crypto asset visibility by seamlessly leveraging third-party CycloneDX BOM files in the BOM Inventory.

For more information, see BOM Upload and Crypto Asset Inventory topic.

Agentless PQC Crypto Discovery via VM Integrations (Qualys)

  • The platform now integrates with Qualys VM to enable agentless discovery of cryptographic assets by leveraging existing vulnerability scan data without additional deployment overhead.
  • It automatically identifies and catalogs key cryptographic components across scanned systems, including cryptographic libraries, SSL/TLS protocols, cipher suites, and digital certificates.
  • Discovered assets are consolidated into a centralized inventory to provide immediate, comprehensive visibility into cryptographic usage across your environment.
  • This visibility empowers security teams to evaluate Post-Quantum Cryptography (PQC) readiness, identify potential risk areas, and prioritize quantum-safe migration efforts more effectively.

    For more information, see Qualys Integration topic.

ITSM Integration & Controlled Remediation
  • The PQC inventory now integrates with ITSM to establish a unified, auditable mechanism for tracking and executing cryptographic risk remediations.
  • Ticket awareness is embedded directly into the inventory with Ticket ID, Ticket Status, and Action fields, enabling seamless ticket creation with intelligent grouping (e.g., per asset or service) to prevent duplicate tickets.
  • The solution supports both manual ITSM workflows and controlled automated certificate remediation, enabling end-to-end governance across security, application owners, and infrastructure teams.
  • ITSM serves as the single source of truth for remediation status and lifecycle tracking, while the PQC inventory functions as the central visibility and control layer.

For more information, see ITSM Integration & Controlled Remediation topic.

SSH

  • SSH Certificate Rotate/Renew with Key Rotation

    • Rotate from Key Inventory rotates the key and its associated SSH certificate together. It generates a new key pair, issues a new certificate based on the current policy, deploys and verifies both on every endpoint, and then retires the old key and certificate.
    • Renew from Certificate Inventory reissues the certificate against the existing key when the certificate is nearing expiry. It does not change the key.
    • Delete from Key Inventory removes the key and its associated certificates together. The system pre-selects the certificates and displays an explicit warning if you deselect any certificate. You can choose to remove the key and certificates from the inventory only or from the endpoints as well.
    • Delete from Certificate Inventory removes only the certificate and retains the associated key.
    • The system tracks failed endpoints and provides retry options from the Recently Deleted views.

    Result: Certificates are rotated, renewed and removed from the inventory they belong to, with per-endpoint verification and audit, and no certificate can be issued beyond the life of its signing CA.

  • Migrate to Certificate in Key Inventory

    • Migrate to Certificate in Key Inventory moves existing keys to CA-signed certificates. The system first checks each key for eligibility:

      • It migrates clean keys directly.
      • It rotates weak keys before migrating them.
      • It holds keys with other identified risks, keys that are not present on any endpoint, and keys for which only the public key is known until you remediate them.

      The system issues the certificate against the public key already in use and signs it using the CA mapped to the governing Key Policy. The user's private key remains unchanged, and the system does not install anything on the client.

      The system carries the restrictions defined in authorized_keys into the certificate. If the system cannot map a critical option, it blocks the migration instead of weakening access controls.

    • Coexistence Period and Decommission

      After deploying and verifying the certificate on a host, the system keeps the original key entry and the certificate active together for the Coexistence Duration defined in the Key Policy. The system snapshots this duration when the migration starts.

      After the coexistence window ends, the Post-Window Action determines how the system handles the original key entry:

      • Manual Confirmation: Keeps the key entry active until an administrator approves its removal.
      • Auto-Deactivate: Automatically removes the key entry.

      The system decommissions each key separately on each host. Before removing the authorized_keys entry, it stores the line exactly as it appeared. If certificate access fails on a host, Rollback Decommission restores the original entry. The Migration Activity tile tracks migration progress using the following statuses:

      • Done
      • In Progress
      • Awaiting
      • Partial
      • Failed

    Result: You can move SSH access from static, non-expiring keys to short-lived, centrally governed certificates on a host-by-host basis without interrupting active sessions. The process also provides a rollback option at each stage if certificate-based access fails.