MLchartDataset catalogue

Public key certificate

Term · Cybersecurity · MLC-T-CYB-003371

1. A digital document issued and digitally signed by the private key of a certification authority that binds an identifier to a cardholder through a public key. The certificate indicates that the cardholder identified in the certificate has sole control and access to the private key.

2. A set of data that uniquely identifies a public key (which has a corresponding private key) and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a Certification Authority (i.e., a trusted party), thereby binding the public key to the owner.

3. A set of data that uniquely identifies a public key that has a corresponding private key and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a certification authority (i.e., a trusted party), thereby binding the public key to the owner.

4. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber’s public key. The certificate indicates that the subscriber identified in the certificate has sole control of and access to the private key. See also [RFC5280].

5. A digital representation of information which at least (1) identifies the certification authority issuing it, (2) names or identifies its subscriber, (3) contains the subscriber's public key, (4) identifies its operational period, and (5) is digitally signed by the certification authority issuing it. [ABADSG]. As used in this CP, the term “Certificate” refers to certificates that expressly reference the OID of this CP in the “Certificate Policies” field of an X.509 v.3 certificate.

6. A digital representation of information which at least (1) identifies the certification authority issuing it, (2) names or identifies it’s Subscriber, (3) contains the Subscriber’s public key, (4) identifies it’s operational period, and (5) is digitally signed by the certification authority issuing it.

7. A digital representation of information which at least (1) identifies the certification authority (CA) issuing it, (2) names or identifies its subscriber, (3) contains the subscriber's public key, (4) identifies its operational period, and (5) is digitally signed by the certification authority issuing it.

8. See certificate.

9. A data structure that contains an entity’s identifier(s), the entity's public key (including an indication of the associated set of domain parameters) and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e. a certificate authority, thereby binding the public key to the included identifier(s).

10. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its cryptoperiod.

11. A set of data that uniquely identifies a key pair owner that is authorized to use the key pair, contains the owner’s public key and possibly other information, and is digitally signed by a Certification Authority (i.e., a trusted party), thereby binding the public key to the owner.

12. See public-key certificate.

13. See public key certificate.

14. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity (e.g., using an X.509 certificate). Additional information in the certificate could specify how the key is used and its validity period.

15. A data structure that contains an entity’s identifier(s), the entity's public key (including an indication of the associated set of domain parameters) and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e., a certificate authority, thereby binding the public key to the included identifier(s).

16. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.

17. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber to a public key. The certificate indicates that the subscriber identified in the certificate has sole control and access to the private key. See also Request for Comment 5280.

18. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber to a public key. The certificate indicates that the subscriber identified in the certificate has sole control and access to the private key. See also RFC 5280.

19. A set of data that uniquely identifies an entity, contains the entity’s public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.

20. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period. (Certificates in this practice guide are based on IETF RFC 5280).

21. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period. (Certificates in this practice guide are based on IETF RFC 5280.)

22. Also known as a digital certificate. A digital representation of information which at least
1. identifies the certification authority issuing it,
2. names or identifies its subscriber,
3. contains the subscriber's public key,
4. identifies its operational period, and
5. is digitally signed by the certification authority issuing it.

23. A data structure that contains an entity’s identifier(s), the entity's public key and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e. a certificate authority, thereby binding the public key to the included identifier(s).

24. A digital document issued and digitally signed by the private key of a Certificate authority that binds the name of a Subscriber to a public key. The certificate indicates that the Subscriber identified in the certificate has sole control and access to the private key. See also [RFC 5280].

Table 1. Record
IdentifierMLC-T-CYB-003371
FieldCybersecurity
Abbreviationcertificate
ReferencesFIPS 201-3 from RFC 5280 (adapted); FIPS 186-5; FIPS 204; NIST SP 800-63-4; NIST SP 800-63A-4; NIST SP 800-32 [Withdrawn] from ABADSG (plus note); NIST SP 800-32 [Withdrawn] from ABADSG; CNSSI 4009-2015 from NIST SP 800-32, CNSSI No. 1300; CNSSI 4009-2022 from CNSSI No. 1300; CNSSI 4009-2015; NIST SP 800-56A Rev. 2 [Superseded]; NIST SP 800-57 Part 2 [Superseded]; NIST SP 800-57 Part 1 Rev. 3 [Superseded]; NIST SP 800-89; NIST SP 800-57 Part 1 Rev. 4 [Superseded]; NIST SP 800-57 Part 1 Rev. 5; NIST SP 800-57 Part 1 Rev. 3 [Superseded]; NIST SP 800-57 Part 2 [Superseded]; NIST SP 800-57 Part 2 Rev.1; NIST SP 800-57 Part 2 Rev.1; NIST SP 800-56B Rev. 2; NIST SP 1800-21C; NIST SP 800-57 Part 1 Rev. 4 [Superseded]; NIST SP 1800-16B from NIST SP 800-57 Part 1 Rev. 4 (under Public-key certificate); NIST SP 1800-17b; NIST SP 1800-17c; NIST SP 800-63-3 [Superseded]; NIST SP 800-57 Part 1 Rev. 5; NIST SP 1800-16C from NIST SP 800-57 Part 1 Rev. 4 (under Public-Key Certificate); NIST SP 1800-16D from NIST SP 800-57 Part 1 Rev. 4 (under Public-key certificate); NISTIR 7711; NIST SP 800-56B Rev. 1 [Superseded]; NIST SP 800-63-2 [Superseded]; NIST CSRC Glossary
Record as JSON 
{
  "id": "MLC-T-CYB-003371",
  "term": "Public key certificate",
  "field": "Cybersecurity",
  "definition": "1. A digital document issued and digitally signed by the private key of a certification authority that binds an identifier to a cardholder through a public key. The certificate indicates that the cardholder identified in the certificate has sole control and access to the private key.\n\n2. A set of data that uniquely identifies a public key (which has a corresponding private key) and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a Certification Authority (i.e., a trusted party), thereby binding the public key to the owner.\n\n3. A set of data that uniquely identifies a public key that has a corresponding private key and an owner that is authorized to use the key pair. The certificate contains the owner’s public key and possibly other information and is digitally signed by a certification authority (i.e., a trusted party), thereby binding the public key to the owner.\n\n4. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber’s public key. The certificate indicates that the subscriber identified in the certificate has sole control of and access to the private key. See also [RFC5280].\n\n5. A digital representation of information which at least (1) identifies the certification authority issuing it, (2) names or identifies its subscriber, (3) contains the subscriber's public key, (4) identifies its operational period, and (5) is digitally signed by the certification authority issuing it. [ABADSG]. As used in this CP, the term “Certificate” refers to certificates that expressly reference the OID of this CP in the “Certificate Policies” field of an X.509 v.3 certificate.\n\n6. A digital representation of information which at least (1) identifies the certification authority issuing it, (2) names or identifies it’s Subscriber, (3) contains the Subscriber’s public key, (4) identifies it’s operational period, and (5) is digitally signed by the certification authority issuing it.\n\n7. A digital representation of information which at least (1) identifies the certification authority (CA) issuing it, (2) names or identifies its subscriber, (3) contains the subscriber's public key, (4) identifies its operational period, and (5) is digitally signed by the certification authority issuing it.\n\n8. See certificate.\n\n9. A data structure that contains an entity’s identifier(s), the entity's public key (including an indication of the associated set of domain parameters) and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e. a certificate authority, thereby binding the public key to the included identifier(s).\n\n10. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its cryptoperiod.\n\n11. A set of data that uniquely identifies a key pair owner that is authorized to use the key pair, contains the owner’s public key and possibly other information, and is digitally signed by a Certification Authority (i.e., a trusted party), thereby binding the public key to the owner.\n\n12. See public-key certificate.\n\n13. See public key certificate.\n\n14. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity (e.g., using an X.509 certificate). Additional information in the certificate could specify how the key is used and its validity period.\n\n15. A data structure that contains an entity’s identifier(s), the entity's public key (including an indication of the associated set of domain parameters) and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e., a certificate authority, thereby binding the public key to the included identifier(s).\n\n16. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.\n\n17. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber to a public key. The certificate indicates that the subscriber identified in the certificate has sole control and access to the private key. See also Request for Comment 5280.\n\n18. A digital document issued and digitally signed by the private key of a certificate authority that binds an identifier to a subscriber to a public key. The certificate indicates that the subscriber identified in the certificate has sole control and access to the private key. See also RFC 5280.\n\n19. A set of data that uniquely identifies an entity, contains the entity’s public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period.\n\n20. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period. (Certificates in this practice guide are based on IETF RFC 5280).\n\n21. A set of data that uniquely identifies an entity, contains the entity's public key and possibly other information, and is digitally signed by a trusted party, thereby binding the public key to the entity. Additional information in the certificate could specify how the key is used and its validity period. (Certificates in this practice guide are based on IETF RFC 5280.)\n\n22. Also known as a digital certificate. A digital representation of information which at least\n1. identifies the certification authority issuing it,\n2. names or identifies its subscriber,\n3. contains the subscriber's public key,\n4. identifies its operational period, and\n5. is digitally signed by the certification authority issuing it.\n\n23. A data structure that contains an entity’s identifier(s), the entity's public key and possibly other information, along with a signature on that data set that is generated by a trusted party, i.e. a certificate authority, thereby binding the public key to the included identifier(s).\n\n24. A digital document issued and digitally signed by the private key of a Certificate authority that binds the name of a Subscriber to a public key. The certificate indicates that the Subscriber identified in the certificate has sole control and access to the private key. See also [RFC 5280].",
  "abbreviation": "certificate",
  "references": [
    "FIPS 201-3 from RFC 5280 (adapted)",
    "FIPS 186-5",
    "FIPS 204",
    "NIST SP 800-63-4; NIST SP 800-63A-4",
    "NIST SP 800-32 [Withdrawn] from ABADSG (plus note)",
    "NIST SP 800-32 [Withdrawn] from ABADSG",
    "CNSSI 4009-2015 from NIST SP 800-32, CNSSI No. 1300; CNSSI 4009-2022 from CNSSI No. 1300",
    "CNSSI 4009-2015",
    "NIST SP 800-56A Rev. 2 [Superseded]",
    "NIST SP 800-57 Part 2 [Superseded]; NIST SP 800-57 Part 1 Rev. 3 [Superseded]",
    "NIST SP 800-89",
    "NIST SP 800-57 Part 1 Rev. 4 [Superseded]; NIST SP 800-57 Part 1 Rev. 5; NIST SP 800-57 Part 1 Rev. 3 [Superseded]",
    "NIST SP 800-57 Part 2 [Superseded]; NIST SP 800-57 Part 2 Rev.1",
    "NIST SP 800-57 Part 2 Rev.1",
    "NIST SP 800-56B Rev. 2; NIST SP 1800-21C",
    "NIST SP 800-57 Part 1 Rev. 4 [Superseded]; NIST SP 1800-16B from NIST SP 800-57 Part 1 Rev. 4 (under Public-key certificate)",
    "NIST SP 1800-17b; NIST SP 1800-17c",
    "NIST SP 800-63-3 [Superseded]",
    "NIST SP 800-57 Part 1 Rev. 5",
    "NIST SP 1800-16C from NIST SP 800-57 Part 1 Rev. 4 (under Public-Key Certificate)",
    "NIST SP 1800-16D from NIST SP 800-57 Part 1 Rev. 4 (under Public-key certificate)",
    "NISTIR 7711",
    "NIST SP 800-56B Rev. 1 [Superseded]",
    "NIST SP 800-63-2 [Superseded]",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/public-key-certificate/"
}

Record 3,354 of 4,669 in Cybersecurity terminology (MLC-0102). Request the full dataset.