Open Stack System and Cloud Computing - Coursework Example

Open Stack System Academic Lecturer’s Number Due Introduction Cloud computing entails creating efficient use of the computing assets i.e. hardware and software that are served jointly by the (internet) network. We refer it as ‘Cloud Computing’ because it holds the symbol of Cloud, which usually symbolizes vast networks particularly the ‘Internet’. The obstacles in communication associated with the system diagram are demonstrated by the ‘Cloud’ symbol. Cloud computing utilizes the inaccessible services to handle customer’s data, software and working out for the requirements and mitigates the user in managing these prerequisites (OBrien, J., Marakas, G., 2010). Monetarily, the core advantage of cloud computing is that, the user goes for the services they require and not get stressed about the highest point services. The user is assumed to pay for what he has been utilizing only, rather than lengthy calculations and getting upset for prospects. The ease of access to their sources is offered every time through the internet from the Cloud. There is a stress-free time for users as they don’t need to deal with the fixations at the other end. The customers only acquire the particular IT services they need just the way they would go for any other service. Due to this additional advantage, Cloud computing has also been acknowledged as ‘Utility Computing’. In a world of computing, a considerable resource along with the vast expansion proposal is becoming a massive venture for the IT industry. The perception of a highly scalable group of hardware and software resources has appeared as a sparkling star in most cases. An organization gets to spend much lesser and have fewer investments by opting for Cloud services as it gives an additional advantage to the cloud users. It is done by following the rule of ‘pay as you go ‘, which encourages the firms to cut off their expenses efficiently. The organizations are no more liable to pay unnecessarily for the services they do not utilize. Avoiding payment allows them to meet high practice and facilitates the user to pay the actual services acquired. It also enables the organizations to save an enormous portion of money for them. Cloud computing is referred to as a technology designed to smoothing the process of a suitable network contact. It also accomplishes the mutual compilation of constructive computing resources (i.e. networks, servers, physical and virtual storage devices, applications and services). The resources can be hastily presented and commenced with the slightest amount of management exertion or service source interface. Following are the obligatory provisions for Cloud Computing. These structures should be accomplished so that it accurately reckons any service as being Cloud based and lacking them being marked the right cloud computing technology would not be executed (Nowduri, 2011). Self –Servicing A customer, who requires computing services immediately at a definite time, can be granted resources such as CPU-time in a voluntary manner without the call for any human interaction with source providers. Network Access The essential computing resources are mostly offered over internet (network), and several customers utilize them (applications), which possess diversified proposal. Like cellular phones, microcomputers that include laptops and PDA’s situated at the user’s end. The broad network access provides the excessive value, and it also boosts the capacity of the advantages provided by Cloud Computing. Resource Pooling Cloud service providers cater computing resources in a grouped form (i.e. collected together) so that various customers could be served. It can be attained by means of “multi-tenancy” focusing several customers of the similar resources or by virtualization focusing virtual devices indicating physical hardware. It is achievable by possessing various physical resources along with virtual resources with dynamism in order to allocate and reallocate according to the customer’s needs. Economies of scale and specialization of resources play a role of the ‘Motivational Forces’ following the idea of a pool focused computing theory. The outcome of such a shared model is the gloom of physical computing resources. It indicates that the resources are concealed from the users; the customer does not possess any know-how of the location, structure, and foundation of the resources that they have acquired. For example, Users are unable to locate their data that where it is assumed to be stored in a definite Cloud. This facilitates a genuine user-friendly condition of resources to the customers and consequently allows resource grouping without sacrificing the secrecy of the management structure of the resource provisioning methodology. Services and Types of Cloud Computing Cloud computing can be defined by classifying it into two categories. There are two ways of categorizing the clouds. First one produces from the several services provided by the Clouds while the other one produces from the different forms of the Clouds that are based on the magnitude and user admission system demonstrated by the Clouds. Types of Cloud Clouds can be alienated into three types based fundamentally on the network size, the customer’s number, and the protection of admission. The types are (Bento, A. M., & Aggarwal, A. 2013): Public Clouds, Private Clouds, and Hybrid Clouds Public Clouds Public Clouds illustrates the conventional meaning of Cloud computing technology. They symbolize measurable, animatedly available usually virtualized resources communal over the network (Internet). The offsite third party source measure resources and charges its users on the pay-as – you go basis. Think Grid, an organization caters a multitenant architecture for providing services which involve software –as-a-service, platform-as-a-service, hosted storage. Other famous Cloud sources include Salesforce and Amazon EC2. Private Cloud Private Cloud is a word that describes a computing architecture providing hosted services on private networks. Outsized organizations opt for this type of Cloud computing to offer in-house services for consumers that are contained within the organization. The company network and its information center managers can create a local cloud for their consumers. On the other hand, private clouds abolish several advantages associated with Cloud computing, primarily because firms are required to procure, constitute and control their personal clouds. Therefore, they are unable to gain the proper advantages of Cloud computing as far as the non-commitment flexible accessibility of resources is concerned. Hybrid Cloud Hybrid as its name describes, is a blend of resources from internal and external resources. It is among the most dependable and prominent option for businesses and firms, whereby an organization can have a choice of using a Public Cloud service for computing on daily basis. However, the business related information would be concealed in its data centre employed by the firms. Highly regarded and massive scale organizations have already invested a big capital in its communications needed to offer resources in-house. It can be among the valid motives for the firms to acquire a Hybrid Cloud. The other reason could be the security associated with the public Clouds. In fact, the public cloud being deficient in providing the information secrecy has played as a critical barrier to the use of Public Clouds (Ryan, 2011). The data security provided by the Public Clouds has forced the organizations to go to the Private Clouds as far as their data authenticity is concerned. Virtual Private Cloud A focused type of Cloud is the cryptographic Cloud storage launched by the mind boggles at Microsoft. This specific storage solution facilitates the consumers with the security delivered by a Private Cloud while ensuring expenditure reserves intrinsic of a Public Cloud. Cloud Services The Cloud has been distinguished on the foundation of three unusual service models according to various individual. In accordance with our assumptions, all the three essential services of the Clouds are Hierarchical in such a manner that one presents the others. The service models are defined as: Software as Services (SaaS): The Cloud in these model users comprehends their relevant applications in a hosting environment which can be monitored through a diversified network based consumers by different customers. The consumers may be the Web browsers, PDAs, desktops etc. The Cloud model service has been used most extensively although it is the most misinterpreted model. Consequently, a lot of perplexity and argument has come forth in relation to the same service model. New Needs Because cloud computing is highly demand and used, a new issue is required in the system to satisfy the customers and providers. First, we need a single set of tools to integrate and manage public clouds and private clouds (Hybrid cloud). In addition, there is a great need for a cheap open source tool to manage on-premise private Clouds that is downloadable from the Cloud network. Some of these Clouds include Host private, public and community Clouds. A community cloud can be seen as a multi-tenant infrastructure. It is shared by different organizations that are from a specific group and have a common computing concern. These interests might be related to audit requirements, or may be related to performance requirements (Margaret Rouse, community cloud). There is an interest indifferent in managing instances in different public clouds for redundancy and reliability. On the Security side and because of clouds security issues that is a wondering point till now I will talk about it further in the paper, there is a demand on run instances with critical financial transaction and company’s proprietary data in private cloud. To have a single dashboard to manage the entire instances in the “hybrid” cloud is the critical need. From all these issues Open Stack appears. Open Stack Open Stack is an open-source IaaS provider venture, which obtains sustainability by multiple cloud service providers. The venture was originated by NASA and Rack space in 2010, whereas at this time various firms have become its component (e.g. HP, Cisco, Dell etc.) (DATA MONITOR: Dell inc. 2009). Two sub-projects are included along with the terms of the Apache License for its discharge; Nova for computing resources (virtual machines, network, block storage) (Kerner, 2013). A crucial goal of the Nova Project is to give backing to various IaaS APIs at the matching time. At present two APIs are being executed: Open Stack API 1.0 (corresponding the present Rack space Cloud Servers API) and the Amazon EC2API. Swift for file- based storage preference. Earlier, the Swift code base used to be an open-sourced edition of the engine behind Rack space Cloud Files service. Nova began as an incorporation attempt between the NASA Nebula IaaS code base and Rack space Cloud Servers API. Eucalyptus is considered as an open-source resolution (under the GNU General Public License) offering IaaS. It incorporates Amazon’s Public Cloud EC2 with other public clouds intended to pursue. The virtual machines that are controlled are XEN- OR KVM-based Linux System. Furthermore, there is compatibility between several VMware technologies in the (closed source) business version. Consumers can quickly upload custom images as Eucalyptus does not contain public images. Considering storage, the Eucalyptus Block Storage offers a platform that is supported by the elastic Block Storage from Amazon. It facilitates the consumer to produce masses, include them in a virtual machine and to take prints of them, at the same time a storage manager known as Walrus is an execution of the Amazon S3 edge. As there is not any built-in controlling system, conversely auto scaling is not compatible. However the Eucalyptus works in align with Nagios and Ganglia. It should be clear that as per ,controlling and scheduling are intrinsic cloud distinctiveness therefore; any open source IaaS solution must involve these elements inside its foundation architecture (e.g. Open Stack provides Swift coverage to States/ Graphite. The idea about this software is to manage a large pool of computer resources (compute, storage and networking) through a data centre managed by a dashboard or OpenStack API. OpenStack Roadmap: OpenStack Software is an open design and development process. The community work within six months time-based release cycle with constant development landmarks. The Community gets together in a Design summit in each planning phase for each release to discuss live developer-working sessions and gather the roadmap. Also they offer public documentation during the development status of the current release and the decisions made at each Design Summit. OpenStack Software Components: There are a lot of the software capabilities, and here are the current capabilities: · OpenStack compute (code-name Nova) The code provided by NASA research library, and it is the central part of IaaS system. It is designed to manage and automate pool of computer resources and can work with widely available virtualization technologies. Building Nova is based on a shared-nothing and a messaging-based architecture. All components that needed in Compute Controller, Volume Controller, Network Controller, and Object Store can be run on multiple servers. It is built to be highly available, Fault tolerant and Recoverable. OpenStack Networking (Neutron) It is an OpenStack project that provides "networking as a service" between interface devices. It gives a flexible network model between the servers to handle the needs. Neutron includes flat networks and VLANs to separate between the server and the traffic. Also, it supports floating IPs that allows the dynamic reroute of traffic to any of the user computer resources. It gives the user control to redirect traffic during maintenance or in case of failure. It supports LBaaS (Load Balancing as a service) to drive the actual load balancing of requests. It provides a single API that allows a user to move easily between different load balancing technologies. · OpenStack Object Storage (Swift) OpenStack object storage uses clusters of standardized servers. The Object and files are written to multiple disk drives spreads among the servers. It is the OpenStack responsibility to ensure the data replication and integrity across the cluster. In case of server failing the software replicates its content to a new location in a group to make sure the data not lost. OpenStack Block storage (Cinder) It is a persistent block level storage device for use with the computer instances. It controls the detaching, creation, and attaching of the block devices mainly to servers. It allows the cloud users to manage their storage needs. It supports numerous storage platforms such as Ceph, NetApp, Nexenta, Solid Fire, and Zadara. It uses Snapshots to create a new block storage volume. In case for the need of backup data stored on block storage volumes Snapshot management provides strong functionality to do that. OpenStack Identity (Keystone) Keystone provides a directory of users mapped to the services that can use in the OpenStack. It is the standard authentication system across cloud operating system, and it accommodate with the existing back-end directory of the system. It can support multiple forms of authentication including standard username and password credentials, token-based systems (which allow users entry of their username and password. The users provide the username and password to obtain a token that allows them to get a particular resource. Once their token has been received, the user can offer the token provides a particular to the remote site. (Alex Martelli) (Token based authentication system)). It also supports AWS-style logins (which uses API key pair as Aws ApiKeyVerifier). OpenStack Image Service (Glance) Glance is useful in the provision of the services, discovery, and delivery and registration services for disk and server images. It makes you able to copy or snapshot a server image and stores it away for use as a template to find the new server up very efficiently and quickly. A glance can store disk and server images in a variety of back-ends. As an administrator you can create base templates from which their users can start new compute instances. As a user you can choose from available images, or create their own from existing servers. OpenStack Dashboard (Horizon) Horizon provides the administrators and the users a graphical interface to use and manage the cloud services. The system is an open source and therefore, you can edit the dashboard to your needs. Developers can automate entry or form tools to control them by applying the original OpenStack As an administrator you can use the dashboard with more privilege to have an overview of the system, create users and projects, assign users to projects and set limitations. As a user you can use self-service portal that allow you to use the services provided by the system with the limits puts by the administrator. OpenStack Telemetry (Ceilometer) It calculates the usage and performance data across the services exists in an OpenStack cloud. It provides visibility and insight to the usage of the cloud across the data points. OpenStack Orchestration (Heat) It is a template-driven engine that allows application developers to describe and automate the deployment of infrastructure. It built to specify compute, storage and networking configurations as well as a detailed post-deployment activity to provide the full prepare of infrastructure as well as services and applications. OpenStack database (Trove) It is designed to run entirely on OpenStack, the service allow the users to handle quickly and easily the features of a relational database without handling complex administrative tasks. Administrators and users can use and manage multiple database instances as needed. OpenStack data processing (Sahara) It provides a simple means for providing a data-intensive application cluster like (Hadoop or Spark). Its the ex Savanna project, renamed due to potential trademark issues. OpenStack Bare-Metal provisioning (Ironic) It aims to provide bare metal machines instead of virtual machines, forked from the Nova Bare metal driver. It supports vendor-specific plug-ins that may implement additional functionality. Open Nebula and Open Stack Open Nebula is referred as an Open-source IaaS Solution, which was primarily nurtured within the structure of an EU-funded project. Open Nabula organizes storage, network, virtualization, monitoring and security technologies. It facilitates the forceful assignment of VM’s combining both information centre resources and inaccessible Cloud resources, as per provision strategies (Kerner, 2013). It possesses a huge customer base with telecommunication firms, system incorporators, and supercomputing centres. In this part, we estimate two open-source of IaaS solution with a consideration of qualitative and quantitative scenarios. Both 3.1 Testbed Description assuming for testing and evaluation together with two physical hosts and subsequent hardware attributes so that the evaluation of the IaaS approaches on peak of the same physical hosts could be performed. We have established OpenNebula v3.3.0 on the first physical host and OpenStack (Nova) v2012.1 on the other one, on these physical hosts. As far as the VMs configuration is concerned, it’s shown in the following table. Furthermore, the configuration of the VCPU is kept equal to a typical decisive factor for our evaluation (GRIFFIN, J., & DANSON, F. (2012)). Qualitative Comparison: We discussed previously that the criteria assumed in our qualitative study that have been used to evaluate OpenNebula and OpenStack. Criteria differ from sustained functionality to security and are as pursue: Models Compatibility: It symbolizes the operational models (i.e. public, private, hybrid, community) which might show compatibility to OpenNebula and OpenStack. Virtualization compatibility: this entails to the compatible fundamental virtualization technology along with the other elements like whether reconfiguration that can be done in the runtime, with or without rebooting, allocation of the virtual resources, etc. Access: It demonstrates the APIs allowing administration of virtual machines with the out-of-band way in as used in several cases throughout debugging. Image Support: This criterion will cover the compatible operating systems and whether a consumer can upload custom operating system images with already installed system, will be evaluated. Resource Selection: It covers the capability to choose the geographical location of the physical resources on which the virtual ones will be installed. Storage Support: It demonstrates the availability of the block storage or file storage and if a Content Distribution Network (CDN) is provided. Auto-scaling Support: It gives exposure to the ability of auto-scaling following accessing data (e.g. CPU or memory usage). High-availability Support: If the sources facilitate consumers to acquire high-availability involving the use of resiliency mechanisms (e.g. live migration, fault- tolerance, automatic backups, etc.). Monitoring Capability: Consumers may find information and notifications about performance deprivation, hardware failures, etc. API Support: Edges provided by the IaaS sources based on many protocols (such as SOAP, REST,), API descriptors (WSDL), standards supported. Security Features: In this criterion, the right to use control management, certificates, password restrictions, source side firewall, etc. are included. Service Level Agreements (SLA) capability: facilitating consumers to negotiate authorizes and scrutinize SLAs with definite aspects. They observed through qualitative analysis and qualitative evaluation that there are some functional features that are not available in OpenStake but OpenNebula provide that features and make it more user-friendly. For VMs deployment, OpenNebula has a web interface while OpenStake uses command line interface for this purpose. Along with this, web interface of OpenNebula provides the feature of resource selection for VMs deployment and also OpenStake does not support some features like auto-scaling and high availability support. One of the interesting points about both OpenStake and OpenNebula is that for SLA negation and management these two do not provide a native mechanism (which is available in ecosystem tools). Quantitative results show that by allowing auto-scaling feature in OpenStake and purposeful storage support in OpenNebula would be beneficial for both respectively. From the assessable point of view, OpenStake has a better performance than OpenNebula when scaling out (increment in the number of VMs) during the deployment process as shown by the similar pending time. In spite of that, in massive at once (not stepped) VMs deployment case, OpenStake has better performance than OpenNebula because OpenStake takes less time in getting the VMs running the state from the acting state. Moreover, using quantitative results of at-once massive VMs deployment case, OpenNebula can get benefit such as algorithm implemented and decreases the under deployment VMs pending time.Quantative and qualitative analysis evaluation results show that for the applications that require quick scaling, OpenStack is the optimum solution. These applications may be called as soft real-time applications (such as Virtual and Augmented Reality, Digital Film Postproduction, etc.) and as the applications of depicting spikes in requested resources-usually those applications which are open for a large group of people (e.g. Animoto application on Facebook) (Kerner, 2013). While OpenNebula would be more suitable for the applications having high elasticity requirements (this feature is not supported in OpenStake) such as smart city scenarios (e.g. by on-demand obtaining and analyzing information for enhancement in car cruise from city sensors smartphones and other cars, etc) or in scenarios of health care which uses OpenNebula features of security features. Security in OpenStack There are many flaws in OpenStake, and these can be addressed to the current released version of OpenStake. These are (Wilshusen, G. C. 2011): No password reset option to users on horizon; it can be reset only within administrator interface while the impact of this flaw in unknown. The project administrator is automatically made the administrator of the whole system in horizon. For cloud computing, OpenStake uses the concept of projects and tenants to group people into logical units. However, administrator of a single project is assigned the managerial role of all the projects by the interface only. He gets the right of user and project creation, can even change projects and remove items. Network API uses Clear text and OpenStack API end points encourage the use of clear text but currently no SSL/TLS support is available. This allows middle attacker, and even “sniffing” passwords over the wire can be trivial. No server-client system authentication allows any host is having access to the DB and the AMQP system can act as a computer node and can launch VMs. Usernames andPasswords Clear text stores the passwords and usernames for accessing images in DB and external devices. While storing images on swift using glance, clear the text stores username and password of swift account along with URL of a swift object in the DB. This may allow any cloud swift user to access information in DB. This is an unnecessary storage of information as username and password are already stored in the configuration file of a glance. On the basis of these problems, cloud security solution has studied which is discussed in later section. In revision section of security in cloud computing, we discovered which issues are often discussed in relation to identity and access management. So this section discusses identity and access management. Risk Management Strategy Risk Management Practices of NASA’s were ineffective for Acquiring and Securing Public Cloud-Computing Services. According to NIST, it is a challenge to assess and manage the risk of transferring data to a public cloud as it is totally under the hand of the cloud provider. To overcome this, risk mitigation contracts should be developed, addressing the business and security risks unique to cloud computing environments. Some clauses should be added in contracts with cloud providers explaining the measurement of performance, how it will be reported, and enforced and specify how Federal privacy, litigation discovery, and data retention and destruction requirements will be met. Moreover, it should be included in the contract that how the cloud service provider will perform security tasks and a third party should inspect it. Finally, roles and responsibilities of the Agency should be explicitly mentioned, the cloud provider, and the cloud broker must drive contractor performance and ensure Agency systems and data are adequately secured. For public cloud services specifications are known as service agreements or service contracts. This service contract includes all the terms and conditions of access and use of the services which the cloud service provider will offer, duration of service, conditions for termination, and disposition of data (e.g., preservation period) when the contract will terminate. Usually all these are contained in multiple documents, including a service level agreement, privacy and acceptable use of policies. NIST has defined two types of cloud computing service contracts: predefined, non-negotiable contracts and negotiated contracts. In first type of contract, the contract terms are prescribed by the cloud provider and these contracts do not impose requirements except the scope of service and availability. They do not address Federal IT security and privacy, production, retention and destruction of data requirements. Moreover, the cloud service provider keeps power to modify the contract without notifying the customer. Negotiated service contracts are like outsourcing contracts for IT services. Terms and condition can be tailored to address company’s requirements for tracking and reporting service ( to check effectiveness), contains technical controls such as incident detection and handling, require compliance with laws and regulations, data ownership rights and the use of validated products having national or international standards. To adopt the best practice, the recommendation from the Federal Chief Information Officer (CIO) and Chief Acquisition Officer Councils is the arrangement for cloud services. It clearly defines how performance is guaranteed (such as the response, mitigation, resolution, time and availability). Providers need to monitor their service levels and have to provide timely reports in case of any failure. If service levels are not met, they should be patently on service provider. On reviewing NASA’s contracts with their public cloud-computing, services provider need to check whether the Agency had implemented adequate risk mitigation measures. We find that contracts met best practices for attaining cloud services as recommended by the CAOC and the Federal CIO and as well as practices identified in FedRAMP.12. For instance, we analysed that contracts defines the roles and responsibilities of the company and way to measure contract or performance, reporting procedure, and enforcement. We also evaluated the contract addressed by Federal privacy, discovery, data retention, and destruction requirements. Finally, it was stated that service providers or brokers appropriately addressed key IT security measures like incident detection and handling practices and service provider’s evaluating procedure. The summarization of results is given in Table. There are five NASA cloud-computing contracts which were reviewed by us; three of them were for cloud services categorized as low-impact services and remaining two were for moderate-impact services. NASA accepted the three low-impacts and one of the moderate-impact service contracts. For the other moderate-impact cloud service hosted by more than 100 internal and external Agency websites, NASA negotiated a contract with eTouch (a cloud-computing broker), to manage service delivery and helps ensure IT security and privacy requirements were met. Conclusion Open Stack is beneficial for companies looking for an edge in todays economy. Cloud computing services are offered by many vendors which are now getting affordable over time. Lower prices allow companies to use the staff for other available tasks, and they can use their resources more efficiently in different projects through paying for services only when needed. These features allow the companies to have a growing support for this model as it is attractive and uses economical pay-as-you-go approach. A major threat that is posed by Open Stack is that it obliterates internal and external boundaries in security concerns. There is a need to study cloud security in order to understand the security of companies’ data. The second level is the availability, and suppliers may be victims of attacks that impede the functioning of its operations. For IaaS cloud environment, this work gives the comparison of two open-source clouding solution; OpenStake and OpenNebula. Both are Apache licensed released open-source software and developed over the internet using open and transparent process. OpenNebula provides private clouding for users while OpenStake provides AWS-like public clouding. Moreover, in OpenNebula functionalities can be offered using a single integrated bundle while in OpenStake a set of feature is a compliment for individual functionalities and capabilities. The implementation of OpenNebula follows some standards like Amazon APIs, OGF, DMTF and SNIA specifications while the implementation of OpenStake follows the requirements of companies that are contributing in this and then forms an AWS. Qualitative and quantitative analysis can be summarized as; the OpenStack version has not much functionality (e.g. auto-scaling) but performs better than OpenNebula while implementing new VMs. In addition to the enhancements purposed in our paper, OpenNebula and OpenStake are the optimum solutions for different applications (e.g. in security-sensitive and city scenarios. OpenNebula is preferable while in time-constrained scenarios OpenStake is preferable). In spite of this, the future evaluation of these open sources clouding solution will be dependent on their updated versions available to the community. These evaluations will also refer the hardware characteristics to identify that at which extent it will affect the provision of services. Moreover, we will perform more quantitative analyses of large infrastructure to collect additional information and will compare the IaaS open solution with Eucalyptus. References Bento, A. M., & Aggarwal, A. (2013). Cloud computing service and deployment models: Layers and management Business Science Reference. DATA MONITOR: Dell inc. (2009). Data monitor Plc. GRIFFIN, J., & DANSON, F. (2012). Analytics and the cloud – the future is here. Financial Executive, 28(9), 97-98. Kerner, S. M. (2013). Openstack cloud goes global to draw in developers, technologies. EWeek, 13-13. Kedar, S. (2009). Introduction to data processing In Database management systems (First ed., pp. 1). India: Technical Publications Pune. Nowduri, S. (2011). Management information systems and business decision-making: Review, analysis, and recommendations. Journal of Management & Marketing Research, 7, 1-8. OBrien, J., Marakas, G., (2010). Management Information Systems. 9th ed. New York McGraw-Hill. STAIR, R.M. and REYNOLDS, G.F., Principles of Information Systems (with Printed Access Card) Course Technology. Wilshusen, G. C. (2011). INFORMATIONSECURITY: Additional guidance needed to address cloud computing concerns. GAO Reports, 1. ZALESKI, J. n.d, Integrating Device Data into the Electronic Medical Record: A Developers Guide to Design and a Practitioners Guide to Application Wiley-VCH. Read More