The most effective way to identify security vulnerabilities in an application is to conduct automated and manual security testing throughout the development lifecycle. This approach ensures that security is continuously evaluated at every stage of development, rather than waiting until the end. Automated tools can help identify common vulnerabilities quickly, while manual testing allows for more in-depth analysis, including testing for complex, contextual security issues. This proactive and ongoing approach reduces the risk of vulnerabilities being overlooked and helps ensure that security is integrated into the application from the start.
Performing code reviews just prior to release is valuable, but it's not comprehensive enough. Security testing should be done early and continuously, not just before release. Relying solely on secure coding practices is important but not sufficient. Even with secure coding practices, testing is essential to identify vulnerabilities.
Waiting for a single penetration test after development is not effective because waiting until the end can allow many vulnerabilities to go unnoticed during development, leaving the application exposed.

Rapid Elasticity refers to the capability of cloud services to scale resources up or down quickly and efficiently in response to varying demand. This characteristic allows cloud environments to dynamically adjust resource allocation (such as computing power, storage, or bandwidth) to meet the needs of users, ensuring that resources are available when required and minimizing waste when demand decreases.
This ability is a key advantage of cloud computing, providing flexibility and cost efficiency for businesses.

The Shared Security Responsibility Model clarifies which security responsibilities are managed by the CSP and which by the CSC, based on the service model. Reference: [CCSK Study Guide, Domain 1 - Cloud Security Models][16 source].

Compensating controls are implemented when the required controls for a cybersecurity framework cannot be met due to technical or practical limitations. These controls are alternative measures that provide similar protection or risk mitigation. Compensating controls help to ensure that the security posture remains strong even when the primary controls cannot be applied.
Detective controls focus on identifying security incidents after they occur but do not replace required controls.
Preventive controls aim to prevent security incidents from occurring but may not always be possible or practical to implement in certain situations. Administrative controls include policies and procedures but do not address the need for compensating measures when technical controls cannot be met.