Presentation is loading. Please wait.

Presentation is loading. Please wait.

Mitigation Principles PROPOSAL OICA/CLEPA

Similar presentations


Presentation on theme: "Mitigation Principles PROPOSAL OICA/CLEPA"— Presentation transcript:

1 Mitigation Principles PROPOSAL OICA/CLEPA

2 Approach Taken Piloted by mapping sample (38) threat examples against the 7 “protection objectives” of the Extended CIA model (see Appendix) Confidentiality Integrity Availability Non-repudiation Authenticity Accountability Authorization Defined mitigation principles for the threat examples based on ‘clusters’ of “protection objectives” combinations (see Appendix) Attempted to pitch the language to not define a specific solution, nor be too high level to appear unconsidered Further work is recommended to reference specific recognized artifacts Extended analysis to all threat examples Communized mitigation principles where feasible

3 Conclusion 18 ‘individual’ mitigation mechanisms proposed (see next slide) Some are compounded to mitigate specific threat examples Excluded are potential mitigations where the Threat might be considered to be in the scope of ‘Safety’ rather than ‘Security’ Mitigation mechanisms can be used for different threats However, mitigation mechanisms may not be able to be applied to all aspects of the ecosystem It seems to result in a manageable amount of mitigation mechanisms

4 Proposed Mitigations Mitigations
Access to files and data shall be authorized Best practices for backend systems shall be followed (e.g. OWASP, ISO group) Confidential data shall be encrypted Cybersecurity best practices for software and hardware development shall be followed Cybersecurity best practices shall be followed for storing private keys Data protection best practices shall be followed for storing private and sensitive data. Data protection regulations of individual countries shall be adhered to. Data shall be (end-to-end) authenticated and integrity protected Internal messages shall contain a freshness value Internal/Diagnostic messages shall be authenticated and integrity protected Measures to detect intrusion are recommended Measures to detect unauthorized privileged access are recommended Measures to ensure the availability of data are recommended Organizations shall ensure the defined security procedures are followed Software and configuration shall be authenticated and integrity protected The certification policy for V2X communication shall be followed. V2X messages shall be Authenticated and Integrity protected V2X messages shall contain a freshness value V2X messages should be checked for plausibility

5 APPENDIX

6 Mitigation principles for sample (38) Threat examples (first pass)
Authentication / Integrity 3x V2X messages shall be authenticated and integrity protected. 5x Software shall be authenticated and integrity protected 1x Only authenticated and integrity protected configuration shall be used 1x Data shall be authenticated and integrity protected 1x Data shall be (end-to-end) authenticated and integrity protected. 1x Data exchanged between the backend and vehicle shall be authen- ticated and integrity protected 1x Internal messages shall be authenticated and integrity protected 1x Diagnostic messages shall be authenticated and integrity protected Authorization 6x Access to files and data shall be authorized Confidentiality 2x Confidential data shall be encrypted Other 1x Internal messages shall contain a freshness value Same? (Software) Same? (Data) Same? (Internal messages)

7 Mitigation principles for sample (38) Threat examples (consolidated)
Authentication / Integrity 3x V2X messages shall be authenticated and integrity protected. 6x Software and configuration shall be authenticated and integrity protected 3x Data shall be (end-to-end) authenticated and integrity protected. 2x Internal/Diagnostic messages shall be authenticated and integrity protected Authorization 6x Access to files and data shall be authorized Confidentiality 2x Confidential data shall be encrypted Other 1x Internal messages shall contain a freshness value

8 Mitigation principles for sample (38) Threat examples (further review)
Best practices 10x Best practices for backend systems shall be followed (e.g. OWASP, ISO group) 2x Cybersecurity best practices shall be followed for storing private keys Miscellaneous 2x Measures to ensure the availability of data are recommended Measures to detect unauthorized privileged access are recommended Measures to detect intrusion are recommended Organizations shall ensure the defined security procedures are followed


Download ppt "Mitigation Principles PROPOSAL OICA/CLEPA"

Similar presentations


Ads by Google