Vulnerabilities / Threats

9/13/2017
02:30 PM
Kelly Sheridan
Kelly Sheridan
Quick Hits
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Businesses Fail to Properly Secure, Assess SSH: ISACA

Frequently used but underappreciated, Secure Shell is rarely secured, assessed, documented, or managed in a systematic way, researchers report.

Most businesses use the Secure Shell (SSH) technology, a cryptographic protocol designed to enable secure file transfers and remote communications. However, it's rare they appropriately secure, document, routinely assess, and manage SSH, as reported in a new ISACA paper released Tuesday.

SSH was developed as a secure alternative to telnet and rsh/rexec. It's primarily used to allow a remote command shell (for example, the Bourne shell or C shell) over a network connection. It also allows port-forwarding capability and implements SFTP to allow secure file transfer.

It's essential for security leaders to ensure SSH is securely deployed and monitor its usage so it continues to protect against man-in-the-middle attacks, isn't misused by privileged insiders, or any number of other troubles. However, ISACA points out several challenges in doing all this well.

For one, businesses are struggling to manage and track SSH cryptographic keys. SSH is natively supported by Amazon Web Services, Google Cloud, and other service providers that offer virtual Linux hosts. Each SSH server has its own key to authenticate the device to clients and as SSH hosts increase on premise and in the cloud, complexities of key management will grow.

There is also a challenge in deciding who is responsible for SSH keys. Usually it's unclear who should handle tasks like managing key inventory and usage, a complexity that underscores the need to integrate controls and processes into broader control management, ISACA explains.

SSH is critical from a security perspective but generally invisible to the business; as a result, executives tend to overlook it. It's necessary for system administrators to operate, but how it's managed doesn't usually affect business processes. This can make it tough to ensure SSH gets executive attention and is addressed in risk management and audit planning.

Read more about SSH challenges and considerations by looking at the full report here.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.