Question
Model Answer
To ensure that software functions as intended while preventing, detecting, and mitigating vulnerabilities.
Functional testing verifies software features; non-functional testing checks performance, scalability, and security attributes.
To test internal logic, structure, and code paths with full knowledge of the source code.
To test system behavior and outputs without any knowledge of internal code or structure.
A hybrid approach where testers have partial knowledge of internal workings to simulate insider threats or limited-access attackers.
Re-running functional and security tests after code changes to ensure no new vulnerabilities or bugs were introduced.
An automated testing technique that sends large volumes of random or malformed input to detect vulnerabilities or crashes.
Introducing deliberate faults or errors into a system to evaluate how well it handles failures and recovers securely.
A simulated attack designed to exploit vulnerabilities and assess the effectiveness of security controls.
Reconnaissance, Scanning, Exploitation, and Reporting.
Scanning identifies potential vulnerabilities; penetration testing attempts to exploit them.
A testing framework that defines test data, tools, and configurations used to evaluate software performance and security.
Open Source Security Testing Methodology Manual — a peer-reviewed framework for performing standardized security testing.
Systems Security Engineering Capability Maturity Model — used to assess and improve an organization’s security engineering processes.
Avoid using production data, anonymize sensitive information, and protect test data with the same security controls as production data.
It confirms that all exposed entry points are identified and protected according to design and threat models.
Verification that cryptographic modules and algorithms meet standards such as FIPS 140-3 for secure implementation.
To recreate real-world environments and user conditions for evaluating security, performance, and reliability.
By using risk scoring models like CVSS (Common Vulnerability Scoring System) that rank vulnerabilities by impact and exploitability.
Defect: coding error; Flaw: design weakness; Vulnerability: exploitable condition due to a defect or flaw.
Automated integration of tests into CI/CD pipelines to detect issues early in the development process.
A predefined threshold for acceptable levels of security defects before release; defines when a build can pass or fail testing.
It ensures unbiased assessment of software security by a third party not involved in development.