New features summary

• Device Ownership rule: A new customizable conditional rule based on the user's device ownership is available now. You can set the rule by selecting the Device Ownership tile under Choose Customizable Rule. You can also include the rule in the conditional policies as per the requirement. For more information, see Device Ownership Rule.

• Support to display blocked action status in Ivanti Neurons for MDM: When a device goes out of compliance, Access blocks the data path. This blocked status of the device can be viewed on Ivanti Neurons for MDM under Devices > Overview. For more information, see Customizable conditional rules

• Day Zero compatibility with Android 13: Ivanti Access is compatible with Android 13.

• Support for rebranding the following list:

  • Splunk application: Splunk application is now rebranded to Ivanti.

  • Tenant provisioning: Rebranding is done in the email sent to the user when new tenants are created.

  • Usage Reports: Access tenant user report and Access IdP-SP usage report are now rebranded to Ivanti.

• Support for rebranding MobileIron Authenticate to Ivanti Zero Sign-on Authenticate: MobileIron Authenticate is now rebranded to Ivanti Zero Sign-on Authenticate.

• Support for rebranding links and privacy policies: The links and privacy polices for MobileIron are now rebranded to Ivanti.

• Support for rebranding logo and images: The logos and images for MobileIron are now rebranded to Ivanti.

• Support for rebranding name and copyright: The name and copyright for MobileIron are now rebranded to Ivanti.

• Support to authenticate cloud applications based on mapped User Name of security key on Android devices: Users are now able to log into cloud applications without entering the User Name manually. The User Name is now mapped with the User Name of the security key.

• Day Zero compatibility with Windows 11: Ivanti Access is compatible with Windows 11.

• Support to enhance the Zero Sign-on user portal: The Zero Sign-on user portal is now user-friendly when accessed from any iOS or Android devices.

• Support for iOS and Android native browsers for FIDO2 authentication: iOS and Android native browsers such as Safari and Chrome can now be used for hardware key log in.

• Support for biometric authentication and registration for iOS and Android devices: The iOS and Android devices can now use Biometrics for authentication and registration for all browsers and operation systems.

• Support to provide user credentials on selecting security key or biometrics: On iOS and Android devices, an option to provide user credentials is provided on selecting security key or biometrics for registration.

• Support for mobile devices as FIDO authenticator: The mobile devices are now supported for FIDO authentication. For more information, see Registering the biometric for Zero Sign-on authentication.

• Support for ZSO reports for FIDO mobile biometric: The ZSO reports are now updated as mobile devices are now supported as FIDO authenticators. For more information, see Reports.

• Support for Windows conditional Access rule for all versions: Windows conditional Access rule is updated to support all Windows platforms including Windows 11. For more information, see Predefined conditional rules.

• Support for conditional Access rule for MAC: Conditional Access rule is now available for MAC. For more information, see Predefined conditional rules.

• Update to conditional Access rules description: The description for all Conditional Access rules are now updated. For more information, see Predefined conditional rules.

• Support for Windows Hello or Mac Touch ID administration configuration: Support to register the biometric using Windows Hello or Mac touch ID that lets you securely sign-in to the work websites on unmanaged desktops using biometric. For more information, see Registering the biometric for Zero Sign-on authentication.

• Support for multi-user scenario for iOS: Session Revocation is now triggered for multi-user sign-in applications. On a shared device, even if a user is signed-out, Session Revocation is still triggered. For more information, see Session Revocation.

• Support to configure portal for FIDO security: A configure portal section is added for managed and unmanaged device configuration that displays information if the portal is configured. For more information, see Passwordless authentication to service providers on unmanaged devices.

• Zero Sign-on rule modification: The FIDO authenticator is provided in the zero sign-on rule to use FIDO hardware key or Windows Hello or Mac Touch ID.

• Zero sign-on authentication default option: On macOS later than v11, browser gives preference to Mac Touch ID even when security key is plugged to the laptop during authentication. However, earlier than macOS v11, the default option for authentication is security key and does not allow to select Mac Touch ID. For more information, see Logging into user portal.

• Support for new biometric auth methods in the filter: The Windows Hello and Mac Touch ID are now available in the filter for auth method in Zero Sign-on report. For more information, see Zero Sign-on Reports.

• Support for Windows Hello and Mac Touch ID administration configuration: Support to register the biometric using Windows Hello or Mac Touch ID that lets you securely sign-in to your work websites on registered devices using biometric. For more information, see Logging into user portal.

This release includes the following new feature and enhancement.

• Bluetooth support for FIDO users: FIDO users can now unlock their desktop on Android and iOS clients using bluetooth technology in offline mode.

• Support for MobileIron Authenticate on M1 chip macOS: MobileIron Authenticate is now qualified on M1 chip macOS.

• Android 12 day zero support: Access Samsung Android 12 day zero is now supported with this release.

• Support to add email ID format for User Portal: User Portal federation SAML subject should contain a value of email id format. For example: When using Microsoft ADFS as an IDP, the SAML subject LDAP attribute must either be UPN or an email ID.
  If email ID format is missing for SAML subject, it causes user portal authentication failure.
  

• Support for Pagination in the Users search option: Pagination is now available for the users search option in Profile > Users.

• Support in Ivanti Access using FIDO hardware keys for unmanaged desktops: For unmanaged desktops, users can now use their FIDO enabled hardware keys to access the service provider with zero sign-on. For more information, see Zero sign-on support in Ivanti Access using FIDO hardware keys for unmanaged desktops.

• Device posture information added for Ivanti Access: Device posture information on Compliant and Non-compliant modes are included for Ivanti Access.