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.

Comments
On-Premise Security Tools Struggle to Survive in the Cloud
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
4/12/2018 | 12:49:31 PM
People are afraid of change
"Adopting cloud-based security tools may require a learning curve, but Gerchow warns companies that sticking with on-prem tools amid the move to the cloud can be dangerous."

This is the most important aspect of the whole document because organizations have not taken the time to fully understand the implications and redesign concepts of the cloud (basically they have not changed their thinking). In this new ecosystem, the cloud is not the all to end all, if you have problems on-premise then the same problems are going to resurface in the cloud due to the bad practices and engineering designs companies have employed at their primary locations.

We need to have an external party, someone who is familiar with cloud design/architecture, implementation, integration and data migration principles. First they would need to perform an assessment, identify any gaps or dependencies associated with the security application, determine (feasibility analysis) if the solution meets their needs, identify costs and then develop a plan to move into that area with a team who is knowledgeable of the intricacies of that CSP (Cloud Service Provider).

If the organizations followed this guidance, then most of the respondents would have a more favorable view of the cloud because it was treated as a project, as history has it, most organizations do not do this, they present the idea to one of their engineers, the engineer has never worked with the provider before, they have to research and figure out how the technology works in the cloud and the cloud application itself, then determine if the application they are used to is provided in the marketplace of that CSP. With all of this, the engineer becomes frustrated and the project is stalled because of the lack of understanding during the inception of the project.

The take away from all of this is as follows:
  • Educate specific members of the organization that you design cloud points of contact
  • Engage a third-party entity to help identify nuances with cloud adoption
  • Develop a 5 point plan using "Agile Scrum" methodologies to help with the deployment process - https://goo.gl/7Bvg6s (Gartner Cloud Adoption Plan)
  • Allow for adequate time to train, test, develop, implement, integrate, deploy your solution in the cloud
  • Finally, document lessons learned and document processes along the way allowing for Standard Operating Procedures (SOPs) to be created during this cloud adoption process

If we follow these steps, I do think the move from on-prem solutions to hybrid off-prem solutions would allow for great understanding and awareness during our journey to Enterprise Global Systems design.

Todd - ITOTS Networks, LLC


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-42692
PUBLISHED: 2022-05-26
There is a stack-overflow vulnerability in tinytoml v0.4 that can cause a crash or DoS.
CVE-2022-31650
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.
CVE-2022-31651
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.
CVE-2022-29256
PUBLISHED: 2022-05-25
sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` e...
CVE-2022-26067
PUBLISHED: 2022-05-25
An information disclosure vulnerability exists in the OAS Engine SecureTransferFiles functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to arbitrary file read. An attacker can send a sequence of requests to trigger this vulnera...