This situation is changing as time goes on, however, as certain vendors now fully support TACACS.Sean Wilkins, co-author of CCNA Routing and Switching 200-120 Network Simulator, examines these two long-time AAA favorites, discussing how they protect your networks vital resources.On small networks, very few people (maybe only one person) should have the passwords to access the devices on the network; generally this information is easy to track because the number of users with access is so low.
In larger organizations, however, tracking who has access to what devices at what level can quickly become complex. This is where authentication, authorization, and accounting (AAA) solutions come to the rescue. These solutions provide a mechanism to control access to a device and track people who use this access. This article discusses the services these protocols provide and compares them to each other, to help you decide which solution would be best to use on a particular network. To make this discussion a little clearer, well use an access door system as an example. A simple authentication mechanism would be a fingerprint scanner; because only one person has that fingerprint, this device verifies that the subject is that specific person. For example, you may have been authenticated as Bob, but are you allowed to have access to that specific room in the building On a network device, are there specific commands that you should be allowed to use and others that you shouldnt A common example in networks is the difference between a tier 1 and tier 2 engineer in a Network Operations Center (NOC): A tier 1 engineer may need to access the device and have the ability to perform a number of informative show commands, but shouldnt be able to shut down the device or change any specific configuration. A network device can log every user who authenticates a device as well as every command the user runs (or attempts to run). This step is important, as it can be used to determine potential security threats and to help find security breaches. Usa rc pam 190 1 physical security programThis solution typically took effect when a user would dial into an access server; that server would verify the user and then based on that authentication would send out authorization policy information (addresses to use, duration allowed, and so on). The accounting piece of RADIUS monitored this exchange of information with each connected user. Since the authentication and authorization were so closely tied together, they were delivered with the same packet types (more on this later); whereas accounting was left as a separate process. UDP is fast, but it has a number of drawbacks that must be considered when implementing it versus other alternatives. For example, when RADIUS was developed, security wasnt as important a consideration as it is today, and therefore RADIUS encrypted only the authentication information (passwords) along the traffic path. Overall, the purpose of both RADIUS and TACACS is the sameperforming AAA for a systembut the two solutions deliver this protection a bit differently. TACACS uses the Transmission Control Protocol (TCP) rather than UDP, mainly due to the built-in reliability of TCP. Using TCP also makes TACACS clients aware of potential server crashes earlier, thanks to the server TCP-RST (Reset) packet. TACACS encrypts the entire contents of the packet body, leaving only a simple TACACS header. Depeche mode best of rar downloadThis design prevents potential attackers that might be listening from determining the types of messages being exchanged between devices. TACACS also implements authentication, authorization, and accounting separately, which makes it possible for each functionality to be delegated to a different server, andor even a different type of server (non-TACACS). With a TACACS server, its possible to implement command control using either access levels (which are further configured on the devices) or using command-by-command authorization based on server users and groups. RADIUS also offers this capability to some extent, but its not as granular on Cisco devices; on some other vendors, this restriction is less limited.
0 Comments
Leave a Reply. |
AuthorMark ArchivesCategories |