18 - Understanding Wireless Client Authentication Flashcards
What are the wireless authentication methods?
• WPA2 Authentication modes o Enterprise mode – 802.1x Individual authentication Authenticates managed devices and known users Corporate use o Personal mode – Pre shared key Common authentication Often authenticates devices, not user SOHO use • Web authentication o Web auth 802.1x incapable devices 802.1x backup authentication Guest user access
___ authentication uses symmetric encryption, meaning that the same algorithm and key that are used to encrypt the credentials are used, in reverse, to decrypt the message. With __, a common password is configured on both sides. Symmetric key encoding is relatively simple; however, it is not recommended for strong user authentication because it is not very resistant to a key attack.
PSK
One issue is that with PSK authentication, is that that if the password is saved on the wireless client, the process does not authenticate the person who makes the connection but rather the __. For this reason, storing personal passwords on laptop or desktop computers is considered dangerous. Unless authentication requires the user to enter credentials, the __, not the user, is being authenticated.
device
An 802.11 complaint WLAN client will use __ authentication by default. __ auth uses no keys. __ auth operates at L1/L2 and does not offer end-to-end security
open
With open auth, the client devices have only authenticated itself as a 802.11 capable device. There is no encryption, per-packet auth, or message integrity check. Additional security measures should be added such as ___.
802.1x
The 802.1X protocol defines port-based access control. The protocol defines three roles:
- Supplicant – the machine that wants to access the network
- Authenticator – the point of access (switch, or AP, or WLC). The authenticator is the point of entrance to the network
- Authentication server – a machine, somewhere in the network, that keeps a list of conditions by which access is granted or refused
The __ connects to the authenticator. At this point, the port on the authenticator is connected from a physical standpoint, however the 802.1x process has not authorised the port, and no frames are passed from the port on __ to the switching fabric. To be allowed to send and receive traffic, the __ needs to send a form of authentication: an ID. If the __does not send an ID, the port remains unauthorised.
supplicant
___ is the service framework that is needed to support large-scale, public key-based technologies. ___ provides a scalable and manageable way to implement strong encryption by using digital certificates.
Public key infrastructure (PKI)
How is PKI used? What is the process?
- Certificate Authorities (CA) generate digital certificates for users (clients) and servers that are used to validate user and server identities
- Clients request a user certificate from a CA and use the cert to authenticate to the server using 802.1X auth (like EAP-TLS or EAP-FAST)
- Servers request a server cert from the CA, which is used by the client to validate the authenticity of the server. A server can also use a self-signed cert in which it acts as its own CA
- Cisco WLCs that are used as the auth server use preinstalled server certs or can request a server cert from a CA
How does Asymmetric Encryption work?
- With asymmetric encryption, a user generates two keys
- A public key and a private key
- Keys are built on a mathematical algorithm, so they work in pairs
- What is encrypted by key 1 can be decrypted only by key 2 and vice versa
With __, the identity of the sender is not protected. When a user sends his encrypted credentials to the server, the server receives the credentials, decrypts it, and reads the senders name and assumes that the credentials belong to that user. However, this cannot be guaranteed because the public key that belongs to the server can be given to anyone.
asymmetric encryption
To enhance security, a process known as __ a message is used. This validates the sender by using the servers public key to further encrypt a message, and if the server is able to decrypt the message using their private key, they know that the message was sent by that sender.
digital signing
__ proves to the server that the public key that it has for a sender, is actually their public key. Someone else could have created a pair of keys, labelled one as the public key that belongs to someone else and sent it to the server. If the server answers this type of message, then the attacker will be able to read the answer.
Nothing
An authority known as a ___ takes the public key that belongs to the sender, adds text that contains their name, the validity duration, and a hash that contains a signed message that is encrypted with a private key that belongs to the authority. A public key to which a trusted 3rd party __ has signed in this manner is called a __.
Certificate Authority (CA), CA, certificate
In an enterprise environment, a __ is a server that can be implemented in various forms. Because the __ is well known, its public key is implemented in the operating system of most computers.
CA