Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Automotive Software - ISO 21434 Compliance Simplified

The modern vehicle comes equipped with a variety of software systems. Especially features that connect it to the outside world, such as online updates, fleet management and communication between vehicles, offer attack surface. The security of automotive software is crucial, not only because bug-induced call-backs are costly, but also because the well-being of passengers depends on it.

Automatically Detect Concurrency Issues in Automotive Software

What to Expect CI Fuzz CLI is an open-source solution that lets you run feedback-based fuzz tests from your command line. Every developer can use it to find bugs and vulnerabilities with three simple commands. In this live stream, our expert Daniel will: All code examples and tools used are open-source.#c/c++ #fuzzing #security #opensource #automotive

Fuzz Testing Automotive Software With Dependencies

The new ISO/SAE 21434 increases the requirement for security testing in the automotive domain. Car manufacturers must now provide advanced security tests for each software component, as part of the validation process. This includes either, penetration testing, vulnerability scanning and/or fuzz testing. But especially the early adoption of fuzz testing is currently becoming best practice among German car manufacturers.

Fuzzing Embedded Systems With Dependencies (for Automotive)

In this recorded live hacking session, Daniel Teuchert, will demonstrate an automated testing approach, that will instantly improve your code coverage and also helps you to protect your automotive software against unexpected edge cases. See full description and use case: page.code-intelligence.com/fuzzing-with-dependencies/20210429