Versasec adds identity authentication server to vSEC:CMS 7.4

Versasec launched vSEC:CMS Identity with vSEC:CMS 7.4 on June 26, 2026, adding a multi-factor authentication server for vSEC:CMS and vSEC:CLOUD. The update is designed to speed passkey adoption, reduce password reliance and give enterprises more control over authentication infrastructure.

Why it matters: - vSEC:CMS Identity is aimed at replacing vulnerable passwords with passwordless authentication for enterprise users. - The release is designed to help organizations close exposed security gaps while keeping control of credential infrastructure on-premises, in air-gapped environments or in private clouds. - The update also supports data sovereignty by avoiding dependence on external cloud identity providers.

What happened: - Versasec announced vSEC:CMS Identity with the release of vSEC:CMS 7.4 on June 26, 2026. - The new server is an advanced, multi-factor authentication server for vSEC:CMS and vSEC:CLOUD. - The product is included for customers using vSEC:CMS Premium and vSEC:CLOUD. - Versasec directed readers to more information.

The details: - vSEC:CMS Identity can be deployed on-premises, in an air-gapped setup or in a private cloud. - The platform integrates directly into existing vSEC:CMS deployments. - Administrators can issue a device-bound FIDO2 passkey during the initial credential issuance process for immediate user authentication. - Organizations can use a primary Active Directory account as the identity foundation for issuing both PKI certificates and FIDO2 passkeys. - The system connects directly to Azure Entra ID. - Versasec says this setup removes duplicate accounts and insecure workarounds. - Administrators can configure short-lived temporary passwords for domain accounts when a hardware token is misplaced and replacement is not possible. - The temporary password process is controlled and auditable. - The update adds full lifecycle management for the Yubico Security Key Enterprise Edition through YubiKey as a Service.

Between the lines: - The launch positions Versasec to sell passwordless authentication as an incremental upgrade to existing credential management deployments, not a separate identity platform. - The emphasis on hybrid directory orchestration suggests enterprises want passkeys without abandoning existing Active Directory and Azure Entra ID setups. - The temporary-password feature signals that the product is also trying to solve operational edge cases, not just security policy.

What's next: - Enterprises using vSEC:CMS Premium or vSEC:CLOUD can begin evaluating vSEC:CMS Identity as part of the 7.4 release. - Broader adoption will likely depend on how quickly organizations move passkey issuance into production across mixed directory environments. - Versasec is likely to build on the 7.4 release as passkey and passwordless authentication demand grows.