We want to inform you that we will be releasing a new Heimdal™ version soon, 2.5.340 RC.
The new Release Candidate version is scheduled to go live on Wednesday, March 10th, in the Dashboard, this being a backend-only release.
Here are the new features and improvements rolling in with the new 2.5.340 RC:
- Data visibility based on customer approval
A new check box functionality in now available in the “Guide” section of the dashboard, tab “Customer Settings”, which permits the dashboard user to choose if they allow Heimdal to view their dashboard data or not (please bear in mind that if the check box is disabled, Heimdal Support team’s ability to assist will be reduced significantly).
- SAML 2.0 Dashboard Login
This feature will allow dashboard users to log in to the Heimdal dashboard with only a click of a button – using their corporate credentials (email & password).
For this functionality, a new option (check box) was added to the “Guide” section of the dashboard, “Customer settings” tab, named: “Log in to the Heimdal Dashboard using SAML2.0”. If this option is checked (enabled), then user can proceed to the configuration of the SAML 2.0 login.
After the configuration is done, one can log in to the Heimdal dashboard by using the “Azure Login” button, available on the Dashboard login/ home page.
If there is no dashboard account matching the Azure account, a new account will be created (granting only “Visitor” role), only if there is a CORP matching your Azure account tenant ID. Otherwise, the user will be redirected to an error page. The newly created account can be accessed only with Azure login.
Vulnerability Management, Patch & Asset Management, Microsoft Updates:
- “Compliance View”, Microsoft Updates, will not apply to inactive machines
We have improved our query related to the Non-Compliant endpoints, shown in the COMPLIANCE VIEW tab, from the Microsoft Updates sub module of the Patch & Asset Management module, in order to display only the non – compliant machines that have been active during the last 6 months (from the selected date).
Privileged Access Management:
Deny elevation of System files
This new functionality consists of the addition, in the Privileged Access Management Setting/ Group policy area, of a check box, named “Deny elevation of system files” which, if enabled, won’t allow the user requesting the elevation of a system file (“Run with AdminPrivilege”) to obtain higher rights nor they will be able to elevate a system file in case they are already (elevated) in an administrator session.
In case the user will try to execute, with administrator privileges a system file, a popup will appear to inform that the execution is not allowed and the process won’t be started.