+ All Categories
Home > Documents > Cisco Asa Black Shield ID

Cisco Asa Black Shield ID

Date post: 11-Mar-2015
Category:
Upload: 8johnwong
View: 121 times
Download: 3 times
Share this document with a friend
12
Copyright © 2008 CRYPTOCard Inc. http:// www.cryptocard.com Implementation Guide for protecting Cisco ASA 5500 Series (ASDM v6.1) with BlackShield ID
Transcript
Page 1: Cisco Asa Black Shield ID

Copyright © 2008 CRYPTOCard Inc. http://

www.cryptocard.com

Implementation Guide for protecting

Cisco ASA 5500 Series (ASDM v6.1)

with

BlackShield ID

Page 2: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) i

Copyright

Copyright © 2008, CRYPTOCard All Rights Reserved. No part of this publication may be

reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any

language in any form or by any means without the written permission of CRYPTOCard.

Trademarks

BlackShield ID, BlackShield ID SBE and BlackShield ID Pro are either registered trademarks

or trademarks of CRYPTOCard Inc. All other trademarks and registered trademarks are the

property of their owners.

Additional Information, Assistance, or Comments

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:

International Voice: +1-613-599-2441

North America Toll Free: 1-800-307-7042

[email protected]

For information about obtaining a support contract, see our Support Web page at

http://www.cryptocard.com.

Related Documentation

Refer to the Support & Downloads section of the CRYPTOCard website for additional

documentation and interoperability guides: http://www.cryptocard.com.

Page 3: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) ii

Publication History

Date Changes

January 9, 2009 Heterogeneous formatting completed - Version 1.0 created.

Page 4: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) iii

Table of Contents

Overview................................................................................................................ 1

Applicability ........................................................................................................... 1

Preparation and Prerequisites................................................................................ 1

Configuration ......................................................................................................... 2

Configure Cisco ASA Web VPN for Two Factor Authentication .......................................2

Define a RADIUS enabled AAA Server group ..............................................................2

Assigning a RADIUS AAA Server to the AAA Server group ...........................................3

Assigning CRYPTOCard Authentication to a Clientless SSL VPN Connection Profile...........4

Assigning CRYPTOCard Authentication to a IPSec VPN Connection Profile ......................5

Troubleshooting ..................................................................................................... 7

Further Information ............................................................................................... 8

Page 5: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 1

Overview

By default Cisco ASA user authentication 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 by using the instructions

below.

Applicability

This integration guide is applicable to:

Security Partner Information

Security Partner Cisco

Product Name and Version Cisco ASA 5500 series with ASDM v6.1

Protection Category Remote Access

CRYPTOCard Server

Authentication Server BlackShield ID

Version Small Business Edition 1.2+

Professional Edition 2.3+

Preparation and Prerequisites

1. Ensure end users can authenticate through the Cisco ASA with a static password before

configuring the Cisco Secure ASA to use RADIUS authentication.

2. BlackShield Pro server installed and a user account assigned with a CRYPTOCard token.

3. BlackShield Agent for Internet Authentication Service (IAS) or Network Policy Server

(NPS).

4. Cisco ASA Server must be configured as a RADIUS client in Internet Authentication

Service (IAS) or Network Policy Server (NPS).

Page 6: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 2

Configuration

Configure Cisco ASA Web VPN for Two Factor Authentication

Configuring the Cisco Secure ASA consists of 4 steps:

Step 1: Define a RADIUS enabled AAA Server group.

Step 2: Assign a RADIUS AAA Server to the AAA Server group.

Step 3: Assign RADIUS Authentication to a Clientless SSL VPN Connection Profile

Step 4: Assign RADIUS Authentication to a IPSec VPN Connection Profile

Define a RADIUS enabled AAA Server group

1. In the Cisco ASDM client select

Configuration.

2. Select Remote Access VPN.

3. Under Remote Access VPN expand

AAA/Local Users then select AAA Server

Group.

Page 7: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 3

4. Select Add in the AAA Server Group

section. Enter the Server Group name

and RADIUS as the Protocol.

Assigning a RADIUS AAA Server to the AAA Server group

1. Under Remote Access VPN expand

AAA/Local Users, AAA Server Group

then on the right highlight the

CRYPTOCard Group.

2. In the “Servers in the Selected

Group” section select Add.

3. Enter the following information

o Choose the interface

o IP address of the BlackShield ID

Pro enabled IAS/NPS agent.

o RADIUS authentication port (1812)

o RADIUS accounting port (1813)

o Server Secret Key (Shared Secret)

Page 8: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 4

4. After adding the AAA Server to the

AAA Server group, you will see it

appear in the AAA Servers in the

selected group section.

Assigning CRYPTOCard Authentication to a Clientless SSL VPN Connection

Profile

The Clientless SSL VPN Connection Profiles include the type of authentication method used

during the negotiation of a VPN connection. To allow CRYPTOCard authentication a RADIUS

enabled profile must be created.

1. In the Cisco ASDM client select

Configuration, Remote Access

VPN.

2. Expand Clientless SSL VPN

Access and highlight Connection

Profiles.

3. In Connection Profiles select

Add.

Page 9: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 5

4. Enter a name for the profile.

5. Under Authentication select

AAA.

6. In the AAA Server Group

dropdown select CRYPTOCard.

7. Complete the additional entries

with the settings required by

your organization.

8. Verify the CRYPTOCard profile is enabled. If required, disable the other Connection

Profiles.

Assigning CRYPTOCard Authentication to a IPSec VPN Connection Profile

The IPSec VPN Connection Profiles include the type of authentication method used during

the negotiation of a VPN connection. To allow CRYPTOCard authentication a RADIUS

enabled profile must be created.

1. In the Cisco ASDM client select

Configuration, Remote Access

VPN.

2. Expand Network (Client) Access

and highlight Connection

Profiles.

Page 10: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 6

3. In Connection Profiles select

Add.

4. Enter a name for the profile.

5. Under Authentication select

AAA.

6. In the AAA Server Group

dropdown select CRYPTOCard.

7. Complete the additional entries

with the settings required by

your organization.

8. Verify the CRYPTOCard profile is enabled. If required, disable the other Connection

Profiles.

Page 11: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 7

Troubleshooting

When troubleshooting RADIUS authentication issues refer to the logs on the Cisco ASA

device.

All logging information for Internet Authentication Service (IAS) or Network Policy Server

(NPS) can be found in the Event Viewer.

All logging information for the BlackShield IAS\NPS agent can be found in the \Program

Files\CRYPTOCard\BlackShield ID\IAS Agent\log directory.

The following is an explanation of the logging messages that may appear in the event

viewer for the Internet Authentication Service (IAS) or Network Policy Server (NPS) RADIUS

Server.

Error

Message:

Packet DROPPED: A RADIUS message was received from an invalid RADIUS

client.

Solution: Verify a RADIUS client entry exists on the RADIUS server.

Error

Message:

Authentication Rejected: Unspecified

Solution: This will occur when one or more of the following conditions occur:

• The username does not correspond to a user on the BlackShield

Server.

• The CRYPTOCard password does not match any tokens for that user.

• The shared secret entered in Cisco Secure ACS does not match the

shared secret on the RADIUS server

Page 12: Cisco Asa Black Shield ID

BlackShield ID Implementation guide for Cisco ASA (ASDM v6.1) 8

Error

Message:

Authentication Rejected: The request was rejected by a third-party extension

DLL file.

Solution: This will occur when one or more of the following conditions occur:

• The BlackShield Agent for IAS\NPS cannot contact the BlackShield

Server.

• The Pre-Authentication Rules on the BlackShield server do not allow

incoming requests from the BlackShield Agent for IAS\NPS.

• The BlackShield Agent for IAS\NPS Keyfile does not match the Keyfile

stored on the BlackShield Server.

• The username does not correspond to a user on the BlackShield

Server

• The CRYPTOCard password does not match any tokens for that user.

Further Information

For further information, please visit http://www.cryptocard.com


Recommended