Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
The BDDK Information Systems Regulation sets binding information security, resilience, and electronic banking rules for banks operating in Turkey, including data localisation and annual penetration testing.

What Is the BDDK Information Systems Regulation?
If your group owns a Turkish bank, or your software runs inside one, you will meet the BDDK Information Systems Regulation early. BDDK is the Banking Regulation and Supervision Agency of Turkey, and its Regulation on Information Systems and Electronic Banking Services of Banks was published in the Official Gazette on 15 March 2020 and applied from 1 July 2020. It replaced a 2007 text that had become unworkable for mobile-first banking.
The regulation is unusually prescriptive by UK standards. Where the PRA and FCA set outcomes and let firms choose how to reach them, BDDK writes the control into the rule, then audits against it.
The primary addressees are banks licensed in Turkey, including branches of foreign banks. Parallel BDDK regulations extend similar information systems requirements to financial leasing, factoring, financing, and savings financing companies. Payment and electronic money institutions moved to a separate regime supervised by the Central Bank of the Republic of Turkey in 2021, so a UK fintech entering the Turkish market needs to establish which regulator owns its licence before mapping controls.
Suppliers are caught indirectly. A bank outsourcing a service must follow the BDDK support services regime, which means your contract, your security measures, and sometimes your premises come into scope of the bank’s own audit.
The text runs across governance, operations, and the customer channel. The themes that generate most project work are these.
A companion BDDK regulation governs independent audit of banks’ information systems and banking processes. Audits must be performed by firms authorised by BDDK, which is a meaningful difference from the UK: you cannot simply appoint your usual assurance provider.
A UK bank meets broadly the same objectives through a different instrument set: the PRA’s operational resilience rules, which required firms to remain within impact tolerances for important business services by 31 March 2025, the FCA’s outsourcing and third-party expectations, and the critical third parties regime created under the Financial Services and Markets Act 2023. Testing in the UK is intelligence-led through CBEST rather than mandated as a fixed annual exercise.
Three practical differences catch UK teams out. First, localisation is a hard rule in Turkey, not a risk assessment. Second, specific technical controls are legally binding rather than guidance, so a compensating control argument carries less weight with the supervisor. Third, Turkish data protection law adds its own layer: the KVKK regime applies to customer personal data alongside banking secrecy obligations, and breach handling follows KVKK notification rules rather than ICO practice.
Groups that operate in London and Istanbul normally build a single control framework mapped to ISO 27001 and then record the Turkish-specific deltas: hosting location, authentication parameters, audit firm authorisation, log retention periods, and the reporting lines BDDK expects. That approach keeps the group policy readable while giving the Turkish entity a defensible mapping during supervision.
The remediation work is usually less about buying tools and more about evidence. BDDK auditors ask for dated records: the test report, the approved remediation plan, the change record, the board minute. If you are preparing a Turkish entity for inspection, or validating a bank’s environment before one, our regulation and compliance services cover both the gap assessment and the technical testing it depends on.
Not by itself. The regulation binds institutions licensed by BDDK in Turkey, including local branches of foreign banks. A UK-authorised bank serving Turkish customers cross-border follows PRA and FCA rules. If you establish a branch or acquire a Turkish bank, the full regime applies to that entity, including the requirement to host primary and secondary systems in Turkey.
Only within limits. Primary and secondary information systems must be located in Turkey, so banks use in-country regions and local data centres, and keep sensitive workloads on infrastructure they can demonstrate is domestically hosted. Several hyperscalers now offer Turkish regions, but each use case still needs documented analysis against the localisation requirement and the support services rules.
The regulation requires periodic security testing of information systems, with at least annual penetration testing of internet-facing and internal environments, performed independently of the teams that build and run those systems. Findings must be risk-rated, tracked to closure, and available to auditors. Many banks test more frequently for payment channels and after significant changes.
Only audit firms authorised by BDDK for information systems and banking processes audit. That authorisation is specific, so a bank cannot appoint an assurance provider purely on the basis of international reputation. Internal audit still performs its own reviews, but the statutory information systems audit has to come from an authorised firm on BDDK’s published list.
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.