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
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14072
PUBLISHED: 2018-07-15
libsixel 1.8.1 has a memory leak in sixel_decoder_decode in decoder.c, image_buffer_resize in fromsixel.c, and sixel_decode_raw in fromsixel.c.
CVE-2018-14073
PUBLISHED: 2018-07-15
libsixel 1.8.1 has a memory leak in sixel_allocator_new in allocator.c.
CVE-2018-14068
PUBLISHED: 2018-07-15
An issue was discovered in SRCMS V2.3.1. There is a CSRF vulnerability that can add an admin account via admin.php?m=Admin&c=manager&a=add.
CVE-2018-14069
PUBLISHED: 2018-07-15
An issue was discovered in SRCMS V2.3.1. There is a CSRF vulnerability that can add a user account via admin.php?m=Admin&c=member&a=add.
CVE-2018-14066
PUBLISHED: 2018-07-15
The content://wappush content provider in com.android.provider.telephony, as found in some custom ROMs for Android phones, allows SQL injection. One consequence is that an application without the READ_SMS permission can read SMS messages. This affects Infinix X571 phones, as well as various Lenovo p...