Explore tens of thousands of sets crafted by our community.
Common Security Protocols
15
Flashcards
0/15
SAML
Purpose: Single Sign-On (SSO) for web applications. Implementation: XML-based framework for exchanging authentication and authorization data.
SSL
Purpose: Establish an encrypted link between a server and a client. Implementation: Uses a handshake mechanism to establish a secure session.
Kerberos
Purpose: Network authentication protocol. Implementation: Uses secret-key cryptography for secure authentication.
SSH
Purpose: Enable secure remote login and other secure network services. Implementation: Encrypted network protocol for remote command execution.
L2TP
Purpose: Tunneling to support VPNs. Implementation: Combines features of PPTP and L2F, generally used with IPsec for encryption.
OAuth
Purpose: Authorization protocol to provide secure designated access. Implementation: Allows users to grant third-party access to web resources without sharing passwords.
OpenVPN
Purpose: Create secure point-to-point connections. Implementation: Open-source VPN protocol that uses SSL/TLS for key exchange.
WPA3
Purpose: Further security improvement over WPA2 for wireless networks. Implementation: Provides stronger data protection and more secure network access control.
IPsec
Purpose: Secure Internet Protocol communications. Implementation: Encrypts and authenticates IP packets.
PPTP
Purpose: Tunneling protocol for creating VPNs. Implementation: Obsolete protocol that encapsulates PPP packets within IP datagrams.
WPA2
Purpose: Secure wireless computer networks. Implementation: Provides government-grade security by implementing the mandatory elements of IEEE 802.11i.
HTTPS
Purpose: Secure communication over a computer network. Implementation: Uses TLS/SSL encryption on top of the HTTP protocol.
TLS
Purpose: Provide secure communications over a computer network. Implementation: Successor of SSL, uses stronger encryption algorithms and improved handshake process.
OpenID Connect
Purpose: Authentication protocol. Implementation: Built on top of the OAuth 2.0 protocol, allows clients to verify the identity of the end-user.
DNSSEC
Purpose: Protect against DNS attacks such as cache poisoning. Implementation: Adds cryptographic signatures to existing DNS records to ensure their authenticity.
© Hypatia.Tech. 2024 All rights reserved.