REGULATOR · EGYPT · BANKING, PAYMENTS, FINANCE
CBE compliance software for Egyptian institutions.
Central Bank of Egypt obligations mapped to controls, evidenced automatically and filed with a named approver — for banks, payment service providers and fintechs licensed in Egypt.
What the CBE requires
The Central Bank of Egypt supervises the banks, payment service providers and fintechs it licenses, and issues what it expects of them as circulars and a cyber security framework rather than as a single standing rulebook.
Those obligations attach to the licensed entity, not to the group around it: a holding company with one CBE-licensed subsidiary answers for that subsidiary, and its other companies carry duties of their own or none at all.
Thiqa parses each circular, maps its obligations onto the control set you already operate, routes them only to the entities that hold the licence, and collects the evidence from your systems — so a named approver signs a pack that is already assembled rather than one built in the weeks before it is due.
Runs alongside FRASAMAPCI DSS v4.0
CBE FAQ
- Which entities do CBE obligations apply to?
- Only the ones that hold a CBE licence. Each obligation is scoped to the licensed entity, so a group with one CBE-licensed subsidiary does not see the rest of its companies carrying duties they do not have.
- Does CBE evidence have to be collected separately from everything else?
- No. Evidence is collected once and attached to every control it proves, so an access review pulled for CBE is the same artefact PCI DSS and ISO 27001 ask for.