Security & Crypto [General Information]

[qor-lb]

Security Feature Team (FT) Overview

---

👥 Leadership & Ownership

• IG Lead: @sunildevda
• Proxy: (Not specified)

Code Owners

(Formal process ongoing)

Company	Contact	GitHub Handle
ETAS	Athul Mallappallil	@ChansAlive
Valeo		@oeweda
IAV	Andre Larberg	@andilar
Qorix	Volker Haeussler	@PandaeDo
Accenture	Markus Schu	@masc2023

---

💬 Communication

• Slack Channel: #C0B0F1J914Z
• FT Meetings: Wednesdays, 10:00 - 11:00 AM CET/CEST.
  • The Zoom meeting link can be found in the SDV Community Calendar.

---

💻 Development Resources

• Main Repository: eclipse-score/inc_security_crypto
• GitHub Project: SEC - Security FT (view)
• Feature Request: score/issues/905
• Pitch Slides & Minutes: discussions/2818

---

📚 General S-CORE Resources

• S-CORE main page
• Get Involved
• Technical Documentation
• Project Handbook
• S-CORE releases & roadmap

[sunildevda]

06-May-26, 10-11 o'clock

Agenda:

1. [Organizational topic] Check participants
2. [Organizational topic] Additional meetings needed?
   • We will have currently 3 meetings 06-May-26, 13-May-26 and 20-May-26 before the deadline for consensus 24-May-26. Do we need two more meetings on Monday 11-May-26 and Monday 18-May-26. Note: there are quite a few holidays coming up in Germany this month.
3. [Technical deep dive] How each company views the pitch proposal and what is the solution considering the different pitches?

Participants:
@mina-hamdi (Valeo)
mena dawood (Valeo)
Khalid Ramadan (Valeo)
Islam Abobakr (Valeo)
mbejijou-dev (Valeo)
omar EWEDA (Valeo)
@PandaeDo (Qorix)
@andilar -> Andre Larberg (IAV)
Werner Schreiber (Schaeffler)
Laszlo Marton (BMW)
Daniel Krefft (BMW)
@tina Sayarmoafi (Polito)
@masc2023 (Accenture)
@tizava (ETAS)
@ChansAlive (ETAS)
@OliverHeilwagen (ETAS)
@sunildevda (ETAS)

Minutes:

• Already plan for additional meeting. Create meeting request for Monday 11 May from 10AM to 11AM CET (and if needed another for Monday 18 May). R @sunildevda

Opinions about different pitches:
Schaffler (Werner Schreiber):

• Motivation is to have a solution that works in NxP HSE S32G hardware.
• ETAS solution fits well.
• Valeo has "security as service" which will have daemon and this will be then comparable to ETAS crypto daemon approach. but this is not part of OSS.
• Would be good to have Rust API (could be taken up in future)

BMW (Daniel Krefft & Laszlo Marton):

• ETAS solution seems to be similar to current in house solution.
• Autosar API wrappers are important. Architecture should be extensible to include the autosar apis. and this can be outside SCORE.
• Key store is a different topic. and needs to be aligned with the idea what BMW presented in the pitch.

Valeo (Mina Hamdi & Mena Dawood):

• Build on view from Schaffler.
• Chance to integrate different solutions into one solution.
• Which API to be used at higher level? ETAS APIs are SCORE APIs not like PARSEC which is an open source standard.
• PARSEC would be favored internally but ETAS approach is fine
• Hardware drivers can be plugged in

IAV (Andre Larberg):

• Wish different solutions can fit together. Super group of Crypto APIs.
• Question from Schäffler: IAV firmware emulate the hardware in software

ETAS (Athul, Oliver, Sunil)

• Create IAV Provider to demo direct usage of IAV Primula
• Swap SoftHSMv2 with Valeo Cryptoki
• Align OpenSSL version which is used
• Local Provider
  • Question: What operations shall be supported
  • Proposal: Keyless + Ephemeral key + Public key operations
• API: Shall be shaped / refined in OSS S-Core
• Details in attached pictures below.

Other points:

1. Do we need to have new SCORE API or we use industry standards APIs like PKCS11,...?

• BMW will check the proposal that ETAS pitch has and see if it fits their use case.
• APIs proposed by ETAS is extensible. And can be changed and made better on feedbacks here.
• PKCS11 does not support Certificate based functionalities, so we will anyway have to find a solution that is uniform and also addresses these use cases.

2. First level consensus about the unified solution presented by ETAS:

• In high level, the approach presented by ETAS looks ok. and we need to deep dive this and see if this we go ahead with this approach.
• Voting on next meeting on Monday.

3. LG solution not considered as there is no PR or slides available. If these needs to be addressed then may be a feature request in future to be taken. but right now its not considered.

Unified solution slides:

[sunildevda]

11-May-26, 10-11 o'clock

Agenda:

1. [Organizational topic] Check participants
2. Voting and thoughts for the last meetings proposal
3. Next steps

Participants:
@mina-hamdi (Valeo)
mena dawood (Valeo)
Khalid Ramadan (Valeo)
Alaa Mahdy (Valeo)
Ahmed TAREK-RAMADAN (valeo)
Werner Schreiber (Schaeffler)
LEnard Rhenisch (IAV)
Islam Abobakr (Valeo)
Laszlo Marton (BMW)
@tina Sayarmoafi (Polito)
Seongwok Min (LGE)
se-lo Sebastian (ETAS)
@ChansAlive (ETAS)
@OliverHeilwagen (ETAS)
@sunildevda (ETAS)
@tizava (ETAS)

Minutes:
Valeo (Mina)

• already tried a quick check of PKCS11 integration into ETAS crypto and looks like there are no major integration issues.
• IAV FSM is currently not planned to be integrated into the SCORE.
  Schaeffler (Werner Schreiber):
  • Where to integrate the NxP HSE crypto provider? to keep under the crypto security incubation repo.
• We have a consensus to go ahead with the current proposal and present to the architecture community (with next steps described below)

Next steps:

1. Formal steps for consensus closure:

• Highlight the different solutions with color code and may be combine the different pitch slides and present this to architecture board. R. Sunil
• Present in architecture board. Next Monday 18 May 2026. Mina, Sunil, ...
• Code owners - Open point, how many per company? how is it organized?
• Move from SCORE Crypto Incubation (inc_security_crypto) to SCORE Crypto → check with Lars
• Is there any expectation on the roadmap for 2026?

2. Roadmap on the list of changes that should come by which SCORE release till end of 2026

3. ETAS:

• Create a PR to merge the changes (Copy right update from ETAS → SCORE)
• To improve the architectural changes:
  • Migrate gRPC to mw:com (lola) (little complex. needs timeout implementation. needs some work to be done)
  • Concurrency / Thread safety
  • Performance improvement
  • Local provider concept (Has impact on overall architecture)
• Configuration
• Quality (code coverage, ITF based tests, requirements, user documentation,...)

5. IAV:

• To integrate IAV Primula for SCORE → migrate to SCORE set up example mw:log, bazel, baselibs, copyright updated to SCORE...
• To develop the IAV Primula as crypto provider in C++
• Also, update the API to expose these functionalities at SCORE API level. This basically means to update the following contexts: Signature context (to support CRYSTALS-Dilithium 2/3/5, Falcon 512/1024, SPHINCS+ 128/192/256) , Key exchange (to support CRYSTALS-Kyber 512/768/1024 and HQC 128/192/256)
  • Which all you plan to implement especially we see that in the presentation for FALCON we see the timing is unacceptable for automotive? -Y yes it could be suitable for secure boot. all 5 algorithms will be part of SCORE solution.
• Timing measurement (after mw:com (lola)) to compare the additional delay that is introduced due to Lib Daemon communication v/s the measurements shown in pitch slides. We could start with gRPC to get the basic infrastructure and can be doing in parallel with existing solution.
• Quality artifacts for the crypto provider (as expected by SCORE tools and process)

6. Valeo:

• To integrate PKCS11 as crypto provider → migrate to SCORE set up example mw:log, bazel, baselibs, copyright updated to SCORE ...
• To have only one version of OpenSSL on the target
• Quality artifacts for the crypto provider (as expected by SCORE tools and process)

7. Schaffler:

• Fork the ETAS SCORE Crypto / SCORE Crypto incubation repo. Try out implementing one crypto algorithm on HSE and see how it goes.
• Fork the Valeo solution and also try the same thing. this currently is in Rust.
• Try all the three different possibility of integrating the HSE Crypto providers (as shown in the picture) and see how it goes.
• To do performance benchmark on actual hardware and also compare against software provider (ex. PKCS11 → openSSL) -> far future. current focus is on above steps.

8. BMW

• PoC with ETAS code, deploy on the target. migrate the current application from internal solution to ETAS SCORE solution. This will also include API evaluation.
• To do performance benchmark on actual hardware and also compare against software provider (ex. PKCS11 → openSSL) -> far future.

9. Open points/other points:

• Integration point for different Crypto providers? either below SCORE crypto provider or PKCS11 or openSSL -> document this as one of the design decision.
• APIs shall be reviewed and changed/improved where necessary.

10. Come prepared with the propose code owners from each company (if needed) by our next meeting on coming Wednesday.
11. Rough timelines for each of these steps (for roadmap perpetration)

Rough sketch of different contributions from different companies:

[sunildevda]

13-May-26, 10-11 o'clock

Agenda:

• [Organizational topic] Check participants
• Review of the slides with unified solution to present to architecture community
• Code owners
• Time lines for next steps
  • SCORE milestone releases for 2026: https://github.com/eclipse-score/score/milestones
  • Security FT: SEC - Security FT
  • Security for SCORE 0.8 release (13.Jul.2026):
  • Security for SCORE 0.9 release (07.Sep.2026): Security for S-CORE Release v0.9 #2888
  • Security for SCORE 1.0 release (02.Nov.2026):

Participants:
Seongwok Min (LGE)
@tizava (ETAS)
se-lo Sebastian (ETAS)
@mina-hamdi (Valeo)
Volder Haeussler (Qorix)
Werner Schreiber (Schaeffler)
@oeweda
basheerFZ
Laszlo Marton (BMW)
@ChansAlive (ETAS)
@OliverHeilwagen (ETAS)
@sunildevda (ETAS)
Ahmed Rushdy (valeo)
Khalid Ramadan (Valeo)
@GuruprasadBhatL (ETAS)
Islam Abobakr (Valeo)

Minutes:

• Reviewed the unified solution slides (below) and will be presented in architecture community on Monday 18.May 2026
• Code owners: ETAS (Athul - @ChansAlive, @OliverHeilwagen), Valeo ( @oeweda ), Volker Haeussler (Qorix), Markus shu
• Code owners skills to be checked example as shown here: https://eclipse-score.github.io/score/main/modules/orchestrator/docs/safety_mgt/module_codeowners.html. There will be separate invite for this. R. Volker Haeussler
• Open point: Who is/are the code owners from IAV?
• Rough plan for the next steps:

Feature/topic	Contents	Date	Task owner	Task #	SCORE release version -
Create a PR to merge the changes	Copy right update from ETAS → SCORE	22.May.2026	ETAS		v0.8
Integrate GitHub workflows	Tests on Linux only (take over the GitHub workflows from other existing repos like SOME/IP or LCM)	08.June.2026	ETAS		v0.8
Data plane changes		08.June.2026	ETAS		v0.8
Step 1: Migrate gRPC to mw:com (lola) PoC with google test	Move to lola PoC with one isolated googletest. Crypto api to daemon is still in gRPC. With multi client. No timeout. No access control	08.June.2026	ETAS		v0.8
Step 2: Migrate gRPC to mw:com (lola)	Migrate Crypto API to deamon to lola. No timeout. No access control.	20.July.2026	ETAS		v0.9
Architecture documentation for concurrency / Thread safety	Analysis to make the existing architecture is thread safe (concurrency works as expected). Implementation is not in scope. Will be planned based on the analysis outcome	06.July.2026	ETAS		v0.9
Test on QNX8 (local tests)	Get the integration tests running on QNX8 (currently tests are running on Linux only).  Integration tests depends on the ITF set up and not sure when ITF will be stable in SCORE.	20.July.2026	ETAS		v0.9
Analysis for performance improvement	Tests and measurements to understand which code parts take what parts	03.Aug2026	ETAS		v0.9
Local provider concept	Has impact on overall architecture. Only concept and possibly some PoC code.	31.Aug.2026	ETAS		v0.9
Movement from incubation repo to crypto repo	Expected maturity level?  We can do it immediately. After the feature request is approved and closed.  Integration to reference integration repo after more maturity (quality artifacts)	?			v0.9
Changes in lola (dependency to be implemented in lola for Crypto use case)	Config less approach For access control -> get client UIDs	Expected end of 2026
Integrate IAV Primula to SCORE	migrate to SCORE set up example mw:log, bazel, baselibs, copyright updated to SCORE.. Open point: Will it be a separate repo?		IAV
Implement the IAV Primula crypto provider in C++			IAV
Implement Signature context and Key exchange	update the API to expose these functionalities at SCORE API level. This basically means to update the following contexts: Signature context (to support CRYSTALS-Dilithium 2/3/5, Falcon 512/1024, SPHINCS+ 128/192/256) , Key exchange (to support CRYSTALS-Kyber 512/768/1024 and HQC 128/192/256)		IAV?
Integrate PKCS11 (Cryptoki) to SCORE	migrate to SCORE set up example mw:log, bazel, baselibs, copyright updated to SCORE..	To be given in next meeting	Valeo
Have only one version of OpenSSL on target		To be given in next meeting	Valeo
Fork ETAS and Valeo solution and try integration of HSE	This is just to get familiar, nothing will be checked in SCORE. Or? Already started with Option 1. OpenSSL calls are being migrated to HSE calls. Code will be merged after the first step is completed by ETAS.	End of June	Schaffler
PoC for integrating HSE crypto provider for all three integration points		To be taken up later after step 1	Schaffler
PoC with ETAS code, deploy on the target.	migrate the current application from internal solution to ETAS SCORE solution. This will also include API evaluation.	End of June	BMW
Timeout support	in the new approach this can be done in crypto only.
Configuration		2027
Key management functionalities like import key, export key, KDF,...		2027
Certificate management and services		2027
Crypto features like Encryption/Decryption, Signature generation/verification, ..		2027
Quality (code coverage, ITF based tests, requirements, user documentation,...)		2027

Unified solution slides:

[sunildevda]

20-May-26, 10-11 o'clock

Agenda:

• [Organizational topic] Check participants
• Updates from Architecture presentation:
  • Meeting minutes: https://github.com/orgs/eclipse-score/discussions/2457?sort=new#discussioncomment-16957084
  • Went smoothly. no main points raised.
  • Code owners should also be committer. to check this internally in each company.
  • Code owners: ETAS: Athul - @ChansAlive, Valeo: @oeweda, Qorix: @PandaeDo (Volker Haeussler), Accenture: @masc2023 (Markus shu), IAV: @andilar (Andre Larberg)
• Planning board: SEC - Security FT (view)
  • Epics and tasks for ETAS contributions created for next steps till milestone release 0.9
  • Code freeze is two weeks before the milestone release date.
  • High level target is to get the Crypto to be part of milestone release 0.9 -> this means Crypto shall be integratable in the reference integration repo.
  • Timelines for Valeo, Schaffler contributions.
• Hash is also part of Baselibs and this integrates OpenSSL. Checking with Baselibs team about the use cases: https://github.com/orgs/eclipse-score/discussions/2390?sort=new#discussioncomment-16903198. Target is to replace the hash from baselibs and to be offered as part of Crypto.

Participants:

Meeting minutes:

• Committer process to be checked and followed for each committer in the company.

  • Role descriptions: https://eclipse-score.github.io/process_description/main/roles/index.html (process)
  • Detailed version: https://gist.github.com/AlexanderLanin/332d7b258d9b23c09408fa6ad0df5630
  • Committer training: https://www.eclipse.org/projects/training/
  • Found in: https://eclipse-score.github.io/score/main/platform_management_plan/security_management.html#securi…
  • CODEOWNERS example file: https://github.com/eclipse-score/baselibs/blob/main/.github/CODEOWNERS

• Precondition from incubation repo to proper repo needs some minimum documentation like component requirements, .. There is a template and we need to fulfill all the conditions for this. https://github.com/eclipse-score/module_template. This is planned in the issue: Initial module documentation inc_security_crypto#17

• For planning remove the rename from Integrate GitHub workflows inc_security_crypto#8 and move it to a different ticket.

• . Mina, Werner and IAV will create the Epics and Tasks for Valeo, Schaffler and IAV contributions. Process work instructions for planning:
  https://eclipse-score.github.io/score/main/platform_management_plan/project_management.html#planning-tracking

• Valeo the target is 8 June 2026 for both Cryptoki integration and migrate to one openssl version.

• Milestones for Schaffler

• Step 1:

• PoC for options 1,2,3 of NXP HSE integration

• select one use case each (e.g., single shot hashing) and get it running on NXP eval board

• investiage implementation alternatives (exisiting within each option)

• Due date: end of June

Step 2:

• define implementation concept and align with Security&Crypto team
• aspects like legal and performance to be considered
• make implementation planning considering inputs from Security&Crypto team
• Due date: end of July

Step 3:

• Implementation and testing phase, alignec to the overall timeline

• Hash movement from Baselibs need to also check about the quality expectation, lib or lib+daemon approach, maturity expectation and so on. Sunil and Oliver H are in discussion with Andre Babanin and will update here again later.