Automated driving · Level 4 · Connected vehicles
For global manufacturers entering the European market: cybersecurity for the vehicles, teams and partners behind your growth in Europe, with Germany as a particular focus.
At a glance
01Partnering for European readiness
Three steps, in this order. You decide how far we go together.
A joint review of your architecture and of the regulations that apply in Europe and Germany.
Your path to qualification by European OEMs.
Together, we adapt your projects and products for Europe.
02Automated and autonomous driving
A specialised German team with OEM-side experience. Talk to us about a project or simply a question.
Autonomous driving · since 2024
ISO/SAE 21434 assessments of an autonomous-driving software platform for a global technology company.
Automated driving · since 2022
Security engineering for automated driving functions of a European OEM, from risk analysis to test specification.
OEM and tier 1
Cybersecurity interface agreements with global tier-1 suppliers, including the supplier of an automated-driving compute platform, and onboarding of their teams into the OEM’s security process.
Qualification
Qualification programme for one of Germany’s largest automotive engineering service providers, plus workshops for a European OEM’s security engineers.
Automotive team
Management with more than 25 years in automotive software projects for German OEMs.
Client names are confidential. References can be discussed in person.
03Focus on Germany
Together, we get ready for what German and European OEMs, fleet customers and assessors ask, and help initiate the right conversations.
Germany has had a legal framework for Level 4 since 2021. Operation requires a KBA permit or EU type approval and an operating area approved by the responsible state authority.
A technical supervisor can intervene remotely, over radio links protected against unauthorised access.
They work with ISO/SAE 21434 work products, TISAX®-level information security and clear cybersecurity interface agreements.
Camera and location data in public spaces fall under the GDPR and the German data protection authorities.
04Regulatory affairs
As of November 2026.
Since 11 Sep 2026 · from 11 Dec 2027
Reporting obligations since 11 September 2026, full obligations from 11 December 2027.
From 12 Sep 2026
Access by design for new connected products.
Since 1 Aug 2025
Cybersecurity requirements for internet-connected radio equipment.
From 20 Jan 2027
Including protection against corruption of machinery and its software.
Since 2021
Legal framework for Level 4 with technical supervision and protected radio links.
05For suppliers
European OEMs work with a defined cybersecurity process. We have negotiated these interfaces from the OEM side and know the work products involved.
Case study
Agreed responsibilities on both sides and supplier teams that work within the OEM’s security process.
06Getting started
A significant first step with a clear result, then scale.
Two days with your homologation and engineering leads, on site or online: priorities and a roadmap for Europe.
Together, we map your specific requirements: European variants, target markets and partners.
Independent penetration test of one vehicle, system or charging product, with a report for engineering and a summary for stakeholders.
Multi-year collaboration for your European and German roll-out, with one point of contact.
07Case studies
Automotive · Autonomous drivingISO/SAE 21434 assessments
A global technology company develops a vehicle operating system and software stack for autonomous driving, with many teams and its own development process under ISO/SAE 21434.
Result
Commissioned continuously since 2024: independent assessments that give the teams early feedback, milestone by milestone.
Automotive · European OEMSecurity engineering
New driving functions, a defined OEM process under ISO/SAE 21434 and many suppliers working in parallel.
Result
Consistent, auditable security work products and far fewer questions at release.
Automotive · European OEMSupplier integration
A European OEM sources systems from global tier-1 suppliers, including an automated-driving compute platform. Responsibilities for cybersecurity are agreed per component, before development starts rather than at release.
Result
Agreed responsibilities on both sides and supplier teams that work within the OEM’s security process.
Engineering servicesTraining programme
One of Germany’s largest automotive engineering service providers wanted to qualify its own specialists in automotive security, alongside their projects and close to practice.
Result
A programme the customer now runs on its in-house learning platform.
08FAQ
Yes. We work with manufacturers and suppliers worldwide who develop for the European market. Much of the work can be done remotely; workshops and tests can take place on site in Europe.
ISO/SAE 21434 does not certify companies. Our engineers are qualified as Automotive Cybersecurity Engineers (TÜV NORD), and we hold a TISAX® label with assessment level 3.
Yes. We usually work in your process, tools and templates, so the work products fit straight into your organisation.
Under NDA and according to our TISAX®-assessed processes. Client names are confidential; references can be discussed in person.
Contact
Tell us briefly about your product and your plans for Europe. Together, we work out the right first step.
or call us: +49 151 42019537
Moritz Krebbel
Managing Director · Product Security
Automotive and autonomous driving · EU Cyber Resilience Act · Security by design
Andreas Fechner
Managing Director · Enterprise Security
Penetration testing · Security assessments · Digital resilience
