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
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-20782
PUBLISHED: 2019-02-17
The GloBee plugin before 1.1.2 for WooCommerce mishandles IPN messages.
CVE-2019-8407
PUBLISHED: 2019-02-17
HongCMS 3.0.0 allows arbitrary file read and write operations via a ../ in the filename parameter to the admin/index.php/language/edit URI.
CVE-2019-8408
PUBLISHED: 2019-02-17
OneFileCMS 3.6.13 allows remote attackers to modify onefilecms.php by clicking the Copy button twice.
CVE-2016-10742
PUBLISHED: 2019-02-17
Zabbix before 2.2.21rc1, 3.x before 3.0.13rc1, 3.1.x and 3.2.x before 3.2.10rc1, and 3.3.x and 3.4.x before 3.4.4rc1 allows open redirect via the request parameter.
CVE-2019-8393
PUBLISHED: 2019-02-17
Hotels_Server through 2018-11-05 has SQL Injection via the API because the controller/api/login.php telephone parameter is mishandled.