Pass the WGU Courses and Certificates Secure-Software-Design Questions and answers with ValidTests

Manual peer review refers to the systematic examination of software source code by developers other than the original author. This practice is recognized as a valuable tool for reducing software defects and improving the quality of software projects. It involves developers inspecting the code to find and fix mistakes overlooked in the initial development phase, which enhances both the overall quality of software and the developers’ skills. Peer code review is less formal and more “lightweight” than the code inspections performed in the past, and it provides benefits such as knowledge transfer, increased team awareness, and creation of alternative solutions to problems.

References:

Expectations, Outcomes, and Challenges Of Modern Code Review1

Introduction to Software Engineering/Quality/Code Review2

Software Security during Modern Code Review: The Developer’s Perspective3

Penetration testing is an activity where a simulated attack is performed on a software product to identify vulnerabilities that could be exploited by attackers. It is a proactive and authorized attempt to evaluate the security of an IT infrastructure by safely trying to exploit system vulnerabilities, including OS, service and application flaws, improper configurations, and risky end-user behavior. In the context of the Ship phase of the Security Development Lifecycle (SDL), penetration testing is conducted as a final check to uncover any potential security issues that might have been missed during previous phases. This ensures that the software product is robust and secure before it is released.

References:

The Ship phase of the SDL includes activities such as policy compliance review, vulnerability scanning, penetration testing, open-source licensing review, and final security and privacy reviews1.

Penetration testing is a critical component of the Ship phase, as it helps to identify and fix security vulnerabilities before the software is deployed2.

The privacy impact statement requirement that defines how personal information will be protected when authorized or independent external entities are involved is best categorized under Third party requirements. This aspect of privacy impact assessments ensures that personal data is safeguarded even when it is necessary to involve third parties, which could be service providers, partners, or other entities that might handle personal information on behalf of the primary organization. These requirements typically include stipulations for data handling agreements, security measures, and compliance checks to ensure that third parties maintain the confidentiality and integrity of the personal information they process.

References:

Guide to undertaking privacy impact assessments | OAIC1

A guide to Privacy Impact Assessments - Information and Privacy2

Personal Information Protection Law of China: Key Compliance Considerations3

Privacy Impact Assessment - General Data Protection Regulation (GDPR)4

Privacy impact assessment (PIA) - TechTarget5

Comprehensive and Detailed In-Depth Explanation:

ISO/IEC 27001 is an international standard that outlines the requirements for establishing, implementing, maintaining, and continually improving an information security management system (ISMS). Achieving ISO 27001 certification demonstrates an organization's commitment to information security and provides assurance to customers and stakeholders that security best practices are in place.

In the context of the software development life cycle (SDLC), post-release certifications refer to obtaining formal certifications, such as ISO 27001, after a product has been developed and released. This process involves a comprehensive assessment of the organization's information security practices to ensure they align with the standards set forth by ISO 27001. The certification process typically includes:

Gap Analysis: Evaluating existing information security measures against ISO 27001 requirements to identify areas needing improvement.

Implementation: Addressing identified gaps by implementing necessary policies, procedures, and controls.

Internal Audit: Conducting internal audits to verify the effectiveness of the ISMS and readiness for external assessment.

External Audit: Engaging an accredited certification body to perform a thorough evaluation, leading to certification if compliance is demonstrated.

By pursuing ISO 27001 certification post-release, the company aims to enhance its security posture, comply with international standards, and build trust with its customer base.

References:

ISO/IEC 27001:2022 - Information Security Management Systems

 The principle of running with the least privilege is a fundamental security concept that involves granting users only the permissions they need to perform their tasks and no more. This minimizes the risk of a user gaining access to administrator-level functionality that they are not authorized to use. By limiting the privileges of user accounts to the bare minimum necessary, the potential damage from various attacks, such as privilege escalation, is significantly reduced.

References: The concept of least privilege is widely recognized as a critical security measure. Resources like Exabeam’s article on preventing privilege escalation and TechTarget’s guide on privilege escalation attacks provide insights into how enforcing least privilege can mitigate such threats12. These sources verify that running with the least privilege is an effective mitigation technique against the threat of unauthorized access to elevated privileges.

Comprehensive and Detailed In-Depth Explanation:

The scenario outlines the process of decommissioning a legacy application after a new product has successfully taken over its functions. This corresponds to the End of Life phase in the Software Development Life Cycle (SDLC).

The End of Life phase involves retiring outdated systems and transitioning users to newer solutions. This phase ensures that obsolete applications are systematically phased out, reducing maintenance costs and potential security vulnerabilities associated with unsupported software.

In this case, running both the legacy and new applications concurrently provided a safety net to ensure the new system's stability. After confirming the new product's reliability, the organization proceeds to disable the legacy system, marking its End of Life.

References:

Systems Development Life Cycle

Comprehensive and Detailed In-Depth Explanation:

Preventing the disclosure of sensitive information in application responses is primarily addressed by implementing proper Error Handling and Logging practices.

When errors occur, applications may inadvertently reveal sensitive data through detailed error messages. To mitigate this risk, error handling mechanisms should be designed to provide generic error messages to end-users, while detailed error information is logged securely for internal review. This approach ensures that sensitive information, such as system configurations, stack traces, or personal data, is not exposed to unauthorized users.

The OWASP Secure Coding Practices emphasize the importance of error handling and logging to prevent information leakage:

"Ensure that error messages displayed to users do not reveal sensitive information that can be exploited by attackers."

References:

OWASP Secure Coding Practices - Quick Reference Guide

The phase being described is the Implementation phase of the SDLC. During this phase, the actual development starts, and the product begins to be built. The teams are actively writing code, which is a key activity of the Implementation phase. This phase involves translating the design and specifications into executable code, developing the software’s features, and then integrating the various components into a full-fledged system.

References:

The Software Development Life Cycle (SDLC): 7 Phases and 5 Models1.

What Is the Software Development Life Cycle? SDLC Explained2.

SDLC: 6 Main Stages of the Software Product Development Lifecycle3.

Software Development Life Cycle (SDLC) Phases & Models4.

Option D best addresses security change management, here's why:

Focus on Change: The question directly asks about a modification to how remote administration is secured. This aligns with the core goal of security change management, which is to evaluate and control the security implications of changes to systems.

Security-Specific: The question is explicitly concerned with security, not general functionality or requirements.

Practical Aspect: Remote administration access is a frequent target for attackers, making it a common area for security change management scrutiny.