Two-factor Authentication:Highlighting the Multi-factor Authentication Layer of thePortalGuard PlatformA Tokenless ApproachUnderstanding PortalGuard’s
• Define PortalGuard• Understand the need for two-factor authentication• Learn about PortalGuard’s Two-factor Authentication Options• See the step-by-step Authentication Process• Know the technical requirementsBy the end of this tutorial you will be able to…
The PortalGuard software is a Contextual Authentication platformwhich is focused on enhancing usability, while maintaining abalance between security, auditing and compliance for your web,desktop and mobile applications.• Single Sign-on• Password Management• Password Synchronization• Self-service Password Reset• Knowledge-based• Two-factor Authentication• Contextual Authentication• Real-time Reports/AlertsUsability Security
Before going into the details…• Configurable by user, group or application• Configure One-time Password (OTP) length, expiration and format• Send OTP via SMS, email, transparent token and printer• No SMS gateway required• Cost effective and competitively priced• Tailored Authentication for an exact fit• Enforced for direct access to applications, VPN using RADIUS and duringa self-service password reset, recovery, or account unlock
Two-factor Authentication is…Used to increase security by requiring:“Something you know”“Something you have”AND
Aren’t all Two-factor Authentication Solutions the Same?They will increase your security however…• Inflexible• Low usability• High total cost of ownership• Tokens are expensive, forgotten and need replacement/repair
ONE-TIME PASSWORD (OTP)Transparent Tokens• Web/cloud application directly• VPN connection using RADIUS• Self-service password reset,recovery, or account unlock
How do I choose?SMS• Attack Prevention – both passive and active• Total Cost of Ownership• Support/Maintenance Requirements• Client-side Software• Ease of Use• Portability
• Increased security - add an extra layer of authentication to applicationaccess, VPN access, or during a self-service password reset• Reduce Risk - prevent attacks by leveraging credentials which expireafter one use• Usability - leverage hardware a user already has for increased useradoption• Eliminate forgotten passwords - leverage a username and OTP only ascredentials• Configurable - to the user, group or application levels• Flexible - multiple OTP delivery methods available
PortalGuard provides flexibility…Allows you to configure whether the enrollment will be forced or able tobe postponed “x” number of times by the user.
Step 1:PortalGuard’s login screen is presented when a user visits the web-application.Step 2:The user enters their username and clicks continue.Step 3:The PortalGuard server sends the OTP to the user’s mobile phonewithin 5-10 seconds, in the form of an SMS.Step 4:The user is prompted for a password and OTP.Step 5:The user enters in the OTP they received and clicks “Log On”.Step 6:The user gains access to the web-application and data.Step 7:This is an example of a user attempting to use an expired OTP that wasnever used. Once the expired OTP is entered, the user is denied accessand prompted to cancel the process or request a valid OTP.
Step 1:PortalGuard’s login screen is presented when a user visits the web-application.
Step 2:The user enters their username and clicks continue.
The PortalGuard server sends the OTP to the user’s mobile phonewithin 5-10 seconds, in the form of an SMS.Step 3:
Step 4:The user is prompted for a password and OTP.
Step 5:The user enters in the OTP they received and clicks “Log On”.
Step 6:The user gains access to the web-application and data.
Step 6:This is an example of a user attempting to use an expired OTP that wasnever used. Once the expired OTP is entered, the user is denied accessand prompted to cancel the process or request a valid OTP.
RADIUS Support:An internet standard that was designed primarily to authenticateremote users• Cisco• JuniperNetwork Access Server (NAS) = “RADIUS Client”PortalGuard = “RADIUS Server”• Citrix• Checkpoint• User accounts defined locally• LDAP Authentication• X.509 certificates• RADIUS
Step 1:The user attempts to connect to the NAS/firewall using either abrowser or VPN client software and is prompted for username andpassword.
Step 2:The NAS communicates the credentials to the PortalGuard serverusing the RADIUS protocol.The PortalGuard server validates the user’s credentials against itsconfigured user repository (e.g. Active Directory).Step 3:
PortalGuard replies to the RADIUS request with an Access-Challengeresponse that includes a custom message that should be displayed tothe user and a random identifier (the “state”) that the NAS will sendback to PortalGuard to identify the same user session.Step 4:The user attempts to connect to the NAS/firewall using either abrowser or VPN client software and is prompted for username andpassword.Step 5:
The NAS displays the custom message requesting the user to enterthe OTP that was sent to their mobile device.Step 6:
Step 7:The user enters the OTP from their mobile device and submitsit to the NAS.
The NAS communicates the credentials to the PortalGuard serverusing the RADIUS protocol.Step 8:Step 9:The PortalGuard server replies to the RADIUS 2nd request with anAccess-Accept response.
The NAS accepts the user’s authentication and the VPNtunnel/session is established. The user is then able to accessinternal resources (e.g. “crm.acme.com”).Step 10:
Configurable through the PortalGuard Configuration Utility:• Expiration, aka “time-to-live” (TTL)• Length• Format• Numeric characters only• Upper/lowercasecharacters• Upper/lowercase &numeric characters• Upper/lowercase,numeric and symbolcharacters• Delivery format, including From, Subject and Body fields
A MSI is used to install PortalGuard on IIS 6 or 7.x.This version of PortalGuard supports direct access and authenticationto cloud/browser-based applications, only.• .NET 2.0 framework or later must be installed• (64-bit OS only) Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)• 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• 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• The network appliance must support RADIUS as an authentication option• The network appliance must support the Access-Challenge response type as well asthe State and Reply-Message attributes• PortalGuard must be licensed for RADIUS support• End-user enrollment of mobile devices or challenge answers must be performedexternal to the RADIUS protocol
THANK YOUFor more information visit PortalGuard.com or Contact Us