To aim for a secure application as an end result, it is important to consider security from the beginning of the software development lifecycle (SDLC). Therefore, the correct phase of SDLC to start aiming for a secure application as an end result is the Requirement Gathering Phase.
Option A: Go-Live (deployment to production) - This phase involves releasing the software to the end-users. While security testing can be conducted during this phase, it is too late to start aiming for a secure application as an end result.
Option B: Support and Maintenance - This phase involves maintaining and improving the software after it has been deployed to the end-users. While security improvements can be made during this phase, the focus should be on maintaining the security of the existing software rather than starting from scratch.
Option C: Requirement Gathering Phase - This phase involves identifying the business requirements and goals of the software. It is important to consider security requirements during this phase to ensure that the software is designed with security in mind from the beginning.
Option D: Prototyping Phase - This phase involves creating a preliminary version of the software to test its functionality. While security testing can be conducted during this phase, the focus is on testing the software's functionality rather than securing it.
Therefore, the answer is: The Answer is: C.