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.

News

7/3/2016
08:00 AM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail

6 Ways To Keep Androids Safe

Security managers have their hands full protecting Android devices, but there are common sense steps they can take to beat back attackers.
1 of 7

1 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Gen Chang
50%
50%
Gen Chang,
User Rank: Apprentice
7/5/2016 | 11:01:34 PM
Re: More ways
I'm surprised you didn't list a browser with adblocking capabilities. All the rest of your suggestions are great. The last one, I'm not familiar with, and so, will look it up. I'm using a new global ad blocker for no-root that's just been published to GitHub. Block This is the name, and if you Google the name, there's lots more information. XDA has a couple threads and readit too.
Anwarali
50%
50%
Anwarali,
User Rank: Apprentice
7/5/2016 | 1:37:41 AM
Re: More ways
good post.

theb0x
100%
0%
theb0x,
User Rank: Ninja
7/4/2016 | 9:53:17 AM
More ways
1) Disable all unnessisary services / applications

2) Keep Bluetooth off unless currently being used to help prevent Bluejacking attacks

3) Install a firewall. There are plenty of firewalls that do not require root. (ie No Root Firewall) They use a locally bound VPN loopback to allow the filtering of all network traffic

4) Turn off WiFi when not being used to prevent authentication with rogue access points and MITM attacks

5) Use a VPN on all Wifi networks

6) Be aware of apps with excessive permisions

7) Disable EXIF geolocation metadata on your camera

8) Encrypt your phone

9) Set a screen autolock that requires a pin / pattern

10) Disable ADB Developer Tools

11) Disable visable passwords typed in all apps

12) Install Netcut Defender to prevent ARP Spoofing and Internet Gateway Spoofing attacks

 

 

 
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.