---
title: "Segura® Platform v4.2.4"
slug: "release-notes-v4-2-4"
updated: 2026-07-10T12:16:41Z
published: 2026-07-10T12:16:41Z
canonical: "docs.senhasegura.io/release-notes-v4-2-4"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Segura® Platform v4.2.4

## In this article

- [About this release](/docs/release-notes-v4-2-4#about-this-release)
- [Changelog](/docs/release-notes-v4-2-4#changelog)

---

## About this release

On April 29, 2026, we released version 4.2.4 of Segura® Platform. The release includes 13 changes across 7 modules.

- **Release date**: 2026-04-29

For information on how to update Segura® Platform, see [Update Segura®](/v4-2/docs/installation-update-senhasegura).

---

## Changelog

### Certificate Manager

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-9944** | Fixed two issues that caused the private key to not be returned properly when using the `download_key` parameter. |
| **SSGR-9986** | Fixed an error when importing certificates into the **Certificate Manager** that were found through discovery of enterprise applications in Azure. Now, all discovered certificates are imported correctly. |

---

### EPM Admin Web Interface

#### Changed

| Item | Description |
| --- | --- |
| **SSGR-9320** | Added privilege profiles to **EPM Windows**. Privilege profiles allow simplifying permission management, eliminating duplication, and applying configurations consistently across large environments. **Note**: This feature will only be fully operational starting from version `v4.2.6`. **See the documentation**: - [About privilege profiles](/v4-2/docs/general-epm-about-privilege-profiles). - [How to create a privilege profile on EPM Windows](/v4-2/docs/epm-windows-create-privilege-profile-epm-windows). - [Privilege profile](/v4-2/docs/epm-windows-privilege-profile). |

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-10128** | Fixed an issue where the **Status** field displayed `Yes` and `No` instead of the standardized `Enabled` and `Disabled` values across Policy screens. All reports in the module now follow a consistent status display format. |

---

### EPM Windows

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-10478** | Fixed issue where the Visual Studio Code application wasn't being executed through **EPM Windows** regardless of access policies or elevation, even when invoked directly via tokenization. |

---

### Executions

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-10015** | Fixed a regression where the **Authentication Credential** field was incorrectly marked as required when configuring a credential profile with **Use own password to connect** disabled. Filling in the **Credential Username** field alone now correctly satisfies the authentication configuration requirement, restoring the behavior documented and present in previous releases. |

---

### Framework

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-9941** | Fixed an issue that displayed an incorrect language in **PAM Core** notifications. |

---

### PAM Core

#### Changed

| Item | Description |
| --- | --- |
| **SSGR-8571** | Added support for DUO Push MFA authentication in **Terminal Proxy** and **RDP Proxy** sessions on the **Segura® Platform**. With this enhancement, users with DUO configured can approve authentication through the mobile application to complete access, while maintaining compatibility with the current proxy flow and with methods already used in the environment. **See the documentation**: - [How to access RDP Proxy with Duo Push authentication](/v4-2/docs/pam-sessionmanagement-how-to-access-rdp-proxy-with-duo-push-authentication) - [How to access Terminal Proxy with Duo Push authentication](/v4-2/docs/pam-sessionmanagement-how-to-access-terminal-proxy-with-duo-push-authentication) |

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-10043** | Fixed an issue where cloned credentials did not inherit the access policy association from the original credential. |
| **SSGR-10312** | Fixed an issue where the password policy was not loaded in the interface during credential creation. |
| **SSGR-8405** | Fixed an issue that triggered incorrect email alerts about failed credential backups. Backup files were successfully copied to the remote server, but the system failed to set file permissions at the destination folder. |
| **SSGR-9903** | Fixed an issue where the manual password generation for a credential did not follow the custom policy linked to it, applying the default system policy instead. |

---

### Proxy

#### Fixed

| Item | Description |
| --- | --- |
| **SSGR-10220** | Fixed an issue in **RDP Proxy** where the authentication credential configured in the session settings was always used when a RemoteApp was configured, even when RemoteApp access was not selected. |

---