Skip to main content

Cloud Security - The Way Ahead

Cloud Security is of two types. The Public Cloud Security and the Private Club Security. Both the options need a set of controls that are different and needs to be addressed separately.

The Private Cloud Security is just an extension of the security parameters that are taken into consideration when we handle physical servers. Each device as in every other case are to be addressed as an individual entity and the process and procedures that are applicable to a physical box are applicable to the virtual ones.

However, there is one major difference, the host machines, Each host machines may host different servers and services on a single physical device. Considering this , it would be wise on the security team to ensure that they are grouped based on the criticality of the applications hosted.

There are a few pros and cons of such an exercise. The first major advantage is that you ensure by grouping sensitive servers to a single physical host and take all necessary precaution to  protect the systems as well as logical separation that id due. However, it opens another can of worms, a single compromise on the host systems makes all the systems (all critical ones) vulnerable and therefore increasing the surface area of attack of sensitive systems.

Again the argument would be since all the host systems are invisible it makes it that more difficult for them to be weakened and therefore offers that level of security. The controls in place in addition, physical and logical are monitored more intently that any breach or weakness is detected immediately and remediation steps are taken.

What about encrypting the guest systems so that the host systems administrators cannot see what is on the guests? The control set available is large and an effective strategy evolved to ensure that maximum benefits can be realized from virtualization initiatives.

Comments

Popular posts from this blog

Malware Damage - It is real and you need to be ready ...

  Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...

CIO Questions answered - Your comments welcome - The reflections of the inner self

Briefly describe the typical size and organization of an IT team that you have managed. Include the division of responsibilities, how you track progress, etc. My experience ranges from me working independently, mainly to maintain my independence when I perform audits to managing a team of more than 25 - 100 consultants in various roles. I have handled multiple projects simultaneously where we have multiple consultants (typically from five to ten) working on multiple projects. We have used a set of tools to specifically monitor progress as well as the milestones. The projects involved were simple roll out of products (Microsoft Active Directory Domain Builds, Log Consolidation, Vulnerability Management) in line with product specifications to complex integration of systems that involves building multiple SoA interfaces for healthcare applications. For a successful project there needs to be proper delegation, personally I believe a person can deliver if he is not micromanaged, identifyi...

A Roadmap to move from Cloud to In premise - The reverse migration -- Is Cloudflation at myth?

 Cloudflation as a term is being used and talks on the spiralling cost of cloud bills for an organization. The easily available and provisioning options leads to workloads that run for no reasons, orphaned accounts and a gamut of costs that are accrued by multiple departments without much of an oversight. There is a trend to reduce the workloads and have a semblance of order. It is imperative that we have plans that helps to reverse the migration to cloud and bring back some of the workloads that might work cheaper to run local. Is there a roadmap to achieve this goal? A few pointers in this direction A roadmap for moving from the cloud to in-premise computing should include the following steps: Assess current workloads: Assess the current workloads that are running on the cloud and determine which workloads would be most suitable for in-premise computing. Identify in-premise infrastructure: Identify the in-premise infrastructure that will be needed to run the identified workloads....