Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
BDDK requires banks and other institutions it supervises in Turkey to commission independent penetration testing at least annually, across a prescribed set of scope headings, and to remediate what it finds.

What Is the BDDK Penetration Testing Requirement?
In Turkey, a bank that has not been penetration tested in the past year is in breach of a rule, not merely behind on good practice. BDDK, the Banking Regulation and Supervision Agency, has required periodic independent security testing of banks since well before the current information systems regulation, and the obligation now sits inside that regulation alongside the rest of the electronic banking control set. Unusually for a financial regulator, BDDK has also published the scope headings it expects a test to cover.
The core obligation applies to banks licensed in Turkey, including local branches of foreign banks. Parallel BDDK rules extend equivalent information systems requirements to financial leasing, factoring, financing, and savings financing companies. Payment institutions and electronic money institutions moved to supervision by the Central Bank of the Republic of Turkey in 2021 and carry their own testing obligations under that regime, so the first question for any firm entering the Turkish market is which regulator holds its licence.
Suppliers are pulled in indirectly. Where a bank outsources a service under the support services rules, the bank’s testing programme is expected to reach the outsourced environment, which means your systems may be tested because your client is obliged to test them.
BDDK’s published guidance sets out the domains a test must address, and a report that omits one without justification will be queried. The headings include, in substance:
Tests must be performed by parties independent of the teams that build and operate the systems, findings must be risk-rated, and remediation must be tracked to closure with evidence available to the statutory information systems audit. Significant changes to systems in scope are expected to trigger additional testing rather than waiting for the annual cycle.
There is no general legal requirement for a UK bank to run an annual penetration test. UK assurance works through three separate mechanisms. First, intelligence-led testing: CBEST, run under the Bank of England with the PRA and FCA, uses genuine threat intelligence to design red team scenarios against the firms that matter most to financial stability, and GBEST does the same for government. Second, outcome-based supervision: the PRA’s operational resilience expectations required firms to be able to remain within impact tolerances for important business services by 31 March 2025, and testing is how a firm evidences that. Third, scheme requirements: PCI DSS requires at least annual internal and external penetration testing of the cardholder data environment, which catches most UK banks through the card estate rather than through banking regulation.
The contrast is one of philosophy. CBEST asks what a capable adversary would actually do to this firm, is expensive, and happens on a multi-year cycle for a small population. The BDDK requirement asks every bank to cover a defined list every year, which guarantees baseline coverage across the sector at the cost of a certain amount of box-ticking. Firms operating in both markets often run the Turkish scope as a floor and layer scenario-driven red team work on top where the risk justifies it.
The failure mode is predictable: a scope copied from last year, a report delivered three weeks before the audit, and findings closed on paper. Three habits help. Agree the scope against the current asset inventory rather than the previous statement of work, because new mobile features, acquired entities, and cloud workloads appear faster than scope documents are rewritten. Separate retesting from the main engagement so that closure is evidenced independently. And give the tester the same credentials and network position that a compromised employee would have, since an unauthenticated external test alone will not satisfy the internal infrastructure and core application headings.
At Privia Security, we deliver BDDK-aligned testing programmes and the retest evidence that follows them through our Penetration Test Services.
At least once a year across the prescribed scope headings, with additional testing after significant changes to systems in scope. Many banks test payment and internet banking channels more frequently, and treat the annual exercise as the comprehensive baseline rather than the only testing activity. Retesting of remediated findings is expected and is normally evidenced separately from the original report.
A party independent of the teams that develop and operate the systems being tested, with demonstrable competence. Unlike the statutory information systems audit, which must come from a firm BDDK has authorised, penetration testing is not restricted to a published list, so the bank is responsible for assessing the tester’s qualifications, methodology, and independence and for documenting that assessment.
The published scope headings include social engineering against staff, and banks routinely commission phishing and voice-based exercises as part of the annual programme. Scope and consent need care: testing employees raises employment law and personal data questions, so agree the rules of engagement, the handling of individual results, and the reporting format with HR and the data protection function before the exercise begins.
It is the closest, but not a direct substitute. CBEST is intelligence-led red teaming run under the Bank of England for firms whose failure would affect financial stability, performed on a multi-year cycle against realistic threat scenarios. The BDDK requirement is a broad annual test against a defined list of domains, applying to every bank in the market. One optimises for realism, the other for coverage.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.