Cloud Security: Making the Invisible … Visible

Living in Colorado and having 14,000-foot mountains in my backyard, there are times I end up driving into the clouds. One minute I can be traveling in sunshine and great weather and the next, a cloud surrounds my car.

Entering a cloud, things begin to lose visibility. Soon, you can barely make out anything around you. This is a good time to slow down and get clarity on your surroundings.

As the business market continues to drive into the cloud, it too comes with risk of diminished visibility. The major cloud providers give you tools to secure platforms in the cloud, but they don’t provide you the means of monitoring those solutions to know what is happening in the platform or within a cloud datacenter.

Besides a bill for your monthly traffic, compute and storage usage, you don’t have visibility of what the traffic is within the cloud.

For many, cloud security can be a challenging prospect as each provider has slightly different ways of implementing their security stack. You may have secured your cloud devices, but how do you know what traffic goes in and out of them? And just because you identify the appropriate ports and protocols that are allowed, that doesn’t mean your application can’t be compromised and data exfiltrated through those ports and protocols.

How to Gain Better Cloud Visibility

The challenge when working within the cloud is making the invisible, visible. Cloud providers do not rely upon layer 2 connections, but rather route all the traffic based upon their own algorithms/methods.

In most cloud systems, depending upon how well you’ve defined your security rules, when you launch a new device within a cloud environment, all the other devices within that environment can send traffic to and from each other. This is why micro-segmentation has become one of the cloud buzzwords; we needed the ability to restrict traffic at the host or interface level.

While micro-segmentation will allow you to restrict traffic, how do you inspect the traffic?

How Virtual Firewalls Secure Cloud Environments

SonicWall provides two products to help with this problem of visibility within the cloud: Network Security Virtual Firewall (NSv) and Web Application Firewall (WAF). These products each have their own purposes, but when implemented correctly, they will provide you visibility within the cloud.

Every cloud provider allows you to modify the default route paths and direct traffic within their infrastructure. With these routes, you can direct traffic in and out of NSv or WAF in order to provide additional visibility and inspection of the traffic within your cloud.

You can further improve cloud security by adding Deep Packet Inspection (DPI), Capture Advanced Threat Protection (ATP) multi-engine cloud sandboxing, which includes Real-Time Deep Memory Inspection (RTDMITM), and traffic reporting and analysis.

Setting up the custom route tables to direct traffic within a cloud provider can be a daunting task. SonicWall’s Remote Implementation Service for the NSv Firewalls can help.

Whether you use the SonicWall NSv or the WAF within the cloud, you will have the ability to shed light upon the traffic within the cloud and know that it’s appropriate for your environment. Take back control of your traffic by bringing it to a higher level — above the clouds.

SonicWall Partner Enabled Services

Optimize your investment in SonicWall products with professional services delivered by SonicWall Advanced Services Partners trained to provide world-class professional services for SonicWall customers.

Web attacks in November 2018

The first step in a web attack begins with mass-scanning the web for vulnerable applications and/or servers. When unpatched software is identified, an attempt is made to exploit the vulnerability. Any vulnerability in the web application, database, operating system or in the network will lead to an attack on the web server.

Successful exploitation could lead to information disclosure, denial-of-service conditions or achieve arbitrary code execution with the privileges of the server.

SonicWall Threat Research Lab has observed attempts to exploit unpatched vulnerabilities on the web.  Find below the software list that were most attacked in November 2018.

PhpMyadmin:
phpMyAdmin is a free software tool written in PHP, which helps users to perform the administration task on MySQL and MariaDB over the Web user interface. phpMyAdmin supports a wide range of operations like managing databases, tables, columns, relations, indexes, users, and permissions via the Web user interface.

Apache Struts2:
Apache Struts 2 is an open-source web application framework for developing Java EE web applications. It uses and extends the Java Servlet API to encourage developers to adopt a model–view–controller architecture

TomCat:
Apache Tomcat, often referred to as Tomcat Server, is an open-source Java Servlet Container developed by the Apache Software Foundation. Tomcat implements several Java EE specifications including Java Servlet, JavaServer Pages (JSP), Java EL, and WebSocket, and provides a “pure Java” HTTP web server environment in which Java code can run.

JBoss:
JBoss Enterprise Application Platform (EAP) is an application server written in Java, which implements the Java Platform, Enterprise Edition (Java EE) specification.

Oracle WebLogic:
Oracle WebLogic Server is an enterprise-class multi-tier Java Application Server platform. WebLogic is typically used as a platform for large enterprise web applications. The components of the WebLogic Platform include an Application Server, Portal, Application Integration service and HTTP web server.

Internet Information Server (IIS) :
The Internet Information Server (IIS) is a collection of Internet services packaged with several versions of the Windows operating system. IIS includes a Web server service that is capable of serving static, as well as dynamic content.

WordPress:
WordPress is a free and open-source content management system based on PHP and MySQL. Features include a plugin architecture and a template system.

How to mitigate?

1. Use latest software and apply security patches whenever they are available
2. Do not use default credentials
3. Do not use default configuration
4. Turn off all unnecessary features by default
4. Secure configuration files

How to configure SonicWall Web Application Firewall (WAF) to protect against a whole suite of web attacks such as Cross-site scripting, SQL Injection, OS Command Injection, and many more:
https://www.sonicwall.com/en-us/support/technical-documentation/web-application-firewall
How to configure SonicWall firewall to prevent brute force attacks:
https://www.sonicwall.com/en-us/support/knowledge-base/171006033550997
How to block Denial of Service attacks using Intrusion Prevention:
https://www.sonicwall.com/en-us/support/knowledge-base/170502507163643
How to protect SQL servers from Injection attacks:
https://www.sonicwall.com/en-us/support/knowledge-base/170504288959461