Abstract

The introduction of security flaws into a system may result from design or implementation mistakes. It entail far-reaching consequences for connected embedded or cyber-physical systems, including physical harm. Security experts focus either on finding out and deriving security mechanisms from more or less explicitly defined security requirements or on the a posteriori assessment of vulnerabilities, namely pentesting. These approaches however often miss the necessary iterations between security countermeasures and system functionalities in terms of design and deployment. Worse, they generally fail to consider the implications of security issues over the system’s safety, like for instance the adverse effect that security countermeasures may produce over expected deadlines due to costly computations and communications latencies. SysML-Sec focuses on these issues throughout design and development thanks to its model-driven approach that promotes exchanges between system architects, safety engineers, and security experts. This paper discusses how SysML-Sec can be used to simultaneously deal with safety and security requirements, and illustrates the methodology with an automotive use case.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.