Configurable Password Management: Balancing Usability and Compliance

Password Management Layer

v.3.2-004

PistolStar, Inc. dba PortalGuard PO Box 1226 Amherst, NH 03031 USA Phone: 603.547.1200 Fax: 617.674.2727 E-mail: [email protected] Website: www.portalguard.com
2012, PistolStar, Inc. dba PortalGuard All Rights Reserved.

Tech Brief Configurable Password Management

PortalGuard Configurable Password Management: Balancing Usability and Compliance

Table of Contents
Summary ................................................................................................. 2 The Basics............................................................................................... 2 PortalGuard Password Management ....................................................... 3 Features .................................................................................................. 3 Benefits ................................................................................................... 3 How it Works ........................................................................................... 4 Password Policies ........................................................................ 4 Policy Search Order and Precedence .......................................... 4 User Profiles ................................................................................ 5 Step-by-Step Process .................................................................. 5 Configuration ........................................................................................... 9 Deployment ........................................................................................... 13 IIS Install................................................................................................ 13 System Requirements ........................................................................... 13 Supporting Videos ................................................................................. 14 Platform Layers ..................................................................................... 14

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 1

Tech Brief Configurable Password Management

Summary
Implementing strong authentication security for web-based applications before deployment to your production environment is the ideal approach however, many projects take longer than expected so some applications are deployed without security policies in place, such as password quality, password expiration and strike counts. Password management is usually added later when a security audit uncovers an application as being non-compliant. To make a web-based application compliant, you need to decide whether to build or buy a complete authentication security solution. Buying an offthe-shelf solution, such as PortalGuard, offers the much needed enterprise-ready security functionality that easily integrates into your existing web-based and SQL applications. Sometimes developers may not consider the organizations data accessed by the webbased application to be sensitive and therefore, increasing security becomes a secondary consideration during deployment. A low risk application may require either no authentication or the use of just a username and password, though this approach should not be used in applications with medium or high risk. Please review other PortalGuard tech briefs on increasing web-based authentication security with approaches such as contextual and two -factor authentication. These tech briefs provide more information on the security risks of using just passwords as a single barrier to blocking unauthorized access to your organizations data.

The Basics
Passwords remain an important aspect of authentication security. A poorly chosen password may result in unauthorized access and/or exploitation of an organizations resources and critical data. The purpose of password management policies is to establish and enforce the security standard for the creation of strong passwords, the protection of those passwords, and the frequency of which to change them. However, one of the first steps to password management is educating your users on password best practices via a security awareness program with information such as: Never share your account Never use the same password for multiple systems Never tell a password to anyone, including those claiming to be from security or customer service within your organization Never write down a password Never provide a password over the phone, e-mail or instant messaging Make sure to log off or lock your workstation before leaving a computer unattended Change your password whenever you suspect it may have been compromised Passwords should be alpha-numeric at a minimum General password management best practices provide the foundation for strong organizational security policies, including: How complex a password needs to be should be based on risk The frequency to which you change your passwords should be based on risk At all points, passwords should be protected from being exposed

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 2

Tech Brief Configurable Password Management

PortalGuard Password Management

PortalGuards password management goes beyond the foundational principles and provides enhanced functionality which improves the security of passwords while improving usability for users. This is done with features such as strong password policy enforcement, password synchronization, and self-service password reset. By creating this balance between security and usability PortalGuard can significantly reduce Help Desk calls and increase user adoption. To provide you with flexibility, PortalGuards password management policies can be configured down to the individual user, group or domain hierarchy, enforcing the appropriate level of security for each.

Features
Password Complexity - customizable rules for minimum and maximum length, and uppercase, lowercase and special characters. Complexity checks can also be performed during each login to assure compliance. Password History - prevent users from reusing their last n passwords Password Expiration - set expiration and grace periods Strikeout/Lockout Limits - enforce a configurable number of strikes before an account lockout and optionally specify a minimum lockout time the user must wait before the account is automatically unlocked and they can again attempt to login Prevent Users from Sharing Credentials - limit multiple concurrent logon sessions Lockout Inactive User After n Days - identify and stop access from dormant user accounts Help Desk/Verbal Authentication - prove users identity when calling into the Help Desk by answering a series of challenge questions Email Calendar Reminders - set reminders in users email client calendar of upcoming password expirations Password Meter - provide users with visual clue of the strength of the password when resetting or creating one Auditing/Logging - record user login activity including invalid usernames, last login, last password change, etc. Administrative Dashboard - provides administrators with a snapshot of recent user login activity Tailored Authentication - extend the PortalGuard framework to include specific functionality which provides an exact fit with your requirements

Benefits
Configurable - to the individual user, group or domain hierarchy Increased usability maintains user productivity and satisfaction with functionality such as the password strength meter, email calendar reminders, and self-service password reset Increased security prevents both common password and code injection attacks by enforcing strong password management best practices Balances security and usability with functionality to support both compliance and user demands Implement password best practices including account lockout limit, unlock threshold, and password history

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 3

Tech Brief Configurable Password Management

Compliance web-based and SQL applications now meet required industry and regulatory standards Cost effective reduce password related Help Desk calls

How It Works
Password Policies
PortalGuard uses the concept of policy-based security settings to enforce password management rules for users. You can have multiple sets of rules defined within PortalGuard. Each set of rules is referred to as a policy. You can then assign users to a policy on an individual basis or by a group or domain hierarchy. If a policy is not applied to anyone, then its rules will never be enforced. Policies can be enabled or disabled. Only policies which are both enabled and have users assigned to them are enforced by PortalGuard. There are key aspects to each password policy including password length, formation, duration and practice. With those in mind you can define password policies so that all user accounts are protected with strong passwords. Below are examples of policies you can enforce: Define password history policy setting so that several previous passwords are remembered. With this policy setting, users cannot reuse old passwords when their password expires. Define the maximum password age policy setting so that passwords expire as often as necessary for your environment, typically, every 30 to 90 days. With this policy setting, if an attacker cracks a password, the attacker only has access to the network until the password expires. Define the minimum password age policy setting so that passwords cannot be changed until they are more than a certain number of days old. This policy setting works in combination with the password history policy setting. If a minimum password age is defined, users cannot repeatedly change their passwords to get around the password history policy setting and then use their original password. Users must wait the specified number of days to change their passwords. Define a minimum password length policy setting so that passwords must consist of at least a specified number of characters. Long passwords--seven or more characters--are usually stronger than short ones. With this policy setting, users cannot use blank passwords, and they have to create passwords that are a certain number of characters long.

Policy Search Order and Precedence

With policies capable of being applied to individual users, groups and domain hierarchies, it is a common occurrence for a user to have multiple policies applied to them. At run-time however, only a single policy will be enforced for the user. This disparity is resolved by searching for applicable policies in the following manner with each subsequent search becoming a less explicit match: 1. Policies applied directly to a user 2. Policies applied to a group 3. Policies applied to a domain or OU 4. The default policy
2012, PistolStar, Inc. dba PortalGuard All rights reserved. Page 4

Tech Brief Configurable Password Management

User Profiles
User profiles are where PortalGuards user-specific information is stored. Some examples of the data include, but are not limited to: Strike count Last login time Password expiration date Hashed answers to challenge question Last password change time Accepted Terms of Use time

A profile is created for each user automatically as they log in through PortalGuard so it is not necessary to preload any user accounts. These user profiles can be stored as flat files on the PortalGuard server or in a SQL database for accessibility in clustered configurations.

Step-by-Step Process
Step 1: The users password is expired, but within the grace period. PortalGuard notifies the user, but provides the option of temporarily skipping the password change and going directly into the application because they are still in the grace period. The user defers the password change by clicking the link shown and is allowed to login.

Step 2: A few days later, the user attempts to log in and the password is now expired. PortalGuard enforces this by requiring the user to change their password before being allowed into the application.

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 5

Tech Brief Configurable Password Management

a. If PortalGuard is configured to use a password meter, it is automatically updated as the user types their new password. Only when the new password is sufficiently complex will the user be allowed to submit the password change.

b. If PortalGuard is configured to use standard password quality rules, the user is notified which rules have been satisfied by the new password and which must still be addressed.

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 6

Tech Brief Configurable Password Management

Step 3: When password history is enabled, a password that satisfies the complexity rules may still be rejected by the PortalGuard server for being previously used by the user.

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 7

Tech Brief Configurable Password Management

Step 4: Once the new password is acceptable, PortalGuard changes it in the target user repository (e.g. Active Directory, LDAP or a custom SQL table) in real-time and notifies the user of the success.

Step 5: If a password minimum age is enabled and the user attempts to manually change their password again, PortalGuard will prevent it.

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 8

Tech Brief Configurable Password Management

Configuration
NOTE: All the following settings are policy specific, so you can have different values for different users/group/hierarchies.

Configurable through the PortalGuard Configuration Utility:

Password Rules (Policies): Minimum length Maximum length Minimum lowercase Minimum uppercase Minimum numeric Minimum special Active Directory Complexity

Rule Grouping - for combining standard password rules into pools where only a subset must be met

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 9

Tech Brief Configurable Password Management

Enable/Disable Password Meter - minimum required score when enabled

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 10

Tech Brief Configurable Password Management

Password History - by number of entries or time

Password Dictionary - standard words that passwords cannot contain

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 11

Tech Brief Configurable Password Management

Enforce Complexity Rules During Login - any policy changes can be enforced immediately instead of waiting until the next time the users password expires Regular Expression checking - for rules that cannot be enforced using the out-of -the-box rules in PortalGuard

Password Expiration: Expiration period - number of days between required password changes Grace period - number of days before the expiration date when the user will receive notification of the impending expiration Expire first use - expire the password the first time the user authenticates through PortalGuard Minimum Age - number of minutes until a password can be changed again Calendar reminders - optional sending of reminders for the day the users password will expire next Lockout Strike limit - number of consecutive failed authentication attempts until the users account is locked in PortalGuard Lock expiration - optional number of seconds until a lockout automatically is cleared Strike messages - controls the level of information when a strike or lockout occurs, from the most generic (bad username or password) to the most helpful (bad password - you have 1 strike and your account will be locked when 3 strikes are reached) Inactivity - the number of days of PortalGuard inactivity until an account is considered dormant in PortalGuard. The PortalGuard server will then prevent login through its interface using these accounts
2012, PistolStar, Inc. dba PortalGuard All rights reserved. Page 12

Tech Brief Configurable Password Management

Session concurrency - prevent multiple simultaneous login sessions through the PortalGuard interface using the same credentials Help Desk/Verbal Authentication - enables the optional functionality that allows Help Desk staff to verbally identify users over the phone by asking a configurable set of questions Auditing Log last login - track last login date/time for users Log last password change - track last password change date/time for users Log last password recovery - track last password reset/recovery date/time for users Require acceptance - optional setting for requiring users to accept a Terms of Use agreement before allowing a login to complete URL for rejection - the URL where users should be redirected if they decline the Terms of Use

Deployment
Implementation of the PortalGuard platform is seamless and requires no changes to Active Directory/LDAP schema. A server-side software installation is required on at least one Microsoft IIS server on the network.

IIS Installation
A MSI is used to install PortalGuard on Microsoft IIS 6 or 7.x. If installing PortalGuard on Microsoft IIS 7.x/Windows Server 2008, make sure to have installed the following feature roles prior to launching the MSI: 1. All the Web Server Management Tools role services 2. All the Application Development role services 3. All Microsoft IIS 6 Management Compatibility role services The MSI is a wizard-based install which will quickly guide you through the installation.

System Requirements
This version of PortalGuard supports direct access and authentication to cloud/web-based applications, only. PortalGuard can be installed directly on the following web servers: IBM WebSphere/WebSphere Portal v5.1 or higher Microsoft IIS 6.0 or higher Microsoft Windows SharePoint Services 3.0 or higher Microsoft Office SharePoint Server 2007 or later

The PortalGuard Web server also has the following requirements on Windows operating systems: .NET 2.0 framework or later must be installed (64-bit OS only) Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)
2012, PistolStar, Inc. dba PortalGuard All rights reserved. Page 13

Tech Brief Configurable Password Management

PortalGuard is fully supported for installation on virtual machines. Furthermore, PortalGuard can currently be installed on the following platforms: Microsoft Windows Server 2000 Microsoft Windows Server 2003 (32 or 64-bit) Microsoft Windows Server 2008 (32 or 64-bit) Microsoft Windows Server 2008 R2

NOTE: When run in "Sidecar" mode, PortalGuard can provide its functionality on any web server that uses a HTML login page. If you have a platform not listed here, please contact us at [email protected] to see if we have recently added support for your platform.

Supporting Videos
Please view the following videos to watch a demo of PortalGuards password management offerings: Balancing Usability & Compliance: Discussing Password Management Password Strength Meter Demonstration

Platform Layers
Beyond password management, PortalGuard is a flexible authentication platform with multiple layers of available functionality to help you achieve your authentication goals: Contextual Authentication Tokenless Two-factor Authentication Real-time Reports / Alerts Knowledge-based Self-service Password Reset Single Sign-on

[Platform Visual on Next Page]

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 14

Tech Brief Configurable Password Management

###

2012, PistolStar, Inc. dba PortalGuard All rights reserved.

Page 15