From 5d2dbaa83fc7f959853790cc8479e98965ae2d90 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 31 Mar 2025 13:27:47 +0000 Subject: [PATCH 1/2] Add new trust list: The Hubject V2G PKI --- data/the-hubject-v2g-pki.yaml | 132 ++++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 data/the-hubject-v2g-pki.yaml diff --git a/data/the-hubject-v2g-pki.yaml b/data/the-hubject-v2g-pki.yaml new file mode 100644 index 0000000..44fdfcd --- /dev/null +++ b/data/the-hubject-v2g-pki.yaml @@ -0,0 +1,132 @@ +id: the-hubject-v2g-pki +name: The Hubject V2G PKI +description: >- + # Hubject V2G PKI Overview + + + The **Hubjecte V2G PKI (Vehicle-to-Grid Public Key Infrastructure)** is a + security framework designed to facilitate secure communication and + authentication between electric vehicles (EVs), charging stations, and other + entities within the e-mobility ecosystem. It is a critical component of the + **ISO 15118** standard, which governs **Plug & Charge** technology, allowing + for seamless and secure EV charging without requiring physical payment methods + or manual user authentication. + + + + ## **Key Components of the Hubject V2G PKI** + + + ### 1. **Root Certificate Authority (Root CA)** + + - The trust anchor for the entire ecosystem. + + - Issues certificates to intermediate CAs (Sub-CAs). + + + ### 2. **Subordinate Certificate Authority (Sub-CA)** + + - Issues certificates to participants such as charging stations, EV + manufacturers, and mobility operators. + + - Ensures that entities are authenticated and authorized to participate in + Plug & Charge. + + + ### 3. **Provisioning Authority (PA)** + + - Manages the distribution of **Contract Certificates** to EV users. + + - Ensures that only valid and verified vehicles and users can participate in + Plug & Charge transactions. + + + ### 4. **Registration Authority (RA)** + + - Responsible for verifying the identity of entities before issuing + certificates. + + - Handles certificate lifecycle processes, including issuance, renewal, and + revocation. + + + ### 5. **Certificate Revocation List (CRL) and Online Certificate Status + Protocol (OCSP)** + + - Supports real-time validation and revocation of certificates to maintain + system security. + + + + ## **How the Hubject V2G PKI Works** + + + ### **1. Certificate Issuance** + + - Electric vehicle manufacturers and charging station operators obtain + certificates from the Sub-CA. + + - EV users receive **Contract Certificates** tied to their charging + agreements, enabling Plug & Charge. + + + ### **2. Authentication Process** + + - When an EV connects to a charging station, the station verifies the + vehicle’s Contract Certificate against the Hubject V2G PKI. + + - Mutual TLS (mTLS) is used to establish a secure communication channel. + + + ### **3. Transaction Validation** + + - The charging station authenticates the EV’s certificate. + + - The EV verifies the charging station’s certificate, ensuring both parties + are trusted. + + + ### **4. Payment and Billing** + + - Once the vehicle is authenticated, the system initiates and logs the + charging session. + + - Payment is processed automatically based on the linked Contract Certificate. + + + + ## **Security Features of Hubject V2G PKI** + + - **Mutual Authentication:** Both EVs and charging stations authenticate each + other using X.509 certificates. + + - **Data Integrity:** Digital signatures protect communication from tampering. + + - **Confidentiality:** All communication is encrypted to prevent + eavesdropping. + + - **Certificate Lifecycle Management:** Ensures timely renewal and revocation + of certificates to maintain trust. + + + + ## **Key Standards and Compliance** + + - **ISO 15118-2 and ISO 15118-20:** Defines Plug & Charge communication + protocols. + + - **ETSI and eIDAS:** Ensures compliance with European security regulations. + + - **WebTrust for CAs:** Establishes best practices for PKI operations. +website: https://www.hubject.com/download-pki +contact: '' +ccadb: false +legal-context: '' +audit: [] +requirements: [] +discussions: [] +issues: [] +trust-lists: + info: '' + policy: https://www.hubject.com/download-pki + trust: [] From 026346af9ac34d23b8ef64441b0c9217505178b0 Mon Sep 17 00:00:00 2001 From: Paul van Brouwershaven Date: Mon, 31 Mar 2025 15:35:01 +0200 Subject: [PATCH 2/2] Update and rename the-hubject-v2g-pki.yaml to hubject-v2g.yaml --- data/hubject-v2g.yaml | 9 +++ data/the-hubject-v2g-pki.yaml | 132 ---------------------------------- 2 files changed, 9 insertions(+), 132 deletions(-) create mode 100644 data/hubject-v2g.yaml delete mode 100644 data/the-hubject-v2g-pki.yaml diff --git a/data/hubject-v2g.yaml b/data/hubject-v2g.yaml new file mode 100644 index 0000000..c965856 --- /dev/null +++ b/data/hubject-v2g.yaml @@ -0,0 +1,9 @@ +id: hubject-v2g +name: The Hubject V2G PKI +description: >- + The Hubject V2G PKI (Vehicle-to-Grid Public Key Infrastructure) is a security framework designed to facilitate secure communication and authentication between electric vehicles (EVs), charging stations, and other entities within the e-mobility ecosystem. + It is a critical component of the ISO 15118 standard, which governs Plug & Charge technology, allowing for seamless and secure EV charging without requiring physical payment methods or manual user authentication. +website: https://www.hubject.com/download-pki +ccadb: false +trust-lists: + policy: https://www.hubject.com/download-pki diff --git a/data/the-hubject-v2g-pki.yaml b/data/the-hubject-v2g-pki.yaml deleted file mode 100644 index 44fdfcd..0000000 --- a/data/the-hubject-v2g-pki.yaml +++ /dev/null @@ -1,132 +0,0 @@ -id: the-hubject-v2g-pki -name: The Hubject V2G PKI -description: >- - # Hubject V2G PKI Overview - - - The **Hubjecte V2G PKI (Vehicle-to-Grid Public Key Infrastructure)** is a - security framework designed to facilitate secure communication and - authentication between electric vehicles (EVs), charging stations, and other - entities within the e-mobility ecosystem. It is a critical component of the - **ISO 15118** standard, which governs **Plug & Charge** technology, allowing - for seamless and secure EV charging without requiring physical payment methods - or manual user authentication. - - - - ## **Key Components of the Hubject V2G PKI** - - - ### 1. **Root Certificate Authority (Root CA)** - - - The trust anchor for the entire ecosystem. - - - Issues certificates to intermediate CAs (Sub-CAs). - - - ### 2. **Subordinate Certificate Authority (Sub-CA)** - - - Issues certificates to participants such as charging stations, EV - manufacturers, and mobility operators. - - - Ensures that entities are authenticated and authorized to participate in - Plug & Charge. - - - ### 3. **Provisioning Authority (PA)** - - - Manages the distribution of **Contract Certificates** to EV users. - - - Ensures that only valid and verified vehicles and users can participate in - Plug & Charge transactions. - - - ### 4. **Registration Authority (RA)** - - - Responsible for verifying the identity of entities before issuing - certificates. - - - Handles certificate lifecycle processes, including issuance, renewal, and - revocation. - - - ### 5. **Certificate Revocation List (CRL) and Online Certificate Status - Protocol (OCSP)** - - - Supports real-time validation and revocation of certificates to maintain - system security. - - - - ## **How the Hubject V2G PKI Works** - - - ### **1. Certificate Issuance** - - - Electric vehicle manufacturers and charging station operators obtain - certificates from the Sub-CA. - - - EV users receive **Contract Certificates** tied to their charging - agreements, enabling Plug & Charge. - - - ### **2. Authentication Process** - - - When an EV connects to a charging station, the station verifies the - vehicle’s Contract Certificate against the Hubject V2G PKI. - - - Mutual TLS (mTLS) is used to establish a secure communication channel. - - - ### **3. Transaction Validation** - - - The charging station authenticates the EV’s certificate. - - - The EV verifies the charging station’s certificate, ensuring both parties - are trusted. - - - ### **4. Payment and Billing** - - - Once the vehicle is authenticated, the system initiates and logs the - charging session. - - - Payment is processed automatically based on the linked Contract Certificate. - - - - ## **Security Features of Hubject V2G PKI** - - - **Mutual Authentication:** Both EVs and charging stations authenticate each - other using X.509 certificates. - - - **Data Integrity:** Digital signatures protect communication from tampering. - - - **Confidentiality:** All communication is encrypted to prevent - eavesdropping. - - - **Certificate Lifecycle Management:** Ensures timely renewal and revocation - of certificates to maintain trust. - - - - ## **Key Standards and Compliance** - - - **ISO 15118-2 and ISO 15118-20:** Defines Plug & Charge communication - protocols. - - - **ETSI and eIDAS:** Ensures compliance with European security regulations. - - - **WebTrust for CAs:** Establishes best practices for PKI operations. -website: https://www.hubject.com/download-pki -contact: '' -ccadb: false -legal-context: '' -audit: [] -requirements: [] -discussions: [] -issues: [] -trust-lists: - info: '' - policy: https://www.hubject.com/download-pki - trust: []