25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Accounting This is typically the third action after authentication <strong>and</strong><br />

authorization. But again, neither authentication nor<br />

authorization are required. Accounting is the action of<br />

recording what a user is doing <strong>and</strong> has done.<br />

In the distributed client/server security database model, a number of<br />

communications servers, or clients, authenticate a dial-in user's identity through<br />

a single, central database, or authentication server. The authentication server<br />

stores all information about users, their passwords, <strong>and</strong> access privileges.<br />

Distributed security provides a central location for authentication data that is<br />

more secure than scattering the user information on different devices throughout<br />

a network. A single authentication server can support hundreds of<br />

communications servers, serving up to tens of thous<strong>and</strong> of users.<br />

Communications servers can access an authentication server locally or remotely<br />

over WAN connections.<br />

Several remote access vendors <strong>and</strong> the Internet Engineering Task Force (IETF)<br />

have been in the forefront of this remote access security effort, <strong>and</strong> the means<br />

whereby such security measures are st<strong>and</strong>ardized. Remote Authentication Dial<br />

In User Service (RADIUS) <strong>and</strong> Terminal Access Controller Access Control<br />

System (TACACS) are two such cooperative ventures that have evolved out of<br />

the Internet st<strong>and</strong>ardizing body <strong>and</strong> remote access vendors.<br />

Remote Authentication Dial-In User Service (RADIUS) is a distributed security<br />

system developed by Livingston Enterprises. RADIUS was designed based on a<br />

previous recommendation from the IETF's Network Access Server Working<br />

Requirements Group. An IETF Working Group for RADIUS was formed in<br />

January 1996 to address the st<strong>and</strong>ardization of RADIUS protocol; RADIUS is<br />

now an IETF-recognized dial-in security solution (RFC 2058 <strong>and</strong> RFC 2138).<br />

Similar to RADIUS, Terminal Access Controller Access Control System<br />

(TACACS) is an industry st<strong>and</strong>ard protocol specification, RFC 1492. Similar to<br />

RADIUS, TACACS receives an authentication request from an NAS client <strong>and</strong><br />

forwards the user name <strong>and</strong> password information to a centralized security<br />

server. The centralized server can either be a TACACS database or an external<br />

security database. Extended TACACS (XTACACS) is a version of TACACS with<br />

extensions that Cisco added to the basic TACACS protocol to support advanced<br />

features. TACACS+ is another Cisco extension that allows a separate access<br />

server (the TACACS+ server) to provide independent authentication,<br />

authorization, <strong>and</strong> accounting services.<br />

Although RADIUS <strong>and</strong> TACACS authentication servers can be set up in a variety<br />

of ways, depending on the security scheme of the network they are serving, the<br />

basic process for authenticating a user is essentially the same. Using a modem,<br />

a remote dial-in user connects to a remote access server (also called the<br />

network access server or NAS) with a built-in analog or digital modem. After the<br />

Chapter 22. <strong>TCP</strong>/<strong>IP</strong> security 873

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!