DSI-Cloud Computing

Questions: 1. Discuss the requirements for remote administration, resource management and SLA management. It may be useful to consider Morad and Dalbhanjans operational checklists for DSIs OSDS. This section should be no more than two to three pages in length. 2. Discuss briefly how you will consider application resilience, backup and disaster recovery for your chosen provider in relation to OSDS. This section should be no more than two to three pages in length. 3. Use Erls SLA guidelines to assess the SLA for your chosen provider. This section should be no more than two to three pages in length. 4. Provide a covering one to two page executive summary of these two assessments to DSI Executive Management and summarise the major opportunities and risks that have been identified in your assessments. Answers: Introduction This article is about a government related department DSI. It provides critical data to the government department as well as it spread data to the public area. It is necessary that the data given by the DSI should be correct, i.e. If DSI will give any false statement to government or to the public, and then it will affect the reputation of the government as well to DSI department. The rate of the data is booming at high peak as the population is increasing. To manage the large chunk of data, the DSI is deciding to shift its business from OSDS to cloud computing form. The DSI wants to select a system which is reliable, and also it should be risk-free. The DSI wants to take a perfect decision on the architecture, and on the model used for cloud computing (Almutairi, Ghafoor, 2014). This implementation of this decision requires a lot of the investment cost, so the DSI wants to take a perfect and fruitful decision. Any incorrect decision will lead to loss of investment cost as well as i t can harm the data stored in the database, and further, it will cause loss to the DSI department as well as it will affect the reputation of the department and government. There are various requirements related to resource management, remote administration, and SLA management The various cloud computing deployment models that vary with their architecture Public cloud computing: This is based on a pay per use technology. The customer has to pay by the application, data, or services used by them (Wang, 2015). The setup of this method is inexpensive. This is a cheap method because all the applications cost, hardware tool cost, and software tool cost are managed by the cloud provider. There is no any wastage of resources, as the customer uses the resources depending on the requirement and pay for the resources depending on the use. It is a less expensive method as compare to the other models. Private cloud computing: These are managed by the internal providers. In the organizations, there are separate team for handling this service of cloud computing. It is used for critical data, and it is an expensive method. It is different from a private model, because it is accessed by the unique organization. Hybrid cloud provider: It is a combination of both private as well as public cloud. These are managed by internal as well as by external providers. It is managed by the internal as well as by the external cloud providers. Community cloud: It is accessed by the limited cloud users. If those specific customers, give access to the external entities or users for accessing the data then they can also access the data from the cloud servers. Inter-cloud: It is a combination of more than two clouds, which are interrelated with each other. The DSI should adopt the Hybrid model because it is a combination of both private and public cloud computing models. If DSI goes for private, then it is an expensive method, and it needs a lot of investment costs. If DSI goes for public, then it is not safe as the DSI has to send information to the public, and government and the data are very critical and sensitive, and it needs to be placed confidentially (Avram, 2014). Then, it should opt for the hybrid as the less sensitive data should be placed on the public cloud, and important data should be placed on the private cloud so that outsiders cant play with the crucial information. The different cloud computing delivery models are: IaaS-Infrastructure as a Service: They provide a full control over the cloud computing environment. It is a safe model, as the data used by the cloud users is monitored (by the IaaS). It also helps in managing the software as well as hardware requirements, required by the different cloud customers. PaaS-Platform as a Service: They provide a limited control on the cloud computing environment. SaaS-Software as a Service: They provide a very limited control on the cloud computing environment. It doesnt provide support in managing the customer requirements. DSI should opt for Infrastructure as a Service model. It provides proper monitoring of the data (accessed by the cloud users). It also helps in, managing, and creating the applications, and hardware and software needs (Almutairi, Ghafoor, 2014). Also, it monitors the whole cloud computing environment carefully. Both the models and architecture are mentioned in the SLA. This agreement also contains the capacity, speed, performance, throughput, etc. that the cloud providers are going to provide to the users. The various steps related to application resilience, disaster recovery, and backup management. In case of cloud computing (mostly in case of private cloud), the information can be updated or damaged by the attackers. Prevention is better than cure. The DSI data are very important, and it should be placed and managed in a secure manner. The DSI should place the critical data in a private place so that hackers cant affect the data. The DSI should place the important information on the private cloud and the cloud server should be monitored by the team of the organization, and other data should be placed in the public cloud. The DSI can use a firewall to make the data safer. A Firewall is a combination of software as well as hardware, and it is used for securing the data from the outsiders attack. Also, the proper backup of the information should be taken, and copies should be placed in the data centers (within the organization, and the data centers present outside of the organization). The various security and government requirement required for this plan (for disaster management): Backup of the data: The backup of the data should be taken for the safety purpose. The replicated copies of the data should be placed on the internal as well as on the external servers. Encryption: It can be public key encryption or it can be private key encryption. In case of private key encryption, the sender and receiver both have private keys. In case of public key encryption, the sender has a public key, but the receiver has a private key (Choo, 2014). The sender sends the encrypted data to the receiver, and the receiver access the data by decoding or unlocking it (by using private key). The encrypted file should be placed on the cloud server so that it can access or used only by the valid and authorized person. Authentication: The proper Id should be given to all employees for accessing the server data and access given to different employees vary depending upon the ID given to the employees. Firewall: It should be placed on the servers, so that the data cant be interrupted by the outsiders. Any authorized person cant able to access the data. Password: A strong password should be created by the employees who are accessing cloud servers. The password should contain characters, symbols, special characters, and numbers; so that it can be easily hacked. Moreover, two-time verification technique should be used (while creating the password). The employee who is creating their ID for the data server has to create a password and also the employee has to enter the number (verification code that the person receives on the mobile). This provides safety as the theft cant access the data until the theft can hack the phone of the person (earlier, the verification code sent to that phone). System logs: The system should manage the log time and duration of accessing the database. The various guidelines related to SLA: Cloud source: The party that requires this service or the users. Cloud provider: The party that provides this facility, the party can be a part of the organization, or it can be outsiders. Cloud server: The place which is used for placing and managing the data. Pay-Per-Use: The more the person uses the service, the more amounts the person has to pay to the providers. Log: A log should be maintained for recording the services used by the cloud users. SLA: It is an agreement between both the parties, i.e. between the cloud provider, and between the cloud customers. This agreement contains the capacity, speed, performance, throughput, etc. that the cloud providers are going to provide to the users. The DSI should make an agreement for the hybrid architecture and for IaaS model. Conclusion The DSI data are very important and it should be placed and managed in a secure manner. The DSI should place the critical data in a private place so that hackers cant affect the data. The DSI should adopt the Hybrid model, because it is a combination of both private and public cloud computing models (Avram, 2014). If DSI goes for private then it is an expensive method, and it needs lots of the investment cost. If DSI goes for public, then it is not safe as the DSI has to send information to the public, and government and the data are very critical and sensitive and it needs to be placed confidentially. Then, it should opt for the hybrid as the less sensitive data should be placed on the public cloud, and important data should be placed on the private cloud so that outsiders cant play with the crucial information. DSI should opt for Infrastructure as a Service model. It also helps in managing and creating the applications, and hardware and software needs. Also, it monitors the whole c loud computing environment carefully. References Almutairi, A. Ghafoor, A. (2014). Risk-Aware Virtual Resource Management for Multitenant Cloud Datacenters. IEEE Cloud Comput., 1(3), 34-44. Avram, M. (2014). Advantages and Challenges of Adopting Cloud Computing from an Enterprise Perspective. Procedia Technology, 12, 529-534. Chen, J., Han, J., Deng, Y., Zhong, H., Wang, N., Li, Y. et al. (2015). Wisdom as a Service for Mental Health Care. IEEE Transactions On Cloud Computing, 1-1. Choo, K. (2014). A Cloud Security Risk-Management Strategy. IEEE Cloud Comput., 1(2), 52-56. Madria, S. Sen, A. (2015). Offline Risk Assessment of Cloud Service Providers. IEEE Cloud Comput., 2(3), 50-57. Pawtucket. (2014). Patient Portal Increases Communication Between Patients and Providers. (2014). BVCHC. Retrieved 19 April 2016, Raghavendra, G. (2012). Impact of adapting Cloud Computing Technology in health care industry. Sri Lanka Journal Of Bio-Medical Informatics, 2(4). Ritu Sharma, Manu Sood,. (2011). Enhancing Cloud SAAS Development with Model Driven Architecture. International Journal On Cloud Computing: Services And Architecture, 1(3), 89-102. Wang, Y. (2015). Cloud-dew architecture. International Journal Of Cloud Computing, 4(3), 199. Weinman, J. (2016). Hybrid Cloud Economics. IEEE Cloud Comput., 3(1), 18-22.