DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Interesting closing letter from FTC to Verizon concerning WEP default on older routers

Posted on November 12, 2014 by Dissent

From the FTC

Ms. Dana Rosenfeld
Kelley Drye
Washington Harbour, Suite 400 3050 K Street, NW Washington, D.C. 20007

Dear Ms. Rosenfeld:

UNITED STATES OF AMERICA FEDERAL TRADE COMMISSION WASHINGTON, DC 20580

November 12, 2014

As you know, staff in the Division of Privacy and Identity Protection has conducted an investigation into possible violations of Section 5 of the Federal Trade Commission Act by your client, Verizon Communications, Inc. (“Verizon”). The investigation considered whether Verizon engaged in unfair or deceptive acts or practices by failing to secure, in a reasonable and appropriate manner, the routers it provided to its High Speed Internet (DSL) and FiOS customers.

Among other things, our investigation examined the fact that Verizon regularly shipped routers to consumers with the default security set to an outdated encryption standard known as Wired Equivalent Privacy (“WEP”). Due to certain weaknesses in WEP, the Institute of Electrical and Electronics Engineers (“IEEE”) deprecated this standard in 2004 in favor of a new standard known as Wi-Fi Protected Access (“WPA”), and later, Wi-Fi Protected Access 2 (“WPA2”).1 However, until recently, Verizon continued to ship some router models with the WEP encryption standard. As a result, many Verizon customers still have routers that are set to the outdated WEP standard, leaving them vulnerable to hackers.

Despite this concern, staff has determined to close this investigation. Among the factors we considered were Verizon’s overall data security practices related to its routers, along with efforts by Verizon to mitigate the risk to its customers’ information. Indeed, Verizon has recently taken several steps to address the concerns regarding the security of its customers’ routers. First, the company has pulled all WEP-defaulted routers from its distribution centers and set them to WPA2, ensuring that all routers distributed going forward will be set to WPA2 by default. Second, the company has implemented an outreach campaign targeting customers that are currently using WEP or no encryption and asking these customers to update their security settings to WPA2. Lastly, for those customers that have older routers incompatible with WPA2, the company is offering an opportunity to upgrade to WPA2-compatible units. We encourage consumers to take advantage of these opportunities to update their router security.

We continue to emphasize that data security is an ongoing process. As risks, technologies, and circumstances change over time, companies must adjust security practices accordingly. In the past, defaulting consumer routers to WEP may not have been unreasonable, given concerns about compatibility with older computing devices. However,what constitutes reasonable security changes over time as new risks emerge and new tools become available to address them. As most all consumer devices on the market today are compatible with WPA2,it would likely be unreasonable for Internet Service Providers (“ISPs”) or router manufacturers to continue to default consumer routers to WEP encryption. We hope and expect that all companies that provide consumers with these products will ensure reasonable and appropriate default security settings.

The closing of this investigation is not to be construed as a determination that a violation may not have occurred, just as the pendency of an investigation should not be construed as a determination that a violation has occurred. The Commission reserves the right to take such further action as the public interest may require.

Category: Business SectorCommentaries and Analyses

Post navigation

← Coca-Cola sued over stolen laptops breach
Civilian employee for Coast Guard accused of stealing personal information →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach
  • HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI
  • Additional 12 Defendants Charged in RICO Conspiracy for over $263 Million Cryptocurrency Thefts, Money Laundering, Home Break-Ins
  • RIBridges firewall worked. But forensic report says hundreds of alarms went unnoticed by Deloitte.
  • Chinese Hackers Hit Drone Sector in Supply Chain Attacks
  • Coinbase says hackers bribed staff to steal customer data and are demanding $20 million ransom
  • $28 million in Texas’ cybersecurity funding for schools left unspent
  • Cybersecurity incident at Central Point School District 6

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025
  • License Plate Reader Company Flock Is Building a Massive People Lookup Tool, Leak Shows
  • FTC dismisses privacy concerns in Google breakup

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.