Tanzania Regulation

Parliament of Tanzania

The e-Government General Regulations, 2020

ICTICT formsICT governanceICT maturity assessmentICT policyICT procurementICT project implementationICT project managementICT project performance auditICT project planningICT project reviewICT projectsICT security complianceICT servicesICT sourcingadministrative governanceadvisory bodiesappointmentsaudit reportingbrowser compatibilitybusiness continuitybusiness process re-engineeringcommittee administrationcommittee governancecommittee meetingscommittee procedurecommittee recordscommittee structurecommunications infrastructurecomplaintscomplianceconflict resolutionconflictscustomer supportdatadata compliancedata dictionariesdata disposaldata governancedata managementdata retentiondata sharingdata storagedelegationsdeploymentdesign sharingdigital accessibilitydigital governmentdigital transformationdigitizationdocument copyingdomain namesdomain namespace administrationdomain registrationdomain transferdomain/service registratione-governmente-government infrastructuree-government management and operationse-government policye-government securitye-government serviceselectronic dataelectronic data managementelectronic data sharingelectronic exchangeelectronic procedureelectronic recordsfees and chargesformsgovernancegovernment ICTgovernment ICT securitygovernment ICT sourcinggovernment committeegovernment digital servicesgovernment meetingsgovernment operationsgovernment oversightgovernment resourcesgovernment service administrationgovernment servicesgovernment systems evaluationguidelinesidentification badgesincident responseinformation managementinformation systemsinspectioninspection follow-upinspection noticeinspection procedureinspection reportinginstitutional registrationinternal reportinginternet connectivityinteroperabilitylanguage accessibilitymeeting administrationmeeting conveningmeeting decision-makingmeeting minutesmeeting noticemeeting proceduremobile messagingname registrationnetwork and information systemsnetwork infrastructurenotification and responseoperations and maintenanceoperations oversightpaymentpenaltiesprofessional feesproject approvalproject approval processproject governanceproject scopepublic administrationpublic institution communicationpublic institution procedurespublic institutionspublic sector compliancepublic sector governancepublic service deliverypublic servicesrecord keepingrecordkeepingrecords accessrecords managementregistrationregulationsregulatory inspectionregulatory recommendationsreportingsecurity compliancesecurity governanceservice co-location requestservice conditionsservice deliveryservice pricingservice provisionservice reliabilityservice requestsshared servicessoftware protectionstandardsstandards compliancesystem developmentsystem securitytermination of serviceuser interfaces

Jurisdiction: Tanzania
Structure: 118 provisions
Citation: The e-Government General Regulations, 2020
Dates: Undated source snapshot

More statute details

Dates: Undated source snapshot

Publicly available, excluded from search-engine indexing

This page remains available for direct research for the following reasons:

The record does not meet this release's canonical indexing criteria. (market-indexing-disabled)
The record does not meet this release's canonical indexing criteria. (emergency-noindex)

On this page

Professional statute overview

Enactment structure, operative effect and source provenance

Official source

Purpose and legislative effect

“This section is titled “Interpretation” and sits within Part II on management and operations of e-Government.”

This section is titled “Interpretation” and sits within Part II on management and operations of e-Government. This section is about convening meetings of the National e-Government Steering Committee. This section is titled “Establishment of e-Government Technical Committee.” This section concerns the convening of meetings of the e-Government Technical Committee. This section concerns the quorum of the e-Government Technical Committee.

How the instrument operates

01
Start with the recorded version

Undated source snapshot. The date shown identifies this source expression and should not be treated as proof that no later change exists.
02
Locate the controlling provision

Use the provision map, part headings and full-text filter to move from the broad subject to the exact legal language.
03
Read conditions and exceptions together

Keep subsections, definitions, provisos and cross-references in context before drawing a legal conclusion.
04
Verify currency and official wording

Confirm later legislation, commencement notices and corrections with the official publisher before advice, filing or reliance.

Research entry points

Selected provisions across the instrument. Open any row to continue with the exact stored text.

Interpretation

This section is titled “Interpretation” and sits within Part II on management and operations of e-Government.

Section 2

Government critical system and application software Protection

This section concerns protection of government critical systems and application software.

Section 51

(1) The Authority shall issue guidelines, procedures

The Authority must issue guidelines, procedures, and criteria for approval of new systems, and public institutions must follow them.

Section 24

Save as provided in any other written law, a public

A public institution must manage and govern electronic data across its whole life cycle, unless another written law provides otherwise.

Section 53

Where Professional Fees are applicable, the unit (man-day) rate is TZS 300,000

If Professional Fees apply, the unit (man-day) rate is TZS 300,000 payable to the Authority.

Section 2

Source and current-law status

Source record view

Source record from oagmis.oag.go.tz · Undated source snapshot

Verify current force

The source record does not state a definitive current-law status. Check the official publisher and later amendments before relying on this text.

For advice, pleadings, or compliance decisions, retain the official source and confirm the current consolidated provision.

Official record

Source-indexed provision map

Sections and provisions

Search by section, heading, part or exact legal wording. Every result remains linked to the stored source record.

Search within this statute

Search all stored provisions in this version.

Showing 118 of 118 provisions

Provision 112Offence 4Interpretation 2

§ 2InterpretationInterpretation

This section is titled “Interpretation” and sits within Part II on management and operations of e-Government.

2. Interpretation. PART II MANAGEMENT AND OPERATIONS OF e-GOVERNMENT

Section 2Verify source

Part

PART II

§ 3Convening of meetings of National e-Government SteeringProvision

This section is about convening meetings of the National e-Government Steering Committee.

3. Convening of meetings of National e-Government Steering Committee.

Section 3Verify source

§ 6Establishment of e-Government Technical CommitteeProvision

This section is titled “Establishment of e-Government Technical Committee.”

6. Establishment of e-Government Technical Committee.

Section 6Verify source

§ 7Convening of meetings of e-Government Technical CommitteeProvision

This section concerns the convening of meetings of the e-Government Technical Committee.

7. Convening of meetings of e-Government Technical Committee.

Section 7Verify source

§ 8Quorum of e-Government Technical CommitteeProvision

This section concerns the quorum of the e-Government Technical Committee.

8. Quorum of e-Government Technical Committee.

Section 8Verify source

§ 9Subcommittees of Technical CommitteeProvision

This section is titled “Subcommittees of Technical Committee.”

9. Subcommittees of Technical Committee.

Section 9Verify source

§ 10Convening of meetings of Institutional ICT Steering CommitteeProvision

This section is about convening meetings of the Institutional ICT Steering Committee.

10. Convening of meetings of Institutional ICT Steering Committee.

Section 10Verify source

§ 11Quorum of Institutional ICT Steering CommitteeProvision

This section is about the quorum for the Institutional ICT Steering Committee.

11. Quorum of Institutional ICT Steering Committee.

Section 11Verify source

§ 13Records of meetings of Institutional ICT Steering CommitteeProvision

This provision is about records of meetings of the Institutional ICT Steering Committee.

13. Records of meetings of Institutional ICT Steering Committee.

Section 13Verify source

§ 14Review of e-Government policy frameworkProvision

This section is titled “Review of e-Government policy framework.”

14. Review of e-Government policy framework.

Section 14Verify source

§ 15Co-operation on determination of e-Government projects andProvision

This section concerns co-operation on determining e-Government projects and initiatives.

15. Co-operation on determination of e-Government projects and initiatives.

Section 15Verify source

§ 16Preparation and submission of progress reportsProvision

This section is titled “Preparation and submission of progress reports.”

16. Preparation and submission of progress reports. 1 GN. No. 75 (contd.) e-Government General

Section 16Verify source

§ 17Determination of conflicts and complaintsProvision

This section is titled “Determination of conflicts and complaints.”

17. Determination of conflicts and complaints.

Section 17Verify source

§ 18Correlation of ICT Steering Committee and ICT Management UnitProvision

This section is about the correlation between the ICT Steering Committee and the ICT Management Unit.

18. Correlation of ICT Steering Committee and ICT Management Unit. PART III e-GOVERNMENT INFRASTRUCTURE AND SYSTEMS

Section 18Verify source

§ 3The Chairman of the National e-Government SteeringProvision

The Chairman must convene Committee meetings, and the Secretary must give each member seven days’ prior notice with the agenda, date, time, and place.

3. The Chairman of the National e-Government Steering Committee shall, on such date, time and place, convene meetings of the Committee, and the Secretary shall issue to each member of the Committee, seven days’ prior notice specifying the agenda, date, time and place of meeting

Section 3Verify source

§ 4(1) Two-third of the members of the National eProvision

The committee needs at least two-thirds of its members for a meeting to have a quorum. If the Chairman is absent, members present must choose one of their number to act as Chairman for that meeting. The Committee may also co-opt people from inside or outside government to provide expertise, but they cannot vote.

4.-(1) Two-third of the members of the National e- Government Steering Committee shall constitute a quorum for a meeting of the Committee. (2) In the absence of the Chairman, the Committee members present at the meeting shall elect one of the members to act as Chairman for that meeting. (3)The National e-Government Steering Committee may co-opt persons from within or outside the Government to provide expertise in particular area of e-Government, and such person shall have no right to vote. 6 GN. No. 75 (contd.) e-Government General Submission of reports to Minister

Section 4Verify source

§ 5The National e-Government Steering Committee shallProvision

The National e-Government Steering Committee must prepare a semi-annual report of its deliberations and submit a copy to the Minister.

5. The National e-Government Steering Committee shall prepare semi-annual report of its deliberations and submit a copy to the Minister. Establishmen t of e- Government Technical Committee

Section 5Verify source

§ 6(1) Subject to section 17 of the Act, there isProvision

This section establishes the e-Government Technical Committee and says its members are appointed by the Minister. The Committee may also co-opt people from inside or outside government, but co-opted persons cannot vote.

6.-(1) Subject to section 17 of the Act, there is established the e-Government Technical Committee which shall be composed of the following members appointed by the Minister: (a) the head of ICT from the Ministry who shall be the Chairman; (b) a head of ICT nominated from each of the following: (i) Prime Minister’s Office; (ii) ministry responsible for finance; (iii) ministry responsible for local government; (iv) ministry responsible for communication; (v) ministry responsible for agriculture; (vi) ministry responsible for health; (vii) ministry responsible for lands; (viii) ministry responsible for industry and trade; (ix) ministry responsible for education; (x) ministry responsible for National defense; and (xi) ministry responsible for water; (c) a head of department of the Authority responsible for: (i) e-Government compliance and security management; (ii) e-Government operations; and infrastructure and (iii) e-Government service management; (d) a head of ICT from each of the following institutions- (i) Government Security Office; (ii) Tanzania Communication Authority; Regulatory (iii) Tanzania Revenue Authority; (iv) representative of learning institutions; government higher (v) Bank of Tanzania; (vi) National Identification Authority; (vii) Registration, Insolvency and Trusteeship 7 GN. No. 75 (contd.) e-Government General Agency; (viii) Tanzania Immigration Department; and (ix) Business Registration and Licensing Agency. (2) The e-Government Technical Committee may co-opt persons from within or outside the Government, and such person shall have no right to vote.

Section 6Verify source

§ 7(1) The Chairman of e-Government TechnicalProvision

The Chairman of the e-Government Technical Committee must convene Technical Committee meetings, and the Secretary must give each member at least seven days’ notice with the agenda, date, time, and place.

7.-(1) The Chairman of e-Government Technical Committee shall, on such date, time and place, convene meetings of the Technical Committee. (2) Pursuant to sub-regulation (1), the Secretary of the e- Government Technical Committee shall issue to each member, a seven days’ prior notice specifying the agenda, date, time and place of meeting.

Section 7Verify source

§ 8(1) Two-third of the members of the e-GovernmentProvision

Two-thirds of the committee members make a quorum, and if the Chairman is absent, the members present must choose one member to act as Chairman for that meeting.

8.-(1) Two-third of the members of the e-Government Technical Committee shall form a quorum for a meeting of the e- Government Technical Committee. (2) In the absence of the Chairman, the members present at the meeting shall elect one of the members to act as Chairman for that meeting.

Section 8Verify source

§ 9(1), The e-Government Technical Committee shallProvision

The e-Government Technical Committee must establish subcommittees for listed topics, and a subcommittee may co-opt people from inside or outside the Committee.

9.-(1), The e-Government Technical Committee shall establish subcommittees on the basis of the following - (a) e-Government policy and strategy; (b) e-Government standards; (c) e-Government projects and programme; (d) any other matter as the e-Government Technical Committee may deem appropriate. Convening of meetings of e- Government Technical Committee Quorum of e- Government Technical Committee Subcommitte es of Technical Committee (2) A subcommittee established this regulation may co-opt persons from within or outside the e- Government Technical Committee. terms of in Convening of meetings of Institutional ICT Steering Committee

Section 9Verify source

§ 10(1) The Chairman of Institutional ICT SteeringProvision

The Chairman must convene Steering Committee meetings and give each member seven days’ notice with the agenda, date, time, and place. The accounting officer may appoint subcommittee members, and those members are directly accountable to that accounting officer.

10.-(1) The Chairman of Institutional ICT Steering Committee shall convene meetings of the Institutional ICT Steering Committee, and shall for that purpose, issue to each member, a seven days’ notice specifying the agenda, date, time and place of meeting. (2) The accounting officer to which the Institutional ICT Steering Committee relates may appoint persons from within or outside the Institutional ICT Steering Committee to constitute as 8 GN. No. 75 (contd.) e-Government General Quorum of Institutional ICT Steering Committee Decision of Committees Records of meetings of Institutional ICT Steering Committee Review of e- Government policy framework a subcommittee of the Steering Committee. (3) The appointed sub-committees members shall be directly accountable to the accounting officer to which the Institutional ICT Steering Committee relates.

Section 10Verify source

§ 11Two-third of the members of the Institutional ICTProvision

Two-thirds of the Institutional ICT Steering Committee members must be present to form a quorum for a Steering Committee meeting.

11. Two-third of the members of the Institutional ICT Steering Committee shall form a quorum for a meeting of the Steering Committee.

Section 11Verify source

§ 12(1) For the purpose of this Part, at any meeting ofProvision

If there is a tie at a Committee meeting, the Chairman of the Committee has the casting vote.

12.-(1) For the purpose of this Part, at any meeting of Committees, a decision of the majority of the members present shall be recorded as a decision of a Committee. (2) At any meeting of Committees, the Chairman of the respective Committee shall have a casting vote where there is a tie of a decision of the members present.

Section 12Verify source

§ 13(1) Minutes of each Institutional ICT SteeringProvision

The Secretary must record committee meeting minutes properly and file them at the public institution’s offices before the next ordinary Committee meeting; the Committee must confirm the minutes and the Chairman must sign them.

13.-(1) Minutes of each Institutional ICT Steering Committee meeting shall be (a) recorded by the Secretary in a proper form; (b) confirmed by the Committee and signed by the Chairman; (2) The Secretary shall, before the next ordinary meeting of the Committee, file minutes of each Institutional ICT Steering Committee meeting at the offices of the respective public institution. (b) Working relationship of Committees

Section 13Verify source

§ 14(1) The Minister may for purposes of providingProvision

The Minister may require the e-Government Technical Committee to coordinate a review of e-Government policy or strategy, and public bodies and other stakeholders must provide input as specified by the Committee.

14.-(1) The Minister may for purposes of providing strategic and policy directions on the administration, management and operation of e-Government services, require the e-Government Technical Committee to co-ordinate the review of e-Government policy or strategy. (2) The Authority, a public institution and other stakeholders shall, in the manner and time specified by the e- Government Technical Committee, submit to the e-Government Technical Committee input on the review of e-Government policy or strategy required in terms of sub regulation (1). (3) The e-Government Technical Committee shall consolidate inputs submitted to it under subregulation (2) and recommend to the National e-Government Steering Committee for approval. (4) The National e-Government Steering Committee 9 GN. No. 75 (contd.) e-Government General Co-operation on determinatio n of e- Government projects and initiatives Preparation and submission of progress reports shall review and approve the e-Government policy or strategy. (5) The National e-Government Steering Committee shall submit the approved proposal e-Government policy or strategy to the Minister for endorsement and subsequent implementation by the Government and other stakeholders in accordance with the Act. (6) A public institution shall prepare and implement its ICT policy and strategy based on approved national ICT policy, e-Government policies and strategies.

Section 14Verify source

§ 15(1) The Institutional ICT Steering Committees shallProvision

The committees must review ICT project proposals and recommend on them, and proposals must go through the Authority for assessment and possible review by the e-Government Technical Committee.

15.-(1) The Institutional ICT Steering Committees shall receive, review and recommend on ICT project proposals from the head of ICT unit of the respective public institution. (2) ICT project proposal considered by an Institutional ICT Steering Committee shall be submitted to the Authority through the accounting officer of the respective public institution and through the platform directed by the Authority. (3) The Authority shall assess the project proposal to determine whether it is a key ICT project. (4) Where the Authority determines that a project proposal submitted to it is a key ICT projects proposal, it shall forward to e-Government Technical the project proposal Committee for review and recommendation. (5) The e-Government Technical Committee shall, at its earliest meeting possible, convene to review the proposals and provide feedback to the Authority. (6) For the purpose of this regulation, “key ICT project” means a project which has linkage with other bigger initiatives. shall

Section 15Verify source

§ 16(1) The secretariat of Institutional ICT SteeringProvision

Public institutions must submit approved quarterly reports within 14 days after each quarter; the Authority consolidates and shares them, and the e-Government bodies review and report onward.

16.-(1) The secretariat of Institutional ICT Steering ICT Committee implementation ICT Steering the Committee for review and approval, and such report shall be deemed to be the report of a public institution. submit Institutional prepare to quarterly report and (2) A public institution shall within fourteen days from the end of each quarter, submit it’s approved quarterly report to, and in the form and manner specified by the Authority. (3) The Authority shall consolidate approved quarterly reports of public institutions and share a copy with the e- Government Technical Committee. (4) The e-Government Technical Committee shall submit the a bi-annual e-Government secretariat of the National e-Government Steering Committee. implementation report to (5) The National e-Government Steering Committee 10 GN. No. 75 (contd.) e-Government General shall review, provide guidance to the e-Government Technical Committee and advice the Minister where appropriate.

Section 16Verify source

§ 17(1) Where a conflict emerges during the course ofProvision

If a conflict arises during implementation of an ICT project, it is to be resolved by mediation, either before the Authority or before the e-Government Technical Committee depending on who the conflict is between.

17.-(1) Where a conflict emerges during the course of implementation of an ICT projects, whether between a public institution and the Authority or between public institutions, a resolution of the conflict shall be dealt with as follows: (a) in the case of conflict arising between public institutions, through mediation before the Authority; (b) in the case of conflict arising between a public institution and the Authority, through mediation before the e-Government Technical Committee. (2) A complaint lodged by any party in conflict shall suffice for the mediator to initiate mediation and summon parties to that effect.

Section 17Verify source

§ 18Save as otherwise provided in any other written law,Provision

An ICT Management Unit of a public institution must prepare and submit specified ICT strategies, policies, and reports, and do other duties directed by the Institutional ICT Steering Committee, unless another written law provides otherwise.

18. Save as otherwise provided in any other written law, an ICT Management Unit of a public institution shall- (a) formulate and submit Steering Committee, strategies, internal guidelines and procedures; the Institutional ICT institutional ICT policies, to Determinatio n of conflicts and complaints Correlation of ICT Steering Committee and ICT Management Unit (b) prepare and submit to the Institutional ICT Steering Committee institutional ICT projects implementation reports (c) prepare and submit to the Institutional ICT Steering Committee institutional ICT quarterly reports as required under regulation 16(2); (d) undertake such other duty as the Institutional ICT Steering Committee may direct. PART III e-GOVERNMENT INFRASTRUCTURE AND SYSTEMS (a) Requirements for infrastructure and systems Approval of communicat ion infrastructur e

Section 18Verify source

Part

PART III

§ 19Approval of communication infrastructureProvision

This section is titled “Approval of communication infrastructure.”

19. Approval of communication infrastructure.

Section 19Verify source

§ 22Sourcing of Government ICT owned resourcesProvision

Section 22 is titled “Sourcing of Government ICT owned resources.”

22. Sourcing of Government ICT owned resources.

Section 22Verify source

§ 26Conditions and terms for services and facilitiesProvision

This section is titled “Conditions and terms for services and facilities.”

26. Conditions and terms for services and facilities.

Section 26Verify source

§ 27ICT projects implementation guidanceProvision

Section 27 gives guidance on implementing ICT projects.

27. ICT projects implementation guidance.

Section 27Verify source

§ 28Time for approval of project concept noteProvision

This section is about the time for approval of a project concept note.

28. Time for approval of project concept note.

Section 28Verify source

§ 36Response to inspectionProvision

Section 36 is titled “Response to inspection” and appears in Part IV on e-government services.

36. Response to inspection. PART IV e-GOVERNMENT SERVICES

Section 36Verify source

§ 19(1) The Authority shall approve communicationProvision

The Authority must approve public institution communication infrastructure that complies with the regulations, keep a database of approved infrastructure, and handle justification requests for non-standard infrastructure.

19.-(1) The Authority shall approve communication infrastructure of a public institution to ensure their compliance with regulations governing detailed specifications and standards of computers and other related equipment and tools for the use by public institution. (2) For the purpose of sub-regulation (1), the Authority shall maintain and make available to a public institution database of all communications infrastructure approved for use by public institutions. 11 GN. No. 75 (contd.) e-Government General Optimizatio n of infrastructur e (3) Where a public institution has a compelling need to for in use a communication accordance with the detailed the specifications and standards, the public institution shall submit to the Authority a request which justifies use of the communication infrastructure. infrastructure not provided regulations governing (4) The Authority shall, upon receipt of the justification request under sub regulation (3), recommend to the Minister for the communications approval or rejection of infrastructure that is not otherwise provided in regulations governing the detailed specifications and standards. the use of (5) The Authority may return a justification request to a institution with appropriate written recommendation public necessary for consideration and resubmission by the public institution.

Section 19Verify source

§ 20(1) A public institution shall, for the purpose ofProvision

A public institution must use Authority-approved or secured Government infrastructure for specified data exchange and connectivity, and must seek Authority approval in the stated cases.

20.-(1) A public institution shall, for the purpose of optimization of infrastructure, ensure that- (a) data and information exchange between it and another public through a secured is done Government network or infrastructure approved by the Authority; institution (b) internet connectivity or connectivity with an institution other than a Government Institution is done through an infrastructure approved by the Authority (2) A public institution that wants to use shared Government infrastructure shall request to the Authority for sharing of Government ICT infrastructure in a manner and format as provided in the First Schedule to these regulations. (3) Where a shared infrastructure as provided for in accordance with the Act or these Regulations does not fit a public institution requirements, the institution shall, prior to acquisition, deployment or use of another infrastructure, seek approval from the Authority Issuance of recommend ations

Section 20Verify source

§ 21(1) Subject to section 23(2) of the Act, a publicProvision

A public institution doing construction or infrastructure development must share the related ICT design with the Authority as soon as appropriate, and the Authority must issue recommendations within 14 days after receiving it.

21.-(1) Subject to section 23(2) of the Act, a public institution undertaking construction or development of infrastructure shall, at the earliest appropriate moment, share with the Authority the related ICT design. (2) The Authority shall, not later than fourteen days from receipt of ICT related design from a public institution undertaking construction, issue its recommendations to the public institution. 12 GN. No. 75 (contd.) e-Government General Sourcing of Government ICT owned resources

Section 21Verify source

§ 22Subject to Section 26(1)(a) of the Act, a publicProvision

A public institution must, as far as practicable, use approved ICT sourcing options such as home grown, vendor neutral, technology neutral, or open source based software when sourcing ICT systems.

22. Subject to Section 26(1)(a) of the Act, a public institution shall, as far as practicable and during sourcing of ICT systems, use approved - (a) home grown solutions; (b) vendor neutral solutions; (c) technology neutral solutions; or (d) open source based software. System developmen t standards

Section 22Verify source

§ 23A public institution shall, as a minimum requirementProvision

A public institution must follow the Authority’s guidelines on required standards when developing, deploying, operating, and maintaining information systems.

23. A public institution shall, as a minimum requirement during information system development, deployment, operations and maintenance, comply with guidelines on the following required standards issued by the Authority- (a) requirement gathering standards; (b) requirements Analysis standards; (c) design standards; (d) development standards; (e) testing standards; (f) deployment standards; and (g) operations and maintenance standards. Approval of new systems

Section 23Verify source

§ 24(1) The Authority shall issue guidelines, proceduresProvision

The Authority must issue guidelines, procedures, and criteria for approval of new systems, and public institutions must follow them.

24.-(1) The Authority shall issue guidelines, procedures and criteria for approval of new systems. (2) A public institution shall adhere to guidelines and procedures for approval of new systems. Criteria for integrated systems

Section 24Verify source

§ 25A public institution shallProvision

A public institution must support interoperability by collaborating on e-Government services, defining shared services, considering interoperability in process re-engineering, and ensuring data and network systems comply with the Regulations.

25. A public institution shall- (a) in attaining organization interoperability- (i) collaborate with a respective public institution and the development, deployment and delivery of e-Government services; the Authority in (ii) define its shared services; (iii) consider interoperability during business process re-engineering; (b) ensure data from various applications are in compliance with regulation 54(1); (c) ensure that all the hardware and software components of the network and information system communicate in and compliance with these Regulations. successfully and information transfer 13 GN. No. 75 (contd.) e-Government General Conditions and terms for services and facilities

Section 25Verify source

§ 26(1) The AuthorityProvision

26.-(1) The Authority issue guidelines specifying the terms and conditions upon which the specified facilities or services rendered within the scope of the functions of the Authority shall be provided to the public institutions. shall (2) The Director General may terminate service rendered to a public institution where the public institution, upon receipt of a one-month notice and a reminder thereof fails to comply with the terms and conditions for use of the facility and service. (b) ICT Projects implementation ICT projects implementat ion guidance

Section 26Verify source

§ 27(1) Subject to Section 24 of the Act, ICT projectsProvision

Public institutions must prepare and submit ICT project concept notes, and the Authority must review qualifying projects and give guidance and clearance.

27.-(1) Subject to Section 24 of the Act, ICT projects implementation standards and guidelines issued by the Authority shall incorporate the following components- (a) ICT project initiation which shall contain details of project concept note; (b) ICT project planning which shall contain details of ICT project management; and (c) ICT project monitoring which shall contain details of progress report and project closure. (2) A public institution shall prepare ICT project concept note or proposal during initiation of ICT projects in the manner specified in the standards and guidelines issued by the Authority. (3) A public institution shall, prior to implementation for a particular financial year in line with the prescribed procedures for planning and budget preparation, using Form 007 as prescribed in the Second Schedule to these Regulations, submit an ICT project concept note to the Authority. (4) The Authority shall review a concept note and provide guidance and clearance on any ICT project of a public institution whose value is of, or above fifty million shillings. (5) Notwithstanding subregulation (4), the Authority shall provide guidance and clearance on any ICT project of a public institution whose value is below fifty million shillings: (a) where the project involves two or more public institutions; (b) where the project relates to national security and safety;or (c) upon the directives of the Minister. 14 GN. No. 75 (contd.) e-Government General (6) The Authority shall, where it deems appropriate, return to the respective public institution a proposal not cleared in terms of sub regulation (4) (a) with for rectification and re-submission by the respective public institution; or recommendations of the Authority (b) with recommendations of the Authority that the project does not suffice to be implemented on grounds of non-compliance with the requirements of the Act and these Regulations. Time for approval of project concept note

Section 27Verify source

§ 28The Authority shall, not later than fourteen workingProvision

The Authority must write to the respective public institution with its determination under regulation 27 within 14 working days after receiving a project concept note.

28. The Authority shall, not later than fourteen working days from the date of receipt of a project concept note, communicate its determination under regulation 27 in writing to the respective public institution. ICT projects planning

Section 28Verify source

§ 29Subject to the requirement of these Regulations, aProvision

A public institution must prepare and submit an ICT project management plan to the Authority using Forms 008 to 013.

29. Subject to the requirement of these Regulations, a public institution shall prepare and submit to the Authority ICT project management plan using Forms 008 to 013 as prescribed in the Second Schedule to these Regulations. ICT projects performance audit

Section 29Verify source

§ 30(1) The Authority shall, for the purpose of ICTProvision

The Authority must use specified tools for ICT project performance audits and notify the institution before auditing.

30.-(1) The Authority shall, for the purpose of ICT project performance audit, use the following tools– (a) Government ICT project management standards issued by the Authority; (b) general accepted and widely used project (management) standards; (c) separate and standardized criteria that have been terms of the standards issued in derived from paragraph (a); and (d) sub-criteria established by designated project auditor in relation to the actual project and the respective public institutions context into account. (2) The Authority shall, prior to conducting performance audit, inform the institution to be audited the intention and objectives of the audit. (3) For the purpose of enabling the Authority to efficiently carry out the audit, the relevant institution shall make available all the required documents for the audit in a timely manner. (4) For ease of ICT project information access and retrieval, a public institution shall keep ICT project records in a manner and format prescribed by the Authority. 15 GN. No. 75 (contd.) e-Government General (5) Upon completion of the audit and before issuing the final audit report, the Authority shall submit, in writing, the audit findings to the audited institution for response. (6) An audited institution shall submit to the Authority detailed responses to the audit findings within fourteen days of receiving the audit findings. (7) The Authority shall submit the audit report to the audited institution with recommendations. (c) Conduct of inspection and investigation on ICT projects and systems Appointmen t of inspectors Notification of inspection Conduct of inspection

Section 30Verify source

§ 31(1) The Director General shall appoint officers of theProvision

The Director General must appoint Authority officers as inspectors, and each duly appointed inspector must be issued a badge or identification for inspections.

31.-(1) The Director General shall appoint officers of the Authority to be inspectors for the purpose of these Regulations. (2) Every inspector duly appointed shall be issued with badge or identification as recognition during inspection.

Section 31Verify source

§ 32(1) The Authority shall, in writing, serve the publicProvision

The Authority must give a public institution 14 days’ written notice before an inspection, unless it is a spot inspection with just cause. The public institution must confirm receipt and make required information available to inspectors.

32.-(1) The Authority shall, in writing, serve the public institution a fourteen days’ notice of its intention to conduct inspection, except that the Authority may forego the required notice period where such inspection is a spot inspection and which the Authority determines there is a just cause so to do. (2) In the notification letter, a public institution shall confirm in writing or through official email that it has received the notification for the inspection and will make all required information available and accessible by the inspectors.

Section 32Verify source

§ 33(1) An inspector shall conduct inspection based onProvision

An inspector must carry out inspections using the inspection plan and collect information by examining documents, interviewing people, and observing activities, equipment, and conditions.

33.-(1) An inspector shall conduct inspection based on details on the inspection plan. (2) An Inspector may adjust the plan to ensure the inspection objectives are achieved. (3) An inspector shall collect information through examination of relevant documents with direct access, interviews and observation of activities, equipment and conditions in the inspected areas. (4) Where the public institution refuses access to records or copying of documents or there is any withholding of documents or denial of access to areas to which the inspector has legal access, the inspector shall record the refusals and include in the inspection observations. Inspection observations

Section 33Verify source

§ 34(1) All inspection observations shall be documentedProvision

The inspector must document all inspection observations and report them to the Authority using Form 014.

34.-(1) All inspection observations shall be documented by the inspector, and where appropriate, copies shall be made of records containing inconsistencies or illustrating non-compliance. 16 GN. No. 75 (contd.) e-Government General Closing meeting Response to inspection (2) At the end of the inspection, the inspector shall review all observations to determine which observations are to be reported as non-compliance or quality system deficiencies, and documented in a clear, concise manner together with supported evidence. (3) The Inspector shall, using Form 014 as prescribed in the Third Schedule to these Regulations, report to the Authority the observations with reference to- (a) specific requirements of the standard or other related documents against which the inspection has been conducted; (b) the nature and scope of the inspection; and (c) the inspection methodology used.

Section 34Verify source

§ 35(1) At the end of the inspection, the inspector shallProvision

After an inspection, the inspector must hold a closing meeting with the inspected public institution and both sides must sign the prescribed form and appendix listing the findings.

35.-(1) At the end of the inspection, the inspector shall hold a closing meeting with the inspected public institution with a view to present inspection observations to the institution to ensure that the results of the inspection are clearly understood and that there is no misunderstanding by either the inspector or the public institution. (2) The inspector and public institution shall sign a prescribed form and an appendix listing all the findings noted during the inspection.

Section 35Verify source

§ 36(1) A public institution shall, not later than fourteenProvision

A public institution must send the Authority a written response to inspection findings within 14 days after the closing meeting, and include an implementation plan with a timetable for remedial measures.

36.-(1) A public institution shall, not later than fourteen days after closing meeting, submit to the Authority a written response of the inspection findings. (2) A response under subregulation (1) shall be accompanied with an implementation plan setting out the timeline for remedial measures. (3) The Authority may assign an inspector to conduct a follow up inspection for verification on the implementation of corrective actions. (4) The Authority may require a public institution to undertake additional actions where the remedial measures are found not to be satisfactorily executed. PART IV e-GOVERNMENT SERVICES Use of ICT to deliver government services

Section 36Verify source

Part

PART IV

§ 37Use of ICT to deliver government servicesProvision

This section is titled “Use of ICT to deliver government services.”

37. Use of ICT to deliver government services.

Section 37Verify source

§ 39Reliable and citizen-centric e- Government servicesProvision

This section is titled “Reliable and citizen-centric e-Government services.”

39. Reliable and citizen-centric e- Government services.

Section 39Verify source

§ 40Use of appropriate channels and languages to deliver e- GovernmentProvision

E-Government services should be delivered using appropriate channels and languages.

40. Use of appropriate channels and languages to deliver e- Government services.

Section 40Verify source

§ 41Consideration of persons with limited access and disabilitiesProvision

This section is about considering persons with limited access and people with disabilities.

41. Consideration of persons with limited access and disabilities.

Section 41Verify source

§ 42Adequate support systems to end usersProvision

Section 42 is titled “Adequate support systems to end users.”

42. Adequate support systems to end users.

Section 42Verify source

§ 43Maintenance and promotion of integrated and interoperable systemsProvision

Section 43 is titled “Maintenance and promotion of integrated and interoperable systems.”

43. Maintenance and promotion of integrated and interoperable systems.

Section 43Verify source

§ 44Digitalizing work processes and sharing of administrative informationProvision

Section heading for digitalizing work processes and sharing administrative information under e-Government security.

44. Digitalizing work processes and sharing of administrative information. PART V e-GOVERNMENT SECURITY

Section 44Verify source

§ 37A public institution shall, for the purposes of properProvision

A public institution must document its business processes, assess whether ICT can be applied, plan and implement the ICT solution, include revenue-related processes in the plan, inform the public about e-Government services, and keep improving those services.

37. A public institution shall, for the purposes of proper delivery of government services through the use of ICT- (a) document its business processes and maintain a 17 GN. No. 75 (contd.) e-Government General service register for identification and documentation of all services it offers; (b) perform a detailed analysis to determine feasibility of applying ICT to the business process in rendering its service; (c) develop and implement a road map in line with ICT Strategy for the purpose of implementing the technological solutions in rendering the identified e- Government services in accordance with paragraph (b); (d) ensure that the road map referred to under paragraph (c) incorporates all business processes that facilitate revenue generation to which the public institution is mandated to generate; (e) provide public awareness of all available e- Government services through available channels of communication with wider outreach; and (f) continuously improve the e- Government services to cope with emerging changes in the environment including changes in technology.

Section 37Verify source

§ 38A public institution shall, in ensuring re-engineeringProvision

A public institution must document, analyze, and improve its business process, and apply ICT to the re-engineered process.

38. A public institution shall, in ensuring re-engineering of its business process: (a) document in detail the existing business process; (b) analyse the business process to determine areas that can be optimized for performance improvement; re-engineering document new or revised business process; and (d) apply ICT on the re-engineered business process. (c) perform business process and Reengineeri ng business processes Reliable and citizen- centric e- Government services

Section 38Verify source

§ 39A public institution shall for the purpose of ensuringProvision

A public institution must keep e-Government services reliable and citizen-focused by running business continuity measures, using approved communication infrastructure, maintaining service agreements, and using appropriate channels and languages.

39. A public institution shall for the purpose of ensuring that the e- Government services rendered are reliable and citizen- centric. (a) implement business continuity management including operationalizing a disaster recovery plan submitted to the Authority in terms of these Regulations that covers such system which facilitate the rendering of such e- Government services. (b) use the approved communication infrastructure to host its ICT systems that deliver e- Government services as prescribed under these Regulations; and (c) maintain the service level agreements with their respective facilitate accessibility of e- Government services to guarantee providers who service 18 GN. No. 75 (contd.) e-Government General reliability of e-Government services. Use of appropriate channels and languages to deliver e- Government services

Section 39Verify source

§ 40A public institution shall, for the purpose of ensuringProvision

A public institution must make e-Government services accessible, including by using at least Kiswahili and English in user interfaces, keeping Kiswahili as the default, supporting language switching, providing access through suitable technologies, and ensuring web systems work across browsers.

40. A public institution shall, for the purpose of ensuring that e- Government services are accessible to citizens based on available technologies, ensure that- (a) user interface of systems delivering e- Government services are presented to the end users in at least two languages of Kiswahili and English, Kiswahili being the default language, and the users are given option to switch between the preferred languages; (b) e- Government services are accessible to users and connectivity types of through different technologies- (i) (ii) through web based technologies; through mobile are technically feasible and accessible to all users of mobile devices; or channels which (iii) through any other emerging technology; and (c) the systems delivering e- Government services over the web is browser independent to ensure cross- browser compatibility. Consideratio n of persons with limited access and disabilities

Section 40Verify source

§ 41(1) A public institution shall, for the purpose ofProvision

A public institution must make e-Government services accessible, including by considering universal access and accessibility support for persons with disabilities.

41.-(1) A public institution shall, for the purpose of ensuring e- Government services are accessible to users with limited access and disabilities- (a) ensure that design of the systems to be used in delivering e- Government services into consideration the universal access by users with limited technology; takes (b) as far as practicable, ensure systems delivering e- Government services are designed with accessibility assistance, in hardware and software, to persons with disabilities. Adequate support systems to end users;

Section 41Verify source

§ 42A public institution shall, for the purpose of ensuringProvision

A public institution must provide an accessible e-service support desk, try to keep it operating and responsive, and tell users when it will not be accessible.

42. A public institution shall, for the purpose of ensuring e-Government services delivered have adequate support systems to the end users- (a) establish e-service support desk is easily accessible to enhance delivering of e-service to end users; that (b) endeavor to ensure the support desk provides services throughout, and that the services are responsive to 19 GN. No. 75 (contd.) e-Government General Maintenanc e and promotion of integrated and interoperabl e systems Digitalizing work processes and sharing of administrati ve information Mandate of the Authority on E- Government security Authority to oversee operations of Center Technical Advisory Team the problems of their respective users; (c) communicate to e- Government services users whenever the service support desk will not be accessible.

Section 42Verify source

§ 43A public institution shall, for the purpose ofProvision

A public institution must follow the prescribed e-Government interoperability framework, standards, and technical guidelines issued by the Authority.

43. A public institution shall, for the purpose of maintaining and promoting integrated and interoperable systems to be used in service provision, adhere to the prescribed e- Government interoperability framework, standards and technical guidelines issued by the Authority.

Section 43Verify source

§ 44A public institution shall, for the purpose ofProvision

A public institution must use approved ICT solutions to digitize its core activities and make them interoperable for electronic information exchange.

44. A public institution shall, for the purpose of reduction of paper document- (a) implement approved ICT solutions to digitize its core activities, means of communication, filing and documentation management, attendance registry and any other approved processes; and (b) ensure the implemented are interoperable to facilitate exchange of information within and among public institutions electronically. solutions ICT PART V e-GOVERNMENT SECURITY (a) Management and governance of e-Government security

Section 44Verify source

Part

PART V

§ 45Mandate of the Authority on E-Government securityProvision

Section 45 concerns the Authority’s mandate on e-government security.

45. Mandate of the Authority on E-Government security.

Section 45Verify source

§ 46Authority to oversee operations of CenterProvision

This provision is titled “Authority to oversee operations of Center.”

46. Authority to oversee operations of Center. 2 GN. No. 75 (contd.) e-Government General

Section 46Verify source

§ 51Government critical system and application software ProtectionProvision

This section concerns protection of government critical systems and application software.

51. Government critical system and application software Protection.

Section 51Verify source

§ 52Compliance to e-Government security standards and guidelinesProvision

This section concerns compliance with e-Government security standards and guidelines.

52. Compliance to e-Government security standards and guidelines. PART VI ELECTRONIC GOVERNMENT DATA MANAGEMENT

Section 52Verify source

§ 45The Authority shall, through the e-GovernmentProvision

The Authority must develop a mechanism, through the e-Government security operations center, to enforce rules, strategies, standards, guidelines, and procedures for e-Government security implementation.

45. The Authority shall, through the e-Government security operations center develop mechanism for enforcement of rules, strategies, standards, guidelines and procedures for implementation of e-Government security as provided in the Act.

Section 45Verify source

§ 46The Authority shall oversee the operations of the eProvision

The Authority must oversee the e-Government Security Operations Center and may require implementation reports and issue operational directives for it.

46. The Authority shall oversee the operations of the e- Government Security Operations Center, hereinafter referred to as it shall require implementation reports and issue operational directives on the Center. the “Center”, and for that purpose

Section 46Verify source

§ 47(1) Without prejudice to the mandate of DirectorProvision

The Center must obtain operational advice and input from a technical advisory team, and the team’s operations must follow a Charter approved by the Authority.

47.-(1) Without prejudice to the mandate of Director General over the Centre, and for better implementations of its duties, the Center shall obtain operational advice and input from the technical advisory team which shall comprise of members appointed by the Authority as follows: (a) three representatives from the Authority; 20 GN. No. 75 (contd.) e-Government General (e) (d) (b) (c) a representative from the Ministry; a representative from the Ministry responsible for ICT sector; a representative from the Ministry responsible for Finance; a representative from the Ministry responsible for local government authorities; representatives from key Government institutions for National Security and Law responsible enforcement; a representative from TCRA; an ICT Security officer appointed from any public institution as may be determined by the Authority. (2) The operations of the technical advisory team shall be in accordance with the provisions of the Charter prepared and approved by the Authority. (g) (h) (f) Duties of Center

Section 47Verify source

§ 48The duties of the e-Government Security OperationProvision

The e-Government Security Operation Center must carry out government cyber security coordination, oversight, training, incident reporting, awareness, and protection tasks.

48. The duties of the e-Government Security Operation Center shall be to- (a) coordinate implementation of Government Cyber Security Strategy; (b) harmonize, coordinate, assess, audit, document, report and provide assurance on Government cyber security initiatives; (c) provide training and institutions awareness regarding implementation of Government Cyber Security Strategy ; raise public (d) receive, consolidate and analyze Government Cyber annual report from public Security Strategy institutions; (e) communicate, maintain and oversee compliance on ICT security principles, standards and guidelines for the Government; (f) provide ICT security protections commensurate with the risk and magnitude of the harm resulting from the potential cyber threat on government information and systems; (g) review public institutions’ ICT security policies and strategies; (h) identify and categorize government critical systems in consultation with and application software relevant stakeholders; (i) facilitate establishment of institutional computer 21 GN. No. 75 (contd.) e-Government General emergency readiness teams; (j) receive, consolidate and analyze reports from the public institutions relating to categorize Government Critical systems and application software; (k) create awareness and build capacity of public institutions regarding the risks in cyberspace; (l) develop, maintain and enforce control mechanisms for protecting Government information and ICT systems; (m) maintain and manage a database of Government Single Point of Contact that responds to cyber security incidents; (n) forecast and provide alerts on cyber security incidents in public institutions; (o) coordinate incidents institutional cyber security responses and collaborate with relevant stakeholders with regards to such incidents responses; (p) perform on demand and security assessment to critical ICT infrastructure and critical services in order to assess their vulnerabilities to cyber security threats; scheduled (q) promote awareness on information sharing regarding cyber security in public institutions; (r) create and update cyber security incidents register in public institutions. (b) e-Government Security Standards and Guidelines Government domain naming standards

Section 48Verify source

Part

PART VI

§ 54Electronic Data collection or creationProvision

This section is titled “Electronic Data collection or creation.”

54. Electronic Data collection or creation.

Section 54Verify source

§ 58Principles of electronic data sharing and exchangeProvision

This section is titled “Principles of electronic data sharing and exchange.”

58. Principles of electronic data sharing and exchange.

Section 58Verify source

§ 59Electronic data sharing and exchangeProvision

Section 59 is titled “Electronic data sharing and exchange” and appears under Part VII on fees and charges.

59. Electronic data sharing and exchange. PART VII FEES AND CHARGES

Section 59Verify source

§ 53Save as provided in any other written law, a publicProvision

A public institution must manage and govern electronic data across its whole life cycle, unless another written law provides otherwise.

53. Save as provided in any other written law, a public institution shall manage and govern electronic data throughout the whole life cycle of the data, and includes- (a) collection or creation; (b) capturing; (c) retrieve; (d) security; (e) preservation; (f) migration; (g) storage; (h) transmission; (i) usage; (j) sharing; (k) retention; and (l) disposal.

Section 53Verify source

§ 54(1) A public institution shall, prior to collection orProvision

Public institutions must prepare a data dictionary before collecting or creating electronic data, create data according to that dictionary, and avoid recreating primary data for the same portfolio or discipline.

54.-(1) A public institution shall, prior to collection or creation of electronic data, prepare institutional data dictionary in a manner specified in the standards and guidelines issued by the Authority in collaboration with the institution responsible for records and archive management. (2) A public institution shall create electronic data in accordance with data dictionary referred to under sub regulation (1). (3) Data created by a public institution for a specified portfolio or discipline shall be the primary data for that portfolio or discipline and shall not be recreated by that institution or another public institution for the same portfolio or discipline: Provided that, the data created is owned by that public institution that initially created it. (4) A public institution may access primary data of another public institution through data sharing mechanism as specified in these Regulations. Electronic data maintenance

Section 54Verify source

§ 55A public institution shallProvision

A public institution must keep its data repository updated and send the updated changes to the data sharing and exchange platform within 48 hours of the update.

55. A public institution shall- (a) regularly update its data repository to ensure accuracy and consistency of data; (b) not later than forty eight hours from the time of update, transmit the updated changes into the data sharing and exchange platform provided for under 24 GN. No. 75 (contd.) e-Government General Electronic data storage Electronic data disposal Cap. 309 Principles of electronic data sharing and exchange these regulations, Provided that, updated changes concerning information that is of National, security or safety concern shall not be unreasonably delayed.

Section 55Verify source

§ 56A public Institutions shall use Government storageProvision

Public institutions must use government storage facilities only to store data owned by that institution.

56. A public Institutions shall use Government storage facilities only for storing data owned by that Institution.

Section 56Verify source

§ 57A public institution shall dispose or retain electronicProvision

A public institution must handle electronic data disposal or retention according to the law governing that institution and the Records and Archives Management Act.

57. A public institution shall dispose or retain electronic data in the manner provided under the law governing the public institution and in accordance with the Records and Archives Management Act.

Section 57Verify source

§ 58For the purpose of ensuring efficient and effectiveProvision

Public institutions must follow principles for efficient and effective data sharing and exchange.

58. For the purpose of ensuring efficient and effective data sharing and exchange, public institutions shall adhere to the following principles: (a) business process or organizational interoperability: which relates to the collaboration between entities in the development, deployment and delivery of e- Government services, and to the interaction between services, and supporting processes; (b) information or semantic interoperability: which the exact meaning of that relates information are applications various understandable by any application even though if the application was not developed for this purpose; to ensuring from (c) technical interoperability: which ensure that all the hardware and software components of the network and information system physically communicate and transfer information successfully, and includes key aspects such as open interfaces, interconnection services, data integration and middleware, data presentation and exchange, accessibility and security services. Electronic data sharing and exchange

Section 58Verify source

§ 59(1) There is established a data sharing and exchangeProvision

The Authority establishes a data sharing and exchange platform, and public institutions must share and exchange data through that platform or another Authority-approved means, subject to prescribed terms and conditions.

59.-(1) There is established a data sharing and exchange platform by the Authority to facilitate efficient data sharing and exchange in the Public Service. (2) Public institutions shall, subject to such terms and conditions as may be prescribed by the Authority share and exchange data through - (a) the platform referred to under sub regulation (1); or (b) any other means as may be approved by the 25 GN. No. 75 (contd.) e-Government General Authority PART VII FEES AND CHARGES Imposition of fees and charges

Section 59Verify source

Part

PART VII

§ 61Variation or change of feesOffence

This provision is titled “Variation or change of fees.”

61. Variation or change of fees. PART VIII OFFENCES AND PENALTIES

Section 61Verify source

§ 60(1) The Authority shall, for the purpose of ensuringProvision

The Authority must collect fees and charges for its services as set out in the Fourth Schedule, but certain public bodies are exempt from paying the full fees for specified e-government services.

60.-(1) The Authority shall, for the purpose of ensuring efficient and effective e-government infrastructure and system operations, collect fees and charges for service rendered by the Authority in a manner set out in the Fourth Schedule to these Regulations. subregulation (2) Notwithstanding (1), ministries, independent departments, Regional Secretariat and Local Government Authorities shall be exempted from the payment of the whole fees and charges in respect of e-office (Cloud-Standard Based), Government e-mailing System-GMS (Cloud-Standard Based) and Enterprise Resource Management Suite-ERMS (Cloud-Standard Based) services as set out in the Fourth Schedule to these Regulations. (3) For the purpose of this regulation, “independent department” has the meaning ascribed to it under the Public Service Act and Regulations made thereunder. Variation or change of fees

Section 60Verify source

§ 61(1) The Minister may, upon advice of the DirectorOffence

The Minister may vary or waive fees or charges, if advised by the Director General, and must cause an official notice to be issued for any variation or waiver.

61.-(1) The Minister may, upon advice of the Director General, vary or waive any fees or charges. (2) The Minister shall cause to be issued an official notice of any variation or waiver made pursuant to subregulation (1). PART VIII OFFENCES AND PENALTIES Offences and penalty

Section 61Verify source

Part

PART VIII

§ 62Offences and penaltyOffence

This section is titled “Offences and penalty,” but the provided text does not state the rule.

62. Offences and penalty. ________ Schedules _________ 3 GN. No. 75 (contd.) e-Government General THE e-GOVERNMENT ACT (NO. 10 OF 2019) __________ REGULATIONS __________ (Made under section 60) _________ THE e-GOVERNMENT GENERAL REGULATIONS, 2020 PART I PRELIMINARY PROVISIONS Citation

Section 62Verify source

§ 62Any person who contravenes or fails to comply withOffence

Anyone who fails to comply with these Regulations commits an offence and may be fined, imprisoned, or both if convicted.

62. Any person who contravenes or fails to comply with these Regulations commits an offence and shall, on conviction, be liable to a fine of not less than two million shillings but not exceeding twenty million shillings or to imprisonment for a term of not less than six months but not exceeding five years or to both. 26 GN. No. 75 (contd.) e-Government General __________ FIRST SCHEDULE ___________ (Made under regulation 20(2)) ___________ SHARED INFRASTRUCTURE REQUEST PROCEDURES AND FORMS

Section 62Verify source

§ 1SHARED INFRASTRUCTURE REQUEST PROCEDUREProvision

A Public Institution must request shared infrastructure from the Authority, use the prescribed form, pay any prescribed fees or charges, and follow the procedure electronically.

1. SHARED INFRASTRUCTURE REQUEST PROCEDURE a) A Public Institution shall request shared infrastructure from the Authority by submitting a formal request addressed to the Director General. b) A Public Institution Shall fill a prescribed form (Forms 001 to 006) below with details of the shared infrastructure service requested and send it along with the request in (a). c) Where fees and charges are applicable, the Authority shall compute the costs of the shared infrastructure and communicate the same with the Public Institution. d) The Public Institution shall pay the prescribed fees or charges to the Authority. e) The Authority shall offer the shared infrastructure service to the Public Institution. f) Without prejudice to any other law, the procedures described in ((a) to (e)) above shall be conducted electronically.

Section 1Verify source

§ 2SHARED INFRASTRUCTURE SERVICE REQUEST FORMSProvision

Form 001 for domain registration must be completed with the required items, including payment evidence, and asterisked items are mandatory.

2. SHARED INFRASTRUCTURE SERVICE REQUEST FORMS FORM 001: DOMAIN REGISTRATION FORM GENERAL CONDITIONS: i. Well filled form ii. Evidence of payment for domain registration fee iii. Items with an asterisk (*) are MANDATORY

Section 2Verify source

§ 1REGISTRATION TYPEProvision

This section lists registration type options: modify, new, or delete.

1. REGISTRATION TYPE modify (M) * new (N) delete (D)..: ……………………….

Section 1Verify source

§ 3E* CountryProvision

3e.* Country...............: +255 TANZANIA 27 GN. No. 75 (contd.) e-Government General

Section 3EVerify source

§ 4* DESCRIPTION OF ORGANISATION & DOMAINProvision

Section heading only: “DESCRIPTION OF ORGANISATION & DOMAIN.”

4. * DESCRIPTION OF ORGANISATION & DOMAIN:

Section 4Verify source

§ 7KFax NumberProvision

Organizations running name servers for a branch of the TZ Domain namespace are told to fill out questions 8 and 9 for delegation purposes.

7k. Fax Number: Fill out question 8 and 9 for delegations purposes (i.e. those organizations running name servers for a branch of the TZ Domain namespace)

Section 7KVerify source

§ 9SECONDARY SERVER: HOSTNAME, NETADDRESSProvision

Section 9 is titled “Secondary Server: Hostname, Netaddress.”

9. SECONDARY SERVER: HOSTNAME, NETADDRESS

Section 9Verify source

§ 2Section 2Provision

Registering a name on the Internet under the .tz ccTLD is treated as acceptance, in good faith, that the registrant has the right to use the name.

2. By the registration of your name on the Internet (under dot tz ccTLD), e-GA accepts in good faith that you have the right to the use the name. Our function in registering names on the Internet under go.tz TLD space is to assure that the name does not conflict with any other name in the name space requested. 28 GN. No. 75 (contd.) e-Government General

Section 2Verify source

§ 5Section 5Provision

If you register or use a name, you must indemnify and hold harmless against certain litigation costs, and the applicant must certify the name does not violate trademark or similar statutes.

5. The user by your registration and use of the name and/or your continued use of an existing name, agrees, as part of your request for name registration, to indemnify and hold harmless from any and all costs, fees, expenses arising from litigation involving trademark, trade name, service mark, and any other name infringements, or other reasons. The party requesting registration of this name certifies that to her/his knowledge, the use of this name does not violate trademark or other statutes. Registering a domain name does not confer any legal rights to that name and any disputes between parties over the rights to use a particular name are to be settled between the contending parties using normal legal methods (See RFC 1591). FORM 002: DOMAIN TRANSFER FORM GENERAL CONDITIONS: i. ii. Fill the form correctly and submit. Items with asterisks (*) are MANDATORY

Section 5Verify source

§ 4* DOMAIN TRANFER KEY (get it from your current Registrar)Provision

Section heading referring to a domain transfer key from the current registrar.

4. * DOMAIN TRANFER KEY (get it from your current Registrar):

Section 4Verify source

§ 5*DOMAIN SERVICES. Please, list all services and the corresponding public IPProvision

This form asks for the services a domain points to and the corresponding public IP addresses; if e-GA will host the service, the public IP should be left blank.

5. *DOMAIN SERVICES. Please, list all services and the corresponding public IP addresses the domain is currently pointing to including your website. If the service(s) are to be hosted by e-GA, leave Public IP blank. S/No. Service Public IP Address The domain “” is pointing to the following services: 1 2 3 4 5 6 Declaration: I declare that the above information is correct. *Filled By (Full Name): *Title: *Date: __________________________________________________________________________ _______ ~end~ 29 GN. No. 75 (contd.) e-Government General FORM 003: SOFTWARE / APPLICATION CO-LOCATION REQUEST FORM Application owner Application support team End users Others

Section 5Verify source

§ 3Section 3Provision

The GovSms mobile platform must be used only for transactional SMSs on behalf of a public institution, and commercial or promotional messages must not be sent through it.

3. Admin Users Support Team Concurrent users Other(Expected public + Departments) Name of the Co-Located Institutions Name of the Software / Application Objective of the application clearly articulating purpose, beneficiary etc. Key stakeholders Services offered by the Software/Application Maximum number of users Type and number of Ports Used Types of Protocols Used Processing power Memory size Storage size Internet Bandwidth Type of Operating system used Type of DB Management System used Is the Co-Located system a Primary / DR site ? 30 GN. No. 75 (contd.) e-Government General FORM 004: CO-LOCATION REQUIREMENTS FORM Details Name of Public Institution: Item Description Server/Equipment Name Quantity Serial Number (S/N) Model Rack Mountable (Yes/No) Required Rack Space (U’s or equip dimensions) Power Supply Type (AC/DC) Number of Power Supplies Voltage (each) Amperage (each) Number of Ethernet Connections Required NIC Teaming/Bonding (Yes/No) Link Speed and Duplex Requirements Public IP Addressing Requirements 31 GN. No. 75 (contd.) e-Government General FORM 005: GOVERNMENT MOBILE PLATFORM (MGOV) REGISTRATION FORM A. Details of the Public Institution Name: Contact Details: B. Contact Person Information Office Name * : First Name * : Middle Name : Last Name * : Email Address * : Mobile No * : Alternative Mobile No : Designation : C. Supervisor Information Name * : Email Address * : Mobile No * : Alternative Mobile No : Designation : D. Service Description Terms and Condition I/We agree that the SMS platform (GovSms) provided by Government of Tanzania will be used to send transactional SMSes only on behalf of a public institution; AND I/we also agree not to send any commercial communications and not to mix any promotional communications with its transactional message sent to a subscriber through this SMS platform. 32 GN. No. 75 (contd.) e-Government General FORM 006: QUESTIONNAIRE FOR BANDWIDTH ALLOCATION Answer S/N 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Name of Public Institution: Question How many staffs/employees regularly use internet in your organization? a.) 0-50 users b.) 50-100 users c.) 100-200 users d.) 200-500 users e.) More than 500 users Do you locally host you organization website? Do you locally host email application? Do you have any other web hosting facilities? How many? Do you have VoIP application? Do you perform online backups (FTP)? Do you have audio/video conference facilities? What mode of Anti-virus updates in your organization, server based or individual computers? What is your current bandwidth capacity from your ISP? Who is your current ISP? How many public IPs do you have/wish to have? Do you have fiber backbone connectivity? What is the manufacturer and model of your gateway router? If your public IPs changes, will your customers be affected? SECOND SCHEDULE GOVERNMENT ICT PROJECT MANAGEMENT (Made under regulations 27(3) and 29) FORM 007: GOVERNMENT ICT PROJECT CONCEPT NOTE Project Title: State below the link between project with the Institutional strategy Problem/opportunity statement: Project Benefits: An outline of what the benefits are to the organisation, individuals or stakeholders in delivering the project Project Objectives: The specific objectives for the project. NOTE: the 33 GN. No. 75 (contd.) e-Government General objectives can be one line or more detailed text. Project Deliverables:

Section 3Verify source

§ 2Section 2Provision

This section says the project scope includes the project’s boundaries.

2. Project scope This project will include: This section defines the boundaries of the project.

Section 2Verify source

§ 1Section 1Provision

This project must not include planning details at this stage.

1. This project will not include: Planning details should not be included at this stage.

Section 1Verify source

§ 1Section 1Provision

This section contains form fields for reporting, tracking, and approving government ICT projects.

1. Success Criteria: How you will measure the success of the project. NOTE: the success criteria must be measurable. Constraints: Key Assumptions: Break down Initial implementation cost: Examples here can be specific (a skill which the project team must have) resources, or a legal deadline – NOTE: only include time and money if you can quantify them. Break down ongoing Costs: 1 Total costs (attach a breakdown of the overall budget) • VAT*– …………………………………………. Planned Start Date: Signature of Project Manager: Accounting officer Approval Planned Completion Date: Date: Date: FORM 008: GOVERNMENT ICT PROJECT STAKEHOLDERS ANALYSIS Stakeholde r Their requirement from the project What the project needs from them Perceived attitudes and/or risks Actions to take FORM 009: GOVERNMENT ICT PROJECT IMPLEMENTATION TIMELINE Time [in weeks & months] 34 e-Government General GN. No. 75 (contd.) Mil est one s Delivera bles (as per the concept note) FORM 010: GOVERNMENT ICT PROJECT CHANGE REQUEST CHANGE REQUEST Originator Phone: Items to be changed Date of request Change request no. Reference(s) Description of change (reasons for change, benefits, date required) Estimated cost, and time to implement (quotation attached? Yes No ) Priority / Constraints (impact on other deliverables, implications of not proceeding, risks) FORM 011: GOVERNMENT ICT PROJECT CHANGE EVALUATION AND APPROVAL Change evaluation What is affected Related change requests Name of evaluator Change approval Accepted Rejected Deferred Comments Work required (resources, costs, dates) Date evaluated Signature Name Signed Date 35 GN. No. 75 (contd.) e-Government General FORM 012: GOVERNMENT ICT PROJECT RISK REGISTER FORM S/ n Description of risk Impact on project Mitigation actions Responsibility for mitigation action(s) Timeline for mitigation action(s) FORM 013: GOVERNMENT ICT PROGRESS REPORT Project Name:…………………………………… ………………… Reporting Period: Project Manager: Prepared by: Project Description: Date Prepa red: Statu s DELAYED /ON TRACK Project Phase: Project End Date: dd/mm/yyyy Key Deliverables Completed this period Key Deliverables Outstanding this period Key Deliverables for next reporting period Deliv ery Date Deliver y Date Risk Management Issue Management Change Management No Risk Action No Issue Action Details Appro ved 36 GN. No. 75 (contd.) e-Government General THIRD SCHEDULE GOVERNMENT ICT PROJECT/SYSTEMS INSPECTION (Made under regulation 34(3)) FORM 014: GOVERNMENT ICT PROJECT INSPECTION FORM Title of the Report: Executive Summary Background Summary of Observed Issues General Recommendations Conclusion

Section 1Verify source

§ 31 IssueProvision

3.1 Issue Title A Actions Taken Status Issue Actions Taken Status Issue Description Associated Risks Consequences Rating Recommendations Management Responses and Action Plan 37 GN. No. 75 (contd.) e-Government General

Section 3Verify source

§ 32 IssueProvision

A section heading for an issue item, not a substantive rule.

3.2 Issue Title B Issue Description Associated Risks Consequences Rating Recommendations Management Responses and Action Plan

Section 3Verify source

§ 50 ConclusionProvision

This schedule lists fees and charges for specified authority services, including setup fees, annual subscriptions, storage charges, and SMS/USSD-related charges.

5.0 Conclusion Name and Signature of the Inspector ____________ FOURTH SCHEDULE ____________ FEES AND CHARGES FOR SERVICES RENDERED BY THE AUTHORITY Proposed Service No 1 Application system development, customization, or integration1 Application maintenance support2 e-Office Standard Based) (Cloud- and 2 (Made under regulation 60(1)) Chargea ble (Yes/No) Yes Charging Criteria Amount/ Rate Actual Cost and Man-days Actual Cost + Professional Fees Yes Yes initial % of development cost. Storage capacity, number of 10% development cost per year. the of initial • One-time and setup 1,800,000. installation fee: TZS 1 Includes mobile application, web-based/shared systems, system integrations, websites etc. 2 Includes mobile application, web-based/shared systems, system integrations, websites etc. 38 GN. No. 75 (contd.) Proposed Service No e-Government General Chargea ble (Yes/No) Charging Criteria users Amount/ Rate • Annual subscription fee: per (includes TZS institution 200GB) per year.3 6,500,000 3 Government e- Mailing System – GMS (Cloud- Standard Based) Yes Storage capacity, number email accounts. 4 Enterprise Resource Management Suite – ERMS (Cloud- Standard Based) Yes Storage capacity, number users • Additional storage: TZS 3,500 per GB per year. • Customization Actual Cost Professional Fees. cost: + • One-time and 600,000. setup of installation fee: TZS • Annual subscription fee per email account per 11,000 TZS year: (includes per email account per year. • Additional storage: TZS per per GB 2GB) 3,500 domain per year. • Customization Actual Cost Professional Fees. cost: + • One-time and setup 5,000,000. of installation fee: TZS • Annual subscription fee: per (includes TZS institution 200GB) per year. 9,800,000 • Additional storage: TZS 3,500 per GB per year. Customization Actual Cost Professional Fees. cost: + • 5 6 ICT management framework development4 Project Concept Yes Actual Cost and Man-days Actual Cost + Professional Fees No N/A N/A 3 Extra storage beyond the optimized storage will be chargeable at the rate of Tsh. 3,500 per GB per year. 4 Includes ICT strategies, policies, enterprise architecture, disaster recovery plan, etc. 39 GN. No. 75 (contd.) e-Government General Proposed Service No Chargea ble (Yes/No) Charging Criteria Amount/ Rate 7 Review Review Note Review Project Inspections and Investigation On-demand Project Inspections and Investigation On-demand System and Audit Regular System Review and Audit On-demand Project Inspections and Investigation On-demand System and Audit Regular System Review and Audit System General Compliance Review On-demand Security Assessment Regular Security Assessment Regular Project Performance Audit On-demand Project Performance Audit ICT ICT 8 Advisory staff public Embedding into institutions. Technical support/assistance Technical support/assistance involving resources. Consultancy and Yes Actual Cost Actual Cost Yes Yes Actual Cost and Man-days Actual Cost + Professional Fees Actual Cost and Man-days Actual Cost + Professional Fees Yes Actual Cost Actual Cost Yes Yes Actual Cost and Man-days Actual Cost + Professional Fees Actual Cost and Man-days Actual Cost + Professional Fees Yes Actual Cost Actual Cost No N/A N/A Yes Actual Cost Actual Cost No N/A N/A No Actual Cost Actual Cost Yes No Yes Actual Cost and Man-days Actual Cost + Professional Fees N/A Actual Cost and Man-days N/A Actual Cost + Professional Fees No N/A N/A Yes Actual Cost and Man-days Actual Cost + Professional Fees Yes Actual Cost Actual Cost + Professional 40 GN. No. 75 (contd.) e-Government General Proposed Service No Chargea ble (Yes/No) Charging Criteria Amount/ Rate Use and No and Man-days Fees N/A N/A and Yes Actual Cost and Man-days Actual Cost + Professional Fees Training 9 Common Software Hardware Approval/Re- approval Specialized Software Hardware Approval/Re- approval 10 Colocation services Yes Rack space Bandwidth Application hosting services Yes 11 Websites hosting Yes services 12 Standard Secure Layer Socket (SSL) Certificate Yes Computing (Processors, RAM), Storage, platform upgrades, etc. Computing (Processors, RAM), Storage, platform upgrades, etc. Number of domains/ subdomains • Minimum Space: One rack-unit TZS 2,000,000 • Bandwidth : 1,850,000 per Mbps per year • Additional space shall be charged as multiple of the minimum space. • Minimum Specifications: One (1) processor core + 4GB RAM + 100GB: TZS 1,750,000 per year. • Additional be requirements as shall charged multiple of the minimum specifications. • Annual Fee: TZS 700,000 (includes SSL Certificates for one sub-domain and 10GB storage) • Additional storage: TZS 3,500 per GB per year. • Annual Single Fee: domain TZS 480,000 per domain per year • Annual Fee: Multi-domain a 4 TZS 1,100,000 maximum domains/subdomains. for of Operation, Administration and Management fee: TZS 1,550,000 per year per site per Mbps 13 Government Yes Network (GovNet) 14 Domain Yes of and Number sites bandwidth size Number of TZS 25,000 per domain per 41 GN. No. 75 (contd.) e-Government General Proposed Service No registration hosting and Chargea ble (Yes/No) Charging Criteria domains 15 Overseas No N/A year. N/A Amount/ Rate Government Employee Travel Permit Request (e- Vibali) e-Government Mobile Financial Transaction Services 16 Yes Transactions 17 SMS Push (Bulk Yes SMS Count SMS) • TZS 65 per transaction. • Non-financial transaction fee: normal SMS price (see below). • TZS 15/SMS : Where SMS < 1,000,000 per month • TZS 13/SMS: Where SMS between (1,000,001 – 4,000,000) per month • TZS 10/SMS: Where SMS > 4,000,000 per month TZS 100 SMS Push SMS) SMS Pull SMS) 18 USSD Hosting (MT Yes Transaction (MO Yes Transaction TZS 100 Menu Yes TZS 2,400,000 Server Resource + Annual USSD Code Maintenance Fee NOTE:

Section 5Verify source

§ 1All the prices included in this schedule are taxes exclusiveProvision

The prices in this schedule do not include taxes.

1. All the prices included in this schedule are taxes exclusive

Section 1Verify source

§ 2Where Professional Fees are applicable, the unit (man-day) rate is TZS 300,000Provision

If Professional Fees apply, the unit (man-day) rate is TZS 300,000 payable to the Authority.

2. Where Professional Fees are applicable, the unit (man-day) rate is TZS 300,000 payable to the Authority. Dodoma, GEORGE H. MKUCHIKA, 22nd January, 2020 Minister of State-President's OfficePublic Service Management and Good Governance 42

Section 2Verify source

Part

PART I

§ 1These Regulations may be cited as the e-GovernmentInterpretation

This section says the Regulations may be cited as the e-Government General Regulations, 2020.

1. These Regulations may be cited as the e-Government General Regulations, 2020. Interpretation

Section 1Verify source

§ 2In these Regulations, unless the context requiresProvision

This section defines terms used in the Regulations, such as Act, Authority, Board, data dictionary, data integration, data repository, data owner, and electronic data.

2. In these Regulations, unless the context requires otherwise – “Act” means the e-Government Act; Act No. 10 of 2019 Technical the National e-Government Steering and “Authority” means the e-Government Authority established under section 4 of the Act; “Board” means the Board of Directors of the e-Government Authority established under section 7 of the Act; “Committees” means Committee, e-Government Institutional ICT Steering Committee; “data dictionary” means a set of information describing the structure of a data and the relationship contents, format, and between its elements, used to standardize and control access to and manipulation of the data; “data integration” means the routing of data from multiple (databases, systems, applications) into a disparate sources single system or platform within or public across institutions; “data repository” means a central place where data of a public Committee institution is stored and managed; “data owner” means the public institution that created the original data for a specified portfolio or discipline; 4 GN. No. 75 (contd.) e-Government General networks to communicate; citizens based in Tanzania; “Disaster Recovery Plan or in its acronym “DRP” means a documented, structured approach with instructions for responding to unplanned incidents that impacts e- Government services offered by public institutions; “electronic data” means information that has been prepared or acquired and managed by a public institution within the scope of its duties and that has been processed by digital means to be expressed in codes, letters, sound, images, objects or any other mode; “gateway” means computer network component that enables two or more discrete “home grown solutions” mean an ICT solutions or systems developed by Tanzanian “ICT Management Unit” means an ICT Management Unit established in terms of Section 21 of the Act; “Institutional ICT Steering Committee” means the Institutional ICT Steering Committee established in terms of section 18 of the Act; “interconnection services” means the set of legal rules, technical and operational arrangements between network operators that enable customers connected to one network to communicate with customers of other network; “middleware” means software that facilitates exchange of data between two same application network environment or across different hardware environments; “Minister” means the Minister responsible for e-Government; “Ministry” means the Ministry responsible for e-Government; “National e-Government Steering Committee” means the National e-Government Steering Committee established under section 16 of the Act; “open interface” means a point where systems, whether hardware or software, can interact or accept inputs from other systems; programs within and the “open source based software” means a software whose source code is publicly accessible and can be modified and shared; “primary data” means the original data created by a public institution for a specified “Secretary” means the Secretary to the Board, designated as such in terms of Section 7(4) of the Act; “Service Level Agreement or in its acronym “SLA” means an agreement between a public institution and service portfolio or discipline; 5 GN. No. 75 (contd.) e-Government General provider that defines the level of services expected from service provider lying out the metrics by which service is measured, and remedies for not meeting the agreed service standards the provider is obligated to meet; “shared Government infrastructure” means a Government ICT resource for use by public institutions collaboratively under specified terms and conditions; “shared services” means generic services that are jointly used by public institutions in different business processes of various public institutions; “supporting processes” means processes whose sole purpose is to ensure the proper functioning of the core processes; “support desk” means a unit or section or designated personnel within a public institution that is responsible for providing assistance or support on all technical matters related to e- Government delivery; “technology neutral solutions” means solutions which are not tied with a specific technology; and “vendor neutral solutions” means solutions of a vendor that are compatible and inter- operable severally with other vendor’s solutions. PART II MANAGEMENT AND OPERATIONS OF e-GOVERNMENT (a) Conduct of business of Committees Convening of meetings of National e- Government Steering Committee Quorum

Section 2Verify source

Part

scheduled

§ 49(1) For the purpose of ensuring that the domainProvision

Public institutions must register their domain names with the Authority and make an annual declaration of the officially registered domain.

49.-(1) For the purpose of ensuring that the domain names of public institutions are secured, a public institution shall - (a) have their domain names registered by the Authority; and (b) make declaration of officially registered domain annually (2) A public institution shall, unless otherwise approved by the Authority, register only one unique and simple domain name for all its business operations, and all other domain requirements shall be captured by a subdomain under its officially registered domain. Government ICT maturity assessment

Section 49Verify source

§ 50(1) Authority shall perform annual evaluation ofProvision

The Authority must evaluate public institutions’ ICT maturity every year and use the results to set ICT security standards.

50.-(1) Authority shall perform annual evaluation of public institutions ICT maturity status by- 22 GN. No. 75 (contd.) e-Government General (a) requiring public institutions evaluation and submit the report to the Authority; (b) verifying the evaluation and publish the results in to perform self- public institutions ICT maturity report; (2) Where an evaluation has not been performed in any particular financial year by a public institution, the Authority shall use the most recent available published ICT maturity status. (3) Where a public institution has no evaluation record, the Authority shall use the lowest possible ICT maturity status. (4) For the purpose of this regulation the Authority shall use ICT maturity status to define requisite ICT security standards.

Section 50Verify source

§ 51(1)The Authority shall perform annual evaluation toProvision

The Authority must conduct an annual evaluation, require public institutions to submit evaluation reports, and may require corrective ICT maturity measures when minimum security requirements cannot be met.

51.(1)The Authority shall perform annual evaluation to establish presence of Government critical systems and application software and their minimum security requirements by- Government critical system and application software Protection (a) requiring public institutions evaluation and submit the report to the Authority; (b) verifying the evaluation and publishing the results in the Government critical systems and application software report. to perform self- (2)Where minimum security requirements necessary to protect Government critical system and application software cannot be implemented by a public institution because of low ICT maturity status, the Authority shall require a public institution to- (a) raise its level of ICT maturity to enable it to security implement prescribed minimum requirements; or ICT (b) surrender the technical ICT aspects of the operations of Government critical system and application software to a more capable public institution as determined by the Authority. Compliance to e- Government security standards and guidelines

Section 51Verify source

§ 52(1) A public institution shall comply with requisiteProvision

A public institution must follow the required ICT security standards, based on its ICT maturity status. The Authority must assess a public institution’s e-Government security compliance and issue a report, either on its own initiative or when asked by a public institution or the Minister.

52.-(1) A public institution shall comply with requisite ICT security standards in accordance with institutional ICT maturity status. (2) The Authority shall, whether suo motu or upon request by a public institution or the Minister, undertake e- Government security compliance assessment of a public institution and issue a security compliance report. 23 GN. No. 75 (contd.) e-Government General electronic data management Electronic data collection or creation PART VI ELECTRONIC GOVERNMENT DATA MANAGEMENT

Section 52Verify source

Legislative relationships

3 referenced instruments

Names are derived from the stored provision headings and citation-enrichment layer. Treat this as a research index and verify each relationship against the source text.

A–F

3 instruments

Act and these Regulations
Section 27
Authority to be inspectors for the purpose of these Regulations
Section 31
Directors of the e-Government Authority established under section 7 of the Act
Section 2

Recorded versions and source checkpoint

1 version available in this collection

Current-law checkpoint

Undated version · currentEnglish

This relationship view does not by itself establish whether another instrument remains in force.

Check official source

Source-linked research

Ask AI about this statute

The overview, provisions, and source records above are public. Continue in a separate conversation with this statute’s jurisdiction and source version attached.

The e-Government General Regulations, 2020

Publicly available, excluded from search-engine indexing

Purpose and legislative effect

How the instrument operates

Start with the recorded version

Locate the controlling provision

Read conditions and exceptions together

Verify currency and official wording

Research entry points

Source and current-law status

Source record view

Sections and provisions

Search within this statute

3 referenced instruments

Recorded versions and source checkpoint

Ask AI about this statute