When of the following BEST describes now the security principle of validation of a user's access and actions differ within a DevSecOps mindset versus a more traditional approach to this principle?
I remember studying that in DevSecOps, validation is more about continuous monitoring rather than just at a single point. So, I think option C might be right.
Hmm, this is a tough one. I'm a bit confused about the differences between the traditional and DevSecOps approaches to validation. I'll need to carefully read through the options and try to identify the key distinctions.
I've got a good feeling about this one. The DevSecOps approach to validation seems to be more continuous and ongoing, rather than just focused on credentials at the point of access. I'll go with option C.
Ah, this is a tricky one. I'm not entirely sure about the distinction between "at the point of access" and "at the point of request." I'll need to review my notes on DevSecOps principles to make sure I'm understanding this correctly.
Hmm, this question seems to be testing our understanding of the differences between traditional and DevSecOps approaches to user validation. I'll need to carefully consider the nuances of each option.
Okay, let's see here. I think the key is to understand how the validation process differs in a DevSecOps mindset versus a more traditional approach. I'll need to really think through the implications of each answer choice.
Hmm, I'm a bit unsure about this one. The privacy notice is mentioned, but I'm not sure which lawful basis it would primarily refer to. I'll have to think this through step-by-step.
I'm a bit confused by the wording of the question. It's asking about "two of the following statements" being correct, but there are more than two options. I'll need to read through them all and figure out which two are the right answers.
I'm a bit stumped on this one. I know the individual methods, but I'm not sure what the combined approach would be called. I'll have to review my notes and see if I can figure this out.
I'm a bit confused, but I think ERC stands for requests tied to specific applications, while EIPs are broader improvements. Maybe I need to review their definitions again?
Wait, we're supposed to validate users' actions too? I thought we just needed to check their credentials. This DevSecOps thing sounds like a lot of extra work.
I agree with Gayla. Continuous validation is key in a DevSecOps environment. You can't just rely on credentials and hope for the best. Security has to be baked in at every step.
I think option C is the best answer. In a DevSecOps mindset, the validation of user access and actions is a continuous process, not just a one-time check at the point of access or request.
Shenika
3 months agoNettie
3 months agoGracia
3 months agoMacy
4 months agoRoyal
4 months agoShanda
4 months agoZoila
4 months agoDiane
4 months agoCelestina
5 months agoNathalie
5 months agoWillard
5 months agoLou
5 months agoBarrett
5 months agoBritt
5 months agoTambra
5 months agoLaquanda
5 months agoChau
5 months agoRashad
5 months agoMeghan
9 months agoIrma
9 months agoLettie
9 months agoRosio
8 months agoLilli
8 months agoAlex
8 months agoDonte
9 months agoGayla
9 months agoLamar
8 months agoDelmy
8 months agoDiego
8 months agoKaran
9 months agoDomonique
9 months agoBeata
9 months agoCammy
9 months agoLenita
11 months agoMargarita
11 months agoDonte
11 months ago