Better Windows Network Security. Control User Access.

By   ISBuzz Team
Writer , Information Security Buzz | Aug 19, 2013 01:18 am PST

One important way to improve Windows Network Security is to control users from accessing the network based on criteria that you have specified.

UserLock sets this kind of stringent access control entry by restricting user logons according to customized user access policies. It continuously monitors all login and session events, automatically applying custom policies to permit or deny logins, workstation access and usage/connection time.

This post looks at the type of restrictions made and the level of granularity offered.

Defining protected accounts

The defined protected accounts can be made up of users, user groups or Organizational Units (OU) onto which UserLock rules can be applied. User Protected accounts always override Group and OU Protected account settings. With Group and OU permissions you can choose the policy rule that UserLock should use.

Note: Because UserLock integrates with Active Directory, just type the user account name and UserLock will check for that account against Active Directory and add it in the console.

For each protected account, the following restrictions can then be set.

The Maximum Number and Type of Opened Sessions

limit session number for windows network security

Define the number of concurrent sessions allowed. This includes the maximum number of simultaneous workstations where a user can be logged on, the maximum number of terminal sessions that a user can open and the total interactive sessions (workstations and terminal) allowed.

Restrict also the maximum number of simultaneous Wi-Fi/VPN sessions that a user can open (including 0 sessions) and allowed IIS sessions.

A maximum limit for combinations of several kinds of sessions can also be set.

An option is available to allow or deny a user to logoff an existing session if the number of allowed sessions has already been reached.

Workstation restrictions

IP restriction for windows network security

Restrict the workstations/terminals from where a protected account may logon. Set a restriction by an IP range, a computer name/IP or Organizational Unit.

Read the full article here

Chris Bunn | | @IS_Decisions

Chris is Community Manager of IS Decisions, a Software Vendor specializing in Infrastructure and Security Management solutions for Microsoft Windows.

Software solutions developed for Network Administrators:
– secure, monitor and report on network access and user sessions
– audit access to sensitive files and folders
– perform remote installations of applications and updates across the network
– automate the inventory of Windows assets (hardware, software, settings, eventlogs)

More than 3,000 clients worlwide trust IS Decisions:
Airbus, American Express, AXA, Banco Santander, Bank of Tokyo, Barclays, Boeing, Citizen, Ernst & Young, GlaxoSmithKline, Hewlett-Packard, HSBC, Konica, IBM, Lockheed Martin, L’Oréal, Microsoft, Mitsubishi, Saint Gobain, Siemens, Smurfit Stone, Texas A&M University, Time Warner, United Nations, University of Cambridge, University of Pennsylvania, US Department of Justice, US Air Force, US Army, US Navy, Virgin, …

IS Decisions is a Microsoft Partner Silver Independent Software Vendor.

Notify of
0 Expert Comments
Inline Feedbacks
View all comments

Recent Posts

Would love your thoughts, please comment.x