-
Notifications
You must be signed in to change notification settings - Fork 25
process: add isosae21434 #576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
License Check Results🚀 The license check preparation job ran successfully. Status: Click to expand output
|
The created documentation from the pull request is available at: docu-html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see inline comments
"Clause 14: End of cybersecurity support and decommissioning" - as this is in responsibility of system integrator | ||
|
||
"Annex A-H:" - as it contains no requirements and work products | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where will the tailoring within the relevant clauses be documented? If not done in this PR please create respective follow-up ticket
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see #696
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
* Requirements | ||
.. std_req:: org_management_1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recent communication from VDA suggests that use of clause/sub-clauses numbers and identification of work products in Open Source is possible without asking for approval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see #696
65aed2f
to
254c34d
Compare
|
||
"Clause 7: Distributed cybersecurity activities" - as the project is organized as open source project | ||
|
||
"Clause 9: Concept" - as this is in responsibility of system integrator |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is responsibility of the system integrator, would it make sense to put this somewhere as a requirement for the system integrator.
We should consider to place our "expectations" to external aspects (Operating System, Integrator, applications, hardware abstraction) somewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Compare ISO 26262 blueprint and link to PR for the security plan, see #696
|
||
|
||
.. note:: | ||
Titles of the ISO/SAE 21434 standard clauses are from official `ISO website <https://www.iso.org/search.html>`_ (search for "21434"). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have to state that this list is based on version :2021 (or 1st edition) to make sure where it is created against?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followed the style of ISO 26262, also not mentioned 2018 there yet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added version now
47b4440
to
bf0515a
Compare
Add isosae21434 mapping list
bf0515a
to
77c3ca5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for now
Add isosae21434 mapping list