PCCET · Question #179
Before incorporating the DevSecOps process, when was security applied in the software- development lifecycle?
The correct answer is C. Right at the end, after the development ended. This question asks about the traditional point where security was integrated into the SDLC before the adoption of DevSecOps.
Question
Before incorporating the DevSecOps process, when was security applied in the software- development lifecycle?
Options
- AIn every step of the lifecycle
- BRight in the middle
- CRight at the end, after the development ended
- DRight at the beginning, before the development started
How the community answered
(35 responses)- A3% (1)
- B6% (2)
- C91% (32)
Why each option
This question asks about the traditional point where security was integrated into the SDLC before the adoption of DevSecOps.
Applying security in every step is the principle of DevSecOps, not the traditional approach.
Security was not typically integrated right in the middle; it was largely a final, separate phase.
Historically, security was often treated as an afterthought in traditional software development, primarily applied right at the end of the lifecycle after development was completed. This 'bolt-on' approach led to late detection of vulnerabilities and costly rework.
Applying security right at the beginning is a 'shift-left' approach, characteristic of modern secure development, not the pre-DevSecOps norm.
Concept tested: Traditional vs. DevSecOps security integration in SDLC
Source: https://learn.microsoft.com/en-us/azure/devops/learn/devops-at-microsoft/shift-left-security?view=azure-devops
Topics
Community Discussion
No community discussion yet for this question.