Nokta Guard
Get a Quote

Penetration Testing for CBRT-Licensed Payment and E-Money Institutions

The Central Bank of the Republic of Turkey (TCMB/CBRT) Communiqué on the information systems of payment and electronic money institutions requires these institutions to run scenario-based penetration tests covering internal and external threats at least once a year and to report the results to the Central Bank. Nokta Guard plans and reports the test within the procedures annexed to the Communiqué.

Drag and drop, or click.

01 / 03

What is the CBRT Information Systems Communiqué and who does it cover?

The Communiqué on the Information Systems of Payment and Electronic Money Institutions and Data Sharing Services of Payment Service Providers in the Field of Payment Services was published in Official Gazette No. 31676 on 1 December 2021.

It governs the management of payment and e-money institutions' information systems, their audit by authorized independent audit firms, and data sharing services.

02 / 03

Penetration testing expectations

  • Frequency and scope: information systems undergo scenario-based penetration testing covering internal and external threats at least once a year.
  • Who tests: natural or legal persons with no role in meeting information security requirements who hold a national or international penetration testing certification.
  • Method: tests follow the procedures in Annex EK-5 of the Communiqué.
  • Remediation: priority findings are remediated as soon as possible under a board-approved action plan.
  • Reporting: test results, critical vulnerabilities and their remediation status are reported to the Central Bank at least once a year.

03 / 03

How to prepare with Nokta Guard

We clarify with you, at the proposal stage, the certification and competence requirements the regulation sets for the testing provider.

Penetration testing is distinct from the independent information systems audit regulated separately in the Communiqué; we cover the penetration testing side.

  • Penetration testing of payment pages, mobile wallet apps, APIs and merchant integrations.
  • Internal and external network scenarios and, where needed, social engineering tests.
  • A risk-classified report that feeds your action plan and CBRT reporting.
  • Retesting after remediation and a closure record.

FAQ

Frequently Asked Questions

How often must payment institutions run penetration tests?
Is CBRT penetration testing the same as the independent information systems audit?
How are penetration test results reported to the CBRT?
Which systems should a payment institution penetration test include?

Popular searches

No results match your search.

Results could not be loaded. Please try again.