BRSA
Banking Regulation and Supervision Agency
Industries Regulated
Banking and lending
Region: Middle East / Europe
Turkey combines detailed banking internal-systems requirements with information-systems regulation, capital-market governance and a mature personal-data protection regime. Banks and enterprises need a defensible connection between risk governance, internal audit, technology incidents and time-bound breach notification.
Middle East / Europe governance, risk and compliance intelligence
Banking Regulation and Supervision Agency
Industries Regulated
Banking and lending
Capital Markets Board
Industries Regulated
Capital markets and listed companies
Personal Data Protection Authority
Industries Regulated
Cross-sector data controllers and processors
National Cyber Incidents Response Center
Industries Regulated
Government and critical infrastructure
The applicable perimeter depends on entity type, licence and sector. These priorities provide a practical starting point for programme design and evidence management.
01Each row translates an official regulatory source into an operational GRC focus, then identifies only the platforms with a defensible workflow or evidence role.
| Regulation and Authority | Applies To | Operational Focus | Platform Fit and Workflow Support | Source |
|---|---|---|---|---|
| Banking Law No. 5411BRSA | Banks and other institutions within the Law’s scope | Internal control, risk management, internal audit systems, consolidated oversight and governance responsibilities. |
Audit universe, risk-based planning, RCM-linked testing, working papers, evidence, findings and follow-up. Risk and control registers, assessments, appetite or limits, KRIs, treatments, approvals and board reporting. BoundaryWorkflow and evidence support only. Applicability and legal interpretation remain with the organisation and its advisers. |
Source |
| Regulation on Information Systems and Electronic Banking ServicesBRSA | Banks operating in Turkey | Information-systems governance, risk controls, continuity, third-party services, security events, monitoring and electronic-banking resilience. |
Third-party risks, controls, assessments, treatments, approvals, KRIs and oversight reporting. Cyber-event intake, escalation, investigation, root cause, corrective action, recovery tracking and audit trail. BoundaryWorkflow and evidence support only. Applicability and legal interpretation remain with the organisation and its advisers. |
Source |
| Communique on Corporate Governance II-17.1CMB | Publicly held companies within the Communique’s applicable scope | Board and committee governance, internal control and audit oversight, risk management, disclosure and accountable follow-up. |
Risk and control registers, assessments, appetite or limits, KRIs, treatments, approvals and board reporting. Risk-based assurance, control design and effectiveness testing, evidence, findings and action follow-up. BoundaryNotification workflow and evidence can be configured. Submission to an authority requires an approved process or integration. |
Source |
| Personal Data Protection Law No. 6698KVKK | Data controllers and processors within scope | Data-security measures, controller accountability, internal audits and notification when data is obtained unlawfully. |
Incident intake, assessment, investigation, notification workflow, corrective action, escalation and closure evidence. Audit universe, risk-based planning, RCM-linked testing, working papers, evidence, findings and follow-up. BoundaryNotification workflow and evidence can be configured. Submission to an authority requires an approved process or integration. |
Source |
| Board Decision No. 2019/10 on Breach NotificationKVKK | Data controllers, including relevant overseas controllers | 72-hour Board notification, affected-person communication, breach documentation, response plans and accountable ownership. |
Incident intake, assessment, investigation, notification workflow, corrective action, escalation and closure evidence. Risk-based assurance, control design and effectiveness testing, evidence, findings and action follow-up. BoundaryNotification workflow and evidence can be configured. Submission to an authority requires an approved process or integration. |
Source |
This mapping is an implementation aid, not legal advice. It describes configurable workflow and evidence support, not automatic compliance. Always validate applicability, current versions, implementation dates and supervisory expectations with qualified advisers and the relevant authority.
Brochure-Validated Capability
The mapping uses the capabilities documented in the current brochures. It does not extend the platforms beyond their stated functional scope.

Best suited to enterprise risk ownership, risk and control registers, assessments, appetite and tolerances, KRIs, treatments, approvals, dashboards and board reporting.

Best suited to the audit universe, risk-based planning, engagement execution, RCM-linked design and effectiveness testing, evidence, findings, approvals and follow-up.

Best suited to incident intake, triage, investigation, root-cause analysis, escalation, notifications, corrective and preventive actions, closure and lessons learned.
The platforms support governance workflows, accountability, evidence and reporting. They do not calculate regulatory capital or liquidity, replace technical cybersecurity monitoring, provide legal interpretation, issue external-audit opinions or automatically file statutory notifications unless an approved integration and process are configured.
Use one traceable workflow to translate requirements, manage execution and demonstrate oversight.
01

