Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A BDDK information systems audit is the statutory independent audit of a Turkish bank’s IT governance, controls, and banking processes, performed only by audit firms that BDDK has authorised.

What Is a BDDK Information Systems Audit?
Turkish banks do not choose whether their information systems get audited externally. BDDK, the Banking Regulation and Supervision Agency, requires an independent audit of information systems and banking processes, carried out by a firm that BDDK itself has authorised and that appears on a published list. The resulting report goes to the bank’s board and audit committee and is available to the supervisor. For a UK group that has just acquired a Turkish bank, this is usually the first compliance obligation that cannot be absorbed into existing group assurance arrangements.
The engagement normally splits into two bodies of work. The information systems audit examines how IT is governed and controlled: strategy and organisation, change management, access management, operations, continuity and recovery, information security, and the management of outsourced services. Control objectives derive from international IT governance practice, so an auditor’s workpapers will feel familiar to anyone who has worked with COBIT or with ISO 27001 Annex A.
The banking processes audit looks at the application controls inside specific business processes: lending, deposits, payments, treasury, and the reporting that feeds regulatory returns. The question there is not whether a server is patched but whether the data that leaves the process can be relied upon, which means completeness, accuracy, authorisation, and segregation of duties inside the application.
Both strands produce findings rated by significance, with management responses and remediation deadlines. Open findings carry forward and are re-tested, so a bank that accumulates unresolved items builds a visible pattern for the supervisor.
The restriction on who may perform the audit is the detail UK readers most often get wrong. BDDK authorises audit firms specifically for information systems and banking processes audit, and the list is public. Reputation elsewhere does not substitute. Your group’s usual assurance provider may well hold the authorisation through a Turkish member firm, but that has to be confirmed rather than assumed, and the engagement letter, the team’s local qualifications, and the rotation rules all sit under Turkish rules rather than group policy.
Independence requirements follow from this. The firm performing the audit cannot have implemented the controls it is assessing, which rules out the convenient arrangement where a consultancy builds the control framework and then signs off on it.
A UK bank’s IT control environment is assured through a different mechanism set. Internal audit carries the primary responsibility under the three lines model, with the Chartered Institute of Internal Auditors’ financial services code setting expectations for independence and board access. External assurance appears in specific places: controls reports under ISAE 3402 or SOC 2 from service providers, PCI DSS assessment for card environments, and ISO 27001 certification where a firm chooses it.
The closest regulatory analogue is the skilled person review under section 166 of the Financial Services and Markets Act 2000, where the FCA or PRA requires a firm to commission a report from a firm drawn from an approved panel. The difference is decisive: a section 166 review is ordered when the supervisor has a concern, while the BDDK audit happens on a cycle whether or not anything is wrong. Operational resilience expectations in SS1/21, the outsourcing rules in SS2/21, and the critical third parties regime introduced by the Financial Services and Markets Act 2023 cover similar subject matter, but through supervisory dialogue and self-attestation rather than a mandated external audit report.
Groups that run a single control framework usually map it once to the Turkish requirements and then maintain a delta register: hosting location, authorisation of the audit firm, retention periods, reporting lines to the Turkish board, and the evidence formats auditors expect. The evidence question is where projects lose time. Turkish auditors ask for dated, attributable records rather than a description of how a process works, so a change ticket with an approval name and timestamp carries more weight than a policy document that describes the approval requirement.
It is also worth separating the audit from the technical testing that feeds it. The penetration testing obligation is a distinct requirement whose output the auditor will ask to see, and it should be commissioned early enough that findings can be remediated before the audit window. At Privia Security, we run readiness assessments and the supporting technical work through our cyber risk analysis services, so that the first audit of a newly acquired entity is not also its first honest gap assessment.
The information systems audit runs on an annual cycle, while banking process audits are planned across a rolling programme so that material processes are covered over a defined period. The exact scope and timing are agreed between the bank, the audit firm, and the supervisory expectations in force. Open findings from earlier years are re-tested, so remediation progress is visible across cycles.
No. The statutory audit must come from a firm authorised by BDDK for information systems and banking processes audit, and it must be independent of the design and operation of the controls being assessed. Group internal audit continues its own work in parallel, and its coverage is relevant evidence, but it cannot replace the external engagement or its reporting.
Findings are rated, assigned to management, and tracked to a remediation plan with deadlines. The supervisor sees the pattern across cycles, and persistent high-rated findings attract supervisory attention, including requests for action plans and, in serious cases, administrative measures. The practical consequence for most banks is pressure on the IT budget and visible board-level ownership of the remediation programme.
Not a direct one. UK banks rely on internal audit, voluntary certification, service provider assurance reports, and supervisory engagement under the PRA’s operational resilience and outsourcing expectations. The nearest regulatory tool is a section 166 skilled person review, but that is commissioned when the supervisor has a specific concern rather than on a fixed annual cycle.
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.