Source: OJ L, 2025/1190, 18.6.2025

Current language: EN

Article 15 Use of internal testers


Summary What does Article 15 of the RTS on threat-led penetration testing say?

This article sets out the rules governing the use of internal testers when conducting a TLPT.

Rather than simply permitting or prohibiting internal testers, the article conditions their use on a series of specific organisational arrangements that financial entities must have in place.

These cover the need for a formal policy, safeguards to protect the entity's broader defensive capabilities during the test, and minimum team composition and employment tenure requirements.

The article also connects to Article 7(1) of this Regulation, which sets out tester requirements that the TLPT authority must consider when approving the use of internal testers, and to Article 27(2)(a) of DORA, which governs that approval itself.

Notably, testers from an ICT intra-group service provider are treated as internal testers for these purposes.

Important points:

  • Establish a formal, documented, and periodically reviewed policy for managing internal testers, covering suitability, competence, conflicts of interest, team composition (a test lead plus at least two members), a 12-month employment requirement, and training provisions.
  • Ensure that using internal testers does not negatively impact the entity's defensive or resilience capabilities or the availability of resources for ICT-related tasks during the TLPT.
  • Disclose the use of internal testers in the test initiation information, the red team test report, and the TLPT summary findings report.

Springlex's summary of the article, a reading aid, not a substitute for the legal text.

    1. Financial entities shall establish all of the following arrangements for the use of internal testers:

      1. the establishment and implementation of a policy for the management of internal testers in a TLPT;

      2. measures to ensure that the use of internal testers to perform a TLPT does not negatively impact the financial entity’s general defensive or resilience capabilities regarding ICT-related incidents or significantly impacts the availability of resources devoted to ICT-related tasks during a TLPT;

      3. measures to ensure that internal testers have sufficient resources and capabilities to perform a TLPT.

    2. The policy referred to in point (a) shall:

      1. contain criteria to assess suitability, competence, potential conflicts of interest of the internal testers and specify management responsibilities in the testing process;

      2. be documented and periodically reviewed;

      3. provide that the internal testing team includes a test lead, and at least two additional members;

      4. require that all members of the test team have been employed by the financial entity or by an ICT intra-group service provider for the preceding 12 months;

      5. include provisions on training on how to perform penetration testing and red team testing of the internal testers.

    1. Where a TLPT authority approves the use of internal testers in accordance with Article 27(2), point (a), of Regulation (EU) 2022/2554, the TLPT authority shall consider the requirements laid down in Article 7(1) of this Regulation.

    1. When using internal testers, the financial entity shall ensure that such use is mentioned in the following documents:

      1. the test initiation information referred to in Article 9;

      2. the red team test report referred to in Article 12(2);

      3. the report summarising the relevant findings of the TLPT referred to in Article 26(6) of Regulation (EU) 2022/2554.

    1. Testers employed by an ICT intra-group service provider shall be considered as internal testers of the financial entity.

We're continuously improving our platform to serve you better.

Your feedback matters! Let us know how we can improve.

Found a bug?

Springflod is a Swedish boutique consultancy firm specialising in cyber security within the financial services sector.

We offer professional services concerning information security governance, risk and compliance.

Crafted with ❤️ by Springflod