Under active development Content is continuously updated and improved

SA-11(5)Developer Security Testing

PBMM (P3)
Secret (P3)
Management

>Control Description

DEVELOPER SECURITY TESTING AND EVALUATION | PENETRATION TESTING / ANALYSIS The organization requires the developer of the information system, system component, or information system service to perform penetration testing at organization-defined breadth/depth and with organization-defined constraints.

>Supplemental Guidance

Penetration testing is an assessment methodology in which assessors, using all available information technology product and/or information system documentation (e.g., product/system design specifications, source code, and administrator/operator manuals) and working under specific constraints, attempt to circumvent implemented security features of information technology products and information systems. Penetration testing can include, for example, white, gray, or black box testing with analyses performed by skilled security professionals simulating adversary actions. The objective of penetration testing is to uncover potential vulnerabilities in information technology products and information systems resulting from implementation errors, configuration faults, or other operational deployment weaknesses or deficiencies.

Penetration tests can be performed in conjunction with automated and manual code reviews to provide greater levels of analysis than would ordinarily be possible.

>Tailoring Guidance

Apply to boundary and other security critical components. For COTS products require 3rd party evaluation such as Common Criteria.

Ask AI

Configure your API key to use AI features.