IS Decisions opens UserLock 6.0 Beta Testing Program

We are pleased to announce the UserLock 6.0 Beta Testing Program.

UserLock limits concurrent logins, restricts access, monitors, alerts and reports on session activity throughout the corporate Windows network.

UserLock 6.0 is a major upgrade that comes with numerous new features and enhancements including:

- Time quotas: ability to define daily, weekly, monthly, etc. quotas.
- A third type of Protected Account: Organizational Units.
- Protection of IIS sessions (Ex: control access to Outlook Web Access or an Intranet).
- Ability to set the protected zone by selecting multiple computer Organization Units.
- Ability to define restrictions on workstations with computer Organizational Units.
- Audit and display session with local accounts.
- Specialized reports for RAS sessions (history, evolution and statistics).
- And more…

UserLock 6.0 Beta Testing Program

UserLock 6 beta will be ready in a couple of weeks. Would you like to test it?

Join our Beta Testing Program by filling out this online Web form.

We will share documents and resources and provide personalized technical support during your tests of the Beta.

Thank you in advance for your interest in UserLock 6.0!

Permalink 0 notes Comments

UserLock and FileAudit help guard against rogue sys admins

Back in September 2010, Network World published an insightful article by Carolyn Duffy Marsan, titled «6 tips for guarding against rogue sys admins».

In this article, Carolyn underlined the fact that «one of the biggest threats that organizations face is losing sensitive data […] to theft from their own employees. The threat is greatest from systems and network administrators, who have privileged access to vast amounts of corporate data and are responsible for most compromised records in insider cases.»

Carolyn then described several practical steps IT departments can take to minimize the insider threat, including:

«Restrict and monitor users with special privileges»

More easily said than done if you only rely on native Windows features. Windows lacks the fundamental and classic login session controls found in other environment like mainframe and midrange systems, UNIX and Netware.

UserLock comes in handy here, as this software solution allows CIOs to:

  • limit or prevent concurrent logins to a Windows network, based on user, user groups or session types,
  • restrict user access to the network with multiple criteria: workstations, time, business hours, and connection type,
  • follow the session activity on the network in real-time and get detailed, graphical reporting,
  • automatically receive popup or email alerts for specific events such as denied logins, successful logins and logoffs.

«Keep user access and privileges current, particularly during times of job changes or layoffs»

Here again, native Windows features are not really oriented to easily provide this functionality.

Imagine the following example:
A Sys Admin (let us call him John) is fired and knows that his dismissal is coming. John is logged on at 04:00 pm and at 04:05 pm the CIO disables and/or deletes his account. Guess what happens? John is still logged on to a workstation and connected to some servers. All he has to do is unlock the workstation, (typically workstations do not go and check unlock requests with the domain controller). The result is that John is still able to work on his desktop and local drives, even though his account has been disabled and deleted.

With UserLock, a CIO can remotely lock, logoff and reset all sessions immediately, from potentially anywhere using the Web interface.

«Monitor employees found guilty of minor online misconduct»

When it comes to employees’ online behavior surveillance, two things are crucial:

To monitor logon sessions

Here again, native Windows features are not sufficient. System Admins are not able to answer the following questions in real time:

  • Who is logged on at which computers?
  • Which computers are being used by a given user?
  • Who are the users currently logged on at this particular computer?

UserLock allows real time session surveillance and monitoring; at all times a CIO knows who is connected, from what workstation(s), since when…

To monitor access to files and folders

To monitor access to an organization’s files and folders, standard Microsoft systems only propose manual event logs. This functionality leaves administrators with hundreds or even thousands of events to decrypt and analyze to pinpoint the information of interest. This generates endless hours of non productive and error-prone work.

FileAudit monitors, archives and reports on access (or access attempts) to sensitive files and folders stored on Microsoft Windows systems.

FileAudit instantly gives a comprehensive list of:

  • read/write accesses
  • file ownership changes (accepted or denied)
  • permission modifications (accepted or denied)

Each record details:

  • the user
  • the domain
  • the date and time of connection and disconnection

for:

  • a file
  • a selection of files
  • a folder and subfolder
  • a selection of folders and subfolders

«Educate your employees about insider threat»

Raising employees’ awareness about insider threat is a key component of an efficient IT security strategy. Regular training or offering a hotline so that employees can anonymously report fraud are part of the insightful measures that should be taken to mitigate insider threat. But one of the most efficient ways to make users security aware is to systematically remind them of their rights and duties each time they log on.

UserLock allows notifying all users prior to gaining access to a system with a tailor- made disclaimer. Users can for example be advised that system usage is monitored, recorded, subject to audit, and that unauthorized use is prohibited and subject to criminal and civil penalties.

Another efficient way is to provide users at each connection with detailed information about their previous logons, so they can easily detect if someone else had successfully logged on (or attempted to log on)as them and potentially impersonated them. This is missing from native Windows features.

At each logon, UserLock provides users with information such as:

  • last workstation logged on,
  • date and time of last successful logon,
  • history of all logons denied by UserLock and Windows since last successful logon,
  • number of logons denied by UserLock and Windows since last successful logon.

We look forward to your comments and concerns. Feel free to post your remarks hereunder or use Twitter or Facebook to exchange with us.

Download UserLock now

Download FileAudit now

Permalink 0 notes Comments

How to remotely (and automatically) shutdown thousands of PCs at night with RemoteExec

RemoteExec description

The example below illustrates the use of a predefined System Action to ensure the automatic shutdown of all workstations. The time you choose for switching off your computer must coincide with your company business needs.

Take note that:

  • A user might be working on the target machine.
  • A session can be opened on the target machine without a user in front of it, but with documents opened or applications running.
  • A session can be locked on the target machine with some documents opened or applications running.


Our goal in this example is to shutdown all computers, even those with documents unsaved or applications running. You should communicate this as part of your global Green Charter to your users.

How to shutdown all computers

  1. Open RemoteExec and go to Remote Jobs/New Remote Job/System action through the Configuration tree.
    RemoteExec configuration tree
  2. In the first section «Settings», choose in the combo list System action named Shutdown.
  3. RemoteExec can check if a user is currently working on the target machine, and can process the System action differently in this case.

    Choosing the option Immediate execution, notify otherwise means:
    • If there is no user connected on the workstation, the shutdown will be initiated immediately.
    • If there is a user connected on the workstation, a Notification will be displayed to the connected user. The shutdown will be initiated depending on the mode defined in step 4 for this Notification.
  4. Notification mode
    Two options to define how the shutdown will be initiated:
    • Execute after showing notification during
      The shutdown will be executed after displaying the message during the number of minutes typed. The Notification displayed can be hidden by users, but it regularly pops in foreground.
    • Indefinitely notify every
      The Notification is displayed indefinitely until users click on the button to initiate the shutdown. Users can hide the Notification, but it will pop again every number of minutes you’ve defined.

    As we defined in the preamble, we want to shutdown all workstations. We will choose here to execute this System action after the Notification period. We will set a sufficient delay allowing users to finish their current work.
  5. Leave the third combo list on the Don’t wait for the end of the execution option. (This option is pertinent in multi action mode, not in our example here).
  6. Check the Force applications to close option.

    We will be sure that all sessions kept opened will be closed. Although users have been informed about this Green Charter action, there will be always some thoughtlessness.
  7. Set your Notification message to explain the imminent shutdown and provide instruction to avoid losing documents/work recently modified.
  8. We want to power off all workstation from our network. That’s why in Target Computers section we have selected the whole domain. As we don’t want servers to be concerned by this Remote Action, we will set the Filter section option named OS level only to workstation.
  9. The remote shutdown job is now ready and fully set.

    This is how the Notification will be displayed to users connected on the target machines:
  10. Click in Quick Access Pane on
  11. Enter a name on the Schedule Wizard for this new task.
  12. Once validating the new task name, the Windows scheduler pop-up will appear. Set the task to Daily and the hour settings in according to your company hours. Validate by clicking OK. You will be prompted to set an administrative account for this task.

    In this example setting 09h30 PM means that the computers will be powered off by 10:00 at the latest. (9h30 + 30 minutes countdown).

    The RemoteExec Scheduler now displays our new scheduled Job.

Want more ?

In this example, all computers have been shut down during the night. In the same way, you may decide to automatically switch on computers on allowing users to work immediately upon their arrival. This is also possible through RemoteExec Wake up System action.

The computers using the Wake-on-line technology (available on most computers today) can be remotely powered on if this option is enabled. You just have previously to scan the Mac addresses and Subnet of your network machines using the System action Get wake up info (which can also be scheduled). Then using the same concept, you can choose to wake up users’ computers automatically.

During your tests

If for any reason you remotely launch a shutdown that you want to abort, you can use the specific System action.

Permalink 3 notes Comments
"

The more times a user is logged in to the network, the harder it is to determine if that user is really the person who logged in.

Limiting the number of concurrent connections to two or even one makes tracking users’ network access easier and provides an additional level of security by reducing the number of Iogged in but unattended workstations.

Administrator accounts, in particular, should have limited concurrent connections. If an administrator should receive a denied login due to a current connections limit he would immediately know that his account had been compromised, or that another login had been inadvertently left active.

"

Protecting Your Network Against Known Security Threats (Novell Research)


Prevent/limit concurrent logins to your Windows network using UserLock

Permalink 0 notes Comments

Protect Windows networks from careless and fraudulent users

According to several recent studies, the most costly or damaging attacks against information systems are more often caused by insiders (employees or contractors with authorized access).


Taking this fact into account, we developed an enterprise software solution named UserLock, whose main goal is to protect Windows networks from careless and/or fraudulent users, thus efficiently mitigating insider threat.

UserLock logo

UserLock allows IT security teams to:


- prevent or limit simultaneous logon (same ID, same password), per user or user group
- record all session logging and locking events in an ODBC database (Access, SQL Server, Oracle, MySQL,…) for future reference
- monitor user sessions in realtime (who is connected, from which workstation(s), for how long…)
- remotely lock, logoff and reset all interactive sessions
- define working hours and/or maximum session time for protected users and disconnect users with prior warning outside of the defined timeframe(s) and/or when time is up
- restrict user group’s network access per workstation or IP range
- notify all users prior to gaining access to a system with a tailor-made warning message (legal disclaimer, etc.)
- …


More than 750,000 UserLock licenses are already in use by worldwide security-demanding organizations including:
BAE Systems, Banco de Costa Rica, Barclays Bank, BMW, Computer Sciences Corporation, Frito-Lay, Lockheed Martin, Mitsubishi, National Bank of Kuwait, South Wales Police, Telcel, United Nations Organization, US Department of Justice, US Department of Veterans Affairs, US Navy Marine Corps, TimeWarner, …


You will find information about UserLock on our website and this whitepaper will provide you with further details about holes in Windows native login controls and how UserLock fills them in and helps organizations to comply with major regulatory constraints (HIPAA, SOX, PCI, NISPOM, DCID 6/3 - ICD 503, GLBA, US Patriot Act, FISMA…).



Get your free, fully-functional, 180-day copy of UserLock


Permalink 0 notes Comments

PC Mag about UserLock: “It’s an impressive tool”

PC Mag has just reviewed UserLock, our software solution that secures access to Windows networks, comprehensively reports on user sessions and efficiently mitigates insider threat.


This in-depth review has been performed by Samara Lynn, Network Analyst, and published on March 2010, 12th.

PC Mag Logo

We cannot resist the pleasure of quoting some extracts from this review:


- BOTTOM LINE: it’s an impressive product

- Takes away pain using Group Policy for user account control. Intuitive interface. Easy install.

- UserLock efficiently and quickly handled restricting users from network access

- Windows administrators will feel right at home here.

- At a price of $10.50 USD per user session, (the price goes down as the amount of user session licenses purchased goes up) it won’t break the bank, either.

- Setup’s a cinch

- Adding a user account is as easy in UserLock as it is to give folder permissions to a user in Windows.

- The big advantage of UserLock though, is its simplicity.

- More important, [UserLock] aids in shoring up network security.

- Overall, UserLock is a solid tool that any Windows Network Administrator should consider adding to their network management toolkit if tight user access control is mandatory for their organization.



Read the full review in PC Mag

Get a free, fully-functional, 180-day copy of UserLock

Permalink 0 notes Comments

Protect your Windows network from careless and fraudulent users

IS Decisions developed a software solution named UserLock, whose main goal is to protect Windows networks from careless and/or fraudulent users, thus mitigating insider threat.


More than 700,000 UserLock licenses are already in use by worldwide security-demanding organizations including:
BAE Systems, Banco de Costa Rica, Barclays Bank, BMW, Computer Sciences Corporation, Frito-Lay, Lockheed Martin, Mitsubishi, National Bank of Kuwait, South Wales Police, Telcel, United Nations Organization, US Department of Justice, US Department of Veterans Affairs, US Navy Marine Corps, TimeWarner, …

UserLock Logo


UserLock indeed allows IT Security teams to:

- prevent or limit simultaneous logon (same ID, same password), per user or user group

- record all session logging and locking events in an ODBC database (Access, SQL Server, Oracle, MySQL,…) for future reference

- monitor user sessions in realtime (who is connected, from which workstation(s), for how long…)

- remotely lock, unlock, logoff and reset all interactive sessions

- define working hours and/or maximum session time for protected users and automatically disconnect users with prior warning outside of the defined timeframe(s) and/or when time is up

- restrict user group’s network access per workstation or IP range

- notify all users prior to gaining access to a system with a tailor-made warning message (legal disclaimer, etc.)

- …


You will find detailed information about UserLock on our website (as well as a free, 180-day fully-functional trial version), and this whitepaper will provide you with further details about holes in Windows native login controls and how UserLock fills them in and helps organizations to comply with major regulatory constraints (HIPAA, SOX, PCI, NISPOM, DCID 6/3 - ICD 503, GLBA, US Patriot Act, FISMA …).

Permalink 3 notes Comments

Windows networks: why should you monitor login sessions?

Logon session monitoring is being able to say, in real time, who is logged on at which computers and to answer two questions:

- What are all the computers that a given user is currently logged on at?
- Who are the users currently logged on at this particular computer?

Logon Monitoring

There is no way to do that with native Windows functionality, although that would empower System Administrators to efficiently mitigate insider threats.


Instead, what you have to do is figure that out one server at a time.

You can go to a given single Windows server, go to Computer Management > Shared Folders > Sessions, and you can look it up that way.


Think about how difficult that is if you have to check each server individually …



Read more about login sessions monitoring

Permalink 0 notes Comments

Discover WinReporter in use.

WinReporter audits and reports on all Windows assets (hardware, software, settings, eventlogs) across the entire corporate network.



Full details and free fully-functional trial version

Permalink 0 notes Comments

Windows networks: why is logon/logoff reporting important?

There is no way in Windows to get a report saying “John logged on at 8:00 and he logged off at 11:00.”

Users

It is therefore a precious information that gives System Administrators the ability to answer crucial questions when it comes to investigations following an incident. Who was really logged on? Where were they logged on? When did they log on? How long did they remain logged on? When did they log off? At any given time, which people were actually logged on at their Windows systems?



Read more about logon/logoff reporting for Windows networks

Permalink 0 notes Comments