Skip to main content

Cloud Security - is it very different

Many a times it is difficult to find the reasons as to why a cloud application security is very different than any other approaches. A cloud is very similar to a private hosted data center sans the physical security aspects of it.

The various components that build up the system can very well be built into the cloud. IdMs, RBACs, Key or Token based Systems. It is only a matter of time where in the Cloud Providers will partner with all these providers to get the economies of scale.

The approach to the cloud model is not very much different than to a colocation or a private cloud. The Hypervisor is another component that needs to be managed as part of the Vulnerability Management of resources. What is applicable in a traditional model is still applicable to the cloud and in addition the concerns of the cloud. A few questions to answer.. It is more a logical data flow diagram which can help you identify the type of data on move and at rest and the necessary logical controls therefore required.

1. Where exactly is your Cloud Server?

2. How is the data stored and where?

3. Do you push the incidence of protection to the Cloud provider for a fee? It is like insurance, have the clauses built in to address your concerns. Many a times as a cloud provider we have found them to bring to the table a set of services that are very expensive to have internally. For example: Regular Automated VM Scanning,  HIDS and IDS Services, Log Consolidation etc.

4. Have controls to ensure that your devices are protected logically. Physical protection is to be with the provided (The reason to have SAS 70 and other similar arrangements)

5. Encryption of the Operating System and all files : Encryption is an option,

Whole OS encryption vs Just the data at rest? however, do you share it with your provider? Sometimes the benefits of the cloud are lost if you do not leverage the management services offered by the cloud provider. Encryption however can become a major hurdle as it eats lots of processing power!!!!  More muscle needed , but with the easy expansion of resources based on demand..this can be addressed.

The advantages

- The problem of addressing Security Issues on the Host System is pushed to the provider?

- Identification of resources that can be moved to the cloud? What are the criteria for their selection and movement?

Simply stated the advantages of the cloud far outweighs it's disadvantages. A proper approach with encryption and logical controls can achieve the given objective. The objective however, should not be technical but more driven by business and the cloud can be leveraged effectively in such situations. The major advantages being

a. The IT infrastructure can get rid of Capital Costs - It is just operational costs.
b. IT becomes an operational cost and helps to improve the bottom line at least on paper. No dead NPA.
c. Resource reduction , problems related to building infrastructure redundancies - Gone.
d. Volume discounts - Some of the services offered are available at rates that are not even remotely possible in a private enterprise. (IDS Services, Log Consolidation etc) - Economies of Scale.

The major advantage is the human resources needed to run the systems. The shared model helps a lot in leveraging the common resource pool more effectively and efficiently.

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....