Operations

9/10/2015
10:30 AM
Mohan Koo
Mohan Koo
Commentary
100%
0%

What Ashley Madison Can Teach The Rest Of Us About Data Security

For a company whose offering can best be described as discretion-as-a-service, using anything less than state-of-the-art threat detection capabilities is inexcusable.

Thanks to its very public hack and sensationalized dump of full customer data, Ashley Madison has become a household name in a matter of weeks. While the negative attention doesn’t bode well for the company’s long-term viability, Ashley Madison claims “hundreds of thousands” of new users are still signing up each week.

Whether or not you believe that statistic, it’s clear the company’s security failures have shined a spotlight on what not to do when given the task of protecting sensitive consumer data. The fallout from this scandal could forever change the way organizations strategically view and approach security. Ashley Madison’s entire business hinged on its commitment to anonymity, trust, and discretion, and its trumped-up security claims were the cause of its public humiliation.

Although the hacking collective known as the Impact Team targeted the extramarital affair matchmaking site for misleading customers with a bogus “full delete” user privacy feature, the group didn’t hesitate to out the site’s 37 million users as collateral damage to bring down the organization. Ashley Madison must face the consequences for its security negligence.

[Read Ashley Madison Guilty Of Hard-Coded Creds, Weak Bot Detection for the latest details on the breach.]

Before the breach, the company boasted about airtight data security but ironically, still proudly displays a graphic with the phrase “trusted security award” on its homepage. In a Q&A with MOTHERBOARD, the Impact Team asserted that Ashley Madison not only employed substandard security measures but also had a complete disregard for security across the board:

"We worked hard to make a fully undetectable attack, then got in and found nothing to bypass.... Nobody was watching. No security. Only thing was segmented network. You could use Pass1234 from the internet to VPN to root on all servers.”

In the aftermath of the breach, Ashley Madison’s inability to identify the culprit confirms a gaping hole in its security infrastructure. Although former CEO Noel Biderman suggested to Brian Krebs in an interview that the breach was an inside job committed by a trusted third-party contractor, the $500K reward Ashley Madison’s parent company is now offering for intel raises serious doubts. The fact that the company cannot produce a data audit trail to unequivocally determine the perpetrator of this attack only underscores that it did not have proper monitoring and visibility into its own organization.

With its user base now exposed to the world, it's hard to imagine the company won’t face ramifications for its poor security infrastructure and total lack of a forensic framework. For a company whose offering can best be described as discretion-as-a-service, using anything less than the most state-of-the-art threat detection capabilities is inexcusable. Ashley Madison should have had systems in place to detect and flag suspicious behavior from within the network before a hack could occur. In the case of a swift-moving attack, it could have created an irrefutable data trail to decisively name a suspect immediately. Without these measures in place, a bad actor can go unnoticed for months within a company’s network and make off with the “crown jewels” without a trace.

On top of individual class-action lawsuits, Canada’s Office of the Privacy Commissioner is also conducting an investigation, however current Canadian privacy laws don’t allow the Commissioner to levy fines and lack legal teeth when breaches like this come to light. Many privacy advocates hope this event will result in a reevaluation or bolstering of recent privacy laws.

At the organizational level, data security is also moving to center stage for regulators. As more scandals unfold revealing lax corporate policies that place customers in the crosshairs, government entities like the U.S. Federal Trade Commission have been empowered to ensure consumer protection and hold individual organizations accountable for careless security practices.

The notoriety of the Ashley Madison case all but demands public action by regulators to send a message to organizations across the globe. This is an opportunity for the FTC and other legislators to educate businesses about safeguarding data and making honest promises about what’s being done to ensure consumer protection. Companies unable to prove they have the appropriate security measures in place will find themselves in the hot seat—where Ashley Madison is sitting now.

Regardless of the legal ramifications Ashley Madison will face, this breach should serve as a wake-up call to organizations across industries. Every firm—whether they handle high-risk data or not—opens themselves up to the risk of losing customer trust if they are not effectively defending against threats from both outside and inside the business. Any CEO who isn’t vigilantly protecting his or her company’s assets with systems designed to track user behavior and identify malicious activity is acting negligently and putting the entire organization at risk. And as we’ve seen in the case of Ashley Madison, leadership all the way up to the CEO may very well be forced out when security isn’t prioritized as a core tenet of an organization.

As a co-founder of Dtex Systems, Mohan has been primarily responsible for growing the Dtex business in new vertical markets and geographies, with a strong focus on the cross-sector acquisition of new customers and partners. Over the past 15 years, Mohan has led the Dtex team ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Thomas Claburn
50%
50%
Thomas Claburn,
User Rank: Ninja
9/10/2015 | 4:33:46 PM
the lesson...
...sadly is that people don't care about security until they get hurt.
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
The State of IT and Cybersecurity
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
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.