Secure Sockets Layer (SSL)

{
  "id": "MLC-T-CYB-003764",
  "term": "Secure Sockets Layer (SSL)",
  "field": "Cybersecurity",
  "definition": "1. An authentication and security protocol that is widely implemented in browsers and web servers. TLS provides confidentiality, certificate-based authentication of the receiving (server) endpoint, and certificate-based authentication of the originating (client) endpoint. TLS is specified in [RFC8446] and [SP800-52].\n\n2. Provides privacy and data integrity between two communicating applications. It is designed to encapsulate other protocols, such as HTTP. TLS v1.0 was released in 1999, providing slight modifications to SSL 3.0.\n\n3. A security protocol providing privacy and data integrity between two communicating applications. The protocol is composed of two layers: the TLS Record Protocol and the TLS Handshake Protocol.\n\n4. Provides privacy and reliability between two communicating applications. It is designed to encapsulate other protocols, such as HTTP. SSL v3.0 was released in 1996. It has been succeeded by IETF's TLS.\n\n5. A protocol used for protecting private information during transmission via the Internet. Note: SSL works by using the service public key to encrypt a secret key that is used to encrypt the data that is transferred over the SSL session. Most web browsers support SSL and many web sites use the protocol to obtain confidential user information, such as credit card numbers. By convention, URLs that require an SSL connection start with \"https:\" instead of \"http:\". The default port for SSL is 443.\n\n6. See Transport Layer Security (TLS).\n\n7. An authentication and security protocol widely implemented in browsers and web servers. TLS is defined by RFC 5246. TLS is similar to the older SSL protocol, and TLS 1.0 is effectively SSL version 3.1. NIST SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations, specifies how TLS is to be used in government applications.\n\n8. An authentication and security protocol widely implemented in browsers and web servers. TLS is defined by RFC 5246. TLS is similar to the older SSL protocol, and TLS 1.0 is effectively SSL version 3.1. NIST SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations [NIST SP 800-52], specifies how TLS is to be used in government applications.\n\n9. An authentication and security protocol widely implemented in browsers and web servers. TLS is defined by RFC 5246 and RFC 8446.\n\n10. An authentication and security protocol widely implemented in browsers and web servers. SSL has been superseded by the newer Transport Layer Security (TLS) protocol; TLS 1.0 is effectively SSL version 3.1.\n\n11. An authentication and security protocol widely implemented in browsers and web servers. TLS is defined by [RFC 2246], [RFC 3546], and [RFC 5246]. TLS is similar to the older Secure Sockets Layer (SSL) protocol, and TLS 1.0 is effectively SSL version 3.1. NIST SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations specifies how TLS is to be used in government applications.",
  "abbreviation": "SSL",
  "synonyms": [
    "Transport Layer Security (TLS)"
  ],
  "references": [
    "NIST SP 800-63-4",
    "NIST SP 800-95 from IETF RFC 2246",
    "NIST SP 1800-21B from CNSSI 4009-2015, CNSSI 4009-2022",
    "NIST SP 800-95 from SSL 3.0 specification",
    "CNSSI 4009-2015; CNSSI 4009-2022 from NIST SP 800-63-3 (adapted)",
    "NIST SP 800-63-3 [Superseded]",
    "NIST SP 1800-16B; NIST SP 1800-16C; NIST SP 1800-16D",
    "NIST SP 800-63-2 [Superseded]",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/secure-sockets-layer-ssl/"
}