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.

Cloud

9/28/2020
10:15 AM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail

9 Tips to Prepare for the Future of Cloud & Network Security

Cloud and network security analysts outline trends and priorities businesses should keep top of mind as they grow more reliant on cloud.
2 of 10

The Risk of SaaS Defaults 
As Riley pointed out, most cloud security questions fall into one of three main categories: cloud risk management, infrastructure-as-a-service (IaaS) security, and software-as-a-service (SaaS) control. IaaS usually falls under the control of developers, who can choose from a small number of providers. Lines of business typically control SaaS and can choose from many more providers.
'Unfortunately, many IT professionals would prefer to ignore the burgeoning SaaS market, even though in most cases it represents a more significant area of computing than do IaaS in private clouds,' he said. The sheer size of the SaaS market should be of concern to security teams, who often lack control over which software is downloaded and how it's used.
All services can externally share objects, but the default configuration is to not share. Open buckets, a common security risk, is a customer mistake. SaaS applications are different.
A 'surprising number' of SaaS applications not only allow external shares but open them by default, Riley pointed out. There are arguments over whether this is a design flaw or weakness on the part of the user. Default configuration can be modified, he added, but the organization must have the will to do so.
'There's no point in arguing about what the provider's initial default should be,' he continued. Your organization will obtain cloud services that may put them at risk, and security teams must be aware of this and do something about it. Closing open file shares is the most effective first step in cloud security a business can take, Riley said.
(Image: Guy Sagi -- stock.adobe.com)

The Risk of SaaS Defaults

As Riley pointed out, most cloud security questions fall into one of three main categories: cloud risk management, infrastructure-as-a-service (IaaS) security, and software-as-a-service (SaaS) control. IaaS usually falls under the control of developers, who can choose from a small number of providers. Lines of business typically control SaaS and can choose from many more providers.

"Unfortunately, many IT professionals would prefer to ignore the burgeoning SaaS market, even though in most cases it represents a more significant area of computing than do IaaS in private clouds," he said. The sheer size of the SaaS market should be of concern to security teams, who often lack control over which software is downloaded and how it's used.

All services can externally share objects, but the default configuration is to not share. Open buckets, a common security risk, is a customer mistake. SaaS applications are different.

A "surprising number" of SaaS applications not only allow external shares but open them by default, Riley pointed out. There are arguments over whether this is a design flaw or weakness on the part of the user. Default configuration can be modified, he added, but the organization must have the will to do so.

"There's no point in arguing about what the provider's initial default should be," he continued. Your organization will obtain cloud services that may put them at risk, and security teams must be aware of this and do something about it. Closing open file shares is the most effective first step in cloud security a business can take, Riley said.

(Image: Guy Sagi -- stock.adobe.com)

2 of 10
Comment  | 
Print  | 
Comments
Threaded  |  Newest First  |  Oldest First
JohnHammond
100%
0%
JohnHammond,
User Rank: Author
9/28/2020 | 5:24:15 PM
Great!
Nice article!
dave_cole
50%
50%
dave_cole,
User Rank: Author
9/29/2020 | 12:03:15 PM
Well done
Appreciate the breadth of topics, coverage.
Nahla D.
50%
50%
Nahla D.,
User Rank: Author
9/30/2020 | 9:21:54 AM
Great article!
Very informative article!!! Great job!
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.
CVE-2021-32553
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-17 package apport hooks, it could expose private data to other local users.
CVE-2021-32554
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the xorg package apport hooks, it could expose private data to other local users.