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
 

Recommended Reading:

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.
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.