CBK
Central Bank of Kenya
Industries Regulated
Banking and lending, Regulated financial services
Region: Africa
Kenya’s framework combines Central Bank prudential and cyber guidance, CMA corporate-governance rules and the Data Protection Act. Regulated enterprises need a connected operating model for risk appetite, control testing, incident response, third-party risk and board reporting.
Africa governance, risk and compliance intelligence
Central Bank of Kenya
Industries Regulated
Banking and lending, Regulated financial services
Capital Markets Authority
Industries Regulated
Capital markets and listed companies
Office of the Data Protection Commissioner
Industries Regulated
Cross-sector data controllers and processors
Kenya Computer Incident Response Team Coordination Centre
Industries Regulated
Kenya Computer Incident Response Team Coordination Centre
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 |
|---|---|---|---|---|
| Prudential Guidelines for Institutions Licensed under the Banking ActCBK | Banks and financial institutions licensed under the Banking Act | Corporate governance, risk management, internal controls, internal audit, outsourcing, continuity and supervisory reporting. |
Third-party risks, controls, assessments, treatments, approvals, KRIs and oversight reporting. 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 |
| Risk Management GuidelinesCBK | Banking institutions supervised by CBK | Board risk oversight, appetite, identification, measurement, controls, stress testing, monitoring and reporting. |
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. BoundaryWorkflow and evidence support only. Applicability and legal interpretation remain with the organisation and its advisers. |
Source |
| Guidance Note on Cybersecurity for the Banking SectorCBK | Banks and other institutions within the guidance scope | Cyber governance, threat and risk assessment, controls, incident response, regulatory reporting, recovery and audit. |
Risk and control registers, assessments, appetite or limits, KRIs, treatments, approvals and board reporting. Cyber-event intake, escalation, investigation, root cause, corrective action, recovery tracking and audit trail. BoundaryGRC workflow and evidence support only. The platforms do not replace technical security monitoring, detection or protection tools. |
Source |
| Code of Corporate Governance Practices for IssuersCMA | Issuers of securities to the public | Board effectiveness, risk governance, internal controls, audit committees, disclosure and accountability. |
Risk and control registers, assessments, appetite or limits, KRIs, treatments, approvals and board reporting. 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 |
| Data Protection Act 2019ODPC | Data controllers and processors within scope | Data governance, impact assessment, security, processor oversight, breach notification and compliance evidence. |
Incident intake, assessment, investigation, notification workflow, corrective action, escalation and closure evidence. Privacy risks, controls, assessments, treatment actions, ownership, approvals and management reporting. 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

