Art.26 Advanced testing of ICT tools, systems and processes based on TLPT
Financial entities identified as significant shall carry out, at least every three years, threat-led penetration testing (TLPT) on live production systems covering critical or important functions, performed by qualified
2
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- TLPT scope, threat intelligence, and test reports (at least three-yearly for in-scope entities) · Policy repository / GRC workspace
- TLPT attestation · Vendor register / contract repository
governing documentDocuments that govern the control
none for this control
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- In-scope entity not performing TLPT
- TLPT not covering critical functions
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetArt.25 Testing of ICT tools and systems · Art.27 Requirements for testers for the carrying out of TLPT