What’s New in UserLock 12

New: Enable MFA and access management for all RemoteApp applications

UserLock is now compatible with all RemoteApp applications (before this, only RemoteApp applications with a desktop were supported). You can protect RemoteApp sessions with all of UserLock’s access management capabilities and MFA using all available MFA methods: push notifications, OTP codes, and USB keys.

MFA for RemoteApp allows you to reduce lateral movement by enabling you to control which apps users can access via Remote App.

Note: You need to enroll users in MFA before you can apply MFA to RemoteApp sessions. If you have remote users, follow these instructions to enroll remote users in MFA.

New: Configure MFA by session type

You now configure MFA by session type, including:

• Workstation
• Server
• IIS
• VPN
• SaaS

You’ll see two edit modes for modifying the MFA settings when you enable MFA. Make sure you’ve read the documentation for the use case on each type of session to ensure MFA will be prompted.

• All session types at once: This option allows you to apply the same policy to all session types protected by UserLock.
• By session type: Select this option to apply different MFA policies for each session type.

For example, you can create policies for local servers and IIS sessions that connect outside the network.

New: Configure MFA frequency for every n minutes/hours/days

You have more granularity in choosing how often you want to prompt for MFA. You can prompt users for MFA after a specific period defined by minutes, hours, or days.

This means that, for each session type, you have new options to select how often you want to prompt the user with MFA (see current options for UserLock 12.0 here):

• After a given time: prompt users with MFA at their next logon after a specific period defined by minutes, hours, or days (the option to choose minutes or hours is new in UserLock 12.1).
• After a given time since the last logon from each IP address: This is the same as the above, except the amount of time will be counted from the last connection to that IP address, not the last connection.
• Not configured: MFA will not be prompted unless another policy is applied through another protected account.

New: Configuration wizard

With UserLock 12.1, a new configuration wizard guides you step-by-step to configure the following features:

• UserLock server: server type, protected zone, etc.
• UserLock Web App
• MFA for IIS applications
• UserLock Anywhere

Improved: Support proxy for UserLock Anywhere

UserLock Anywhere now supports HTTP Proxies. You can validate a list of trusted proxies to recover the real client IP address for agents communicating through UserLock Anywhere.

Improved: View notification history for UserLock Push

Now, users can view the notification history in the UserLock Push app. This allows users to show admins what IP address notifications are coming from, allowing them to spot suspicious behavior more easily. It also builds end-user awareness (and responsibility).

This update concerns only Push notifications. OTP accounts do not have a history.

Any inquiries on the new release?

LOGON is a certified IS Decisions partner in Asia. Don’t hesitate to contact our specialist for more information on the product release.

User Logon Security for Windows Active Directory

Enable customized, two-factor authentication (2FA) on Windows logon, Remote Desktop (RDP & RD Gateway), IIS, VPN and Cloud Applications. Apply customized login restrictions by user, group or organizational unit (OU).

Get started with UserLock

Start a free trial with UserLock, with 30-day full version, no user limit, and free technical support.