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.

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
RetiredUser
0%
100%
RetiredUser,
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.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: He still insists that security by obscurity is the way to go.
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-9681
PUBLISHED: 2019-09-17
Online upgrade information in some firmware packages of Dahua products is not encrypted. Attackers can obtain this information by analyzing firmware packages by specific means. Affected products include: IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X...
CVE-2019-9009
PUBLISHED: 2019-09-17
An issue was discovered in 3S-Smart CODESYS before 3.5.15.0 . Crafted network packets cause the Control Runtime to crash.
CVE-2018-20336
PUBLISHED: 2019-09-17
An issue was discovered in Asuswrt-Merlin 384.6. There is a stack-based buffer overflow issue in parse_req_queries function in wanduck.c via a long string over UDP, which may lead to an information leak.
CVE-2019-12755
PUBLISHED: 2019-09-17
Norton Password Manager, prior to 6.5.0.2104, may be susceptible to an information disclosure issue, which is a type of vulnerability whereby there is an unintentional disclosure of information to an actor that is not explicitly authorized to have access to that information.
CVE-2019-14826
PUBLISHED: 2019-09-17
A flaw was found in FreeIPA versions 4.5.0 and later. Session cookies were retained in the cache after logout. An attacker could abuse this flaw if they obtain previously valid session cookies and can use this to gain access to the session.