Content library
CIS 18 controls
16.13: Conduct Application Penetration Testing

Requirement description

Conduct application penetration testing. For critical applications, authenticated penetration testing
is better suited to finding business logic vulnerabilities than code scanning and automated security
testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an
authenticated and unauthenticated user.

How to fill the requirement

CIS 18 controls

16.13: Conduct Application Penetration Testing

Task name
Priority
Status
Theme
Policy
Other requirements
Assessments for defining the scope for threat-led penetration testing (TLPT)
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Technical vulnerability management
2
requirements

Examples of other requirements this task affects

Article 26: Advanced testing of ICT tools, systems and processes based on TLPT
DORA
16.13: Conduct Application Penetration Testing
CIS 18
See all related requirements and other information from tasks own page.
Go to >
Assessments for defining the scope for threat-led penetration testing (TLPT)
1. Task description

Organization carries out threat-led penetration testing. Each test needs to cover multiple critical or important functions of the related financial entity.

To properly define the proportionate scope for TLPT:

  • Financial entities shall identify relevant ICT systems, processes and technologies supporting critical or important functions
  • Financial entities shall assess which of these need to be covered by the TLPT

The result of this assessment shall determine the precise scope of TLPT and shall be validated by the competent authorities.

Regular penetration testing
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Technical vulnerability management
23
requirements

Examples of other requirements this task affects

12.6.1: Management of technical vulnerabilities
ISO 27001
14.2.8: System security testing
ISO 27001
18.2.3: Technical compliance review
ISO 27001
DE.CM-8: Vulnerability scans
NIST
5.36: Compliance with policies, rules and standards for information security
ISO 27001
See all related requirements and other information from tasks own page.
Go to >
Regular penetration testing
1. Task description

Static scans on code are the first step in detecting risky vulnerabilities. However, once a service has been deployed, it is vulnerable to new types of attacks (e.g., cross-site scripting or authentication issues). These can be identified by penetration testing.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.