Threat Intelligence

6/12/2017
12:34 PM
50%
50%

FTC Issues Advice on Mobile Phone Data Security, Identity Theft

The Federal Trade Commission offers hindsight and foresight on ways to reduce identity theft should your mobile device get stolen.

Smartphones are small and easy to lose or have stolen, but the Federal Trade Commission doesn't believe that the data within the device has to suffer the same fate and is offering up steps to minimize identity theft.

The FTC, for starters, is pointing victims to IdentityTheft.gov, where reports can be filed to law enforcement agencies and a personalized recovery plan is drafted. But in addition to the site, the FTC is offering some before and after tips to smartphone users and BYOD workers.

Before a mobile device is lost or stolen, two-factor authentication should be turned on, as well as iOS' "Find My Phone" or Android's "Find My Device" feature, the FTC advises. The agency also recommends users create a lock on their phone, which would require at least a six-digit password, fingerprint scan, or pattern lock. One of the key suggestions offered up by the FTC is that users need to remember to back up the data on their phones.

But once a phone is stolen or lost, accounts that can be accessed by the phone and have passwords automatically remembered should undergo a password change and those accounts that are tied to the phone should be disconnected from the lost or stolen device, the FTC says. The Commission also recommends watch for any notifications that a new device has attached itself to your email or accounts. Another step the FTC advises users take is to notify the carrier that the device is lost or stolen and it could temporarily or permanently disable the SIM card.

Read more about the FTC's smartphone steps 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
No SOPA
0%
100%
No SOPA,
User Rank: Ninja
6/12/2017 | 1:59:15 PM
Requiring Multi-factor Authentication Configuration
I'm often on the fence with government oversight and involvement in too many facets of technology.  But I'd welcome any future regulations that make end user configuration of multi-factor authentication on mobile devices a requirement such that your phone can not be set up without it.  Some applications are already set up this way as we know, but to establish a blanket Federal requirement for MFA would be a blow to the casual cybercriminal.

I know such regulatory oversight is not acceptable to many, but considering the critical mass cybercrime has taken on, I can't imagine we're far from such regulations anyway.  Better the InfoSec community define the regulations now than allow them to be defined later by ill-qualified agents.
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-13435
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.0 for iOS. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method to disable passcode authentication. NOTE: the vendor indicates that this is not an attack of interest w...
CVE-2018-13446
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.1 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode. ...
CVE-2018-14567
PUBLISHED: 2018-08-16
libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.
CVE-2018-15122
PUBLISHED: 2018-08-16
An issue found in Progress Telerik JustAssembly through 2018.1.323.2 and JustDecompile through 2018.2.605.0 makes it possible to execute code by decompiling a compiled .NET object (such as DLL or EXE) with an embedded resource file by clicking on the resource.
CVE-2018-11509
PUBLISHED: 2018-08-16
ASUSTOR ADM 3.1.0.RFQ3 uses the same default root:admin username and password as it does for the NAS itself for applications that are installed from the online repository. This may allow an attacker to login and upload a webshell.