Thiqa

Every CBE requirement, mapped and proven.

The Central Bank of Egypt licenses banks, payment providers and fintechs. Thiqa’s agent maps each new requirement to your controls, collects the evidence and hands a finished pack to your approver.

  • Requirement mapping
  • Entity scoping
  • Evidence collection
  • Policy drafting
  • Named approval

Keep up with every requirement.

The CBE keeps issuing new requirements, not one standing rulebook. The agent parses each as it lands and maps its obligations onto the controls you already run, instead of a second programme.

Every requirement

is parsed and mapped as it arrives. The work is a stream to keep up with, not a project to finish.

How mapping works

Evidence that counts more than once.

No more gathering evidence by hand in the weeks before it’s due. The agent collects it from your systems, checks it against its requirement and attaches each artefact to every control it proves.

Once

is enough. An access review pulled for the CBE is the same artefact PCI DSS and ISO 27001 ask for.

How evidence collection works

Scoped to the licence. Signed by a name.

The rest of your group shouldn’t carry one subsidiary’s duties. Obligations route only to the entities with a CBE licence, the agent assembles the pack, and nothing files until a named approver signs it.

Per entity

not per group. A holding company with one licensed subsidiary answers for that subsidiary alone.

How approvals work

Read the new CBE requirements, pull out every obligation and route it to the controls it applies to.

Working through the requirements

Your CBE work.Reused, not redone.

Stop collecting the same evidence for every framework. Thiqa attaches each CBE artefact to every control it proves, across frameworks.

Frameworks and licences Thiqa covers: CBE, SAMA, FRA, PDPL, ISO 27001, PCI DSS, NIST CSF, SOC 2, GDPR, ISO 27701.

Additional features

  • Requirement intake

    Each new requirement mapped to your controls.

  • Scoped per licensed entity

    Obligations routed only to licensed entities.

  • Automatic evidence

    Evidence collected and checked automatically.

  • Policy drafting

    Each policy block drafted against its obligation.

  • Named approval

    A named approver signs every pack.

  • One control set

    CBE, PCI DSS and ISO 27001 from one set of controls.

Frequently asked questions

What its requirements and its cyber security framework set out, not a single standing rulebook. The Central Bank of Egypt supervises the banks, payment service providers and fintechs it licenses, so for them the work is a stream to keep up with, not a project to finish.

Only the ones that hold a CBE licence. Each obligation is scoped to the licensed entity, so in a group with one CBE-licensed subsidiary, the rest of the group isn’t shown duties it doesn’t carry.

No. Thiqa is not certified, approved, accredited or endorsed by the Central Bank of Egypt, and this page is not regulatory guidance. Thiqa prepares your work: it maps each new requirement, collects the evidence and assembles the pack for your approver.

No. Nothing files until a named approver signs the assembled pack. The agent drafts and collects; the decision stays with your team.

No. Evidence is collected once and attached to every control it proves, so an access review pulled for the CBE is the same one PCI DSS and ISO 27001 ask for.

Put CBE compliance on rails.