Deployment considerations, C h a p t e r, Chapter 2, “deployment considerations – Cisco 3.3 User Manual

Page 77

Advertising
background image

C H A P T E R

2-1

User Guide for Cisco Secure ACS for Windows Server

78-16592-01

2

Deployment Considerations

Deployment of Cisco Secure ACS for Windows Server can be complex and
iterative, depending on the specific implementation required. This chapter
provides insight into the deployment process and presents a collection of factors
that you should consider before deploying Cisco Secure ACS.

The complexity of deploying Cisco Secure ACS reflects the evolution of AAA
servers in general, and the advanced capabilities, flexibility, and features of
Cisco Secure ACS in particular. AAA was conceived originally to provide a
centralized point of control for user access via dial-up services. As user databases
grew and the locations of AAA clients became more dispersed, more capability
was required of the AAA server. Regional, and then global, requirements became
common. Today, Cisco Secure ACS is required to provide AAA services for
dial-up access, dial-out access, wireless, VLAN access, firewalls, VPN
concentrators, administrative controls, and more. The list of external databases
supported has also continued to grow and the use of multiple databases, as well as
multiple Cisco Secure ACSes, has become more common. Regardless of the
scope of your Cisco Secure ACS deployment, the information contained in this
chapter should prove valuable. If you have deployment questions that are not
addressed in this guide, contact your Cisco technical representative for assistance.

This chapter contains the following topics:

Basic Deployment Requirements for Cisco Secure ACS, page 2-2

Basic Deployment Factors for Cisco Secure ACS, page 2-6

Suggested Deployment Sequence, page 2-19

Advertising