リリースWGU Secure-Software-Design更新された問題PDF
Secure-Software-Design問題集と練習テスト（118試験問題)
WGU Secure-Software-Design 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 15
Which secure coding best practice ensures sensitive information is not disclosed in any responses to users, authorized or unauthorized?
- A. System Configuration
- B. Error Handling and Logging
- C. Input Validation
- D. Authentication and Password Management
正解：B
質問 # 16
Which secure coding practice uses role-based authentication where department-specific credentials will authorize department-specific functionality?
- A. Access Control
- B. Data Protection
- C. Authentication
- D. Input Validation
正解：A
質問 # 17
Which software control test examines an application from a user perspective by providing a wide variety of input scenarios and inspecting the output?
- A. Dynamic
- B. Static
- C. White box
- D. Black box
正解：D
解説：
The software control test that examines an application from a user perspective by providing a wide variety of input scenarios and inspecting the output is known as black box testing. This testing method focuses on the functionality of the application rather than its internal structures or workings. Testers provide inputs and examine outputs without knowing how and where the inputs are worked upon. It's designed to test the system's external behavior.
* Black box testing is used to verify that the system meets the requirements and behaves as expected in various scenarios, including edge cases and incorrect input data. It helps in identifying discrepancies between the system's actual functionality and its specified requirements.
* This type of testing is applicable across various levels of software testing, including unit, integration,
* system, and acceptance testing. It is particularly useful for validating user stories and use cases during the software development process.
* Since black box testing treats the software as a "black box", it does not require the tester to have knowledge of the programming languages or the system's implementation. This allows testers to objectively test the software's behavior and performance.
References: The concept of black box testing is well-documented and is a standard practice in secure software design, as outlined by sources such as LambdaTest1 and other industry best practices.
質問 # 18
The security testing team received a report from one of the contracted penetration testing vendors that details a flaw discovered in the login component of the new software product, along with a recommended fix.
Which phase of the penetration testing process is the team in?
- A. Assess
- B. Deploy
- C. Evaluate and plan
- D. Identify
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The team is in the Assess phase of penetration testing. This phase involves actively testing the software, identifying vulnerabilities, and documenting findings with recommendations. Receiving a report detailing a discovered flaw confirms that testing has been conducted and results are being evaluated. The Identify (A) phase involves defining scope and targets, Evaluate and Plan (B) covers planning test activities, and Deploy (C) refers to executing the test environment setup. The OWASP Penetration Testing Guide and NIST SP 800-
115 clarify that assessment includes vulnerability discovery and documentation.
References:
OWASP Penetration Testing Guide
NIST SP 800-115 Technical Guide to Information Security Testing and Assessment Microsoft SDL Security Testing Guidance
質問 # 19
In which step of the PASTA threat modeling methodology will the team capture infrastructure, application, and software dependencies?
- A. Attack modeling
- B. Risk and impact analysis
- C. Define objectives
- D. Define technical scope
正解：D
解説：
The step of the PASTA threat modeling methodology where the team will capture infrastructure, application, and software dependencies is the Define technical scope step. This step involves detailing the technical elements of the project, which includes understanding and documenting the infrastructure, applications, and software dependencies that are critical to the system's operation and security.
References: The PASTA (Process for Attack Simulation and Threat Analysis) threat modeling methodology is a seven-step process that includes defining the technical scope as a critical step for capturing the necessary technical details of the system being analyzed123.
質問 # 20
Due to positive publicity from the release of the new software product, leadership has decided that it is in the best interests of the company to become ISO 27001 compliant. ISO 27001 is the leading international standard focused on information security.
Which security development life cycle deliverable is being described?
- A. External vulnerability disclosure response process
- B. Security strategy for M&A products
- C. Third-party security review
- D. Post-release certifications
正解：D
解説：
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
質問 # 21
The security team has a library of recorded presentations that are required viewing tor all new developers in the organization. The video series details organizational security policies and demonstrates how to define, test for. and code tor possible threats.
Which category of secure software best practices does this represent?
- A. Training
- B. Architecture analysis
- C. Attack models
- D. Code review
正解：A
解説：
The category of secure software best practices being described is Training. This is because the focus is on educating new developers about organizational security policies and coding practices to mitigate potential threats. Training is a proactive approach to ensure that developers are aware of security concerns and are equipped with the knowledge to address them in their coding practices.
: The importance of training in secure software best practices is supported by industry resources such as the SAFECode's "Fundamental Practices for Secure Software Development" which emphasizes the need for application security control definition and management1, and the NIST's Secure Software Development Framework (SSDF) which recommends integrating secure development practices throughout the software development lifecycle2. Additional support for this category can be found in resources detailing effective secure development practices345.
質問 # 22
In which step of the PASTA threat modeling methodology will the team capture infrastructure, application, and software dependencies?
- A. Attack modeling
- B. Risk and impact analysis
- C. Define objectives
- D. Define technical scope
正解：D
解説：
The step of the PASTA threat modeling methodology where the team will capture infrastructure, application, and software dependencies is the Define technical scope step. This step involves detailing the technical elements of the project, which includes understanding and documenting the infrastructure, applications, and software dependencies that are critical to the system's operation and security.
: The PASTA (Process for Attack Simulation and Threat Analysis) threat modeling methodology is a seven- step process that includes defining the technical scope as a critical step for capturing the necessary technical details of the system being analyzed123.
質問 # 23
Company leadership has discovered an untapped revenue stream within its customer base and wants to meet with IT to share its vision for the future and determine whether to move forward.
Which phase of the software development lifecycle (SDLC) is being described?
- A. Design
- B. Requirements
- C. Implementation
- D. Planning
正解：D
解説：
The phase being described is the Planning phase of the SDLC. This initial stage involves gathering business requirements and evaluating the feasibility of the project. It's when the company leadership would typically meet with IT and other stakeholders to share visions for the future, discuss potential revenue streams, and determine the project'sdirection before moving forward with development. This phase is crucial for setting the groundwork for all subsequent phases of the SDLC.
References:
* The Software Development Life Cycle (SDLC): 7 Phases and 5 Models1.
* What Is the Software Development Life Cycle? SDLC Explained2.
* Software Development Life Cycle (SDLC) Phases & Models3.
質問 # 24
The software security group is conducting a maturity assessment using the Open Web Application Security Project Software Assurance Maturity Model (OWASP SAMM). They are currently focused on reviewing design artifacts to ensure they comply with organizational security standards.
Which OpenSAMM business function is being assessed?
- A. Construction
- B. Deployment
- C. Governance
- D. Verification
正解：D
解説：
Comprehensive and Detailed In-Depth Explanation:
The Open Web Application Security Project (OWASP) Software Assurance Maturity Model (SAMM) is a framework designed to help organizations assess and improve their software security posture. SAMM is structured around five primary business functions: Governance, Design, Implementation, Verification, and Operations.
In this scenario, the focus is on reviewing design artifacts to ensure compliance with organizational security standards. This activity aligns with the Verification business function within SAMM. The Verification function encompasses security practices related to assessing and validating the security of software artifacts throughout the development lifecycle. Key practices under this function include:
* Design Review: Evaluating design documents and models to identify potential security issues and ensure that security requirements are adequately addressed.
* Code Review: Analyzing source code to detect security vulnerabilities and ensure adherence to secure coding standards.
* Security Testing: Conducting various testing methodologies, such as penetration testing and vulnerability scanning, to identify and remediate security weaknesses in the software.
By focusing on the Verification function, the organization aims to proactively identify and address security concerns during the design and development phases, thereby enhancing the overall security posture of their software products.
References:
* OWASP SAMM - Verification
質問 # 25
Which type of threat exists when an attacker can intercept and manipulate form data after the user clicks the save button but before the request is posted to the API?
- A. Elevation of privilege
- B. Information disclosure
- C. Spoofing
- D. Tampering
正解：D
解説：
The type of threat described is Tampering. This threat occurs when an attacker intercepts and manipulates data being sent from the client to the server, such as formdata being submitted to an API. The attacker may alter the data to change the intended operation, inject malicious content, or compromise the integrity of the system. Tampering attacks are a significant concern in secure software design because they can lead to unauthorized changes and potentially harmful actions within the application.
References:
* Understanding the different types of API attacks and their prevention1.
* Comprehensive guide on API security and threat mitigation2.
* Detailed analysis of Man-in-the-Middle (MitM) attacks and their impact on API security3.
質問 # 26
During fuzz testing of the new product, random values were entered into input elements Search requests were sent to the correct API endpoint but many of them failed on execution due to type mismatches.
How should existing security controls be adjusted to prevent this in the future?
- A. Ensure sensitive transactions can be traced through an audit log
- B. Ensure the contents of authentication cookies are encrypted
- C. Ensure all user input data is validated prior to transmitting requests
- D. Ensure all requests and responses are encrypted
正解：C
解説：
Validating user input data before it is processed by the application is a fundamental security control in software design. This process, known as input validation, ensures that only properly formed data is entering the workflow of the application, thereby preventing many types of attacks, including type mismatches as mentioned in the question. By validating input data, the application can reject any requests that contain unexpected or malicious data, reducing the risk of security vulnerabilities and ensuring the integrity of the system.
:
Secure SDLC practices emphasize the importance of integrating security activities, such as creating security and functional requirements, code reviews, security testing, architectural analysis, and risk assessment, into the existing development workflow1.
A Secure Software Development Life Cycle (SSDLC) ensures that security is considered at every phase of the development process, from planning and design to coding, testing, deploying, and maintaining the software2.
質問 # 27
Which secure coding best practice says to require authentication before allowing any files to be uploaded and to limit the types of files to only those needed for the business purpose?
- A. Data protection
- B. File management
- C. Communication security
- D. Memory management
正解：B
解説：
The secure coding best practice that requires authentication before allowing any files to be uploaded, and limits the types of files to only those needed for the business purpose, falls under the category of File Management. This practice is crucial for preventing unauthorized file uploads, which can be a common vector for attacks such as uploading malicious files or scripts. By enforcing authentication, the application ensures that only legitimate users can upload files. Additionally, restricting the file types to those necessary for business operations minimizes the risk of uploading potentially harmful files that could compromise the system.
:
OWASP Secure Coding Practices1
File Upload Security Best Practices | CodeHandbook2
File Upload Protection - 10 Best Practices for Preventing ... - OPSWAT3
質問 # 28
The scrum team decided that before any change can be merged and tested, it must be looked at by the learns lead developer, who will ensure accepted coding patterns are being followed and that the code meets the team's quality standards.
Which category of secure software best practices is the team performing?
- A. Architecture analysis
- B. Training
- C. Penetration testing
- D. Code review
正解：C
解説：
The practice described is Code review, which is a part of secure software development best practices. Code reviews are conducted to ensure that the code adheres to accepted coding patterns and meets the team's quality standards. This process involves the examination of source code by a person or a group other than the author to identify bugs, security vulnerabilities, and ensure compliance with coding standards.
References:
* Fundamental Practices for Secure Software Development - SAFECode1.
* Secure Software Development Framework | CSRC2.
* Secure Software Development Best Practices - Hyperproof3.
質問 # 29
Which software-testing technique can be automated or semi-automated and provides invalid, unexpected, or random data to the inputs of a computer software program?
- A. Fuzzing
- B. Static analysis
- C. Bugtraq
- D. Dynamic analysis
正解：A
解説：
Fuzzing is an automated or semi-automated software testing technique that involves providing invalid, unexpected, or random data to the inputs of a computer program1. This process is designed to uncover coding errors, security vulnerabilities, and other potential issues within the software by observing how it behaves under unexpected or malformed inputs. Fuzzing is particularly effective because it can expose corner cases that have not been properly dealt with and can be used to test programs that take structured inputs, such as file formats or protocols2.
References: 1: Wikipedia - Fuzzing 2: DZone - Fuzzing in Software Engineering
質問 # 30
......
Secure-Software-Design試験問題集合格させるのは更新されたのは2026年年最新の認証済み試験問題：https://jp.fast2test.com/Secure-Software-Design-premium-file.html
ガイド（2026年最新）実際のWGU Secure-Software-Design試験問題：https://drive.google.com/open?id=1I2PUTvgyyb09kvUG7BP6yTw-MV5Vj3VH