Navigating agile automotive software development
Download as PPTX, PDF1 like599 views
The document discusses a holistic approach to cybersecurity in automotive software development, emphasizing the integration of DevOps and Agile methodologies. It highlights the importance of threat modeling, continuous integration, and automated testing to identify and mitigate security risks throughout the development lifecycle. The presenters also provide insights on implementing a Jenkins CI system and the need for adaptive security metrics.
Navigating agile automotive software development
- 2. Presenters Jeff Hildreth, Automotive Account Manager Rogue Wave Software Ahmed Abdelrahman, Release Engineer Rogue Wave Software John Chapman, Solutions Architect Rogue Wave Software 2© 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED
- 3. Agenda • A holistic approach to cybersecurity • Blending DevOps and Agile for security • How to implement a Jenkins CI system • Examples of security defects • Q&A 3© 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED
- 4. A holistic approach to cybersecurity
- 5. A holistic approach to cybersecurity © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 5 Information overload Develop an adaptive threat model Threat Model External Data Internal Threat Metric Action
- 6. © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 6 Threat model Most breaches result from input trust issues Threat modeling identifies, quantifies, and addresses security risks by: 1. Understanding the application & environment 2. Identifying & prioritizing threats 3. Determining mitigation actions Identify assets System overview Decompose application Identify threats Prioritize threats
- 7. © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 7 Security overload News Blogs, social media conferences Security standards OWASP, CWE, CERT, etc. Senator Markey report NVD, White Hat, Black Hat OEMs, internal Media More and more software running inside your car Standards and legislation Research Requirements Developers don’t know security (80% failed security knowledge survey)
- 8. Developing a threat metric © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 8 Build score • Automated and functional testing can give you a pass fail metric on every run of the test suite • A metric can be generated from penetration testing based on the number of exploitable paths in your code base • Software quality tools can give you a count of critical static analysis and compiler warnings • A metric can be developed based on the presence of snippets of open source code previously undetected or open source with new known vulnerabilities • All of these metrics can be generated on every build of your software
- 9. DevOps & Agile for security
- 10. Agile development: Integrated security © 2015 Rogue Wave Software, Inc. All Rights Reserved. 10 Adaptive Accept Sprint 1 Sprint 2 Sprint n Release Change Adjust and Track Feedback Review Next Iteration No! Yes! Release to Market Integrate and Test Integrate and Test Integrate and Test Multiple testing points Rapid feedback required “Outside” testing does not meet Agile needs
- 11. DevOps SDLC 11 Continuous Integration SDLC Step UAT/ exploratory testing Functional testing Performance load security Release Deploy Metric Understand Needs Invent Solution Develop Build Commit Idea © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED
- 12. Jenkins CI
- 13. Jenkins CI © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 13
- 14. Security example
- 15. Load, Performance, Security…Testing phase © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 15 Load, Performance, Security, … Testing
- 16. Develop, commit & build © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 16
- 17. Develop, commit & build © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 17
- 18. DevOps SDLC 18 Continuous Integration SDLC Step UAT/ exploratory testing Functional testing Performance load security Release Deploy Metric Understand Needs Invent Solution Develop Build Commit Idea © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED
- 19. Conclusions © 2015 ROGUE WAVE SOFTWARE, INC. ALL RIGHTS RESERVED 19 The application security world is fluid Create concrete, actionable strategies (Threat Metric, analysis & scanning) Delivery cycles are short Update regularly with well-defined process (Agile, CI)
- 20. See us in action: www.roguewave.com Jeff Hildreth | jeff.hildreth@roguewave.com
- 21. Q&A
Editor's Notes
- #11: In an Agile environment, release cycles may be measured in days rather than weeks, making testing for security and compliance more challenging. Agile requires frequent testing and rapid, continuous feedback. Shipping code to a separate group for testing, and receiving results days later, will break the Agile model. To be successful in an Agile environment, compliance and security testing and feedback must be integrated with the rest of the Agile team. Note, with Agile, “Release to Market” doesn’t always mean an external release, Potentially shippable increment, or PSI, and minimum viable product (MVP) are two terms used to describe what may or may not be released to customers. When we examine the process, testing is brought in throughout the development lifecycle, rather than waiting until the development is complete. For this reason, testers are typically part of the Agile teams, and testing user stories are built into the backlog from the outset of the sprint, or iteration.
- #14: http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences An example of unintended behavior introduced via a supplier.
- #16: http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences An example of unintended behavior introduced via a supplier.
- #17: http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences An example of unintended behavior introduced via a supplier.
- #18: http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences An example of unintended behavior introduced via a supplier.
- #20: http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences An example of unintended behavior introduced via a supplier.