Hmm, I'm leaning towards B) embedded. I mean, if security is truly part of the DevSecOps culture, it should be so ingrained in the daily work that it's just second nature. Like brushing your teeth - you don't think about it, you just do it.
Ooh, good point. Automated security checks and controls would definitely be ideal. Although, I wonder if that might miss some of the human element that's important in DevSecOps. Maybe a combination of embedded and automated is the way to go.
I don't know, you guys. I think D) automated is the way to go. If we can get security processes automated as much as possible, that's going to be the most efficient and effective approach in a DevSecOps environment.
Ha! Embedded, integrated, it's all the same, right? Let's be honest, most of us are just going to guess anyway. Maybe we should ask the instructor if they accept 'whatever works' as an answer.
Hmm, I'm not so sure. I was thinking C) integrated might be a better fit. That suggests a more holistic approach, where security is woven throughout the entire process, not just embedded in certain parts.
This is a great question! It really gets to the heart of DevSecOps - integrating security into the entire software development lifecycle. I think the best answer is B) embedded, as that really captures the idea of security being a seamless part of the daily work, not just an add-on or afterthought.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Domonique
6 months agoRuthann
7 months agoDaniel
7 months agoTwana
7 months agoRuthann
7 months agoAdelle
7 months agoLovetta
7 months agoAlfred
8 months agoLevi
8 months agoKarrie
8 months agoMargart
8 months agoMarcelle
8 months agoKaycee
8 months ago