CH 1 Flashcards
involves controlling access to
who can log in to a network device console, Telnet session, or Secure Shell (SSH) session
Device administration AAA
involves securing network access to ensuring
the identity of the device or user before permitting the entity to communicate with
the network.
Network access AAA
lists of commands that an authenticated user
is either permitted or not permitted to run
command sets
IEEE 802.1X cannot use which protocol?
TACACS
TACACS+ was not supported by Cisco ISE until which ISE Version?
2.0
which part of a packet is encrypted with TACACS+ and which port does TACACS+ use?
the entire packet, TCP 49
When using TACACS+ for authentication, what are the three types of packets exchanged between the client (the network device) and the server:
START, REPLY, CONTINUE
This packet is used to begin the authentication request between the AAA
client and the AAA server
START
These messages are sent from the AAA server to the AAA client.
REPLY
These messages from the AAA client are responses to the AAA server
requests for usernames and passwords
CONTINUE
The final REPLY message from the AAA server to the AAA client can include the following
possible values:
ACCEPT, REJECT, ERROR, CONTINUE
The user authentication succeeded, and the authorization process may
begin, if the AAA client is configured for authorization
ACCEPT
The user authentication failed. The login is denied or the end user is prompted to try again, depending on the configuration of the AAA client
REJECT
An error occurred at some point during the authentication. AAA clients typically attempt to authenticate the user again or attempt a different method of authenticating the user
ERROR
The user is prompted for additional information. This value sent from
the AAA server within a REPLY message, indicating that more information is required,
should not be confused with the CONTINUE message sent from the AAA client to
the AAA server
CONTINUE
When using TACACS+ for authorization, only two messages are used between the AAA
client and the AAA server:
REQUEST or RESPONSE
This message is sent from the AAA client to the AAA server to request
authorization
REQUEST
This message is sent from the AAA server back to the AAA client with
the result of the authorization request, including specific details, such as the privilege
level assigned to the end user.
RESPONSE
A RESPONSE message may contain one of the following replies:
FAIL, PASS_ADD, PASS_REPL, FOLLOW, ERROR
This response indicates that the user should be denied access to the
requested service.
FAIL
This response indicates successful authorization, and the information contained within the RESPONSE message should be used in addition to the requested information.
PASS_ADD
This response indicates successful authorization, but the server has
chosen to ignore the REQUEST message and is replacing it with the information
sent back in the RESPONSE message.
PASS_REPL
This reply indicates that the AAA server wants the AAA client to send
the authorization request to a different server. The new server information will be
listed in the RESPONSE packet. The AAA client may use that new server or treat
the response as a FAIL.
FOLLOW
This response indicates a problem occurring on the AAA server. Further
troubleshooting needs to occur.
ERROR
With accounting, there are two message types used. What are they?
Request, Response
This message is sent from the AAA client to the AAA server to indicate a
notification of activity
Request
Three values that may be included in a REQUEST message:
Start, Stop, Continue
This value indicates that a service has begun
Start
This value indicates that the service has ended
Stop
sometimes referred to as a Watchdog or
UPDATE record, is sent when a service has already started and is in progress, but
there is updated information to provide in relationship to the service
Continue
This message is sent from the AAA server back to the AAA client
with the result of the accounting REQUEST message
RESPONSE
RESPONSE messages may contain one of 3 replies:
Success, Error, Follow
This value indicates that the server received the record from the client
Success
This value indicates an error on the server and that the record was not
stored
Error
This value indicates that the server wants the client to send the record
to a different AAA server and includes that server’s information in the RESPONSE
message
Follow
An IETF standard for AAA, based on client/server model, protocol of choice for network access AAA.
RADIUS
One of the major differences in RADIUS and TACACS is that “what” is not separated in a RADIUS transaction.
authentication and authorization
What are the message types with RADIUS authentication/authorization?
Access-Request, Access-Accept, Access-Reject, Access-Challenge
This message is sent from the AAA client to the AAA server to
request authentication and authorization
Access-Request
This message is sent from the AAA server to the AAA client to signal
a passed authentication
Access-Accept
This message is sent from the AAA server to the AAA client to signal
authentication failure and indicate that no authorization has been granted
Access-Reject
This optional message may be sent from the AAA server to the
AAA client when additional information is needed, such as a second password for
two-factor authentications
Access-Challenge
What are the 2 types of messages used in RADIUS accounting?
Accounting-Request, Accounting-Response
This message is sent by the AAA client to the AAA server. It
may include time, packets, DHCP information, CDP information, and so on. The message may be a START message indicating that service has begun or a STOP message
indicating the service has ended.
Accounting-Request
This message acts as an acknowledgment of receipt, so the
AAA client knows the accounting message was received by the AAA server.
Accounting-Response
Unlike TACACS, RADIUS uses what as the transmission protocol?
UDP (1812 for authentication and 1813 for accounting)
allows a RADIUS server to initiate a conversation with a network device and disconnect a user’s session, bounce the port (perform a shut/no-shut), or even tell the device to reauthenticate the user
CoA