Cloud Architecture Models for Scalability and Resource Optimization: Workload Distribution and Resource Pooling Architecture

Learn about workload distribution and resource pooling architecture, two foundational cloud architecture models for scalability and resource optimization. Discover how these models enable efficient resource utilization, dynamic scaling, synchronization, and redundancy in cloud systems.

Introduction:

Cloud architecture plays a crucial role in building highly scalable applications to accommodate expanding datasets, unpredictable traffic patterns, and the need for faster response times. In this article, we will explore two common cloud architecture models: workload distribution architecture and resource pooling architecture. These models provide the foundation for achieving scalability and optimizing resource utilization in cloud systems.

Workload Distribution Architecture:

Workload distribution architecture focuses on horizontally scaling IT resources by utilizing identical resources and a load balancer. The load balancer evenly distributes the workload among available IT assets, such as distributed virtual servers, cloud storage devices, and cloud services. Additional mechanisms that can be part of this architecture include:

• Cloud Usage Monitor: Enables runtime tracking and data processing.
• Audit Monitor: Monitors the system to fulfill legal requirements.
• Hypervisor: Manages workloads and distributes them among virtual hosts.
• Logical network perimeter: Isolates cloud consumer network boundaries.
• Resource clusters: Support workload balancing between cluster nodes.
• Resource replication: Generates new instances of virtualized resources during increased workloads.

Benefits of Workload Distribution Architecture:

• Scalability: Horizontal scaling allows for efficient distribution of workloads, ensuring optimal resource utilization during increased demand.
• Fault tolerance: Distribution of workloads across multiple resources provides fault tolerance and minimizes downtime in case of resource failures.
• Performance optimization: Balancing workloads across resources prevents overload on individual resources, leading to improved performance.

Disadvantages of Workload Distribution Architecture:

• Complexity: Implementing workload distribution architecture can be complex, especially when configuring load balancers, monitoring systems, and ensuring resource synchronization.
• Increased latency: Load balancing and workload distribution can introduce some latency, particularly in processing requests involving large datasets or complex applications.

Resource Pooling Architecture:

Resource pooling architecture involves grouping identical IT resources into pools, which can include physical and virtual resources. These resources are automatically synchronized and maintained by the system. Examples of resource pools include:

• Physical server pools: Networked servers with pre-installed operating systems and applications.
• Virtual server pools: Configured from pre-chosen templates during provisioning.
• Storage pools: File or block-based storage containers.
• Network pools: Pre-configured network devices like virtual firewalls and switches for redundancy, load balancing, and link aggregation.
• CPU pools: Allocate CPU resources to virtual servers.
• Physical RAM pools: Vertically scale newly provisioned physical servers.

Benefits of Resource Pooling Architecture:

• Resource optimization: Resource pooling ensures efficient utilization of IT resources by dynamically allocating them based on demand.
• Simplified management: The architecture simplifies resource management by automatically synchronizing resources and providing administration tools.
• Scalability: Resource pooling enables both horizontal and vertical scalability, allowing for the allocation of additional resources from appropriate pools as workload increases.

Disadvantages of Resource Pooling Architecture:

• Complexity: Managing and organizing resource pools can be complex, especially in large-scale environments with hierarchical structures.
• Synchronization challenges: Keeping identical resources within pools synchronized and maintaining consistency across multiple instances can be challenging, requiring robust synchronization mechanisms.

Conclusion:

Cloud architecture models such as workload distribution architecture and resource pooling architecture are instrumental in achieving scalability, resource optimization, and performance in cloud systems. By leveraging these models, architects can design and implement complex architectures that dynamically scale IT resources, synchronize resources, provide fault tolerance, and optimize resource allocation. These architectural approaches are essential for building highly scalable cloud applications that meet the demands of expanding datasets, unpredictable traffic patterns, and the need for faster response times.

References

G. Palmer Security Notes (2015-2023)

Acitura Education. Load Balanced Virtual Server Instances. Retrieved June 17, 2023: http://cloudpatterns.org/design_patterns/load_balanced_virtual_server_instances.

Related Articles and Content

Exploring the Implications of Artificial Intelligence

Artificial Intelligence in Texas Higher Education: Ethical Considerations, Privacy, and Security

Understanding Business Continuity Planning

https://www.vmware.com/topics/glossary/content/cloud-architecture.html

https://scitis.io/cloud-architecture-simply-explained/?lang=en

5 Questions you should ask

https://cloud.google.com/learn/what-is-cloud-architecture

https://www.informit.com/articles/article.aspx?p=2093407

https://ieeexplore.ieee.org/document/8588188

Workload Distribution

https://www.oreilly.com/library/view/cloud-computing-concepts/9780133387568/ch11.xhtml

Note: This article has been prepared with the assistance of AI, which provided suggestions and revisions to improve the clarity and coherence of the content. However, the original research, decision-making, and final content selection were done by a human author.

Disclaimer

The post Cloud Architecture Models appeared first on .

Applications can be moved to the cloud quickly with little problem if the migration is planned correctly. The process of constructing a plan for migrating a system to the cloud generally includes the following steps:

• Define the system goals and requirements. This process includes considering several factors such as security requirements, scalability requirements, continuity and disaster requirements, as well as others.

• Protect existing data. Items to be addressed include a backup plan agreed upon by the customer and provider, data privacy requirements, and procedures to move out of the cloud in case problems are encountered.

• Use a Consultant if needed. Hiring a reputable cloud expert might save organizations money over the long term.

• Consider vendor lock-ins. Lock-ins can be technical or administrative in nature. Cloud providers should make it easy for customers to move their data if desired.

• Know and document the characteristics of current applications. This includes knowing characteristics such as demand periods, average amount of users, disk storage requirements, database requirements, RAM usage, bandwidth required, and cache required by the application.

• Define training requirements. Training requirements to consider include: employee preparedness, developer training, administrator training, audit group for governance training, help desk support training, an business continuity and disaster recovery training.

• Define a realistic deployment schedule. The plan should provide sufficient time for training, testing, and benchmarking.

• Budget concerns. Key budget factors to consider include cost breakdowns for current data centers so comparative analysis and Return on Investment (ROI) can be calculated. Other factors to consider include; current payroll and projected payroll, current and future licensing and update costs, and current hardware maintenance costs.

• Identify governance issues such as alignment with organizational goals, define internal and external controls, identify and mitigate risks, define access, discover how to access event and system logs for auditing, discover how the provider performs updates and patches, and how to use performance monitoring tools.

Cloud migration can be done using a four-stage cycle as follows:

Assessment

An assessment to determine if the cloud service meets system requirements and if the provider’s services align with the organizations goals. Items to consider include the following:

• Is the cloud system offered a good fit, does it align with the organizations mission and goals? Do not blindly choose a provider.

• What are the organizations capacity demands?

• Accurately determine actual costs. Factors to consider include on-boarding programs, support plans, and new environments that did not exist with the current system.

• Are there going to be any gaps in service after the migration?

• How well do the providers tools align with the organizations existing tools?

Planning

• What applications and environments are good candidates for the cloud? Conduct a comprehensive inventory of applications and determine which are the best fit for a cloud environment.

• What’s the topology of the application architecture? Cloud servers, data services, and networks behave differently than their on-premises counterparts so architecture may have to evolve or change to accommodate.

• Will there be any performance bottlenecks? For example: if your applications have integration points with on-premises systems you may see performance problems due to long-distance connections over public networks.

• Are there hybrid integration plans? It’s unrealistic to think that you’ll move an entire application portfolio to the cloud at once. Treat the cloud as a logical extension of existing systems.

• Have you identified the first adopters? A migration to the cloud can be disruptive so it is important to find people within the organization who are eager and experienced to help define new standards and guide the organization through the transition.

• How will users access the environment?

• Staff training.

• What internal processes have to change in order to capitalize on the new service? Documented procedures for hardware requisition, change management, testing, and deployments may not apply in the same way when using cloud services.

• How will you deploy updated code, data, and configurations to the environment? A new cloud service may or may not work with existing tools.

• Operating plan after the migration.

• Small scale test of the migration plan.

Migration itself.

• How are applications and data being distributed to the cloud? There are several of ways to get applications and data up to a cloud location. For moderately-sized workloads, simple copy commands used over the internet may work. Large data transfers might incur significant bandwidth charges.

• What security controls are in place during transit to the cloud?

• What is being migrated? Is it virtual machines, data, or applications?

• Recreate metadata.

Validation

• Are applications and data reachable? A vital simple test.

• Did all the data make its way into the environment? Through automation, or if required, a manual spot check, verify that both transaction data and reference data was accurately and successfully transferred.

• Can administrative tools access the cloud environment? This should have been performed during the planning phase but it is important to verify this again.

References

Seroter, R. (2015, June 18). The Cloud Migration Checklist. Retrieved August 11, 2016, from InfoQ, https://www.infoq.com/articles/cloud-migration-checklist

Disclaimer

The post The Process of Migrating an Application to the Cloud appeared first on .

Mobile Cloud Computing

Benefits:

• One of the major advantages of cloud computing is that you can access your data from anywhere in the world, using any mobile device that is connected to the Internet.

• Real time data availability: Cloud computing provides access to data in real time whenever and wherever wanted.

• Unlike traditional application models, cloud computing is supported on many different platforms.

• Cloud applications accessed by mobile devices usually have minimal or no upfront cost. Most applications use a pay as you go model.

Disadvantages:

• One major concerns with cloud computing is the security of data as it relates to users and their actions. Mobile users can accidentally provide sensitive information through the network or through using the application. If cloud applications are not properly secured it increases risks related to user actions.

• Another well-known concern with cloud computing is performance. Since applications are hosted on remote servers that are accessed across public networks, this can cause slower responses and slower application speeds.

• An internet connection is required. If an application does not have access to the internet it is often unusable.

Summary

Not everyone can afford to buy and maintain large devices such as laptop or desktop computers, but these same people can often afford a smart phone with a reasonably priced mobile data plan. Major developers such as Microsoft and Adobe already offer suites designed to be run from mobile devices, and directed towards mobile application users.

References

http://www.getcloudservices.com/blog/mobile-cloud-computing-pros-and-cons/.

http://offshorent.com/blog/advantages-of-mobile-cloud-computing

https://themediax.com/what-are-the-advantages-and-disadvantages-of-mobile-cloud-computing/

Disclaimer

The post Mobile Cloud Computing: Benefits & Disadvantages appeared first on .

The Dot Com crash of 2000 and corporate scandals such as Enron highlighted the need for better laws to oversee financial organizations, and also highlighted the need for better corporate governance. IT Governance is the part of corporate governance that includes policies, procedures, and controls that relate to information systems use, performance, Return on Investment (ROI), and risk mitigation

When a company moves services to the cloud it must naturally extend its IT governance to include cloud-based systems and services. Governance includes policies, procedures, and controls that ensure confidence in the accuracy and security of the cloud-based systems, and also ensures the strategic alignment of cloud-based systems with the organizations goals. A key component of the governance process begins with Service Level Agreements (SLA)’s that specify contractual obligations that a cloud vendor must provide and adhere to. One important governance issue that is normally specified in a SLA is limited liability provisions. Fox (2015) states that customers generally want service provider’s liability responsibility to include, among other obligations, coverage for claims arising out of the following:

• Allegations that the cloud services provided by the vendor infringe upon, or violate, the intellectual property or other proprietary rights of any third party.

• Negligence or willful misconduct of the cloud service provider, including its contractors and agents.

• Claims that the cloud service provider including its contractors and agents caused any bodily injury to the customer’s staff, or property damage to the customer’s property.

• A breach of any of the cloud service provider’s data or system security as well as any other customer data privacy obligations.

In contrast, cloud service providers usually try and reduce the scope of their liability towards customers by attempting to negotiate SLA provisions in their favor, for example, trying to limit its liability obligations to customers using a cap on the amount that it is obligated to indemnify the customer for. Customers who agree to caps run the risk of being held accountable for damages that exceed the cap limit even if the damages can be attributed to the provider, provider contractors, and other third-parties that may be associated with the cloud provider (Fox, 2015).

Summary

Regarding the governance of cloud-based systems, it is of utmost importance that customers clearly understand that if their IT systems are hosted on a cloud-based system, their IT governance extends to include those systems. Service Level agreements with cloud providers are a method that organizations can use to extend that governance to cloud-based systems which specifies a level of service that a vendor agrees to provide, and contains provisions that specify items such as liability.

References

Fox, A. (2015, May 07). Common Mistakes Made by Customers and Service Providers when Negotiating Cloud Services Agreements. Retrieved August 10, 2017, from Association of Corporate Counsel, http://www.acc.com/legalresources/quickcounsel/negotiating-cloud-services-agreements.cfm.

Disclaimer

The post The Governance of Cloud-Based Systems appeared first on .

Service-Oriented Architecture (SOA) is a system of solutions characterized in terms of one or more services. Web services as a type of SOA allow programmers to use web services within their programs to perform specific functions.

The following are features and benefits of SOA:

• The Service feature provides the benefits of improved information flow, the ability to safely expose an internal function, and organization flexibility. SOA provides a way to offer software services over the Internet and the world-wide web.

• Service Re-use that has the benefit of lowering software development and management costs.

• Messaging that provides configuration flexibility by providing a way for systems to communicate with each other in a standardized way.

• Message monitoring that provides the benefit of business intelligence, performance measurement, and security attack detection.

• Message control which allows the application of management and security policies.

• Message transformation which is the conversion of data from one format to another through automated field mapping.

• Message security through encryption and cryptographic integrity-check fields.

• Complex event processing. Services can respond to events from other sources. For example, a financial information service might respond to stock-price changes, or a manufacturing production-control service might respond to production process events, such as changes in temperature of the materials being processed.

• Service composition by putting together of a number of simple services to make a more complex one.

• Service discovery which allows a program to discover services at run time instead of having to be pre-programmed. This provides the ability to optimize performance, functionality, and cost, and easier upgrades of systems since upgraded systems can be offered in parallel with older systems.

• Asset wrapping where assets and components are assembled to form a software service. The ability to integrate existing assets provides the benefit of preserving the value of an enterprise’s existing assets, the cost of developing or acquiring replacements is avoided, and there is a smooth migration path from the old architecture to new ones.

• Example: hypervisors that can provide different operating system environments.

• Model driven implementation which provides the ability to develop new functions rapidly.

The disadvantages of SOA are as follows:

• SOA is not suitable for applications with GUI functionalities. These applications require heavy data exchange which makes them much more complex.

• Applications that use asynchronous communication do not work very well with SOA.

• Standalone and short lived application implementations are not well suited for SOA. The development of an SOA for these applications is not worth the time and cost to create them.

SOA Web Services

Programmers use web services to provide specific services across the web for other programs. Web services are intended specifically for other services and not users. Web services typically are used by programmers to create programs to perform tasks that require another company or organization, example; credit card processing for an eCommerce vendor, or for checking a supplier’s inventory. In the first example a customer would order an item from an eCommerce vendor and pay for it using a credit card. The vendors system would have code that would contact the credit card company system to process the details of the transaction then send the results back. The second example, a customer looking for an item wants to know if an item is in stock. The vendor does not physically carry the item but rather processes the order and has it drop shipped directly from the supplier. In this case the vendors system can check with the suppliers system and verify if the item is in stock. In these examples, the vendor is contacting the web services of another company whose system actually processes the request then sends the results back across the internet to the vendor. All the functions and processing is transparent to the users who only see the results in a web page. Web services use what is known as loose coupling to be able to communicate with systems from different organizations. The idea is that with a web service, a program only needs to know the location (URL) of the web service, the web services functions, and parameters, to pass to the web service function. A Web Service Description Language (WDSL) file tells the program requesting web services what functions are available, parameter types, and other information that defines how the systems will communicate with each other. This loose coupling architecture allows systems from different organizations using different architectures and platforms to communicate and use functions provided over the web.

Web Service Roles

Web service architecture can be viewed either as individual roles of each service, or by examining the emerging Web Service Protocol Stack.

There are three major roles within the web service architecture as follows:

• The Service Provider who implements the service and makes it available on the Internet.

• The Requestor who utilizes the service by opening a network connection and sending a request.

• Service Registry which is a centralized directory of services that provides a central place where developers can publish new services or find existing ones.

The Web Service Protocol Stack (WSPS) is still evolving but currently has four layers that are as follows:

• The Service Transport layer which is responsible for transporting messages between applications.

• The XML Messaging layer responsible for encoding messages in a common XML format so that messages can be understood at either end.

• The Service Description layer is responsible for describing the public interface to a specific web service using the previously described WSDL.

• The Service Discovery layer that is responsible for centralizing services into a common registry and providing easy publish/find functionality.

Oracle for example provides an in-depth tutorial that instructs programmers on how to use Oracle XML DB Web services for Service-Oriented Architecture. The tutorial gives an overview and then provides prerequisites, the creation of a binary XML table, reviewing the XML schema in JDeveloper, and using Oracle XML DB Web Services. The tutorial provides code examples for creating network connections, and database protocols and commands to use.

Benefits of Web Services as Black Box

The term “black box” is a module where a software developer does not know or care how processing is performed, but only knows that valid code inputs will produce predictable results. This is another example of the loosely coupled relationship found in web services. The developer can treat the web service as a black box not knowing how the service performs a task, but knows that if they provide valid input to the service that they will get consistent results. This black box functionality provides the benefit of interoperability. The black box web service doesn’t care what creates the valid input, only that it is valid. This means that the input can be created by a variety of programming languages which allows a wide-array of services from different organizations to be able to use the web service. This functionality usually works outside of private networks and provide developers a way to develop non-proprietary solutions. The result is that the services developed are likely to have a longer life-span and offer a better return on investment of the developed service. Web service black box functionality lets developers use their preferred programming languages because of the use standards-based communications methods making web services platform-independent.

Summary

Web services that can be loosely-coupled allow various programs from many different platforms written in many different program languages to use a web service. Programmers do not need to know how the web service actually processes requests; they only need to know how to produce valid code inputs to the service to use it. Web services provide a way for systems to communicate in a standardized way.

References

Oracle XML DB Web Services. (n.d.). Using Oracle XML DB Web Services for Service- Oriented Architecture. Retrieved August 03, 2016, from Oracle.com, http://www.tutorialspoint.com/webservices/web_services_architecture.htm.

MSDN Benefits Web Services. (n.d.). Advantages & Disadvantages of Web Services. Retrieved August 4, 2016, from https://social.msdn.microsoft.com/Forums/en-US/435f43a9-ee17-4700-8c9d-d9c3ba57b5ef/advantages-disadvantages-of-webservices?forum=asmxandxml.

Paul, A. (2011, May 06). Service Oriented Architecture. Retrieved August 4, 2016, from http://www.techyv.com/article/service-oriented-architecture-soa.

The Open Group SOA. (n.d.). Service Oriented Architecture : SOA Features and Benefits. Retrieved August 4, 2016, from https://www.opengroup.org/soa/source-book/soa/soa_features.htm.

Tutorials Point Web Services. (n.d.). Web Services Architecture. Retrieved August 03, 2016 from Tutorials Point, http://www.tutorialspoint.com/webservices/web_services_architecture.htm.

Disclaimer

The post Service-Oriented Architecture (SOA) Web Services appeared first on .

Cloud computing benefits enterprises by reducing costs and allowing them to concentrate on their core business rather than IT and infrastructure related issues. Cloud services provide several security advantages and disadvantages.

Advantages:

• Improved patch management and deployment due to cloud providers using specialized staff.

• Better human-relations reach. Through strong financial positions cloud vendors are able to better screen potential employees for security concerns.

• System redundancy. Cloud solution providers are specialized and as such provide redundant resources.

• Incident response. Client organizations often multi-task personnel, example, the system administrator may also be the organizations security specialist. Cloud providers are able to employ specialist that concentrate in specific areas. Additionally, cloud providers usually use advanced system monitoring and intrusion detection systems.

Disadvantages:

• Location of data. Cloud providers may store data in many different data centers, not all of them may be in the same state, or even the same country. For this reason it is not always clear how the physical location of data will be affected by things such as legal issues or standards compliance.

• Multitenant concerns. Cloud services are often shared between multiple customers. As a result issues such as application errors for one customer might expose private data of other customers.

• Malicious insiders. Even though cloud providers can better screen staff, sometime problems still occur. Malicious insiders can be in a position to compromise an organizations data.

• Contract lock-ins. Organizations have to be very familiar with vendor agreements and clearly understand what they specify.

• Vendor failure. There is always a possibility that a cloud provider fails as a business. An organization could potentially lose data hosted with the failed vendor and have problems recovering it. There is also the potential for loss of revenue while the organization gets systems running elsewhere. The problem is compounded if an organization has to replicate applications from scratch.

Additional security advantages of cloud-based systems include:

• Security through scale. Large scale implementations are usually more cost effective than small scale. This gives cloud vendors the financial resources to implement advanced security measures such as filtering, encryption, and detailed auditing.

• Market demand security. Security has become one of the core factors determining which cloud provider organizations choose. Example, I have selected to evaluate cloud systems for a small hospital as my class project. One of the core requirements is that the providers must be HIPAA compliant and provide HIPAA compliant service agreements. Since this type security is in high demand, I have a large pool of potential vendors to choose from. This large pool creates an environment of competition which reduces costs.

• Security through standardization. As cloud-based services become more popular this leads to more uniform, open and readily available security services that are more resilient against security threats.

• Advantage of concentrated resources. The concentration of resources is potentially dangerous for security. At the same time it can also be used for improving security through other methods. It allows service providers cheaper physical access and security control. The saved resources can be reallocated to improve security.
• Evidence-gathering and Investigation. Cloud computing services offer quick evidence gathering for forensic and investigation purposes.

References

Blake, G. (2010, August 15). The Security Benefits of Cloud Computing. Retrieved July 28, 2016, from http://cloudtweaks.com/2010/08/the-security-benefits-of-cloud-computing/.

Disclaimer

The post Security Advantages & Disadvantages of Cloud-Based Systems appeared first on .

Threats to both cloud-based and on-site solutions should be evaluated with an additional focus directed towards security issues specific to cloud services. Cloud security threats can come from internal or external sources, and can originate as human or software based attacks. Threat agents are as follows; anonymous attackers, malicious service agents, trusted attackers, and malicious insiders. The following is a list of common security threats to cloud-based environments and methods that can be used to mitigate them.

• Traffic eavesdropping. This is a passive attack that can occur when data is being transmitted between cloud services and clients. This include actions such as packet sniffing which examines data in transmission packets, and Man-In-The-Middle (MITM) attacks where an attacker intercepts transmission packets, then can alter messages before forwarding them to their destination.  A MITM attack commonly uses a technique called ARP spoofing. Example, trick user 1 computer into thinking that it is communicating with user 2 computer, and vice versa. To prevent these types of attacks communications between machines should take place over Virtual Private Networks (VPN) when possible. Another mitigation strategy is to ensure communications use Secure Socket Layer (SSL) protocols. Example, web traffic using HTTPS instead of HTTP.

• Denial of Service. Denial of Service (DoS), and Distributed Denial of Services (DDoS) occur when an attacker uses one or many different computers to send a bombardment of message traffic to a system to try and overwhelm it’s resources and take them out of use. Defending against DoS and DDoS attacks is difficult and common strategies to mitigate them usually apply only after the attack has started and caused problems. The best defense against these types of attacks are specialized network firewalls designed to track and recognize DoS attacks, and the use of a number of reverse proxy mechanisms. Reverse proxies determine if incoming traffic is legitimate and allows or drops the incoming packets accordingly.

• Insufficient Authorization. This attack occurs when access or unauthorized levels of access are granted to an attacker in error. This can occur from weak authentication vulnerabilities related to weak passwords or shared accounts. The best protection against this threat includes both logical and physical security controls. Logical controls include administrative policies such as password policies, use firewalls and keep them updated, and auditing of systems. Physical controls include keeping system equipment in locked spaces with controlled access.

• Virtualization Attacks. Since cloud service providers often grant customers administrative rights to virtualized resources, this means they might also be used to attack underlying IT resources. This attack is commonly known as hyperjacking and it is directed towards the virtualization hypervisor software layer where an attacker will try and get control over the hypervisor and gain access to the underlying hardware. Controls such as separate Virtual Local Area Network (VLAN) connections for each service, and the use of separate management networks are the most effective way to mitigate hyperjacking attacks. Example, keep web facing traffic separate from internal traffic, and keep management interfaces on networks separate from all other services.

• Overlapping Trust Boundaries. Since cloud services often share resources among many different customers great care must be taken in establishing boundaries between them. Attackers can target shared resources with the intention of compromising other customers, or the underlying infrastructure as a way to get access to other customers resources. This attack can also include guest-hopping. This is an attack where an attacker might have access to one Operating System (OS), and use that access to try and compromise a different OS within the same cloud system. Establishing secondary private VLANs for each entity provides traffic isolation and is the ideal method for mitigating this threat.

• Malicious Employees. Staff such as software developers often has extensive access to systems which can be misused by disgruntled or terminated employees. Moving services to the cloud reduces this risk with local employees, but cloud service staff still require a stringent screening. Malicious insider threats can be mitigated by using access controls, policies and enforcement, and layered security. Examples; Access controls should be put in place so employees and third-parties can only access specified information and systems. A policy that would explain that when employees and contractors fail to comply, they could face termination of their employment or contractual relationship and lawsuits depending on how the information was misused. Taken together these methods form layered security.

• SQL Injection. This type of attack is directed towards trying to compromise or gain control over database servers and databases. It commonly takes advantage of form type data being sent from a client such as a web browser to an application database server. The attacker alters “injects” their own SQL commands into the data being sent to the server in order to get control of the server, or force the server to divulge data within the database. Controls to mitigate SQL injection threats include; use parameterized queries, use stored procedures, include code that escapes all user supplied input, enforce the concept of least privilege on user access, and the use of white lists to validate user inputs.

• Compromised Interfaces and API’s. APIs and interfaces are commonly the most exposed part of a system because they’re usually accessible from the open Internet. The use of separate VLAN’s for API and management traffic is the most effective method of mitigating this threat.

• Data Loss. Cloud providers generally provide multiple layers of redundancy and extensive data replication. Although a rare occurrence, data loss due to provider error or system problems can still occur. Cloud providers recommend distributing data and applications across multiple zones as additional protection against this threat.

• Loosely defined service contracts. Sometimes organizations do not fully understanding cloud provider contracts and environments and encounter many commercial, financial, technical, legal, and compliance risks. The Cloud Security Alliance (CSA) states that organizations must perform extensive due diligence to understand the risks they assume when they subscribe to a cloud service as the primary mitigation strategy for this risk.

Conclusions

Cloud-based services are exposed to many of the same threats that on-site services are. To protect against these threats, the use of established and proven mitigation strategies should be applied. It is important to recognize though that cloud-based environments are subject to additional threats such as virtualization attacks that do require additional assessment and controls to mitigate the additional security risks. If the common and specific security risks are both properly mitigated, cloud-based services should be just as safe to use as on-site services.

References

Berry-Tayman, L. (2015, January 16). 3 Ways to Protect Your Company Against Malicious Insiders. Retrieved July 28, 2016, from http://idt911.com/education/blog/3-ways-to-protect-your-company-against-malicious-insiders.

Burns, S. (2015, August 05). Virtualization Security Tips: Preventing Hyper Jumping. Retrieved July 28, 2016, from http://www.tomsitpro.com/articles/virtual-security-tips-hyper-jumping,2-776.html.

CloudPatterns. (n.d.). Data Link and Network Layer Trust Boundary Isolation. Retrieved July 28, 2016, from http://cloudpatterns.org/candidate_patterns/data_link_and_network_layer_trust_boundary_isolation.

Hargrave, V. (2012, November 28). What Are Man-in-the-Middle Attacks and How Can I Protect Myself From Them? Retrieved July 28, 2016, from http://blog.trendmicro.com/what-are-man-in-the-middle-attacks-and-how-can-i-protect-myself-from-them/.

OWASP Prevent SQL Injection. (2016, May 25). SQL Injection Prevention Cheat Sheet. Retrieved July 28, 2016, from https://www.owasp.org/index.php/SQL_Injection_Prevention_Cheat_Sheet.

Rashid, F. (2016, March 11). The dirty dozen: 12 cloud security threats. Retrieved July 27, 2016, from http://www.infoworld.com/article/3041078/security/the-dirty-dozen-12-cloud-security-threats.html.

Schultz, G. (2006, August 03). Top 10 ways to secure your stored data. Retrieved July 28, 2016, from http://www.computerworld.com/article/2546352/data-center/top-10-ways-to-secure-your-stored-data.html.

Weiss, A. (2012, July 02). How to Prevent DoS Attacks. Retrieved July 28, 2016, from http://www.esecurityplanet.com/network-security/how-to-prevent-dos-attacks.html.

Disclaimer

The post Security Threats to Cloud–Based Systems appeared first on .

Virtualization of IT resources has become a popular the past few years but has been around in some form for many years. Example;  thirty years ago IBM had virtual operating systems that allowed multiple copies of an operating system to run simultaneously on mainframe computers. Virtualization is the use of hardware and software to create environments that are perceived as one or more different entities.  Example; virtualization can make one server appear as many different machines. Virtualization can create an appearance of multiple instances of Operating Systems (OS)’s, network resources, and storage that are actually being run from a single physical machine. Virtualization is method that converts physical IT resources into virtual resources.

Server Virtualization

Server virtualization makes one server appear as many different servers. Virtual servers can support multiple OS’s of the same or different type. Virtual servers make use of a software layer called a hypervisor. OS’s are installed on the hypervisor software layer instead of directly on the physical hardware. The hypervisor manages each OS’s system execution and resources. Virtual servers provide the following benefits for businesses; they consume less power, have a smaller physical footprint, generate less heat costing less to cool, and they are easier to install and configure. Virtual servers also use physical resources more efficiently particularly CPU utilization. Load balancing and scaling allow virtual servers to be created as loads increase. In contrast when loads are lighter computing resources can be used for other operations reducing waste. Microsoft Hyper-V for example allows an organization to create and manage a virtualized computing environment by using virtualization technology that is built in to Windows Server. Hyper-V allows an organization to establish or expand cloud services, better utilize hardware, improve business continuity, establish or expand a virtual desktop infrastructure (VDI), and use virtual machines to reproduce different computing environments without the need for acquiring or maintaining all the hardware you would otherwise need.

Storage Virtualization

Data virtualization separates physical data storage from logical presentation that users and applications can see. It hides the physical details of the actual storage device. Virtual storage can span many different drives and devices through the use of logical drives which provide the usable space that users and application can see and use. Virtual storage allows businesses to scale storage demand as needed, pay only for resources they need and as they go, transparent backup and data replication, support most common OS’s, users can access storage from most devices anywhere they have a network or internet connection, and it allows for easy file and folder sharing. Example; Dropbox provides software that creates a local virtual drive which will synchronize with cloud storage. This model allows users and application to interact with what appears to be a standard file folder. This type of virtualization provides business users a way to access their files from the Dropbox drive from any device that has an internet connection, automatically replicates their data for protection, and provides a way for users to share files and collaborate with others.

Network Virtualization

Physical networks can be segmented into logical networks such as Virtual Local Area Networks (VLAN), and Virtual Private Networks (VPN). VLANS and VPN’s allow users a way to connect to resources remotely through the creation of a logical secure network. Example; with this model a remote user can connect to datacenter resources remotely through the internet using a VPN connection. The connection itself is created across the internet, host, and user networks, but to the user and the hosted resource, it appears that they are connected via a Local Area Network (LAN). VPN’s allow organizations a way to  establish secure encrypted communications between remote users and resources, simplify communications protocols which lowers costs, scalability, and provide a method for remote employees to access company resources securely and reliably. VLANS allow organizations to segment their physical networks into logical networks. Example, computers in the business office of an organizations connected together on a separate VLAN. VLAN’s benefit organizations by increasing network performance, simplify network management, and simplify and increase network security.  The ability to create VPN’s and VLAN’s is limited to network equipment capable of creating virtual network environments. Example, Cisco offers and extensive line of enterprise networking equipment capable of creating virtual networks for customers that range from small home and office users, to large scale data centers.

Power Virtualization

Virtual Uninterruptible Power Supplies (UPS) allow organization supply power where it is needed, and reduce or power down equipment that is not in use. In combination with UPS management software, organizations can use virtual UPS to automatically scale up or down, or redirect power to mechanisms such as virtual machines as they are created or shut down. Virtual UPS solutions such as Critical Power are designed to work with most major VM vendor applications.

Virtual Desktops

Desktop virtualization is a way to run multiple OS’s at the same time on the same machine. This has several advantages to an organization to include; the ability to run, and switch between, separate OS’s quickly, the ability to run different type OS’s from the same machine, eliminates the need for duplicate hardware, and reduces power consumption. An example of how this can benefit an organization would be a software tester. Running test applications inside virtual desktops eliminates the need to switch between physical machines. Another type of virtual desktop is Virtual Desktop Infrastructure (VDI). VDI allows a computer to pull its OS from the network when it powers up. The benefits of VDI to a business include; multiple users can use the same OS image. This reduces OS administration since updates only need to be applied to a few images instead of several separate machines. Users can choose different OS’s to use for different purposes, example, use Windows 7 for general use, but switch to Windows XP to use a legacy application that will not run in Windows 7. Reduced hardware cost since much of the storage and computing requirements are handled by the OS server. Reduce the need to troubleshoot diverse problems associated with several physical machines. Example, an OS problem can be trouble shot and corrected at the server or in the image instead of having to perform the same operation on every machine in the facility.

Summary

The following are general advantages and disadvantages of virtualization:

Advantages;

• Increased device utilization, particularly CPU utilization.
• Decreased physical device footprint.
• Decreased power consumption.
• Simplified OS and application administration.
• Simplified provisioning and patch management.
• Ease of scalability.
• Increased user access to resources.
• Better flexibility in managing multiple different OS’s.
• More efficient management of software licenses.
• Better utilization reporting leading to better capacity planning.
• Improved disaster recovery and business continuity.

Disadvantages;

• Additional staff training may be required to understand the use of virtualization technology.
• Some applications are not well suited for virtualization. Some applications require specific hardware or drivers.
• Virtualization adds overhead to computing resources making some applications slower.
• Applications that depend on advanced graphics such as 3D modeling software, the required drivers can slow applications noticeably.

References

Brooke, B. (2014, December 31). What is VPN (virtual private network) and what are its advantages and disadvantages? Retrieved July 20, 2016, from https://www.quora.com/What-is-VPN-virtual-private-network-and-what-are-its-advantages-and-disadvantages.

Cisco Products. (n.d.). Cisco Products and Services. Retrieved July 20, 2016, from http://www.cisco.com/c/en_in/products/index.html.

Critical Power. (n.d.). Virtualization and UPS Power Management. Retrieved July 20, 2016, from http://www.criticalpowersupplies.co.uk/virtualization-virtual-power-management.

Dropbox Sharing. (n.d.). Sharing files and folders. Retrieved July 20, 2016, from https://www.dropbox.com/help/topics/sharing_files_and_folders.

Harbaugh, L. (2012, March 22). The Pros and Cons of Using Virtual Desktop Infrastructure. Retrieved July 20, 2016, from http://www.pcworld.com/article/252314/the_pros_and_cons_of_using_virtual_desktop_infrastructure.html.

Mahaney, B. (n.d.). VLAN – Benefits and Limitations. Retrieved July 20, 2016, from http://www.people.eku.edu/mahaneyb/CISStudentClub/1007/index.htm.

TechNet Hyper-V Overview. (2016, May 31). Hyper-V Overview. Retrieved July 20, 2016, from https://technet.microsoft.com/library/hh831531.aspx.

Disclaimer

The post Virtualization of IT Resources. Advantages & Disadvantages appeared first on .

IDaaS, Cloud Data Storage, and Cloud Collaboration

Revised July 03, 2023

The emergence of wide-spread Internet access combined with the development of cloud-based infrastructure, platform, and Software as a Service (SaaS) has created an environment where organizations and everyday users have access to vast amounts of computing resources and applications at the click of a button. In addition to Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and SaaS, cloud computing also encompasses services such as Identification as a Service (IDaaS), Data Storage in the Cloud, and Collaboration in the Cloud.

Identification as a Service (IDaaS):

IDaaS is a service that provides cloud-based ID management, simplifying user identification and authentication processes.

Advantages of IDaaS:

• Fewer accounts and passwords for users to manage
• Reduced password fatigue
• Time savings by logging into multiple systems with a single sign-on
• Centralized administration of user accounts

Disadvantages of IDaaS:

• Single point of failure if the authentication server goes down
• Single breach point if a user account is compromised
• Dependence on reliable network connectivity
• Integration challenges with existing systems

Data Storage in the Cloud:

Cloud storage enables users to access their data from any internet-connected device through web browsers, client software, or APIs.

Advantages of cloud-based storage:

• Scalability to accommodate changing storage needs
• Cost-effectiveness by paying only for the storage used
• Data backup, redundancy, and replication provided by cloud storage providers
• Ease of access through web-based interfaces and mapped logical drives

Disadvantages of cloud-based storage:

• Relatively slower speed compared to local drives
• Concerns about data security and privacy
• Risk of data abandonment if users abandon their cloud-based accounts
• Dependence on reliable internet connectivity

Collaboration in the Cloud:

Cloud-based collaboration tools facilitate remote collaboration and eliminate the need for physical interaction.

Benefits of cloud collaboration:

• Reduced travel costs and time for business staff
• Savings on meeting space expenses
• Increased productivity by eliminating the need for travel
• Expanded opportunities for participation in meetings and training
• Efficient virtual meetings compared to face-to-face meetings

Summary

IDaaS simplifies user login management through single sign-on, despite potential risks. Cloud data storage offers scalability, cost-efficiency, and easy accessibility. Cloud collaboration tools enhance remote collaboration, saving time and costs associated with physical interaction.

References

Palmer, G. Security Notes (2017-2023)

https://www.sunflower-cissp.com/glossary/cissp/2976/identity-as-a-service-or-identity-and-access-as-a-service-idaas

https://www.techadvisor.com/test-centre/internet/best-cloud-storage-3614269/.

https://www.neustar.biz/blog/what-is-single-sign-on-deployment-pros-cons.

https://msdn.microsoft.com/en-us/library/dd586632(v=office.11).aspx.

http://smallbusiness.chron.com/benefits-virtual-meetings-71540.html

Additional Articles

Understanding Business Continuity Planning

IT & Security Framework and Policy Development Team

Virtualization of IT Resources. Advantages & Disadvantages

Exploring the Implications of Artificial Intelligence

Artificial Intelligence in Texas Higher Education: Ethical Considerations, Privacy, and Security

Note: This article has been drafted and improved with the assistance of AI, incorporating ChatGPT suggestions and revisions to enhance clarity and coherence. The original research, decision-making, and final content selection were performed by a human author.

Disclaimer

Terms and Conditions of Use

The post IDaaS, Cloud Data Storage, and Cloud Collaboration appeared first on .

Cloud Computing Models -SaaS, PaaS, IaaS

Revised July 03, 2023

Explore the different cloud computing models – Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS) – and discover their advantages, disadvantages, and the impact they have on organizations.

Software as a Service (SaaS)

SaaS is a cloud computing model that allows users to access software, programs, and data from the cloud. Users can access SaaS services through a web browser, eliminating the need for in-house hosted applications and infrastructure. SaaS applications are typically multi-tenant solutions, where multiple organizations share the same resources, including database resources.

Advantages of SaaS:

1. Reduction or elimination of the need for on-site data centers.
2. Elimination of application administration responsibilities.
3. Pay-per-user basis for on-demand software usage.
4. Scalability of applications, storage, and processing to accommodate higher demand.
5. Improved disaster recovery and business continuity with data stored locally and in the cloud.

Disadvantages of SaaS:

1. Security concerns as sensitive data is entrusted to a third-party provider.
2. Potential service outages that need to be addressed in Service Level Agreements (SLAs).
3. Compliance with specific business and security laws may be required.
4. Some applications may not be well-suited for running in a browser.
5. Availability of the SaaS application depends on reliable network connectivity.
6. Integration with existing and legacy applications may be challenging, relying on APIs and interfaces provided by the cloud vendor.

Platform as a Service (PaaS)

PaaS is a cloud computing model that provides developers with software and hardware resources to build and deploy their own applications. With PaaS, organizations can eliminate the need to purchase and maintain hardware, operating systems, and databases. PaaS offers Windows-based and Linux-based solutions for application development.

Advantages of PaaS:

1. Lower cost of ownership by eliminating the need for server, power, and storage hardware.
2. Reduced administrative overhead as maintenance and administration tasks are handled by the cloud vendor.
3. Automatic updates of system software and patches by the cloud vendor.
4. Alignment of business and IT goals, allowing IT staff to focus on solutions instead of server maintenance.
5. Scalability of cloud solutions to match demand, resulting in cost optimization.

Disadvantages of PaaS:

1. Data security concerns for organizations reluctant to move storage off-site.
2. Integration challenges between new cloud solutions and legacy software.
3. Risk of service agreement breaches by the PaaS provider, potentially making application migration difficult.

Infrastructure as a Service (IaaS)

IaaS is a cloud computing model where the cloud vendor provides computing hardware and resources for customers to install and manage their own systems. In this model, customers have control over the operating systems and management of their environment through a web-based application. IaaS allows organizations to deploy their own data centers without the need to purchase and maintain hardware, providing control over system management and security. Customers only pay for the resources they use.

Advantages of IaaS:

1. Elimination of data center hardware and maintenance staff.
2. Scalability to meet changing resource needs.
3. Lower hardware costs by utilizing cloud infrastructure.
4. Pay-as-you-go billing model for cost optimization.
5. Reduced IT staff requirements with easy setup of test environments using virtualization.
6. Retention of full system administration and management control.

Disadvantages of IaaS:

1. Higher cost compared to other cloud models due to tangible resource usage.
2. Customer responsibility for configuring load balancing, fail-over, and backups.
3. Customer management of virtual machines (VMs) required.
4. Limited control over the geographic location of data.

In summary, cloud computing offers different models (SaaS, PaaS, IaaS) to meet diverse organizational needs. Each model comes with its own set of advantages and disadvantages, allowing organizations to choose the most suitable option based on their requirements.

References

https://aws.amazon.com/types-of-cloud-computing/

https://www.doi.gov/cloud/service

http://aiasecurity.com/2015/09/10/advantages-and-disadvantages-of-saaspaas-and-iaas/.

http://www.zdnet.com/article/saas-pros-cons-and-leading-vendors/.

http://www.opengroup.org/cloud/cloud/cloud_for_business/why.htm.

Additional Articles

Domain Name System (DNS) Security Threats

Virtual Private Network (VPN) Security and Monitoring Controls

Bastion Host Overview

Exploring the Implications of Artificial Intelligence

Artificial Intelligence in Texas Higher Education: Ethical Considerations, Privacy, and Security

Note: This article has been drafted and improved with the assistance of AI, incorporating ChatGPT suggestions and revisions to enhance clarity and coherence. The original research, decision-making, and final content selection were performed by a human author.

Disclaimer

Terms and Conditions of Use

The post Cloud Computing Models -SaaS, PaaS, IaaS appeared first on .