1 | Who the standard binds, what it references and what the appendices hold | 0 |
6.1 | Comply with law, the information security standard and risk policies in every use of cloud | 0 |
6.10 | Consider a cloud solution only after a risk evaluation accepted by the chief information security officer | 0 |
6.11 | Use facilities rated Uptime Institute Tier III or higher, or add resiliency | 0 |
6.12 | Safeguard authentication, authorisation and identity and access management | 0 |
6.13 | Acquire cloud solutions from ICT Authority accredited providers and prioritise government cloud | 0 |
6.14 | Make negotiated SLA requirements supersede the master service agreement | 0 |
6.15.1 | Contracts provide for exit, data sanitisation, confidentiality and breach disclosure | 0 |
6.15.10 | Contracts provide audit mechanisms, retention compliance, end-of-contract data handling and protection on provider takeover | 0 |
6.15.5 | Contracts fix data ownership, intellectual property, Kenyan data location, data protection compliance and service levels | 0 |
6.2 | Do not host critical applications in the public cloud | 0 |
6.3 | Prepare an exit strategy when contracting with the provider | 0 |
6.4 | Obtain providers' latest standards-based security assurance early in procurement | 0 |
6.5 | Store and process MCDA data within Kenya | 0 |
6.6 | Project licensing needs and confirm the provider meets them | 0 |
6.7 | Protect data on foreign nationals under the Data Protection Act and their home laws | 0 |
6.8 | Encrypt cloud data with keys owned and managed by the Government of Kenya | 0 |
7.1.1 | Identify cloud service users and manage their credentials and use | 0 |
7.1.2 | Appoint a cloud service administrator | 0 |
7.1.3 | Appoint a cloud service business manager | 0 |
7.1.4 | Appoint a cloud service integrator | 0 |
7.2.1 | Government cloud providers appoint operations, deployment and service managers | 0 |
7.2.4 | Government cloud providers appoint business, support, inter-cloud, security and risk, and network roles | 0 |
8.1 | Have cloud services independently audited and secure audit evidence in the agreements | 0 |
8.10 | Secure reversibility: retrieve data and artefacts and have the provider delete all copies | 0 |
8.11.1 | Implement cloud security capabilities, detection and network protection | 0 |
8.11.4 | Define security responsibilities, address model-specific threats, catalogue data sensitivity and control keys | 0 |
8.12.1 | Hold a cloud SLA covering quality, security, performance, remedies and stated limitations | 0 |
8.12.4 | Have the SLA classify data objects, state availability, confidentiality, integrity, access and PII handling, and align it with the master agreement | 0 |
8.2 | Guarantee availability and implement governance over the provider relationship | 0 |
8.4 | Require interoperability through standard interfaces and standards evolution | 0 |
8.5 | Govern maintenance and versioning transparently | 0 |
8.6 | Define and monitor SLA performance metrics | 0 |
8.7 | Avoid lock-in through data and application portability | 0 |
8.8 | Protect personally identifiable information and comply with the Data Protection Act | 0 |
8.9 | Implement resiliency processes for continuous or predictable operation | 0 |