CSSLP · Question #362
A digital health startup named NovaLine is designing a new platform and wants to manage security risks through every phase of the software development lifecycle. Which practice should be incorporated
The correct answer is B. Adding security requirements during the architecture and design phase. To effectively manage security risks throughout the software development lifecycle, security requirements must be integrated early during the architecture and design phase and maintained continuously.
Question
A digital health startup named NovaLine is designing a new platform and wants to manage security risks through every phase of the software development lifecycle. Which practice should be incorporated early and maintained continuously to address security risks?
Options
- AConducting a risk assessment only after the project is completed
- BAdding security requirements during the architecture and design phase
- CCloud Security Command Center
- DProviding security training only after coding is finished
- ELimiting security testing to the deployment stage
How the community answered
(41 responses)- A2% (1)
- B78% (32)
- C12% (5)
- D2% (1)
- E5% (2)
Why each option
To effectively manage security risks throughout the software development lifecycle, security requirements must be integrated early during the architecture and design phase and maintained continuously.
Conducting a risk assessment only after project completion is a reactive approach, missing opportunities to mitigate risks early and incurring higher remediation costs.
Integrating security requirements during the architecture and design phase ensures that security is built into the system from the ground up, making it more cost-effective and structurally sound than attempting to bolt it on later and addressing risks proactively.
Cloud Security Command Center is a specific Google Cloud product for security management, not a general practice to incorporate early and continuously across the SDLC.
Providing security training only after coding is finished means developers might have introduced vulnerabilities throughout the coding process due to lack of awareness, making it less effective.
Limiting security testing to the deployment stage is a reactive and insufficient approach, as critical vulnerabilities can be introduced and missed in earlier phases, leading to expensive fixes or breaches.
Concept tested: Security in SDLC - Shift Left
Source: https://learn.microsoft.com/en-us/azure/security/develop/security-dev-lifecycle
Topics
Community Discussion
No community discussion yet for this question.