GhCSA-Budapest-Malabo-AfricaCERT-2024-2025 | Budapest Convention, Malabo Convention, AfricaCERT and 2024-2025 Status | 0 |
GhCSA-CII-Designation-Plan-Audit-Risk | CII Designation, Registration, Cybersecurity Plan, Audit and Risk Assessment | 74 |
GhCSA-Child-OnlineProtection-Awareness-Intl-Coop | Child Online Protection, Awareness, Education and International Cooperation | 0 |
GhCSA-Coord-Ghana-DPA-Cybercrime-Sectoral | Coordination with Ghana DPA 2012, Cybercrime Definitions and Cross-Sectoral Frameworks | 0 |
GhCSA-Crosswalk-NIST-ISO-27001-Sectoral | Crosswalk to NIST CSF 2.0, ISO 27001, ISO 22301 and Sector Standards | 0 |
GhCSA-Cybercrime-Lawful-Access-Preservation | Cybercrime Offences, Lawful Access and Electronic Evidence Preservation | 39 |
GhCSA-Implementation-Roadmap | Implementation Roadmap - Organizational Roles, Tooling and Metrics | 76 |
GhCSA-Incident-Reporting-CERT-GH | Cybersecurity Incident Reporting (24-Hour to CSA) and National CERT-GH Engagement | 49 |
GhCSA-Scope-CSAGhana-Defs | Scope, Cyber Security Authority (CSA Ghana) and Key Definitions | 31 |
GhCSA-Sectoral-Coordination-DPC-NCA-BoG | Sectoral Coordination - Data Protection Commission, NCA, Bank of Ghana and Other Regulators | 0 |
GhCSA-Service-Provider-Licensing-Professional | Cybersecurity Service Provider Licensing and Professional Accreditation | 33 |
GhCSA-Status-2024-2025-Strategy-AI | Implementation Status, Cybersecurity Strategy 2024-2028 and 2024-2025 Pipeline | 0 |
1-4 | Sections 1 to 4: application, the Cyber Security Authority, its objects and functions | 0 |
29-34 | Sections 29 to 34: the Cybersecurity Fund | 0 |
35-38 | Sections 35, 37 and 38: designation of critical information infrastructure and the Authority's audits | 0 |
36.1 | Section 36(1) and (2): register the designated critical information infrastructure with the Authority | 0 |
36.3 | Section 36(3): tell the Authority of a change in legal ownership within seven days | 0 |
39.1a | Section 39(1)(a): report a cybersecurity incident on critical information infrastructure within 24 hours | 0 |
39.1b | Section 39(1)(b) and Directive 5.2(k): cause a cybersecurity audit of the critical information infrastructure every year | 0 |
39.1c | Section 39(1)(c) and Directive 7(b): submit the audit report and the other required reports to the Authority | 0 |
40 | Section 40: unauthorised access to critical information infrastructure (offence) | 0 |
41-46 | Sections 41 to 46: the National and Sectoral CERTs, incident monitoring and early warning | 0 |
44 | Sections 44 and 47(1): operate a sectoral CERT that reports monthly, forwards incidents and follows the Authority's directives | 0 |
47-48 | Sections 47(3), 47(4), 48(1) and 48(3): the reporting platform and the point of contact | 0 |
47.2 | Section 47(2): licensed cybersecurity service providers report on their operations and incidents | 0 |
47.5 | Sections 47(5) and 48(2): every institution reports a cybersecurity incident within 24 hours | 0 |
49 | Sections 49, 50 and 100(2): hold a licence before providing any cybersecurity service | 0 |
49.buy | Section 92 in practice: engage only licensed cybersecurity service providers of the right tier | 0 |
5-28 | Sections 5 to 28: the Board, the Joint Cybersecurity Committee, staff, inspectors, finance and reports | 0 |
51 | Section 51(3) and (5): keep to the licence's terms, conditions and purpose | 0 |
52 | Section 52: never transfer a licence | 0 |
53 | Section 53: renew the two-year licence at least one month before expiry | 0 |
54-56 | Sections 54 to 56: suspension, revocation and review of licensing decisions | 0 |
57 | Section 57 and the CSA Guidelines: accreditation of cybersecurity professionals and establishments | 0 |
58-61 | Sections 58, 60 and 61: product certification, awareness and research | 0 |
59 | Section 59(2) to (4) and Directive 5.2(n): comply with the cybersecurity standards the Authority adopts | 0 |
62-68 | Sections 62 to 68: online offences against children and intimate-image offences | 0 |
64 | Section 64: online service operators must not facilitate or permit child sexual solicitation on their service | 0 |
69-75 | Sections 69 to 75: production orders and interception warrants | 0 |
70 | Sections 70(2), 72(2) and 74(2) to (4): execute production orders and interception warrants and keep them confidential | 0 |
76 | Section 76: install an interception capability when the Authority requests, with a cleared focal person | 0 |
77.1 | Section 77(1) to (3): retain subscriber information six years and traffic and content data twelve months | 0 |
77.4 | Section 77(4): use retained or retrieved data only for the warrant's purpose | 0 |
78-80 | Sections 78 to 80: freezing and realisation of property | 0 |
81-85 | Sections 81 to 85: the Industry Forum, industry codes, international cooperation and the Risk Register | 0 |
86 | Sections 86 and 88: provide information the Authority requests and cooperate with it | 0 |
87 | Section 87: comply with a court-ordered authorisation to block, filter or take down | 0 |
89-100 | Sections 89 to 100 and the Schedules: secrecy, courts, guidelines, penalties, regulations, definitions and transition | 0 |
92 | Section 92: comply with the Authority's directives | 0 |
ACT | The Cybersecurity Act, 2020 (Act 1038): the instrument and its status | 0 |
BILL | The Cybersecurity (Amendment) Bill, 2025: pending, not in force | 0 |
CIID.1-4 | CII Directive paragraphs 1 to 4, 6, 9 and 10: objective, applicability, sectors, the Authority's mandate and entry into force | 0 |
CIID.5.1 | Directive 5.1: board-approved cybersecurity policy for the designated CII, reviewed yearly | 0 |
CIID.5.1c | Directive 5.1(c): appoint a senior accountable officer for cybersecurity governance | 0 |
CIID.5.2a | Directive 5.2(a): identify, classify and catalogue all CII assets | 0 |
CIID.5.2b | Directive 5.2(b): control and manage access to CII systems and services | 0 |
CIID.5.2c | Directive 5.2(c): mitigate cyber risk from employees, customers, suppliers and other third parties | 0 |
CIID.5.2d | Directive 5.2(d): security screening of personnel who handle CII information | 0 |
CIID.5.2e | Directive 5.2(e): cybersecurity awareness and training for all employees | 0 |
CIID.5.2f | Directive 5.2(f): security monitoring and response for timely detection | 0 |
CIID.5.2g | Directive 5.2(g): physical protection of CII systems and dependent assets | 0 |
CIID.5.2h | Directive 5.2(h): maintenance and software updates against equipment failure | 0 |
CIID.5.2i | Directive 5.2(i): business continuity and disaster recovery plans, tested and updated | 0 |
CIID.5.2j | Directive 5.2(j): quarterly cybersecurity risk assessment | 0 |
CIID.5.2l | Directive 5.2(l): keep a cybersecurity risk register for the CII | 0 |
CIID.5.2m | Directive 5.2(m): take part in cybersecurity exercises with the Authority and other sectors | 0 |
CIID.5.2o | Directive 5.2(o): keep source code of critical systems in escrow | 0 |
CIID.5.3a | Directive 5.3(a): investigate and mitigate incidents to the Authority's standards | 0 |
CIID.5.3c | Directive 5.3(c): a point of contact for incident reporting and advisories | 0 |
CIID.5.3d | Directive 5.3(d): disclose vulnerabilities found in audits and assessments within 72 hours | 0 |
CIID.7d | Directive 7(d): notify the Authority of planned significant changes before board approval | 0 |
CIID.7e | Directive 7(e): seek the Authority's clearance one month before a major organisational change | 0 |
CIID.8 | Directive 8: request clearance before any activity that could affect a CII | 0 |