Table Of Contents
Release Notes for Cisco Secure ACS for Windows 4.0
Full Build Number: 18.104.22.168
These release notes pertain to Cisco Secure Access Control Server for Windows, hereafter referred to as ACS version 4.0.
Note The ACS release numbering system for software includes major release, minor release, maintenance build, and interim build number in the MMM.mmm.###.BBB format. For this release, the versioning information is Cisco Secure ACS 22.214.171.124. Elsewhere in this document where 4.0 is used, we are referring to 4.0.1. ACS major release numbering starts at 4.0.1, not 4.0.0. Use this information when working with your customer service representative.
These release notes provide:
System requirements are documented in the Installation Guide for Cisco Secure ACS for Windows. For documentation updates after publication, see Documentation Updates.
See the Supported and Interoperable Devices and Software Tables for Cisco Secure ACS for Windows on Cisco.com.
Upgrading to a New Software Release
ACS New Features
ACS contains the following new and changed features:
•Network Admission Control (NAC) Release 2.0 support—ACS acts as a policy-decision point in NAC deployments. Using configurable policies, it evaluates the credentials received from the Cisco Trust Agent, determines the state of the host, and sends a per-user authorization to the network access device: access control lists (ACLs), a policy-based ACL, or a private VLAN assignment. Evaluation of the host credentials can enforce many specific policies, such as OS patch level and antivirus DAT file version. ACS records the policy evaluation results for use with your monitoring system. ACS also allows hosts without the appropriate agent technology to be audited by third-party audit vendors before granting network access. ACS policies can be extended with external policy servers to which ACS forwards credentials. For example, credentials specific to an antivirus vendor can be forwarded to the vendor's antivirus policy server, and audit policy requests can be forwarded to audit vendors.For more information about the new ACS features to support NAC 2.0, see Support for NAC 2.0
•Increased number of supported devices—ACS can now support up to 35,000 devices.
•Profile-based authentication and authorization—A new feature called network access profiles allows administrators to classify access requests according to network location, membership in a network device group, protocol type, or other specific RADIUS attribute values sent by the network device through which the user connects. Authentication, access control, posture validation and authorization policies can be mapped to specific profiles. An example of a profile-based policy is the ability to apply a different access policy for wireless access versus remote (VPN) access.
•New storage infrastructure— ACS now uses a SQL database to store all the user and configuration information. The new ACS internal database improves scaling and performance and is less reliant on the Windows Registry. The Windows Registry will be used only for application information. A new database password is required during installation. The password is stored in the Windows registry using Microsoft Crypto API. The database is encrypted using a hash of customer-provided password and an internal password. You can use CSUtil to change the password.
•LDAP improvements—ACS caches successful external authentications (using LDAP), allowing it to immediately look up a user during re-authentication. ACS provides improved SSL support. See LDAP Improvements, for more information.
•Japanese browser support—Supports administration of ACS by using MS Internet Explorer 6.0 SP1 and Netscape Communicator 8.0.4 with Sun Java JRE 1.5.0, or MS Internet Explorer 6.0 SP1 with Microsoft Java Virtual Machine, installed on Japanese Windows Operating System (JOS). This feature will be supported for entering data in English (not Japanese).
•TACACS+ and RADIUS key support at group level—Ability to set a shared secret at the group level (Network Device Group).
•Purging capability for cached users in ACS—Ability to remove dynamically saved users from the ACS database via User Setup.
–Support for the Microsoft Windows Callback feature.
–Ability for external users to authenticate via an enable password.
–Certificate revocation list checking during EAP-TLS authentication.
•Online Help - The online documentation, Cisco Secure ACS for Windows User Guide, opens in a separate window. The online help contains a search button and capability to open a PDF version of the user guide.
•NTLM Support - ACS can now operate with NTLM v1, NTLM v2 (with appropriate Microsoft patches), and LAN Manager (if you require it).
•External Novell NDS Database Support - Support for group mappings for external Novell NDS databases is now done by using generic LDAP group set mappings.
•Extended replication support—Administrators can now replicate network access profiles and all related configuration, including:
–Posture validation settings
–AAA clients and hosts
–External database configuration
–Global authentication configuration
–Network device groups
–Shared profile components
–Additional logging attributes
•Machine Access Restrictions (MAR) Exemption Lists—You can specify which groups are allowed access to the network; regardless of whether they pass machine authentication. A MAR exemption list can be configured for specific user groups (for example, managers and administrators).
•RADIUS Authorization Component (RAC) support—Includes RADIUS authorization components as a new type of shared profile component. Shared RACs contain groups of RADIUS attributes that you can dynamically assign to user sessions based on a policy.
•Support of additional Cisco hardware devices—ACS 4.0 includes support for Cisco wireless LAN controllers and Cisco adaptive security appliances.
Support for NAC 2.0
The following features support NAC 2.0:
•EAP-FAST Version 1a support for NAC phase 2—Supports an authenticated tunnel (by using the server certificate) inside of which the provisioning of PACs will occur. EAP types supported inside the tunnel include: EAP-GTC, EAP-MSCHAPv2, and EAP-TLS.
•Agentless host support— Support for Cisco and third-party Audit Servers that determine posture information about a client, without relying on the presence of a NAC-compliant Posture Agent (PA). These types of clients are also referred to as NAC Agentless Hosts (NAH).
•Linux packages support in posture validation—Supports Linux packages for the Cisco:Host plugin. The following extended attributes are available for Linux packages: Cisco:Host:Package:Version and Cisco:Host:Package:Version-String. For additional details, see Support for Linux Packages in Posture Validation.
–Support for an external audit server which determines posture information about a host without relying on the presence of a Posture Agent (PA).
–Posture validation no longer requires NAC databases to verify compliance. You can choose from three options for validation: internal policies located in ACS, policies defined on external servers, and policies defined on audit servers for NAC agentless hosts.
–Authorization for posture validation is now configured within the Network Access Profiles feature. Posture validation no longer requires special authorization rules.
–Changes have been made to optimize posture validation. In previous versions, ACS requested all the credentials by using the type-length-value (TLV) protocol. ACS has been optimized to request only the attributes that are required to evaluate posture validation.
The ACS authentication and authorization service CSAuth supports multithreading to authenticate with the LDAP external database. Multiple users can simultaneously be searched and authenticated against the LDAP server(s).
LDAP over SSL now includes the option to authenticate by using certificate database files other than the Netscape cert7.db file. This new option uses the same mechanism as other SSL installations in the ACS environment.
When ACS checks authentication and authorization of a user on the LDAP server, it uses a connection with LDAP administrator account permissions to search for the user and for the users groups on the directory subtree. ACS keeps those administrator connections open for successive use. It is possible to limit the maximum number of concurrent administrator connections per generic LDAP external database configuration (primary and secondary).
After an LDAP user is successfully authenticated to the LDAP external database, its distinguished name (DN) on the LDAP server is cached in ACS. The cached DN is used during next authentication request of the user to save search time.
Support for Linux Packages in Posture Validation
ACS 4.0 supports Linux packages for the Cisco:Host plugin. The following extended attributes are available for Linux packages:
The following Linux packages are supported:
You can add or remove packages by using the CSUtil tool.
Extended attributes are only supported as descendants of the Cisco:Host application.
The following product documentation is available on ACS:
Table 1 Product Documentation
Document Title Description
Release Notes for Cisco Secure ACS for Windows
New features, documentation updates, known problems, and resolved problems. Available on Cisco.com:
Installation Guide for Cisco Secure ACS for Windows
Details on installation and upgrade of ACS software and post-installation tasks. Available in the following formats:
•PDF on the ACS Recovery CD-ROM.
•Orderable; see Obtaining Documentation.
Product online help.
Help topics for all pages in the ACS web interface. Select an option from the ACS menu; the help appears in the right pane.
User Guide for Cisco Secure ACS for Windows
ACS functionality and procedures for using the ACS features. Available in the following formats:
•You can also access the user guide by clicking Online Documentation in the ACS navigation menu. The user guide PDF is available on this page by clicking View PDF.
•PDF on the ACS Recovery CD-ROM.
•Orderable; see Obtaining Documentation.
Supported Devices and Interoperable Software Tables for Cisco Secure ACS for Windows
Supported devices and firmware versions for all ACS features. Available on Cisco.com:
Installation and User Guide for Cisco Secure ACS for User-Changeable Passwords
Installation and user guide for the user-changeable password add-on. Available on Cisco.com:
The following installation notes are of importance:
•ACS will not install properly if a Sybase server is installed on the same machine.
•Remote installations performed by using Windows Terminal Services are not tested and are not supported. We recommend that you disable Terminal Services while performing any installation or upgrade. Virtual Network Computing (VNC) has been tested successfully.
See the Installation Guide for Cisco Secure ACS for Windows for installation, upgrade, and uninstall instructions, as well as post-installation tasks. For post-installation tasks, see Post-Upgrade Configuration.
ACS 4.0 supports these upgrade and migration paths:
Note To upgrade to version 4.0 from a version earlier than 3.2.3, upgrade to one of the supported upgrade versions, which are listed in this section, and then upgrade to ACS 4.0.
Supported Upgrade Path
ACS supports the following upgrade paths. These paths have been tested and are supported:
•Cisco Secure ACS for Windows, release 3.3.3 to ACS 4.0
•Cisco Secure ACS for Windows, release 3.3.2 to ACS 4.0
•Cisco Secure ACS for Windows, release 3.3.1 to ACS 3.3.3, then to ACS 4.0
•Cisco Secure ACS for Windows, release 3.2.3 to ACS 4.0
•Cisco Secure ACS for Windows, release 3.2.2 to ACS 3.3, then to ACS 4.0
•Cisco Secure ACS for Windows, release 3.2.1 to ACS 3.3, then to ACS 4.0
•Cisco Secure ACS for Windows, release 3.1.2 to ACS 3.3, then to ACS 4.0
•Cisco Secure ACS for Windows, release 3.0.4 to ACS 3.3, then to ACS 4.0
Note If you are upgrading to ACS 3.3.3 and do not have access to that software, review the README text for details on the upgrade procedure.
Supported Migration Path
ACS supports the migration path from ACS 3.1.2 to ACS 3.3.3 to ACS 4.0. This path has been tested and is supported.
Unsupported Migration Path
ACS does not support the following migration paths. These paths have not been tested and are not supported. See the tested and supported paths for migration at Supported Migration Path.
•ACS 3.2.3 to ACS 3.3.3 to ACS 4.0
•Prior to ACS 3.2.3 to ACS 3.3.x to ACS 4.0
The following section contains information about post-upgrade configuration:
•After upgrading to ACS 4.0, you may need to perform additional configuration steps to successfully use ACS and Network Access Profiles (NAP). If you used NAC in ACS 3.3, ACS will not operate in an identical manner in ACS 4.0. For example, you must create a new set of authorization rules for Network Access Profiles that are created during the upgrade process.
•If you used ACS 3.xODBC logging and upgraded to ACS 4.0, preserving your data, you must update the ODBC tables so that the SQL tables continue to work.
For details on how to complete post-installation tasks, see the Installation Guide for Cisco Secure ACS for Windows.
Upgrading From Version 3.3
The following actions are performed automatically when you upgrade from ACS 3.3 to ACS 4.0:
1. Local and external posture policies are automatically transformed.
2. A single Network Access Profile, (configured for NAC only) is created as a process of the upgrade.
3. Each instance of the selected ACS 3.3 Network Posture Validation Database will automatically be transformed into a posture validation rule. All the rules will be associated with the NAP that was created (in step 2). All PA message and URL redirects are mapped correspondingly.
4. A RADIUS Authorization Component will be created for each mapped group. ACS populates the RAC with all attributes that were configured in the user or group setup menus, except for the posture-token Cisco-av-pair. Since the posture-token Cisco-av-pair attribute is generated dynamically at runtime, by ACS, there is not need to configure it manually.
5. If you manually added posture validation attributes in ACS 3.3, they will added to the ACS version 4.0 posture dictionary during the upgrade.
Limitations and Restrictions
The following limitations and restrictions apply to ACS 4.0.
•User/Machine Out-of-Band PAC Provisioning for EAP-FAST v1a has not been tested. The Out-of-band provisioning feature was not tested since the MDC (meetinghouse) supplicant does not support it. (CSCsb46242)
•The TACACs+ and LEAP protocols for Network Access Profiles are not supported in ACS version 4.0.
•Network device limitation will support up to 35,000 devices.
•Installation on Japanese Windows 2000 SP4 or Japanese Windows 2003 SP1 is not supported.
ACS has not been tested for interoperability with other Cisco software. Other than for the software and operating system versions listed in this document, Cisco performed no interoperability testing. Using untested software with ACS may cause problems. For the best performance of ACS, Cisco recommends that you use the versions of software and operating systems in the Supported and Interoperable Devices and Software Tables for Cisco Secure ACS for Windows on Cisco.com.
Tested Windows Security Patches
Cisco Systems officially supports and encourages the installation of all Microsoft security patches for Windows 2000 Server and Windows Server 2003 as used for ACS for Windows.
Cisco experience has shown that these patches do not cause any problems with the operation of ACS for Windows. If the installation of one of these security patches does cause a problem with ACS, please contact Cisco TAC and Cisco will resolve the problem as quickly as possible.
ACS for Windows has been tested with the Windows Server 2003 patches documented in the following Microsoft Knowledge Base Articles:
ACS has been tested with the Windows 2000 Server patches documented in the following Microsoft Knowledge Base Articles:
Cisco issues a security advisory when security issues directly impact its products and require action to repair. For the list of security advisories for Cisco Secure on Cisco.com, see the Cisco Security Advisory: Multiple Vulnerabilities in Cisco Secure Access Control Server at:
The following problems are known to exist in this release:
Cisco AAA Client Problems
Refer to the appropriate release notes for information about Cisco AAA client problems that might affect the operation of ACS. You can access these release notes online at Cisco.com. For NAC-specific client problems, go to http://www.cisco.com/go/nac.
Known Microsoft Problems
Due to a defect in the Microsoft PEAP supplicant provided in the Windows XP Service Pack 2, the PEAP supplicant cannot reauthenticate successfully with ACS. Cisco has opened case SRX040922603052 with Microsoft on this issue. Customers who are affected by this problem should open a case with Microsoft and reference this case ID. Microsoft has prepared hotfix KB885453, which resolves the issue.
When ACS runs on a domain controller and you need to authenticate users with a Windows user database, you must take additional configuration steps; see the Installation Guide for Cisco Secure ACS for Windows, 4.0 for post-installation steps regarding NTLM. A Microsoft hotfix may be required, depending on your configuration.
Known Problems with ACS 4.0
Table 2 contains problems known to exist in ACS 4.0.
Table 3 contains the problems from the ACS 4.0 release that are resolved. Check the Bug Navigator on Cisco.com for any resolved bugs that may not appear here.
The following errors exist in the ACS online help:
•The ACS documentation and short help indicate that you can disable the dynamic user cache, which is incorrect.
•The information in the Accounting Logs in the ACS Online Help contains an error. It should read:
By default, these logs are available in CSV format, with the exception of the Passed Authentications log. You can also configure ACS to export the data for these logs to an ODBC-compliant relational database that you configure to store the log data.
The note for Passed Authentications in the Accounting Log Descriptions table is incorrect and should be disregarded.
The corresponding information in the ACS documentation on Cisco.com is correct.
•The information for the url-redirect-acl variable in the Cisco Secure ACS User Guide for Windows Network Access Profiles chapter is incorrect. The url-redirect-acl value can only be the switch ACL name. A number is not acceptable.
•The short help for the External Posture Validation Audit Server Setup incorrectly states:You then configure posture validation credentials that a NAC Agentless Host (NAH) forwards to the primary audit server or, in a failover scenario, to the secondary audit server.
However, you cannot configure the posture validation credentials that a NAH forwards. The sentence is correct only for NAC external posture validation servers, and not for Audit Servers.
•The minimum Microsoft IIS version required for the User Changeable Password (UCP) Web Server for ACS for Windows Server is Microsoft IIS 5.0. The information as correct in the Installation and User Guide for Cisco Secure ACS User-Changeable Passwords; however, Table 1-3 of the Installation Guide for Cisco Secure ACS for Windows contains an error.
•In the section on ACS Attributes and Action Codes, it incorrectly states:TACACS Attributes: 160, 162RADIUS Attributes 170, 173
It should read the other way around:RADIUS Attributes: 160, 162TACACS Attributes 170, 173
•In the section on downloadable IP ACLs, it incorrectly states that the description of a new IP ACL can be up to 30000 characters. The maximum number of characters allowed in the Description field is 1006 characters.
•Omissions from ACS documentation include:
–We do not support distributed ACS deployments in a NAT environment. If a primary or secondary address is in NAT format, the database replication file will indicate shared secret mismatch. The next release of the documentation will address this omission.
–The Logged-In Users report takes up to 20 seconds to open. All other reports are opened instantly when selected. Specific user information takes several minutes to appear; see CSCsb74228.
–LEAP is not supported when working with Network Access Profiles. You can use LEAP only if your system is operating in legacy ACS mode.
–The ODBC Passed Authentications is not documented in the short help file in the System Configuration > Logging Configuration page. You can click this option to enable and configure ACS to generate an ODBC log of successful login attempts.
–When creating a package.cab file that is larger than 2GB, additional .cab files are created due to the size limit of the packer. The sequence is as follows: the first package name is: package.cab, the second: package1.cab, and so on, until the N package: packageN.cab, where N is the number of packages minus one. The files are saved in the same location that is specified before the packing begins. These files are not stand-alone and all of them must be sent to package. Problems with the packed file (package.cab) may arise if there is not enough hard-disk space.
–The backup procedure does not back up the cert7.db file. If you use this certificate file with an LDAP database, we recommend that you back it up on a remote machine for disaster recovery. When you migrate from an ACS server to ACS appliance, move the cert7.db to a ftp server and download according to the normal provisioning instructions. When you upgrade an ACS appliance, repeat the download procedure as oringinally used to provision the original appliance.
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at firstname.lastname@example.org or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to email@example.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you can perform these tasks:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — firstname.lastname@example.org
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered non-emergencies.
•Non-emergencies — email@example.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
This document is to be used in conjunction with the documents listed in the Documentation Guide for Cisco Secure ACS for Windows document.