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.

Endpoint

9/13/2017
01:20 PM
Dawn Kawamoto
Dawn Kawamoto
Slideshows
50%
50%

10 Ways to Prevent Your Mobile Devices From Becoming Bots

Enterprises may not notice a huge impact on their network's bandwidth, but other repercussions may loom in the background.
Previous
1 of 11
Next

(Image Source: Gunnar Assmy via Shutterstock)

(Image Source: Gunnar Assmy via Shutterstock)

The WireX Android botnet last month snagged tens of thousands of mobile users, in order to wage DDoS attacks against organizations in multiple industries.

While it's clearly taxing to be on the receiving side of a DDoS attack, enterprises that find their mobile devices commandeered as bots also have reason for concern.

"Enterprises may notice their upstream traffic flow will be slightly constrained, but the impact will be negligible," says Robbie Forkish, Appthority CTO. However, Forkish and other security experts note it's still worth a company's time and effort to prevent their mobile devices from becoming bots.

For example, companies may find their IP addresses blacklisted if their mobile devices are swept up into a botnet, notes Andrew Blaich, a security researcher at Lookout.

James Plouffe, lead solutions architect with MobileIron, agrees.

"If you are an enterprise and part of a botnet, then you're consuming bandwidth for things not related to your company," Plouffe says. "Also, it could appear your company is the source of the attack and it could be bad for your company's reputation and you may incur some liability."

In addition to these issues, a company may find that once its mobile workforce is infected with malware, the attackers could turn the bots into another malicious purpose.

"The attacker could change the instructions and have it infiltrate confidential information on the device," says Robert Hamilton, director of product marketing at Imperva.

Here are 10 steps IT security teams can take to reduce the odds their mobile devices will get recruited as bots:

 

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
NetCAT Vulnerability Is Out of the Bag
Dark Reading Staff 9/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16199
PUBLISHED: 2019-09-17
eQ-3 Homematic CCU2 before 2.47.18 and CCU3 before 3.47.18 allow Remote Code Execution by unauthenticated attackers with access to the web interface via an HTTP POST request to certain URLs related to the ReGa core process.
CVE-2019-16391
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows authenticated visitors to modify any published content and execute other modifications in the database. This is related to ecrire/inc/meta.php and ecrire/inc/securiser_action.php.
CVE-2019-16392
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 allows prive/formulaires/login.php XSS via error messages.
CVE-2019-16393
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 mishandles redirect URLs in ecrire/inc/headers.php with a %0D, %0A, or %20 character.
CVE-2019-16394
PUBLISHED: 2019-09-17
SPIP before 3.1.11 and 3.2 before 3.2.5 provides different error messages from the password-reminder page depending on whether an e-mail address exists, which might help attackers to enumerate subscribers.