Security association: Difference between revisions
No edit summary |
|||
Line 8: | Line 8: | ||
*[[IPsec]] |
*[[IPsec]] |
||
*[[Internet Key Exchange]] (IKE) |
*[[Internet Key Exchange]] (IKE) |
||
*[[VPN]] (VPN) |
|||
==Notes== |
==Notes== |
Revision as of 11:12, 1 May 2013
A Security Association (SA) is the establishment of shared security attributes between two network entities to support secure communication. An SA may include attributes such as: cryptographic algorithm and mode; traffic encryption key; and parameters for the network data to be passed over the connection. The framework for establishing security associations is provided by the Internet Security Association and Key Management Protocol (ISAKMP). Protocols such as Internet Key Exchange and Kerberized Internet Negotiation of Keys provide authenticated keying material.[1]
An SA is a simplex (one-way channel) and logical connection which endorses and provides a secure data connection between the network devices. The fundamental requirement of an SA arrives when the two entities communicate over more than one channel. Take an example of mobile subscriber and a base station. The subscriber may subscribe itself for more than one service. Therefore each service may have different service primitives like a data encryption algorithm, public key or initialization vector. Now to make things easier, all this security information is grouped logically. This logical group itself is a Security Association. Each SA has its own ID called SAID. So now the base station and mobile subscriber will share the SAID and they will derive all the security parameters, making things a lot easier.
In a nutshell, an SA is a logical group of security parameters that enable the sharing of information to another entity.
See also
- IPsec
- Internet Key Exchange (IKE)
- VPN (VPN)
Notes
- ^ The Internet Key Exchange (IKE), RFC 2409, §1 Abstract
References
- Internet Key Exchange (IKEv2) Protocol - RFC 4306