Courses and Certificates Changed Secure-Software-Design Questions

The task described involves assessing a document management application that has been in use for many years. This scenario typically requires a security strategy that addresses the unique challenges of legacy code. Legacy code refers to software that has been around for a long time and may not have been developed with current security standards in mind. A security strategy for legacy code would include measures to ensure that the application complies with current organizational policies, which may involve code reviews, updates, and the implementation of modern security practices to mitigate any potential vulnerabilities inherent in older code12.

References:

Remotebase, “Best Practices for Managing Legacy Code”

Medium, “The Engineer’s Complete Guide to Legacy Code”

Parasoft, “Testing Legacy Code & 3 Steps to Update”

The term ‘availability’ in the context of Secure Software Development Lifecycle (SDL) refers to ensuring that systems, applications, and data are accessible to authorized users when needed. This means that the information must be timely and reliable, without undue delays or interruptions. Availability is a critical aspect of security, as it ensures that the software functions correctly and efficiently, providing users with the information they need to perform their tasks.

References:

The definition of availability as per the National Institute of Standards and Technology (NIST) Glossary1.

The Microsoft Security Development Lifecycle (SDL) which emphasizes the importance of availability in secure software design2.

General principles of Secure Software Development Life Cycle (SSDLC) that include availability as a key security goal3.

The step in threat modeling that involves collecting exploitable weaknesses within the product is Identify and document threats. This step is crucial as it directly addresses the identification of potential security issues that could be exploited. It involves a detailed examination of the system to uncover vulnerabilities that could be targeted by threats.

References: The OWASP Foundation’s Threat Modeling Process outlines a structured approach where identifying and documenting threats is a key step1. Additionally, various sources on threat modeling agree that the identification of threats is a fundamental aspect of the process, as it allows for the subsequent analysis and mitigation of these threats2345.