Time Limits Policy and Inactivity Time-Out

Time Limits Policy and Inactivity Time-Out

How important is implementing time limits policy and inactivity time out?

As a means to enforce security standards, organizations can lock or disconnect non-active VDI sessions when detecting inactive end-users.

What do they do?

An admin can set any time between 1 minute to 23 hours 59 minutes as time limits, beyond which sessions can be disconnected. Secondly, an inactivity lock for the client dashboard alone can be set.

Use Cases:

• Setting VDI session time limits by policy helps organizations to better control end-users’ access and behavior, which benefits overall security. For example, you may want to set time limits policy as 3 minutes for a certain group of users like clinicians working on sensitive healthcare data, and maybe 5 hours for relatively less sensitive data for another group of users. Different pools with varying time limits policies can be set to address specific use cases and needs across an organization.

• An organization may give access to multiple applications to users, while requiring them to authenticate before they launch an application. This security policy can be invoked to enforce client dashboard lock up on inactivity.