1 | Purpose, scope and audience | 0 |
2a | Settle the shared access control responsibilities between consumer, provider and any underlying IaaS provider | 0 |
2b | Control network access to the cloud service | 0 |
2c | Isolate pooled resources and wipe them before reallocation | 0 |
2d | Verify the security of newly provisioned virtual machines before they take on work | 0 |
2e | Let consumers review but never modify their metering data | 0 |
2f | Keep consumer data under consumer control, and flag and report any data the provider can read | 0 |
3.1 | Enforce IaaS network boundaries with allowlists and tenant VLANs | 0 |
3.2 | Restrict hypervisor access to authorised cloud administrators | 0 |
3.3a | Isolate virtual machines from one another and set policy on shared clipboards | 0 |
3.3b | Enforce VM resource quotas and protect guest images and inactive VMs | 0 |
3.4 | Monitor the access control APIs of the IaaS platform | 0 |
3.5a | Use a virtualization management system with tiered administrative access and SLA-backed interoperation controls | 0 |
3.5b | Write IaaS access control policy rules by subject, operation, object and environment condition | 0 |
4.1 | Control access to shared operating system memory in PaaS, flushing highly sensitive data on context switches | 0 |
4.2 | Scope APIs to each application and centralise authorisation for microservices | 0 |
4.3 | Synchronise access policy across replicated PaaS data and write the PaaS policy rules | 0 |
5.1 | Preserve the data owner's control over application data held by the SaaS provider | 0 |
5.2 | Protect SaaS data confidentiality with encryption and attribute-based control without crippling performance | 0 |
5.3 | Assign and revoke privileges through a flexible, real-time mechanism | 0 |
5.4 | Apply one access policy to every replica of the data and synchronise policy changes | 0 |
5.5 | Plan multi-tenancy with segregated tenant data and a deliberately chosen authorisation model | 0 |
5.6 | Agree and size the set of attributes and roles used for access management | 0 |
5.7 | Enforce authorisation without disclosing sensitive access control data to the SaaS provider | 0 |
5.8 | Design SaaS APIs so that access policy cannot be circumvented | 0 |
6a | Enable intra-operation between a consumer's VMs for the collaboration period only, within and across hosts | 0 |
6b | Reconcile attribute semantics and policy integration before inter-operation across providers | 0 |
7 | Conclusions and open issues | 0 |
A | Appendix A: Mapping of the guidance to SP 800-53 access control elements | 0 |