In Part 2, we will focus on the automotive industry, as it leads the way in enforcing safety, security, and reliability standards as well as best practices for software development. We will then examine how other industries could adopt similar practices.

1. © 2019 Perforce Software, Inc.
Achieving Software Safety, Security, and Reliability
PART 2: APPLYING LESSONS FROM THE AUTOMOTIVE INDUSTRY

2. perforce.com2 | © 2019 Perforce Software, Inc.
Presenter
Richard Bellairs
Product Marketing Manager
Richard has 20+ years of experience across a wide range of
industries. He held electronics and software engineering
positions in the manufacturing, defense, and test and
measurement industries in the nineties and early noughties
before moving to product management and product
marketing. He now champions Perforce’s market-leading
code quality management solution.

3. perforce.com3 | © 2019 Perforce Software, Inc.
Achieving Software Safety, Security, and Reliability
Common Industry
Challenges
1
Applying Lessons From the
Automotive Industry
2
What Does the
Future Hold?
3

4. perforce.com4 | © 2019 Perforce Software, Inc.
Here’s What We’ll Cover Today
(Lessons from the Automotive Industry)
1
2
3
Automotive Tech Trends
Automotive Standards
Lessons for Other Sectors

5. perforce.com5 | © 2019 Perforce Software, Inc.
Electrification
Autonomous
Driving
Connectivity
Automotive Tech Trends
The Automotive World is
Increasingly Software-centred

6. perforce.com6 | © 2019 Perforce Software, Inc.
https://www.embitel.com/blog/embedded-blog/automotive-control-units-development-innovations-mechanical-to-electronics
Event Data Recorder
Voice/Data
Communications
Electric Power Steering Blindspot Detection
Electronic
Stability Control Entertainment System
Digital Turn Signals
Head-up Display
of innovations driven by electronics and software. of vehicle development costs.40%90%
Navigation System

7. perforce.com7 | © 2019 Perforce Software, Inc.
Vehicle Attack Surface
Source: PenTestPartners LLP
USB, CD, and SD Cards
(firmware updates) MITM
attack
Attack from
Mobile device apps
OTA
Malware delivered
through encoded
music
RF: Cellular, WiFi,
Bluetooth, FM, DAB Telematics
Remote keyless entry
Malicious
firmware updates
Tyre Pressure
Monitoring System
Attack on
vehicle BUS
Direct to CAN –
physical access to CAN
wiring externally
Open source
software vulnerabilities
Attack on certificate
& key stores
Sniffing of user data
through screens and
keypads, transmitted
to outside world
Attack from
downloaded apps

8. perforce.com8 | © 2019 Perforce Software, Inc.
https://emarketing.alixpartners.com/rs/emsimages/2018/pubs/EI/AP_Auto_Industry_Recall_Problem_Jan_2018.pdf
SINCE 2013,
ELECTRONICS
RELATED RECALLS
HAVE GROWN SIX
TIMES FASTER
THAN IN PRIOR
YEARS

9. perforce.com9 | © 2019 Perforce Software, Inc.
Automotive Software Standards
Process Functional Safety Coding Cybersecurity
Automotive SPICE ISO 26262
MISRA,
AUTOSAR
SAE J3061
ISO/SAE 21434

10. perforce.com10 | © 2019 Perforce Software, Inc.
Software
Development
Standards:
Common
Themes
Traceability
Configuration Management
Coding standards
Testing
Requirements Management
Hazard analysis
Security analysis
Documentation

11. perforce.com11 | © 2019 Perforce Software, Inc.
Sources of Defects
REQUIREMENTS
ARCHITECTURE
DESIGN
SOURCE CODE
TEST MATERIALS
DOCUMENTS
DATABASE
WEBSITES

12. perforce.com12 | © 2019 Perforce Software, Inc.
Coding standards help to ensure that software is:
• Safe: It can be used without causing harm.
• Secure: It can’t be hacked.
• Reliable: It functions as it should — every time.
• Testable: It can be tested at the code level.
• Maintainable: It can be maintained, even as your
codebase grows.
• Portable: It works the same in every environment.
Achieve High Code Quality by Using a Coding Standard

13. perforce.com13 | © 2019 Perforce Software, Inc.
Consistent code quality — no matter who writes the code.
Software security from the start.
Reduced development costs
Accelerated time to market.
Compliance with industry standards (e.g., ISO).
Why Use a Coding Standard?
1
2
3
4
5

14. perforce.com14 | © 2019 Perforce Software, Inc.
Achieve High Code Quality by Deploying Static Analysis

15. perforce.com15 | © 2019 Perforce Software, Inc.
Types of Statically Detectable Code Defects
Defect Type Example
Static Memory Static buffer overrun
Dynamic Memory Dynamic buffer overrun
Stack-related Stack overflow
Numerical Division by zero
Resource Management Invalid access already freed memory
Pointer-related Dereferencing a NULL pointer
Concurrency Deadlock
Inappropriate code Redundant code
Other Uninitialized variables

16. Electric Sports Car Innovator, Reported Benefits of Helix QAC:
• MISRA C Compliance:
• Implicitly required by ISO 26262
• Fewer unintentional (human) errors:
• No NULL pointer dereferences
• No indexing overflows
• Etc.
• Trained engineers:
• Writing (almost) MIRA compliant code
• Enforcing new code design guidelines
• Improved quality of process and code:
• Code will not be merged to development
branch if it contains any MISRA violation

17. perforce.com17 | © 2019 Perforce Software, Inc.
Functional Safety Standards
Image from: https://www.tuvsud.com/en/resource-centre/infographics/functional-safety-regulation-landscape

18. Comparing the Medical Device Standard, ISO 62304
with the Automotive Standard, ISO 26262

19. perforce.com19 | © 2019 Perforce Software, Inc.

20. perforce.com20 | © 2019 Perforce Software, Inc.
ISO 62304 ISO 26262 (Automotive Functional Safety)
“
where applicable, unit acceptance criteria should be
defined for:
a) proper event sequence;
b) data and control flow;
c) planned resource allocation;
d) fault handling (error definition, isolation, and recovery);
e) initialisation of variables;
f) self-diagnostics;
g) memory management and memory overflows; and
h) boundary conditions.
“
….but only for Class C devices! Apparently it is okay to
leave out these checks for Class B devices, which can
cause injury, and can certainly pose serious security risks!
COM
PREHENSIVE CODING
REQUIREM
ENTS

21. perforce.com21 | © 2019 Perforce Software, Inc.
Part 3: What Does the Future Hold?
Next Time:

22. Questions?