Hello, Thanks for the videos, it gives a lot of information. Please do the video on Front Camera Module operation and functionality in car, consider my request 😊
Hello Mr Effera, we're glad that you appreciate our videos. Currently, we've created a schedule with tutorials explaining major concerns of the standards, but not how to apply their requirements to components. But we'll think about your proposal. Might be interesting to switch to a different perspective. Cheers Your video team at Kugler Maag Cie
Hello Jake, almost. Many companies simply define as a goal "Our product shall be secure." You can't work with that generic goal. According to the standard, you use the CS goals to specify how you want to protect your asset (in case you aim to mitigate the risk). The goals are important for the next step: the CS concept. There you specify CS requirements and select Cybersecurity Controls to achieve the CS goals; then you assign these requirements to the components in your architecture or to the organizational environment. So the CS goal becomes an additional product requirement. Now you can work with this goal in your regular requirements engineering. Cheers, your video team at Kugler Maag Cie
@@KUGLERMAAGCIE Depending on the CS goal, it could be risk reduction or risk sharing. I was understanding that a desirable CS goal will be pursuing to take all possible countermeasure to protect assets from the product level, and then it will probably expand as a requirement. Thank you for kindly answer.
Additional comments, the reason why I was confused what is the CS goal because I have small understanding concerning safety. So I get some insight from safety. In safety, OEM gives safety goal and concept. This is top-down. But in security, supplier designs a product usually. So determination of security goal and concept is depended on supplier. In this case bottom-up will be adjusted.
You are right. In FS, the risk to life and limb usually lies with the system, so FS objectives are derived at the concept stage - that is the car maker job. FS is about protecting people from system failure. Cybersecurity is the opposite: to protect the car from being compromised by humans. Therefore, an inside-out approach applies here.
We're publishing one video per month. Topics are Functional Safety, Automotive SPICE, and Automotive Cybersecurity. For the last topic, we'll release to more CS videos this year. Maybe in Autumn.
Excellent summary of TARA. Thank you
Thank you very much! :)
You are an awesome trainer man I loved it thoroughly enjoyed the presentation
Hi there, we're glad that you enjoyed the presentation and really appreciate your feedback. Stay tuned! :)
Hi. Thanks for your information... its clear for me.
than we'vew done the job right ;)
Sehr gut gemacht, Danke !
Vielen Dank! :)
Very good lecture
Thank you very much for your feedback! :)
Hello, Thanks for the videos, it gives a lot of information. Please do the video on Front Camera Module operation and functionality in car, consider my request 😊
Hello Mr Effera,
we're glad that you appreciate our videos. Currently, we've created a schedule with tutorials explaining major concerns of the standards, but not how to apply their requirements to components. But we'll think about your proposal. Might be interesting to switch to a different perspective.
Cheers
Your video team at Kugler Maag Cie
I dont' understand well concering S8. Cybersecurity goal. May the goal become just protection of asset ?
Hello Jake,
almost. Many companies simply define as a goal "Our product shall be secure." You can't work with that generic goal.
According to the standard, you use the CS goals to specify how you want to protect your asset (in case you aim to mitigate the risk). The goals are important for the next step: the CS concept. There you specify CS requirements and select Cybersecurity Controls to achieve the CS goals; then you assign these requirements to the components in your architecture or to the organizational environment. So the CS goal becomes an additional product requirement. Now you can work with this goal in your regular requirements engineering.
Cheers, your video team at Kugler Maag Cie
@@KUGLERMAAGCIE
Depending on the CS goal, it could be risk reduction or risk sharing.
I was understanding that a desirable CS goal will be pursuing to take all possible countermeasure to protect assets from the product level, and then it will probably expand as a requirement.
Thank you for kindly answer.
Additional comments, the reason why I was confused what is the CS goal because I have small understanding concerning safety. So I get some insight from safety.
In safety, OEM gives safety goal and concept. This is top-down. But in security, supplier designs a product usually. So determination of security goal and concept is depended on supplier. In this case bottom-up will be adjusted.
You are right. In FS, the risk to life and limb usually lies with the system, so FS objectives are derived at the concept stage - that is the car maker job. FS is about protecting people from system failure. Cybersecurity is the opposite: to protect the car from being compromised by humans. Therefore, an inside-out approach applies here.
when will we have more videos?
We're publishing one video per month. Topics are Functional Safety, Automotive SPICE, and Automotive Cybersecurity. For the last topic, we'll release to more CS videos this year. Maybe in Autumn.