X.509 Certificate Extended Key Usage (EKU) for 5G Network Functions

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 10 March 2024.¶

Copyright Notice

Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

The Operators of 5G systems make use of an internal PKI to generate X.509 PKI certificates for the Network Functions (NFs) in a 5G system. The certificates are used for the following purposes:¶

• Client and Server certificates for NFs in 5GC Service Based Architecture (see Section 6.1.3c of [TS33.310])¶
• Client Credentials Assertion (CCA) is JSON Web Tokens (JWT) [RFC7519] and is secured with digital signatures based on JSON Web Signature (JWS) [RFC7515] (see Section 13.3.8.2 of [TS33.501]).¶
• Certificates for encrypting JSON objects in HTTP messages between Security Edge Protection Proxies (SEPPs) using JSON Web Encryption (JWE) [RFC7516] (Section 13.2.4.4 of [TS33.501]) and Section 6.3.2 of [TS33.210])¶
• Certificates for signing the OAuth 2.0 access tokens for service authorization to grant temporary access to resources provided by NF producers using JWS (see Section 13.4.1 of [TS33.501])¶

[RFC5280] specifies several extended key purpose identifiers (EKU), defined via KeyPurposeIds, for X.509 certificates. In addition, the IANA repository "SMI Security for PKIX Extended Key Purpose" [RFC7299] contains additional KeyPurposeIds. It's important to note that using the anyExtendedKeyUsage KeyPurposeId, as defined in Section 4.2.1.12 of [RFC7299], is generally considered a poor practice. This is especially true for publicly trusted certificates, whether they are multi-purpose or single-purpose, within the context of 5G systems and the 5GC Service Based Architecture.¶

If the purpose of the issued certificates is not restricted, i.e., the type of operations for which a public key contained in the certificate can be used are not specified, those certificates could be used for another purpose than intended, violating the CA policies, and increasing the risk of cross-protocol attacks. Failure to ensure proper segregation of duties means that a NF who generates the public/private keys and applies for a certificate to the operator CA, could obtain a certificate which can be misused for tasks that this NF is not entitled to perform. For example, a NF service consumer could impersonate NF service producers using its certificate. Another example, if the purpose of the certificate is for the NF service consumer is to use it as a client certificate, the NF with this client certificate and corresponding private key must not be allowed to sign the CCA. When a NF service producer receives the signed CCA from the NF service consumer, the NF would accept the token even if CCA is signed with a certificate not issued for this purpose.¶

The KeyPurposeId id-kp-serverAuth (Section 4.2.1.12 of [RFC5280]) can be used to identify that the certificate is for a server (e.g., NF service producer), and the KeyPurposeId id-kp-clientAuth (Section 4.2.1.12 of [RFC5280]) can be used to identify that the certificate is for a client (e.g., NF service consumer). However, there is currently no KeyPurposeIds for the other usages of certificates in 5G System. This document defines the Extended Key Usage (EKU) extension of X.509 public key certificates for signing the JWT Claims set using JWS, encrypting JSON objects in HTTP messages using JWE, and signing the OAuth 2.0 access tokens using JWS.¶

Vendor-defined KeyPurposeIds used within a PKI governed by the vendor or a group of vendors typically do not pose interoperability concerns, as non-critical extensions can be safely ignored if unrecognized. However, using or misusing KeyPurposeIds outside of their intended vendor-controlled environment can lead to interoperability issues. Therefore, it is advisable not to rely on vendor-defined KeyPurposeIds. Instead, the specification defines standard KeyPurposeIds to ensure interoperability across various implementations.¶

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶

5. Implications for a Certification Authority

The procedures and practices employed by a certification authority MUST ensure that the correct values for the EKU extension as well as the KU extension are inserted in each certificate that is issued. The inclusion of the id-kp-jwt, id-kp-httpContentEncrypt and id-kp-oauthAccessTokenSigning KeyPurposeIds does not preclude the inclusion of other KeyPurposeIds.¶

6. Security Considerations

The Security Considerations of [RFC5280] are applicable to this document. This extended key purpose does not introduce new security risks but instead reduces existing security risks by providing means to identify if the certificate is generated to sign the JWT Claims Set, signing the OAuth 2.0 access tokens using JWS or to encrypt the CEK in JWE for encrypting JSON objects in HTTP messages.¶

To reduce the risk of specific cross-protocol attacks, the relying party or the relying party software may additionally prohibit use of specific combinations of KeyPurposeIds. The procedure of using Excluded KeyPurposeId and Permitted KeyPurposeId by an relying party to permit or prohibit combinations of KeyPurposeIds is defined in Section 4 of [RFC9336]. Examples of Excluded KeyPurposeId include the presence of the anyExtendedKeyUsage KeyPurposeId or the complete absence of the EKU extension in a certificate. Examples of Permitted KeyPurposeId include the presence of id-kp-jwt, id-kp-httpContentEncrypt or id-kp-oauthAccessTokenSigning KeyPurposeId.¶

7. Privacy Considerations

In some security protocols, such as TLS 1.2 [RFC5246], certificates are exchanged in the clear. In other security protocols, such as TLS 1.3 [RFC8446], the certificates are encrypted. The inclusion of EKU extension can help an observer determine the purpose of the certificate. In addition, If the certificate is issued by a public certification authority, the inclusion of EKU extension can help an attacker to monitor the Certificate Transparency logs [RFC9162] to identify the purpose of the certificate.¶

8. IANA Considerations

IANA is requested to register the following OIDs in the "SMI Security for PKIX Extended Key Purpose" registry (1.3.6.1.5.5.7.3). This OID is defined in Section 4.¶

+=========+===============================+============+
| Decimal | Description                   | References |
+=========+===============================+============+
| TBD1    | id-kp-jwt                     | This-RFC   |
+---------+-------------------------------+------------+
| TBD2    | id-kp-httpContentEncrypt      | This-RFC   |
+---------+-------------------------------+------------+
| TBD3    | id-kp-oauthAccessTokenSigning | This-RFC   |
+---------+-------------------------------+------------+

IANA is also requested to register the following ASN.1[X.680] module OID in the "SMI Security for PKIX Module Identifier" registry (1.3.6.1.5.5.7.0). This OID is defined in Appendix A.¶

+=========+==========================+============+
| Decimal |     Description          | References |
+=========+==========================+============+
| TBD4    | id-mod-nf-eku            | This-RFC   |
+---------+--------------------------+------------+

9. Contributors

The following individuals have contributed to this document:¶

      German Peinado
      Nokia

      Email: german.peinado@nokia.com

10. Acknowledgments

We would like to thank Corey Bonnell, Ilari Liusvaara, Carl Wallace, Yoav Nir and Russ Housley for their useful feedback.¶

Appendix A. ASN.1 Module

The following module adheres to ASN.1 specifications [X.680] and [X.690].¶

<CODE BEGINS>

NF-EKU
  { iso(1) identified-organization(3) dod(6) internet(1)
  security(5) mechanisms(5) pkix(7) id-mod(0)
  id-mod-nf-eku (TBD4) }

DEFINITIONS IMPLICIT TAGS ::=
BEGIN

-- OID Arc

id-kp OBJECT IDENTIFIER ::=
  { iso(1) identified-organization(3) dod(6) internet(1)
    security(5) mechanisms(5) pkix(7) kp(3) }

-- Extended Key Usage Values

id-kp-jwt OBJECT IDENTIFIER ::= { id-kp TBD1 }
id-kp-httpContentEncrypt OBJECT IDENTIFIER ::= { id-kp TBD2 }
id-kp-oauthAccessTokenSigning OBJECT IDENTIFIER ::= { id-kp TBD3 }

END


<CODE ENDS>

Authors' Addresses