Contents
StandardIETF

RFC 5280

Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

RFC 5280 defines how digital certificates and revocation lists are structured and checked so systems can decide which public keys to trust.

What it is

RFC 5280 is the Internet profile for X.509 public-key certificates and certificate revocation lists (CRLs). A certificate associates a public key with a named subject through an issuer’s digital signature. A CRL identifies certificates an issuer has revoked.

For automotive engineers, it provides a common foundation for certificate-based trust between vehicles, tools and backend services. It is a technical specification, rather than an automotive regulation or a complete vehicle security design.

Who it applies to

It applies to certificate issuers and systems that validate certificates when their chosen protocol or product profile uses this Internet PKI model. In a vehicle programme, these may include OEM certificate services, supplier software, connected ECUs, diagnostic tools and backend applications.

Adoption depends on the system’s requirements. Using certificates does not automatically make every automotive component subject to RFC 5280. Teams should identify which interfaces require it and which additional certificate restrictions their ecosystem imposes.

What it covers

The document specifies certificate fields and extensions, CRL structures and processing, and certification-path validation. A certification path connects a subject’s certificate through issuing authorities to a configured trust anchor.

Element Engineering meaning
Certificate fields Identify the issuer, subject, public key and validity interval.
Extensions Express constraints such as permitted key uses and certificate-authority roles.
Path validation Checks signatures and applicable constraints against configured trust inputs.
CRL processing Supports determining whether a certificate has been revoked.

A valid path alone does not establish that a peer is the intended service or that it may perform a particular vehicle operation. Applications need appropriate identity and authorization checks as well.

How it fits with other documents

X.509 supplies the underlying certificate framework; RFC 5280 profiles it for Internet use. TLS specifications describe secure communication using credentials, while OCSP specifies a separate mechanism for requesting certificate status. Application-specific rules supply additional identity checks.

Automotive cybersecurity engineering should connect these mechanisms to identified threats and security requirements. An OEM certificate profile can narrow implementation choices for interoperability. Neither that profile nor RFC 5280 replaces decisions about credential provisioning, private-key protection or operational access rights.

In practice

Start with an agreed certificate profile shared by the issuer and every consuming implementation. Record supported algorithms, required extensions, intended identities, trust anchors and renewal responsibilities. Make these choices explicit in supplier interfaces and acceptance criteria.

For vehicles, plan around long service lives and intermittent connectivity. Decide how validation obtains trustworthy time, how revocation information reaches an offline vehicle, and what happens when credentials expire during storage or servicing. Define failure handling for each function using the programme’s security and availability requirements.

Test rejection paths alongside successful connections: an untrusted issuer, an expired certificate, an inappropriate key use, an unsupported critical extension and revoked credentials. Exercise trust-anchor replacement and certificate renewal before production. Retain useful diagnostic reasons for failures so service teams can distinguish credential problems from transport faults.

What it means for your discipline

  • CybersecurityCore

    Defines certificate profiles, trust policies and revocation requirements. Reviews whether vehicle and backend implementations enforce the intended trust boundaries.

  • HPC & application softwareCore

    Implements and tests certificate parsing and validation through security libraries. Ensures applications correctly handle validation failures and apply their own identity and authorization checks.

  • E/E architecturePartial

    Allocates trust anchors, certificate authorities and certificate lifecycle responsibilities across vehicles, manufacturing and backend services.

  • Base softwarePartial

    Integrates certificate handling with embedded cryptographic services, storage and time sources. Checks resource limits and validation behavior on constrained ECUs.

  • Diagnostics & lifecyclePartial

    Understands certificate requirements when diagnostic authentication uses X.509 credentials. Plans how workshop tools and vehicles handle expired or revoked credentials.

  • Software update & OTAPartial

    Applies certificate validation where update systems use X.509 signing credentials. Coordinates trust-anchor changes and credential renewal with the update security design.

No direct stake: Functional safety · Hardware & silicon · Networks & communication