Which of the following items is NOT a goal of security deliverables?

Boost your knowledge for the WGU ITAS6231 D487 Secure Software Design Test. Utilize flashcards and multiple-choice questions, complete with explanations and hints, to prepare effectively for success.

A goal of security deliverables is to ensure that security practices are integrated into the software development lifecycle. This includes identifying, mapping, and estimating all relevant activities and requirements that contribute to the overall security posture of the software.

Transferring risk to third parties may be a risk management strategy but is not a specific goal of security deliverables themselves. Security deliverables are focused on identifying vulnerabilities, implementing safeguards, and planning activities related to security. Therefore, while transferring risk can be a part of an overarching security strategy, it does not pertain directly to the creation or management of security deliverables in the development process. The primary intent behind security deliverables is to enhance and maintain security, rather than delegate or offload responsibility for risk to an external entity.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy