Strong Authentication for Cisco ACS 5.x

Transcription

1 Strong Authentication for Cisco ACS 5.x with Powerful Authentication Management for Service Providers and Enterprises Authentication Service Delivery Made EASY

2 Copyright Copyright CRYPTOCard Inc. All rights reserved. The information contained herein is subject to change without notice. Proprietary Information of CRYPTOCard Inc. Disclaimer The information contained in this document may change without notice, and may have been altered or changed if you have received it from a source other than CRYPTOCard Inc. While every effort is made to ensure the accuracy of content offered on these pages, CRYPTOCard Inc. shall have no liability for errors, omissions or inadequacies in the content contained herein or for interpretations thereof. Use of this information constitutes acceptance for use in an AS IS condition, without warranties of any kind, and any use of this information is at the user s own risk. No part of this documentation may be reproduced without the prior written permission of the copyright owner. CRYPTOCard Inc. disclaims all warranties, either expressed or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall CRYPTOCard Inc. be liable for any damages whatsoever, including direct, indirect, incidental, consequential or special damages, arising from the use or dissemination hereof, even if CRYPTOCard Inc. has been advised of the possibility of such damages. Some provinces, states or countries do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply. Links and addresses to Internet resources are inspected thoroughly prior to release, but the everchanging nature of the Internet prevents CRYPTOCard Inc. from guaranteeing the content or existence of the resource. When possible, the reference contains alternate sites or keywords that could be used to acquire the information by other methods. If you find a broken or inappropriate link, please send an with the topic name, link, and its behaviour to support@cryptocard.com. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of the license. Trademarks BlackShield ID, CRYPTOCard and the CRYPTOCard logo are trademarks and/or registered trademarks of CRYPTOCard Corp. in Canada and/or other countries. All other goods and/or services mentioned are trademarks of their respective holders. 2

3 Contact Information CRYPTOCard s technical support specialists can provide assistance when planning and implementing CRYPTOCard in your network. In addition to aiding in the selection of the appropriate authentication products, CRYPTOCard can suggest deployment procedures that provide a smooth, simple transition from existing access control systems and a satisfying experience for network users. We can also help you leverage your existing network equipment and systems to maximize your return on investment. CRYPTOCard works closely with channel partners to offer worldwide Technical Support services. If you purchased this product through a CRYPTOCard channel partner, please contact your partner directly for support needs. To contact CRYPTOCard directly: United Kingdom 2430 The Quadrant, Aztec West, Almondsbury, Bristol, BS32 4AQ, U.K. Phone: Fax: support@cryptocard.com North America March Road, Kanata, Ontario, Canada K2K 2E4 Phone: Fax: support@cryptocard.com For information about obtaining a support contract, see our Support Web page at Overview 3

4 Overview By default Cisco ACS logons requires that a user provide a correct user name and password to successfully logon. This document describes the steps necessary to augment this logon mechanism with strong authentication by adding a requirement to provide a one-time password generated by a CRYPTOCard token using the implementation instructions below. Applicability This integration guide is applicable to: Security Partner Information Security Partner Cisco Systems Product Name and Version Cisco ACS 5.x Protection Category Remote Access Authentication Service Delivery Platform Compatibility Publication History Date Changes Version September 29, 2010 Document created 1.0 Overview 4

5 Preparation and Prerequisites 1. Ensure end users can authenticate through Cisco ACS with a static password before configuring RADIUS authentication. 2. For BlackShield Server: a. BlackShield ID NPS IAS Agent has been installed and configured on the NPS IAS Server to accept Radius authentication from the Juniper SSL VPN. b. Ensure that Ports 1812 UDP and 1813 UDP are open to the NPS / IAS Server c. The NPS IAS Agent must be configured to use either port 80 or port 443 to send authentication requests to the BlackShield ID server. 3. For BlackShield Cloud: a. Add a RADIUS Auth Node configured to accept authentication requests from the Juniper SSL VPN. 4. For BlackShield Server or BlackShield Cloud: a. Create or define a Test account that will be used to verify that Cisco ACS has been properly configured. Ensure that the user name for this account exists in BlackShield ID by locating it in the Assignment Tab. b. Verify that the Test user account can successfully authenticate with a static password, to Cisco ACS before attempting to apply changes and test authentication using a token. c. A Test user account has been created and assigned with a CRYPTOCard token. Preparation and Prerequisites 5

6 Configuration In order for Cisco Secure ACS to authenticate CRYPTOCard token users, a RADIUS Identity Server associated to the BlackShield Server must be added to the Cisco Secure ACS configuration. The RADIUS Identity Server must be enabled in the Identity Store Sequences. Configuring CRYPTOCard authentication using an Identity Store Sequence consists of 2 steps: Step 1. Step 2. Define a RADIUS Identity Server. Define an Identity Store Sequence Defining a RADIUS Identity Server The BlackShield ID Agent for Internet Authentication Service (IAS), Network Policy Server (NPS) or Juniper Steel Belted RADIUS must be defined as a RADIUS Identity Server within Cisco ACS. Perform the following steps: 1. In Cisco Secure ACS select Users and Identity Stores, External Identity Stores, RADIUS Identity Servers then Create. Configuration 6

7 2. Under General enter the Name and Description for the BlackShield RADIUS server. Under Server Connection, Primary Server enter the IP Address or Hostname of the BlackShield RADIUS Server. Enter the Shared Secret defined in the BlackShield server for Cisco ACS. Under Advanced Options the Authentication Port should be set to 1812 and under Accounting Port set The Server timeout should be set to 10 seconds or higher and the Connection Attempts set to If required, populate the Shell Prompts, Directory Attributes and the Advanced tab. Defining an Identity Store Sequence The BlackShield RADIUS Identity Server must be assigned to an Identify Store Sequence. Perform the following steps: 1. In Cisco Secure ACS select Users and Identity Stores, External Identity Stores, Identity Store Sequences then Create. Configuration 7

8 2. Under General enter the Name and Description for the BlackShield RADIUS server. Under Authentication Method List select Password Based. Under Authentication and Attribute Retrieval Search List place the BlackShield Identity Server in the Selected list. Further Information For further information, please visit Configuration 8