R155
UNECE WP.29
Support cybersecurity management expectations with product testing you can point to in assessments and customer reviews.
Compliance
Regulations need tests, not templates.
New automotive cybersecurity rules expect organisations to conduct real security testing on their products. Luchs is built so suppliers can comply — and check the box — with hands-on fuzzing and penetration testing on the ECU.
The mandate
What teams are asked to show.
UNECE WP.29 R155 and ISO/SAE 21434 moved cybersecurity from a best-effort activity to a type-approval and engineering requirement. OEMs push the same expectation into the supply chain: test the item, keep evidence, and do it throughout development — not once at the end.
Luchs exists for that gap. Automated testing that produces repeatable, reviewable results on the actual controller.
21434
ISO/SAE
Help verification and validation of cybersecurity-relevant items with fuzzing and penetration testing inside the lifecycle.
OEM
Supply chain
Give Tier-1 and Tier-2 teams a way to answer OEM questionnaires with hands-on results, not a policy PDF.
Outcome
Compliance that survives a review.
Hands-on
Tests run against the product. Findings are tied to interfaces and mechanisms that actually exist on the ECU.
Repeatable
Automation means the same campaign can run again after a firmware change — not only at a milestone.
Remote
Security testing without standing up a dedicated on-site lab for every programme and every supplier site.
Reviewable
Evidence structured for compliance conversations: what was tested, what failed, and what was verified.