Which design and development deliverable contains the types of evaluations that were performed, how many times they were performed, and how many…

A Security Test Execution Report is a specific deliverable that documents the operational details and metrics of the testing process. Its primary purpose is to provide a summary of the testing activities, including the scope of tests conducted (types of evaluations), the number of initial test runs (how many times performed), and the number of subsequent tests conducted after remediation efforts (how many times re-evaluated). This report provides stakeholders with a clear overview of the testing effort and progress over time.

A. Privacy compliance report: This report focuses narrowly on adherence to privacy regulations (e.g., GDPR, CCPA), not the execution metrics of all security tests.

B. Remediation report: This document details the actions taken to fix identified vulnerabilities, rather than the metrics of the testing process itself.

C. Security testing reports: This is a broad, generic category. The Security Test Execution Report is a more specific type of report that precisely matches the description in the question.

---

1. ISO/IEC/IEEE 29119-3:2021, "Software and systems engineering — Software testing — Part 3: Test documentation." This international standard defines templates for software testing documentation. In Section 8.2.11, it specifies the "Test execution report," which is designed to "summarize the execution of one or more test suites." Its contents include a summary of test activities, which encompasses the scope, number, and status of tests executed and re-executed.

2. NIST Special Publication 800-115, "Technical Guide to Information Security Testing and Assessment." Section 6.2, "Test Report," describes the necessary components of a comprehensive report on testing activities. It states that the report should detail the "activities performed" and "results," which logically includes the types of tests, their frequency, and any re-testing efforts to validate fixes. This aligns with the purpose of a test execution report.

3. Allen, J. H., Barnum, S., Ellison, R. J., McGraw, G., & Mead, N. R. (2008). Software Security Engineering: A Guide for Project Managers. Addison-Wesley Professional. Sourced from the Carnegie Mellon University Software Engineering Institute (SEI), Chapter 11, "Assure Quality: Test and Evaluate," discusses the outputs of the security testing phase. It emphasizes documenting the testing process, including test cases executed, passed, and failed, which forms the basis of a test execution report that tracks initial tests and re-evaluations.