Home > Articles > Certification > Cisco Certification > CCNP Security / CCSP

This chapter is from the book

This chapter is from the book

CCSP Self-Study: Securing Cisco IOS Networks (SECUR)CCSP Self-Study: Securing Cisco IOS Networks (SECUR)

Learn More Buy

This chapter is from the book

This chapter is from the book

CCSP Self-Study: Securing Cisco IOS Networks (SECUR)CCSP Self-Study: Securing Cisco IOS Networks (SECUR)

Learn More Buy

TACACS+ Overview

TACACS+ is an improved version of TACACS. TACACS+ forwards username and password information to a centralized security server. Figure 3-11 shows a typical TACACS+ topology.

Figure 11Figure 3-11 General Features

General Features

TACACS+ has the following features:

  • TCP packets for reliable data transport—TACACS+ uses TCP as the communication protocol between the remote client and security server.

    • —Supports the AAA architecture

  • Link is encrypted—The data payload of IP packets (TCP packets) is encrypted for security and is stored in encrypted form in the remote security database.

    • —Supports PAP, CHAP, and MS-CHAP authentication

    • —Useful for both LAN and WAN security

  • Serial Line Internet Protocol (SLIP), PPP, and ARA supported for dialup security—SLIP is TCP/IP over direct connections and modems, which allows one computer to connect to another or to a whole network. PPP is more robust than SLIP, supporting multiple protocols with built-in security. ARA provides to Macintosh users direct access to information and resources at a remote AppleTalk site. TN3270 and X.121 addresses used with X.25 are also supported.

    • —Auto-command supported

    • —Callback supported

    • —Per-user access lists can be assigned in authorization phase

There are at least three versions of TACACS:

  • TACACS—An industry-standard protocol specification (RFC 1492) that forwards username and password information to a centralized server. The centralized server can be either a TACACS database or a database such as the UNIX password file with TACACS protocol support. For example, the UNIX server with TACACS passes requests to the UNIX database and sends an accept or reject message back to the access server.

  • XTACACS—Defines the extensions that Cisco added to the TACACS protocol to support new and advanced features. XTACACS is multiprotocol and can authorize connections with SLIP, PPP (IP or Internet Packet Exchange [IPX]), ARA, EXEC, and Telnet. XTACACS supports multiple TACACS servers, syslog for sending accounting information to a UNIX host, connects where the user is authenticated into the access server "shell," and can Telnet or initiate SLIP, PPP, or ARA after initial authentication. XTACACS is essentially obsolete concerning Cisco AAA features and products.

  • TACACS+—Enhanced and continually improved version of TACACS that allows a TACACS+ server to provide the services of AAA independently. Each service can be tied into its own database or can use the other services available on that server or on the network. TACACS+ was introduced in Cisco IOS Release 10.3. This protocol is a completely new version of the TACACS protocol referenced by RFC 1492 and developed by Cisco. It is not compatible with XTACACS. TACACS+ has been submitted to the IETF as a draft proposal.

The rich feature set of the TACACS+ client/server security protocol is fully supported in Cisco Secure ACS for Windows software.

The first steps in configuring the router are as follows:

Step 1

 

Enable TACACS+.

Step 2

 

Specify the list of Cisco Secure ACS for Windows servers that will provide AAA services for the router.

Step 3

 

Configure the encryption key that is used to encrypt the data transfer between the router and the Cisco Secure ACS for Windows server.


The aaa new-model command forces the router to override every other authentication method previously configured for the router lines. If an administrative Telnet or console session is lost while enabling AAA on a Cisco router, and no enable password is specified, the administrator may be locked out of the router and may need to perform the password-recovery process specific to that router to regain access to the device.

CAUTION

When using the Cisco IOS aaa new-model command, always provide for an enable password login method. This guards against the risk of being locked out of the router if the administrative session fails while you are in the process of enabling AAA, or if the TACACS+ server becomes unavailable.

Configuring TACACS+

When configuring a NAS to support AAA, as shown in Figure 3-12, at a minimum the following commands should be entered, in the order shown:

Router(config)# aaa new-model
Router(config)# aaa authentication login default tacacs+ enable

Figure 12Figure 3-12 Globally Enabling AAA

Specifying the "enable" authentication method enables you to reestablish your Telnet or console session and use the enable password to access the router once more. If you fail to do this, and you become locked out of the router, physical access to the router is required (console session), with a minimum of having to perform a password-recovery sequence. At worst, the entire configuration saved in nonvolatile random-access memory (NVRAM) can be lost.

To begin global configuration, enter the following commands, using the correct IP address of the Cisco Secure ACS for Windows servers and your own encryption key:

router(config)# tacacs-server key 2bor!2b@?
router(config)# tacacs-server host 10.1.2.4

Or use the following:

router(config)# tacacs-server host 10.1.2.4 key 2bor!2b@?

In this example, the 2bor!2b@? key is the encryption key that is shared between the router and the Cisco Secure ACS for Windows server. The encryption key you choose for your environment should be kept secret to protect the privacy of passwords that are sent between the Cisco Secure ACS for Windows server and the router during the authentication process.

When configuring a TACACS+ key for use on multiple TACACS+ servers, remember that the key must be the same for all TACACS+ servers listed for a given router.

You can specify multiple Cisco Secure ACS for Windows servers by repeating the tacacs-server host command.

After you enable AAA globally on the access server, define the authentication method lists, and then apply them to lines and interfaces. These authentication method lists are security profiles that indicate the protocol (ARAP or PPP) or login and authentication method (TACACS+, RADIUS, or local authentication).

To define an authentication method list using the aaa authentication command, complete the following steps:

Step 1

 

Specify the dial-in protocol (ARAP, PPP, or NetWare Access Server Interface [NASI]) or login authentication.

Step 2

 

Identify a list name or default. A list name is any alphanumeric string you choose. You assign different authentication methods to different named lists. You can specify only one dial-in protocol per authentication method list. However, you can create multiple authentication method lists with each of these options. You must give each list a different name.

Step 3

 

Specify the authentication method. You can specify up to four methods. For example, you could specify TACACS+, followed by local. This would permit you to log in with a local username and password in case a TACACS+ server is not available on the network.

After defining these authentication method lists, apply them to one of the following:

  • Lines—tty lines or the console port for login and asynchronous lines (in most cases) for ARA

  • Interfaces—Interfaces (synchronous or asynchronous) configured for PPP

Use the aaa authentication command, as described in Chapter 2, in global configuration mode to enable AAA authentication processes.

The NAS configuration in Example 3-1 shows only commands important to AAA security.

Example 3-1 Important AAA Security Commands

aaa new-model
aaa authentication login default tacacs+ enable
aaa authentication ppp default tacacs+
aaa authorization exec tacacs+
aaa authorization network tacacs+
aaa accounting exec start-stop tacacs+
aaa accounting network start-stop tacacs+
enable secret 5 $1$x1EE$33AXd2VTVvhbWL0A37tQ3.
enable password 7 15141905172924
!
username admin password 7 094E4F0A1201181D19
!
interface Serial2
 ppp authentication pap
!
tacacs-server host 10.1.1.4
tacacs-server key ciscosecure
!
line con 0
 login authentication no_tacacs

Referring to this configuration, the meanings of the configuration entries are as follows:

  • aaa new-model—Enables the AAA access control model. Use of the no form of this command disables this functionality. You can subsequently restore previously configured AAA commands by reissuing the command.

You could use the aaa authentication login default tacacs+ enable command to specify that if your TACACS+ server fails to respond, you can log in to the access server by using your enable password. If you do not have an enable password set on the router, you will not be able to log in to it until you have a functioning TACACS+ UNIX daemon or Windows NT or Windows 2000 server process configured with usernames and passwords. The enable password in this case is a last-resort authentication method. You also can specify none as the last-resort method, which means that no authentication is required if all other methods failed.

  • aaa authentication login default tacacs+ enable—Sets AAA authentication at login using the default list against the TACACS+ server. For this code, the enable password would be used if the TACACS+ server became unavailable.

  • aaa authentication ppp default tacacs+—Sets AAA authentication for PPP connections using the default list against the TACACS+ database.

  • aaa authorization exec tacacs+—Sets AAA authorization to determine if the user is allowed to run an EXEC shell on the NAS against the TACACS+ database.

  • aaa authorization network tacacs+—Sets AAA authorization for all network-related service requests, including SLIP, PPP, PPP NCPs, and ARA protocols, against the TACACS+ database. The TACACS+ database and the NAS must be configured to specify the authorized services.

  • aaa accounting exec start-stop tacacs+—Sets AAA accounting for EXEC processes on the NAS to record the start and stop time of the session against the TACACS+ database.

  • aaa accounting network start-stop tacacs+—Sets AAA accounting for all network-related service requests, including SLIP, PPP, PPP NCPs, and ARA protocols, to record the start and stop time of the session against the TACACS+ database.

  • username admin password 7 094E4F0A1201181D19—Sets a username and password in the local security database for use with the aaa authentication local-override command.

NOTE

This command shows the password after it has been encrypted, as it would be shown in a display of the router's configuration as a result of the service password-encryption command. The password would be entered as clear text and Cisco IOS would take care of the encryption.

  • ppp authentication pap—Sets PPP authentication to use PAP, CHAP, or both CHAP and PAP. MS-CHAP could also be specified. The ppp authentication if-needed command causes the NAS to not perform CHAP or PAP authentication if the user has already provided authentication. This option is available only on asynchronous interfaces.

  • tacacs-server host 10.1.1.4—Provides the IP address of the TACACS+ server.

  • tacacs-server key ciscosecure—Provides the shared-secret key that authenticates the router on the TACACS+ server. This password permits AAA communications between the router and the TACACS+ server.

The following are the first steps in configuring the router:

Step 1

 

Enable TACACS+.

Step 2

 

Specify the list of Cisco Secure ACS for Windows servers that will provide AAA services for the router.

Step 3

 

Configure the encryption key that is used to encrypt the data transfer between the router and the Cisco Secure ACS for Windows server.

The tacacs-server command is described as follows:

  • tacacs-server host (hostname | ip-address)—Specifies the IP address or the host name of the remote TACACS+ server host. This host is typically a UNIX system running TACACS+ software.

  • tacacs-server key shared-secret-text-string—Specifies a shared secret text string used between the access server and the TACACS+ server. The access server and TACACS+ server use this text string to encrypt passwords and exchange responses. The shared key set with the tacacs-server key command is a default key to be used if a per-host key was not set. It is a better practice to set specific keys per tacacs-server host.

It is possible to configure TACACS+ without a shared key at both the client device (that is, NAS) and the security server (that is, Cisco Secure) if you do not want the connection to be encrypted. This might be useful for a lab or training environment but is strongly discouraged in a production environment.

NOTE

A router can have only one tacacs-server key command even though it might have multiple tacacs-server host commands to configure multiple TACACS+ servers for continuity of service. Therefore, the password that is assigned to the router on each of the TACACS+ servers must be identical and will be the password used in the tacacs-server key command on the router.

On the other hand, the TACACS+ server can communicate with multiple host routers, each of which can use a unique key. The TACACS+ server associates the key with the individual router identities in its database.

The following command specifies that the AAA authentication list called no_tacacs is to be used on the console:

line con 0
 login authentication no_tacacs

Verifying TACACS+

This section explains how to verify AAA TACACS+ operations using the following Cisco IOS debug commands:

debug aaa authentication
debug tacacs
debug tacacs events

Use the debug tacacs command on the router to trace TACACS+ packets and display debugging messages for TACACS+ packet traces.

The output listing below shows part of the debug aaa authentication command output for a TACACS login attempt that was successful. The information indicates that TACACS+ is the authentication method used.

14:01:17: AAA/AUTHEN (567936829): Method=TACACS+
14:01:17: TAC+: send AUTHEN/CONT packet
14:01:17: TAC+ (567936829): received authen response status = PASS
14:01:17: AAA/AUTHEN (567936829): status = PASS

Also, note that the AAA/AUTHEN status indicates that the authentication has passed.

There are three possible results of an AAA session:

  • Pass

  • Fail

  • Error

Pass is the desired output. If you see a Fail or Error result in the debug aaa authentication output, it could be the result of a configuration or hardware error. Check the configuration on the router first to make sure the TACACS+ server information is correct, and then check connectivity to the server. If you find no problems, it could indicate a misconfiguration of the TACACS+ server.

Troubleshooting follows a basic tenant—look for what changed last. If you made a configuration change and the AAA process quit working, double-check the configuration, going so far as to restore the configuration that you saved before making the change (You did do that, didn't you?) to see if AAA service is restored. If your router and AAA server have been communicating with no problems, no configuration changes have been made, and no new users have been added, then that points toward a hardware or circuit problem.

The next two sections examine the debug output for successful and failed attempts.

debug tacacs Command Example Output—Failure

Example 3-2 shows part of the debug tacacs command output for a TACACS+ login attempt that was unsuccessful as indicated by the status FAIL. The status fields are probably the most useful part of the debug tacacs command.

Example 3-2 debug tacacs Command Output for a TACACS Unsuccessful Login Attempt

13:53:35: TAC+: Opening TCP/IP connection to 10.1.1.4/49 
13:53:35: TAC+: Sending TCP/IP packet number 416942312-1 to 10.1.1.4/49
(AUTHEN/START)
13:53:35: TAC+: Receiving TCP/IP packet number 416942312-2 from 10.1.1.4/49
13:53:35: TAC+ (416942312): received authen response status = GETUSER
13:53:37: TAC+: send AUTHEN/CONT packet
13:53:37: TAC+: Sending TCP/IP packet number 416942312-3 to 10.1.1.4/49
(AUTHEN/CONT)
13:53:37: TAC+: Receiving TCP/IP packet number 416942312-4 from 10.1.1.4/49
13:53:37: TAC+ (416942312): received authen response status = GETPASS
13:53:38: TAC+: send AUTHEN/CONT packet
13:53:38: TAC+: Sending TCP/IP packet number 416942312-5 to 10.1.1.4/49
(AUTHEN/CONT)
13:53:38: TAC+: Receiving TCP/IP packet number 416942312-6 from 10.1.1.4/49 
13:53:38: TAC+ (416942312): received authen response status = FAIL
13:53:40: TAC+: Closing TCP/IP connection to 10.1.1.4/49

debug tacacs Command Example Output—Pass

Example 3-3 shows part of the debug tacacs command output for a TACACS login attempt that was successful, as indicated by the status PASS.

Example 3-3 debug tacacs Command Output for a TACACS Successful Login Attempt

14:00:09: TAC+: Opening TCP/IP connection to 10.1.1.4/49
14:00:09: TAC+: Sending TCP/IP packet number 383258052-1 to 10.1.1.4/49 (AUTHEN/START) 
14:00:09: TAC+: Receiving TCP/IP packet number 383258052-2 from 10.1.1.4/49
14:00:09: TAC+ (383258052): received authen response status = GETUSER
14:00:10: TAC+: send AUTHEN/CONT packet
14:00:10: TAC+: Sending TCP/IP packet number 383258052-3 to 10.1.1.4/49 (AUTHEN/CONT) 
14:00:10: TAC+: Receiving TCP/IP packet number 383258052-4 from 10.1.1.4/49
14:00:10: TAC+ (383258052): received authen response status = GETPASS 
14:00:14: TAC+: send AUTHEN/CONT packet
14:00:14: TAC+: Sending TCP/IP packet number 383258052-5 to 10.1.1.4/49 (AUTHEN/CONT) 
14:00:14: TAC+: Receiving TCP/IP packet number 383258052-6 from 10.1.1.4/49
14:00:14: TAC+ (383258052): received authen response status = PASS
14:00:14: TAC+: Closing TCP/IP connection to 10.1.1.4/49

debug tacacs events Output

Example 3-4 shows sample debug tacacs events command output.

Example 3-4 debug tacacs events Command Output

router# debug tacacs events
%LINK-3-UPDOWN: Interface Async2, changed state to up 
00:03:16: TAC+: Opening TCP/IP to 10.1.1.4/49 timeout=15 
00:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 10.1.1.4/49
00:03:16: TAC+: periodic timer started
00:03:16: TAC+: 10.1.1.4 req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (ESTAB)
expire=14 AUTHEN/START/SENDAUTH/CHAP queued 
00:03:17: TAC+: 10.1.1.4 ESTAB 3BD868 wrote 46 of 46 bytes 
00:03:22: TAC+: 10.1.1.4 CLOSEWAIT read=12 wanted=12 alloc=12 got=12 
00:03:22: TAC+: 10.1.1.4 CLOSEWAIT read=61 wanted=61 alloc=61 got=49 
00:03:22: TAC+: 10.1.1.4 received 61 byte reply for 3BD868 
00:03:22: TAC+: req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (CLOSEWAIT) expire=9 
AUTHEN/START/SENDAUTH/CHAP processed 
00:03:22: TAC+: periodic timer stopped (queue empty) 
continues
00:03:22: TAC+: Closing TCP/IP 0x48A87C connection to 10.1.1.4/49 
00:03:22: TAC+: Opening TCP/IP to 10.1.1.4/49 timeout=15 
00:03:22: TAC+: Opened TCP/IP handle 0x489F08 to 10.1.1.4/49 
00:03:22: TAC+: periodic timer started
00:03:22: TAC+: 10.1.1.4 req=3BD868 id=299214410 ver=192 handle=0x489F08 (ESTAB)
expire=14 AUTHEN/START/SENDPASS/CHAP queued 
00:03:23: TAC+: 10.1.1.4 ESTAB 3BD868 wrote 41 of 41 bytes 
00:03:23: TAC+: 10.1.1.4 CLOSEWAIT read=12 wanted=12 alloc=12 got=12 
00:03:23: TAC+: 10.1.1.4 CLOSEWAIT read=21 wanted=21 alloc=21 got=9 
00:03:23: TAC+: 10.1.1.4 received 21 byte reply for 3BD868 
00:03:23: TAC+: req=3BD868 id=299214410 ver=192 handle=0x489F08 (CLOSEWAIT) expire=13
AUTHEN/START/SENDPASS/CHAP processed 
00:03:23: TAC+: periodic timer stopped (queue empty)

In this example, the opening and closing of a TCP connection to a TACACS+ server are shown, and also the bytes read and written over the connection and the connection's TCP status.

The TACACS messages are intended to be self-explanatory or for consumption by service personnel only. However, the following two messages that may be shown require a brief explanation:

  • 00:03:16: TAC+: Opening TCP/IP to 10.1.1.4/49 timeout=15—Indicates that a TCP open request to host 10.1.1.4 on port 49 will time out in 15 seconds if it gets no response.

  • 00:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 10.1.1.4/49—Indicates a successful open operation and provides the address of the internal TCP "handle" for this connection.

There is certainly more information provided in the output than there is time or space to address in this book. For more detailed information, refer to the Debug Command Reference on the documentation CD-ROM, the Cisco.com website, or in printed form.

You can get more meaningful output from debug commands if you first configure the router using the service timestamps type [uptime] datetime [msec] [localtime] [show-timezone] command. The following describes the service timestamps command parameters (the parameters in brackets in the preceding sentence are optional):

  • type—Type of message to time-stamp; debug or log.

  • uptime—Time-stamp with time since the system was rebooted.

  • datetime—Time-stamp with the date and time.

  • msec—Include milliseconds in the date and timestamp.

  • localtime—Time-stamp relative to the local time zone.

  • show-timezone—Include the time zone name in the timestamp.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020