Ghana

Ghana Cybersecurity Act

73 controls. 94 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

73 controls 94 frameworks share controls with it Ghana verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

Ghana Cybersecurity Act Evidence & Implementation Kit

73 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
GhCSA-Budapest-Malabo-AfricaCERT-2024-2025Budapest Convention, Malabo Convention, AfricaCERT and 2024-2025 Status0
GhCSA-CII-Designation-Plan-Audit-RiskCII Designation, Registration, Cybersecurity Plan, Audit and Risk Assessment74
GhCSA-Child-OnlineProtection-Awareness-Intl-CoopChild Online Protection, Awareness, Education and International Cooperation0
GhCSA-Coord-Ghana-DPA-Cybercrime-SectoralCoordination with Ghana DPA 2012, Cybercrime Definitions and Cross-Sectoral Frameworks0
GhCSA-Crosswalk-NIST-ISO-27001-SectoralCrosswalk to NIST CSF 2.0, ISO 27001, ISO 22301 and Sector Standards0
GhCSA-Cybercrime-Lawful-Access-PreservationCybercrime Offences, Lawful Access and Electronic Evidence Preservation39
GhCSA-Implementation-RoadmapImplementation Roadmap - Organizational Roles, Tooling and Metrics76
GhCSA-Incident-Reporting-CERT-GHCybersecurity Incident Reporting (24-Hour to CSA) and National CERT-GH Engagement49
GhCSA-Scope-CSAGhana-DefsScope, Cyber Security Authority (CSA Ghana) and Key Definitions31
GhCSA-Sectoral-Coordination-DPC-NCA-BoGSectoral Coordination - Data Protection Commission, NCA, Bank of Ghana and Other Regulators0
GhCSA-Service-Provider-Licensing-ProfessionalCybersecurity Service Provider Licensing and Professional Accreditation33
GhCSA-Status-2024-2025-Strategy-AIImplementation Status, Cybersecurity Strategy 2024-2028 and 2024-2025 Pipeline0
1-4Sections 1 to 4: application, the Cyber Security Authority, its objects and functions0
29-34Sections 29 to 34: the Cybersecurity Fund0
35-38Sections 35, 37 and 38: designation of critical information infrastructure and the Authority's audits0
36.1Section 36(1) and (2): register the designated critical information infrastructure with the Authority0
36.3Section 36(3): tell the Authority of a change in legal ownership within seven days0
39.1aSection 39(1)(a): report a cybersecurity incident on critical information infrastructure within 24 hours0
39.1bSection 39(1)(b) and Directive 5.2(k): cause a cybersecurity audit of the critical information infrastructure every year0
39.1cSection 39(1)(c) and Directive 7(b): submit the audit report and the other required reports to the Authority0
40Section 40: unauthorised access to critical information infrastructure (offence)0
41-46Sections 41 to 46: the National and Sectoral CERTs, incident monitoring and early warning0
44Sections 44 and 47(1): operate a sectoral CERT that reports monthly, forwards incidents and follows the Authority's directives0
47-48Sections 47(3), 47(4), 48(1) and 48(3): the reporting platform and the point of contact0
47.2Section 47(2): licensed cybersecurity service providers report on their operations and incidents0
47.5Sections 47(5) and 48(2): every institution reports a cybersecurity incident within 24 hours0
49Sections 49, 50 and 100(2): hold a licence before providing any cybersecurity service0
49.buySection 92 in practice: engage only licensed cybersecurity service providers of the right tier0
5-28Sections 5 to 28: the Board, the Joint Cybersecurity Committee, staff, inspectors, finance and reports0
51Section 51(3) and (5): keep to the licence's terms, conditions and purpose0
52Section 52: never transfer a licence0
53Section 53: renew the two-year licence at least one month before expiry0
54-56Sections 54 to 56: suspension, revocation and review of licensing decisions0
57Section 57 and the CSA Guidelines: accreditation of cybersecurity professionals and establishments0
58-61Sections 58, 60 and 61: product certification, awareness and research0
59Section 59(2) to (4) and Directive 5.2(n): comply with the cybersecurity standards the Authority adopts0
62-68Sections 62 to 68: online offences against children and intimate-image offences0
64Section 64: online service operators must not facilitate or permit child sexual solicitation on their service0
69-75Sections 69 to 75: production orders and interception warrants0
70Sections 70(2), 72(2) and 74(2) to (4): execute production orders and interception warrants and keep them confidential0
76Section 76: install an interception capability when the Authority requests, with a cleared focal person0
77.1Section 77(1) to (3): retain subscriber information six years and traffic and content data twelve months0
77.4Section 77(4): use retained or retrieved data only for the warrant's purpose0
78-80Sections 78 to 80: freezing and realisation of property0
81-85Sections 81 to 85: the Industry Forum, industry codes, international cooperation and the Risk Register0
86Sections 86 and 88: provide information the Authority requests and cooperate with it0
87Section 87: comply with a court-ordered authorisation to block, filter or take down0
89-100Sections 89 to 100 and the Schedules: secrecy, courts, guidelines, penalties, regulations, definitions and transition0
92Section 92: comply with the Authority's directives0
ACTThe Cybersecurity Act, 2020 (Act 1038): the instrument and its status0
BILLThe Cybersecurity (Amendment) Bill, 2025: pending, not in force0
CIID.1-4CII Directive paragraphs 1 to 4, 6, 9 and 10: objective, applicability, sectors, the Authority's mandate and entry into force0
CIID.5.1Directive 5.1: board-approved cybersecurity policy for the designated CII, reviewed yearly0
CIID.5.1cDirective 5.1(c): appoint a senior accountable officer for cybersecurity governance0
CIID.5.2aDirective 5.2(a): identify, classify and catalogue all CII assets0
CIID.5.2bDirective 5.2(b): control and manage access to CII systems and services0
CIID.5.2cDirective 5.2(c): mitigate cyber risk from employees, customers, suppliers and other third parties0
CIID.5.2dDirective 5.2(d): security screening of personnel who handle CII information0
CIID.5.2eDirective 5.2(e): cybersecurity awareness and training for all employees0
CIID.5.2fDirective 5.2(f): security monitoring and response for timely detection0
CIID.5.2gDirective 5.2(g): physical protection of CII systems and dependent assets0
CIID.5.2hDirective 5.2(h): maintenance and software updates against equipment failure0
CIID.5.2iDirective 5.2(i): business continuity and disaster recovery plans, tested and updated0
CIID.5.2jDirective 5.2(j): quarterly cybersecurity risk assessment0
CIID.5.2lDirective 5.2(l): keep a cybersecurity risk register for the CII0
CIID.5.2mDirective 5.2(m): take part in cybersecurity exercises with the Authority and other sectors0
CIID.5.2oDirective 5.2(o): keep source code of critical systems in escrow0
CIID.5.3aDirective 5.3(a): investigate and mitigate incidents to the Authority's standards0
CIID.5.3cDirective 5.3(c): a point of contact for incident reporting and advisories0
CIID.5.3dDirective 5.3(d): disclose vulnerabilities found in audits and assessments within 72 hours0
CIID.7dDirective 7(d): notify the Authority of planned significant changes before board approval0
CIID.7eDirective 7(e): seek the Authority's clearance one month before a major organisational change0
CIID.8Directive 8: request clearance before any activity that could affect a CII0

Tell me when Ghana Cybersecurity Act files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Role inventory + RACI
  • Metrics + management review
  • Annual cycle documentation
  • Supervisory dialogue records
  • Role inventory + RACI + DPO designation
  • Operational controls + tooling investment
  • Reporting process + content index
  • Tooling adoption + ESG platform
  • Assurance reports + GRI service
  • Implementation action plan

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for Ghana Cybersecurity Act, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition