Mobile

5/8/2017
12:06 PM
50%
50%

DHS Report Outlines Feds' Mobile Security Threats

The US Department of Homeland Security sent Congress a study on mobile security threats facing federal government workers as well as recommendations for protection.

Mobile devices used by federal government workers are potentially at a higher risk of attack than those used by consumers, solely for the mere fact that they are public-sector employees, according to a report presented to Congress last week by the US Department of Homeland Security.

Cybercriminals targeting government workers' mobile devices view them as a potential channel to accessing back-end computer systems rich in data containing sensitive federal government information and private information on millions of Americans, according to the DHS.

While federal workers are at risk to many of the same cybersecurity threats that the average consumer faces, such as ransomware, banking fraud, and identity theft, some of the solutions to address the mobile security problem differ than that of consumers.

DHS recommends developing cooperative arrangements with mobile network operators to detect, defend, and respond to threats – and potentially extending the DHS National Protection and Programs Directorate authority to achieve these objectives. The study also calls for more policy and procedural changes that recognize mobile security should be treated differently than desktop architecture security.

Some of DHS' recommendations are similar to those practiced by the private sector, such as adopting a mobile device security framework that uses existing standards and best practices, and including mobility in a continuous security diagnostics and mitigation program similar to that of network devices.

Read more on the DHS study here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. 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.