Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

7/9/2019
02:00 PM
Derrick Johnson
Derrick Johnson
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Cloud Security and Risk Mitigation

Just because your data isn't on-premises doesn't mean you're not responsible for security.

The cloud certainly offers advantages, but as with any large-scale deployment, the cloud can also offer unforeseen challenges. The concept of the cloud just being "someone else's data center" makes me cringe because it assumes you're relinquishing security responsibility because "someone else will take care of it."

Yes, cloud systems, networks, and applications are not physically located within your control, but security responsibility and risk mitigation are. Cloud infrastructure providers allow a great deal of control in terms of how you set up that environment, what you put there, how you protect your data, and how you monitor that environment. Managing risk throughout that environment and providing alignment with your existing security framework is what's most important. 

Privacy and Risk
With the EU's General Data Protection Regulation and similar policies in some US states (Arizona, Colorado, California, and others), organizations face increased requirements when protecting data in the cloud. And the solution isn't as simple as deploying data loss prevention software in a data center because the data center has become fragmented. You now have a bunch of services, systems, and infrastructures that aren't owned by you but still require visibility and control.

Cloud services and infrastructures that share or exchange information also become difficult to manage: Who owns the service-level agreements? Is there a single pane of glass that monitors everything? DevOps has forced corporations to go as far as implementing microsegmentation and adjusting processes around firewall rule change management. Furthermore, serverless computing has provided organizations with a way to cut costs and speed productivity by allowing developers to run code without having to worry about infrastructures and platforms. Without a handle on virtual private clouds and workload deployments, however, things can spin out of control and you start to see data leaking from one environment just as you've achieved a comfortable level of security in another.

Mitigation
Several steps can be taken to help mitigate risk to an organization's data in the cloud.

1. Design to align. First, align your cloud environment with cybersecurity frameworks. Often, organizations move to the cloud so rapidly that the security controls historically applied to their on-premises data centers don't migrate effectively to the cloud. Furthermore, an organization may relax the security microscope on software-as-a-service (SaaS) applications such as Salesforce or Office 365. But even with these legitimate business applications, data may end up being leaked if you don't have the right visibility and control. Aligning cloud provider technology with cybersecurity frameworks and business operating procedures provides for a highly secure, more productive implementation of a cloud platform, giving better results and a successful deployment.

2. Make yourself at home. Cloud systems and networks should be treated the way you treat your LAN and data center. Amazon's Shared Responsibility Model, for example, outlines where Amazon's security responsibility ends and your security responsibility begins. While threats at the compute layer exist — as we've seen with Meltdown, Foreshadow, and Spectre — recent cloud data breaches have shown a breakdown in an organization's security responsibility area, namely operating system security, data encryption, and access control. If your organization has standards that govern the configuration of servers, vulnerability management, patching, identity and access management, encryption, segmentation, firewall rules, application development, and monitoring, see to it that those standards are applied to cloud services and are audited regularly.

3. Stop the "sneaking out at night." Not too long ago, you would see organizations struggle with employees who set up unsecured wireless access points in an attempt to gain flexibility and efficiency. Fast forward to today — wireless controllers providing rogue detection and intrusion prevention system capabilities have helped rein in that activity. With the cloud, employees are setting up cloud storage accounts, serverless computing environments, and virtual private networks as needed to circumvent cumbersome change control procedures, cut costs, and gain similar flexibility and efficiency. By rearchitecting legacy networks, readjusting decades-old processes and procedures, implementing cloud proxy or cloud access security broker (CASB) technology, and coupling that with strong endpoint security controls and an effective awareness campaign, an organization can provide that level of flexibility and efficiency but still provide for data protection.

4. Keep a close watch. The cybersecurity operations center (CSOC) should no longer be concerned with just the local network and data centers. The operational monitoring procedures, threat hunting, intelligence, and incident response that the SOC uses also apply to cloud environments where the organization's data resides. Monitoring SaaS applications where corporate data may reside is challenging but can be done using effective endpoint security coupled with the monitoring of cloud access solutions (CASB, proxy, and others). For a serverless environment, depending on your CSOC requirements, this may mean the application of third-party monitoring platforms or solutions beyond what cloud providers offer. In all cases, event logging and triggers need to feed back to the CSOC to be correlated with local event data, analytics, and threat intelligence.

With all the cloud services available, it's no wonder companies struggle to manage risk. Shifting from a culture of "do whatever it takes to get the job done" to "do what is right for the business" takes a lot of coordinated effort and time but is rooted in security becoming a business enabler rather than continuing to be in the business of "no."

Organizations must include security in technology decisions if security is to continue to protect the business, and security must understand the needs of the business and changes in technology in order to be that enabler. To help to prevent people from seeking their own solutions to technology problems, IT and security teams must evolve their assets and functions to accommodate that speed and convenience or find themselves constantly trying to keep up. 

Related Content:

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

 

Derrick Johnson is the National Practice Director for Secure Infrastructure Services within AT&T Cybersecurity Consulting, responsible for its direction and overall business performance. Derrick's practice provides strategic and tactical cybersecurity consulting services ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
7/9/2019 | 2:24:03 PM
What I have been saying for years
There is nothing real called a CLOUD ---- it is an extremely long RJ-45 or fibre-optic cable from your endpoint in your building TO something else - server, datacenter - in another location FAR FAR away under somebody else's hand control.  God knows who THEY are and what they can do with the data.  Woz - the great one from Apple - said years ago that there is NO security in the cloud.  Fools think it is more secure than other choices - it is perhaps less secure because of somebody else's hands on a keyboard.  Warning posted
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Tor Weaponized to Steal Bitcoin
Dark Reading Staff 10/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8369
PUBLISHED: 2019-10-21
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none.
CVE-2019-18224
PUBLISHED: 2019-10-21
idn2_to_ascii_4i in lib/lookup.c in GNU libidn2 before 2.1.1 has a heap-based buffer overflow via a long domain string.
CVE-2019-16985
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app\xml_cdr\xml_cdr_delete.php uses an unsanitized "rec" variable coming from the URL, which is base64 decoded and allows deletion of any file of the system.
CVE-2019-16986
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file resources\download.php uses an unsanitized "f" variable coming from the URL, which takes any pathname and allows a download of it. (resources\secure_download.php is also affected.)
CVE-2019-16987
PUBLISHED: 2019-10-21
In FusionPBX up to v4.5.7, the file app\contacts\contact_import.php uses an unsanitized "query_string" variable coming from the URL, which is reflected in HTML, leading to XSS.