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
Newest First  |  Oldest First  |  Threaded View
Nahla D.
50%
50%
Nahla D.,
User Rank: Author
9/30/2020 | 9:21:54 AM
Great article!
Very informative article!!! Great job!
dave_cole
50%
50%
dave_cole,
User Rank: Author
9/29/2020 | 12:03:15 PM
Well done
Appreciate the breadth of topics, coverage.
JohnHammond
100%
0%
JohnHammond,
User Rank: Author
9/28/2020 | 5:24:15 PM
Great!
Nice article!
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...