Skip to content
BoG CISD 2026 audits
Start free trialCheck your exact scope

14-day trial · no card needed

ebantaafrica.com/app/engagements/example-bank/dashboard
requirements in the library
747requirements in the library
audit areas from the Directive
28audit areas from the Directive
Annex A proportionality tiers
5Annex A proportionality tiers
laws and frameworks mapped
10laws and frameworks mapped
BoG CISD 2026ISO/IEC 27001:2022NIST CSF 2.0COBIT 2019CIS Controls v8Act 987 · Payment SystemsAct 843 · Data ProtectionOWASP ASVSAct 1038 · CybersecurityOWASP Top 10OWASP API Top 10
How an engagement runs

From scoping letter to closed findings.

One workspace for the audit team, the reviewer and the institution, with the Directive's structure built in.

Inside the workspace

Built around the Directive. Not a generic GRC template.

A dashboard that writes the board pack

Weighted compliance, rating bands, weakest areas first, and every law and framework side by side.

75.7%

Largely compliant

  • Competency Framework60.0%
  • Privacy & Data Protection67.9%
  • Preliminary Matters68.3%
  • Electronic Banking Platforms68.5%
  • Cyber Response71.4%
  • Governance80.1%
  • Below 50%
  • 50 to 69%
  • 70 to 84%
  • 85% and up

Worked example: Example Bank PLC, Tier 1.

Maker–checker review

Nobody approves their own work. Returned areas come back with a note; approved ones lock.

  1. Submitted Part II – GovernanceAma O. · Auditor
  2. Returned: add evidence for 5(1)Kofi M. · Reviewer
  3. Approved · area lockedKofi M. · Reviewer

Evidence, straight from the institution

Auditees get their own portal and see only what you asked them for. Every file is scanned and fingerprinted.

Evidence request · CISD 5(1)

Board-approved information security policy

Submitted
Security policy v3 (signed).pdf Scanned

Due 30 November · from Head of Information Security

Reports you can sign

Issued as numbered, fingerprinted PDFs, plus the workbook and findings register.

Audit report · v2

Example Bank PLC – CISD 2026

sha256 5493554a0106…

Every change on the record

Who changed what, when, and what it was before.

  • Kofi M. approved Part II – Governance16:53
  • Ama O. updated CISD 5(1): status Non-Compliant → Partially16:41
  • Head of InfoSec uploaded Security policy v3 (signed).pdf16:22

Tiered automatically

Annex A tiers and alternative controls applied to every requirement, with BoG overrides.

T1T2T3T4T5
After the report

The report is where most tools stop.

Findings go to management for a response, fixes come back with evidence, and you verify them. Next year starts from where this one ended.

Every finding, followed to closure

Send gaps to management in one go. Track who's answered, what's being fixed and what's ready for you to verify.

55of 273 closed

  1. Not sent41
  2. Awaiting response38
  3. Being fixed112
  4. Ready to verify27
  5. Closed55

Management answers in the portal

What they'll do, who owns it and by when. Their response updates the requirement, the dashboard and the report.

CISD 5(3) · Governance

Appoint a Board Committee on cyber and information security risks

Being fixed

Management response

Agreed. The committee charter goes to the Board in its Q1 sitting, with the CISO as secretary.

Owner
Company Secretary
Target
31 March 2027
Verify and closeReturn with noteRecord accepted risk

Next year starts from this one

Roll forward in one step: same client, scope and team. Open findings and still-valid evidence come along.

Client, scope and team28 areas
Open findings carried over218
Evidence still valid64 files
Governance, 2026 → 2027+14.0 pts

Figures from the worked example: Example Bank PLC, Tier 1.

Everyday speed

The hours you get back.

The small things that make a long engagement lighter, for the audit team and the institution alike.

The request list writes itself

Every applicable requirement, grouped by topic, with what usually satisfies it. Pick, choose who and when, and send. The institution gets one email.

Preliminary Matters3 requests
Governance5 requests
Cyber & Information Security Risk Management9 requests
186 requests · 665 requirements Send 186

Find anything

Type a reference like 4(2) and land on the requirement. Engagements, findings and people too, from any page.

4(2)⌘K
CISD 4(2) Obligations of Regulated EntitiesExpand and enhance their cyber security capabilities.
Finding CISD 4(2)Example Bank PLC · Awaiting response

Alerts that mean something

Areas waiting for your review, evidence sent back, fixes to verify. Each opens where you act.

Governance is ready for your review
Ready to verify: CISD 5(3)

Work is never lost

Every change saves as you go. If a session ends, sign in again in another tab and what you typed is saved.

All changes savedjust now

Light, dark, any screen

Fieldwork on an iPad, review on a laptop, a quick check on a phone. Light, dark, or matching the device.

One assessment, every instrument

Assess once. Report against every one.

Each requirement carries its mappings, so a single result counts toward every law and framework it relates to.

  • BoG CISD 2026747
  • ISO/IEC 27001:2022747
  • NIST CSF 2.0747
  • COBIT 2019747
  • CIS Controls v8574
  • Act 987 · Payment Systems347
  • Act 843 · Data Protection286
  • OWASP ASVS155
  • Act 1038 · Cybersecurity140
  • OWASP Top 1078
  • OWASP API Top 1071

Requirements in the CISD 2026 library mapped to each instrument.

For audit firms

Run several CISD engagements at once with one method and a review trail behind every finding.

  • Assign areas across your team
  • Request evidence from the client
  • Issue numbered reports
Learn more

For regulated institutions

Know where you stand against your tier before the auditors arrive, and stay there between audits.

  • Self-assess against your tier
  • Track remediation to closure
  • Keep evidence current
Learn more
Security

Built for people who audit security.

Two-factor and SSO

TOTP for everyone; Entra ID, Google and Okta sign-in with verified domains.

Isolation, tested

Every request checked against the caller's organisation, attacked in tests.

Evidence you can trust

Uploads scanned for malware and fingerprinted; reports too.

A complete record

An append-only activity log with before-and-after values.

Questions

Before you ask.

Still wondering something? Ask us directly; a person who knows the Directive replies within one working day.

Is Ebanta Comply part of, or endorsed by, the Bank of Ghana?
No. It's an independent product built around the published Cyber & Information Security Directive 2026. Ratings and opinions in a report are the auditor's; the platform does the structuring, scoring and record-keeping.
Can an institution use it without an audit firm?
Yes. A regulated institution can scope itself against its Annex A tier, self-assess every requirement, track remediation and keep evidence current, then share the result with its auditors.
How does the institution take part in an audit?
Invite its people as auditees. They get their own portal showing only what was asked of them: evidence requests, findings to respond to, and messages with the audit team. Nothing else in your workspace is visible to them.
Where is our data kept?
On managed cloud infrastructure with encrypted connections, isolated per organisation and checked on every request. Institutions with data-residency or procurement requirements can run it in their own environment. More on the security page.
What happens when the Directive or its annexures change?
The requirement library is versioned. An engagement keeps the version it started with, so an issued report never shifts under you; rolling forward to next year's engagement moves onto the newest version.
What can we take out of it?
The audit report as a numbered, fingerprinted PDF, an Excel workbook of every result, a findings register (CSV) with management's responses, and a full backup of the engagement you can import again.

See exactly what applies to your institution.

The tier checker takes two minutes. No sign-up.