User Guide for the Cisco Secure Access Control System 5.0
Preface
Downloads: This chapterpdf (PDF - 129.0KB) The complete bookPDF (PDF - 12.93MB) | Feedback

Preface

Table Of Contents

Preface

Audience

Document Organization

Document Conventions

Documentation Updates

Notices

OpenSSL/Open SSL Project

License Issues

Obtaining Documentation and Submitting a Service Request


Preface


Last Update: 11/24/10

This guide describes how to use Cisco Secure Access Control System (ACS) 5.0.

Audience

This guide is for security administrators who use ACS, and who set up and maintain network and application security.

Document Organization

This guide contains the following chapters:

Chapter 1, "Introducing ACS 5.0"

Chapter 2, "Migrating From ACS 4.x to ACS 5.0"

Chapter 3, "ACS 5.0 Policy Model"

Chapter 4, "Common Scenarios Using ACS"

Chapter 5, "Understanding My Workspace"

Chapter 6, "Managing Network Resources"

Chapter 7, "Managing Users and Identity Stores"

Chapter 8, "Managing Policy Elements"

Chapter 9, "Managing Access Policies"

Chapter 10, "Monitoring and Reporting"

Chapter 11, "Managing Reports in the Monitoring & Report Viewer"

Chapter 12, "Monitoring & Report Viewer Troubleshooting"

Chapter 13, "Monitoring & Report Viewer System Operations"

Chapter 14, "Managing System Administrators"

Chapter 15, "Configuring System Operations"

Chapter 16, "Managing System Administration Configurations"

Chapter 17, "Understanding Logging"

Chapter 18, "Using the Web Interface"

Appendix A, "AAA Protocols"

Appendix B, "Authentication in ACS 5.0"

Document Conventions

This guide uses the convention whereby the symbol ^ represents the key labeled Control. For example, the key combination ^z means hold down the Control key while you press the key.

Command descriptions use these conventions:

Examples that contain system prompts denote interactive sessions, indicating the commands that you should enter at the prompt. The system prompt indicates the current level of the EXEC command interpreter. For example, the prompt Router> indicates that you should be at the user level, and the prompt Router# indicates that you should be at the privileged level. Access to the privileged level usually requires a password.

Commands and keywords are in boldface font.

Arguments for which you supply values are in italic font.

Elements in square brackets ([ ]) are optional.

Alternative keywords of which you must choose one are grouped in braces ({}) and separated by vertical bars (|).

Examples use these conventions:

Terminal sessions and sample console screen displays are in screen font.

Information you enter is in boldface screen font.

Nonprinting characters, such as passwords, are in angle brackets (< >).

Default responses to system prompts are in square brackets ([]).

An exclamation point (!) at the beginning of a line indicates a comment line.


Caution Means reader be careful. You are capable of doing something that might result in equipment damage or loss of data.


Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.



Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph.



Note Means reader take note. Notes identify important information that you should reflect upon before continuing, contain helpful suggestions, or provide references to materials not contained in the document.


Documentation Updates

lists the updates that are made to the User Guide for the Cisco Secure Access Control System 5.0.

Table 1 Updates to the User Guide for the Cisco Secure Access Control System 5.0

Date
Description

11/24/2010

Updated "Manual PAC Provisioning" section on page B-22 for the bug CSCtj42714.

12/22/2009

Updated Configuring External Policy Servers section.

10/08/2009

Resolved caveat for Release 5.0:

CSCtb85096

Included the ports to be open in firewalls. For more information, see Table 15-1.

Added a note in the Understanding Full replication section.


Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.