CIS Controls v8
CIS Control 16: Application Software Security

CIS Controls v8 CIS-16.13: Conduct Application Penetration Testing

Carry out penetration testing of applications. For critical applications, authenticated penetration testing uncovers business logic flaws more effectively than automated security testing or scanning of code. Penetration testing depends on the tester's skill in manipulating an application by hand, both as an authenticated user and as an unauthenticated one.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 36 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 4 controls

  • CA-8 Penetration Testing
  • CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • SA-11 Developer Testing and Evaluation

FedRAMP Moderate · 4 controls

  • CA-8 Penetration Testing
  • CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • SA-11 Developer Testing and Evaluation

PCI DSS 4.0 · 4 controls

  • 11.4.1 11.4.1 Penetration testing methodology defined and implemented
  • 6.2.3 6.2.3 Code review before release
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.4.1 6.4.1 Public web application review or automated protection

NIST SP 800-218 · 3 controls

  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • ASBv3-PV-7 Conduct regular red team operations

CMMC 2.0 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.12.1e Penetration Testing by Independent Agents
  • 3.14.7e Verify Correctness of Security Functions

NIST SP 800-53 Rev 5 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)

C5 (Germany) · 1 control

  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests

CIS Controls v8.1 · 1 control

  • 16.13 Conduct Application Penetration Testing

ISO 27001:2022 · 1 control

  • 8.29 Security testing in development and acceptance

ISO 27002:2022 · 1 control

  • 8.29 Security testing in development and acceptance

ISO/IEC 42001:2023 · 1 control

  • A.6.2.4 AI system verification and validation
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CIS Control 16: Application Software Security

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-16.13 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 36 it maps to, and the evidence behind each claim, over MCP and REST.