Menu

Use Case:
Testing Embedded Systems with Dependencies

In this hacking session, we will demonstrate an automated testing approach that will instantly improve your code coverage.

Download Full Recording

abhishek_arya_full-1
Abhishek Arya
Principal Software Engineer
Code Intelligence's new Java fuzzer enabled us to quickly find bugs and vulnerabilities in Java applications.
abhishek_arya_full-1
Abhishek Arya
Principal Software Engineer
Benno Evers final
Benno Evers
Senior Software Engineer

Code Intelligence substantially improved the security of our telemetry engine. Thanks to the native CI/CD integration, we will soon have visibility into all places where user input can wreak havoc. No more time-consuming manual audits.

Benno Evers final
Benno Evers
Senior Software Engineer
Andreas Weichslgartner
Andreas Weichslgartner
Developer, Security Professional

Thanks to CI Fuzz, our security testing became significantly more effective. All our developers are now able to fix business-critical bugs early in the development process, without false positives.

Andreas Weichslgartner
Andreas Weichslgartner
Developer, Security Professional
Mike Samuel
Mike Samuel
Security Engineer

I knew a custom fuzzer I wrote way back was not particularly good, but I was still surprised when CI's fuzzer turned up a bunch of bugs that mine never caught. I was impressed with how well versed the CI folk are in identifying properties to check, and how on point the reports were.

Mike Samuel
Mike Samuel
Security Engineer
UseCaseContinental-1-1

Best Practice: Continental

Continental managed to test a large safety module with 18,000 lines of code (LoC) within only one week.
 
The HMI Business Unit at Continental accelerated their development process and increased their test coverage by implementing continuous fuzz testing into their development process. Continental now achieves above 95% code coverage in almost all of its safety modules.
 
Fuzz testing also enabled the developers to mock their hardware with fuzz data. With this new approach, they are now able to protect their software against edge cases and unexpected behaviors. For example, in the case when a sensor should send unusual or erroneous inputs.

Read Article

3 Reasons Why You Should Fuzz Embedded Systems

Embedded systems play a crucial role in many different industries, such as automotive, consumer electronics, healthcare, and many more. Securing such systems is highly important, as their functionality can have a physical impact on our lives (f.e. example in automotive brake-systems).

1. Increased Code Coverage

With feedback-based fuzzing, you can use information about code coverage to guide your test inputs towards critical areas. Read the full article on Why Leading Tech Companies Use Address Sanitizers to Secure Software

2. Early Bug Detection

Feedback-based fuzzing enables you to find bugs and vulnerabilities before they become a real problem. Read the full case article on Fuzzing Embedded Systems with Dependencies

3. No Bug is Safe From Fuzzing

With the CI Fuzz testing platform, our customers regularly uncover new bugs in applications that have already been tested with conventional testing methods. Watch webinar recording on CVE Hunting With Fuzzing in Open Source Software

Get Started With CI Fuzz

Our developers are happy to assist you with the CI Fuzz testing platform to protect your embedded systems.

Get Started