There are many aspects in both the design and operation of the Cloud that will make it susceptible to risks and in which corners can be cut. These fall into a number of major categories;
- It’s design and architecture, especially with respect to scalability and security
- The quality of the hardware, software and network interconnects using to built it
- The processes around the ongoing management and maintenance of the Cloud
- The people responsible for running these processes
One UK solution to this problem is the accreditation provided by the Communications-Electronics Security Group (CESG). This is the government body that provides formal accreditation for any technology or service to be provided to the UK Government. While CESG accreditation is mandatory for the deployment of technology into the UK Defence sector, it’s also becoming widely adopted across major government and commercial organisations. More information on CESG accreditation can be found here: http://www.cesg.gov.uk/about_us/whatwedo.shtml
CESG accreditation is very rigorous and time-consuming to achieve, and once achieved only relates to the version of the hardware/software/service that was accredited. From a business perspective, BT’s aim was to achieve CESG accreditation for our cloud-based SmartNumber services so that they could be deployed within the UK Ministry of Defence and other government customers. The CESG accreditation process looked in great detail at;
- The design of BT DFTS SmartNumbers Cloud, at both a macro and micro level and it’s dependences on any third party interfaces
- Assessment of the components used to build, monitor and maintain the Cloud
- The quality and resilience of the Network Operations Centre used to monitor the day to day running of the Cloud
- The processes around maintaining the cloud, including provisioning, helpdesk
- The people managing the operation of the Cloud, education, qualifications, security clearances
- Scalability and Penetration testing to try to expose any weaknesses regarding resilience, security, and scalability
No comments:
Post a Comment