Cloud computing has many benefits, including greater flexibility, infrastructure cost savings, and enhanced computing performance. However, the cloud presents new security challenges that organizations need to address. A failure to implement security controls and adhere to solid data governance practices could result in a breach.

Preventing Worst Case Scenarios

Consider this scenario, a company begins their migration by getting excited about the possibilities the cloud can provide to their applications. They task a few of infrastructure engineers to work with the developers to start a proof of concept. The migration team modifies the settings and access controls to ensure the application is works.

The migration team, excited with the success of their proof of concept, adds in a few more application features and submits the change ticket for the applications to be moved into production. The migration then grids to a halt. An assessment comes back saying the cloud environment has security holes so large you could drive a truck through them. The migration team discusses how to adjust the cloud application to meet compliance requirements, only to find out they need to completely rebuild the entire cloud environment. The organization executives pull the funding on the now failed project and any future discussions about the cloud are met with frustration.

One of the benefits of cloud computing is that you won’t have to log into every virtual machine to maintain it; you can use code

Sadly, this scenario isn’t rare. However, there are things you can do to make sure this scenario doesn’t happen to you.

Four Ways To Improve Your Cloud Security

1. Understand how the cloud changes your paradigms

While cloud security and in-house security have many similarities, in some ways, they are quite different, which requires a paradigm shift on the part of the organization:

  • Use automation to make your life easier. One of the benefits of cloud computing is that you won’t have to log into every virtual machine to maintain it; you can use code. For example, AWS has several features to automate some security functions, including security groups, which act as firewalls for EC2 instances; network access control lists (ACLs), which act as firewalls for associated subnets; and flow logs, which capture information about the IP traffic going to and from the network interfaces in your virtual private cloud. 

  • Be aware of where your cloud provider’s responsibilities begin and end. While there are some differences depending on your specific setup (private, public, or SaaS), in general, cloud providers are responsible for security of the cloud, and their customers are responsible for security in the cloud. This means that your cloud provider must secure the cloud infrastructure, but your organization is responsible for the applications, data, and services you place within your cloud environment. Remember, if there is a breach, your organization is the one who is ultimately responsible.
How to plan a cloud migration security policy
Written cloud security and data governance policies must be established before the migration commences

2. Create your governance and project plans before you start

  • Define limits on what data classification types you will allow in the cloud. Written cloud security and data governance policies must be established before the migration commences. These policies should clearly define which information and data classifications are to be stored in the cloud, where they belong in the cloud hierarchy, who should have access to each section, and what level of access they should have.

  • Create and follow a project plan. Successful cloud migrations are never built on luck and you should develop a project plan for your migration, just as you would for any other large project. Additionally, be realistic about your scope as cloud migration projects often fail because organizations often try to build too much in their scope. Conversely, if you have not defined what will be in-scope for your cloud environment, then it’s likely you will have some poor architecture design elements that could be easily exploited by hackers. 

  • Stick with your plan, and don’t “chase the shiny.” There always seems to be a new “silver bullet” tool hitting the market that promises to solve all your tech problems, security and otherwise, overnight. Resist the urge to deviate from your cloud migration plan in favor of these tools. They almost never turn out to be as magical as they promise, and you’ll end up wasting money and time.

3. Use your past to change your organization’s future

Cloud migration is a long, tedious process, but it’s also a great opportunity for your company to assess all the old issues you’ve been gritting your teeth and dealing with, and start over with a clean slate.

Many organisations are appointing “home-grown” administrators who have
little or no training in cloud computing or cloud security

Start by picking a specific target, such as a single application or system. Then, review your asset and application inventory, along with your old architecture map. Identify all interdependencies and determine how they will work in the cloud environment – or if they even make sense anymore. Don’t repeat your in-house mistakes in the cloud. 

Update your disaster recovery and security incident response plan. Since your data environment is fundamentally changing, your disaster recovery and security response plan needs to change, too. 

Define who will support and maintain your cloud environment once it’s in production. You must also decide which team within your organization will manage your cloud security during migration and going forward. This needs to be done by someone with adequate security experience; it should not simply be assigned to the help desk.

4. Don’t hesitate to obtain expert help

The biggest contributor to the outbreak of AWS breaches is a lack of expertise. AWS and other cloud environments are very powerful. They are also intricate and highly complex, yet many organizations are appointing “home-grown” administrators who – while they may be very well-versed in in-house data security – have little or no training in cloud computing or cloud security.

If you do not have sufficient cloud expertise in-house, it’s imperative that you partner with a managed security services provider (MSSP) with deep experience in your chosen cloud environment. In addition to ensuring that your environment is configured properly and securely, an MSSP can help you develop a realistic migration plan; address governance, risk, and compliance issues; identify in-house data governance issues and ensure that the same mistakes are not replicated in the cloud; and provide cyber security and incident response services going forward.

Share with LinkedIn Share with Twitter Share with Facebook Share with Facebook
Download PDF version Download PDF version

Author profile

Andy Jordan Special Project Lead, Mosaic451

In case you missed it

Water Plant Attack Emphasizes Cyber’s Impact On Physical Security
Water Plant Attack Emphasizes Cyber’s Impact On Physical Security

At an Oldsmar, Fla., water treatment facility on Feb. 5, an operator watched a computer screen as someone remotely accessed the system monitoring the water supply and increased the amount of sodium hydroxide from 100 parts per million to 11,100 parts per million. The chemical, also known as lye, is used in small concentrations to control acidity in the water. In larger concentrations, the compound is poisonous – the same corrosive chemical used to eat away at clogged drains. The impact of cybersecurity attacks The incident is the latest example of how cybersecurity attacks can translate into real-world, physical security consequences – even deadly ones.Cybersecurity attacks on small municipal water systems have been a concern among security professionals for years. The computer system was set up to allow remote access only to authorized users. The source of the unauthorized access is unknown. However, the attacker was only in the system for 3 to 5 minutes, and an operator corrected the concentration back to 100 parts per million soon after. It would have taken a day or more for contaminated water to enter the system. In the end, the city’s water supply was not affected. There were other safeguards in place that would have prevented contaminated water from entering the city’s water supply, which serves around 15,000 residents. The remote access used for the attack was disabled pending an investigation by the FBI, Secret Service and Pinellas County Sheriff’s Office. On Feb. 2, a compilation of breached usernames and passwords, known as COMB for “Compilation of Many Breaches,” was leaked online. COMB contains 3.2 billion unique email/password pairs. It was later discovered that the breach included the credentials for the Oldsmar water plant. Water plant attacks feared for years Cybersecurity attacks on small municipal water systems have been a concern among security professionals for years. Florida’s Sen. Marco Rubio tweeted that the attempt to poison the water supply should be treated as a “matter of national security.” “The incident at the Oldsmar water treatment plant is a reminder that our nation’s critical infrastructure is continually at risk; not only from nation-state attackers, but also from malicious actors with unknown motives and goals,” comments Mieng Lim, VP of Product Management at Digital Defense Inc., a provider of vulnerability management and threat assessment solutions.The attack on Oldsmar’s water treatment system shows how critical national infrastructure is increasingly becoming a target for hackers as organizations bring systems online “Our dependency on critical infrastructure – power grids, utilities, water supplies, communications, financial services, emergency services, etc. – on a daily basis emphasizes the need to ensure the systems are defended against any adversary,” Mieng Lim adds. “Proactive security measures are crucial to safeguard critical infrastructure systems when perimeter defenses have been compromised or circumvented. We have to get back to the basics – re-evaluate and rebuild security protections from the ground up.” "This event reinforces the increasing need to authenticate not only users, but the devices and machine identities that are authorized to connect to an organization's network,” adds Chris Hickman, Chief Security Officer at digital identity security vendor Keyfactor. “If your only line of protection is user authentication, it will be compromised. It's not necessarily about who connects to the system, but what that user can access once they're inside. "If the network could have authenticated the validity of the device connecting to the network, the connection would have failed because hackers rarely have possession of authorized devices. This and other cases of hijacked user credentials can be limited or mitigated if devices are issued strong, crypto-derived, unique credentials like a digital certificate. In this case, it looks like the network had trust in the user credential but not in the validity of the device itself. Unfortunately, this kind of scenario is what can happen when zero trust is your end state, not your beginning point." “The attack on Oldsmar’s water treatment system shows how critical national infrastructure is increasingly becoming a target for hackers as organizations bring systems online for the first time as part of digital transformation projects,” says Gareth Williams, Vice President - Secure Communications & Information Systems, Thales UK. “While the move towards greater automation and connected switches and control systems brings unprecedented opportunities, it is not without risk, as anything that is brought online immediately becomes a target to be hacked.” Operational technology to mitigate attacks Williams advises organizations to approach Operational Technology as its own entity and put in place procedures that mitigate against the impact of an attack that could ultimately cost lives. This means understanding what is connected, who has access to it and what else might be at risk should that system be compromised, he says. “Once that is established, they can secure access through protocols like access management and fail-safe systems.”  “The cyberattack against the water supply in Oldsmar should come as a wakeup call,” says Saryu Nayyar, CEO, Gurucul.  “Cybersecurity professionals have been talking about infrastructure vulnerabilities for years, detailing the potential for attacks like this, and this is a near perfect example of what we have been warning about,” she says.  Although this attack was not successful, there is little doubt a skilled attacker could execute a similar infrastructure attack with more destructive results, says Nayyar. Organizations tasked with operating and protecting critical public infrastructure must assume the worst and take more serious measures to protect their environments, she advises. Fortunately, there were backup systems in place in Oldsmar. What could have been a tragedy instead became a cautionary tale. Both physical security and cybersecurity professionals should pay attention.

What Are The Positive And Negative Effects Of COVID-19 To Security?
What Are The Positive And Negative Effects Of COVID-19 To Security?

The COVID-19 global pandemic had a life-changing impact on all of us in 2020, including a multi-faceted jolt on the physical security industry. With the benefit of hindsight, we can now see more clearly the exact nature and extent of that impact. And it’s not over yet: The pandemic will continue to be top-of-mind in 2021. We asked this week’s Expert Panel Roundtable: What have been the positive and negative effects of Covid-19 on the physical security industry in 2020? What impact will it have on 2021?

Expert Roundup: Healthy Buildings, Blockchain, AI, Skilled Workers, And More
Expert Roundup: Healthy Buildings, Blockchain, AI, Skilled Workers, And More

Our Expert Panel Roundtable is an opinionated group. However, for a variety of reasons, we are sometimes guilty of not publishing their musings in a timely manner. At the end of 2020, we came across several interesting comments among those that were previously unpublished. Following is a catch-all collection of those responses, addressing some of the most current and important issues in the security marketplace in 2021.