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.

Operational Security

12/4/2018
08:15 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Marriott's Due Diligence Failure Led to Massive Data Breach

After acquiring Starwood, Marriott failed to conduct a proper review of the company's security issues. This lack of due diligence led directly to 500 million records being compromised in a data breach.

The data breach affecting about 500 million Marriott and Starwood customers has made a huge splash in both the popular and the security arenas. It's a reminder of the fragility of information that is used by businesses.

Not only that, the end costs of this episode are going to be staggering.

The first class-action lawsuits on behalf of customers have already been filed. Marriott stock dropped about 6% since the breach was first disclosed on November 30. The loss of confidence of customers in the Marriott brand -- even though the breach involved a Starwood database system -- will also take a great toll. (See Marriott: 500 Million Guest Records Compromised in Data Breach.)

Collateral damage with this kind of breach is very real, with Marriott getting blamed for Starwood's mistakes even though they occurred well before the acquisition. This is similar to what happened when Verizon realized Yahoo had been breached after the acquisition was announced. The terms of the deal had to be retroactively modified. (See SEC Slaps Yahoo Successor With $35M Fine for 2014 Data Breach.)

But, more than that, it shows that how business is conducted today needs to be revised and upgraded. The faults that lead up to this breach were not just due to some simple security fault in a reservation database. They were systemic and deeply rooted in business practices.

The obvious problem here is that Marriott did not perform an effective due diligence on the Starwood computer networks when they bought the company.

A Forrester report sums up the questions around this due diligence situation nicely:

Did Marriott know -- or try to discover -- that Starwood's network and database security controls, processes, and governance made attacks like this possible over a sustained period of time? Did it know that an attacker could get access to the reservation system in the first place -- where the "crown jewels" would obviously be -- and upon obtaining access to that could snag almost every bit of customer data it held and dwell there for multiple years without being detected?

It's not like Marriott didn't have some red flags.

In 2015 -- four days after Marriott announced the acquisition -- Starwood reported a different breach. Attackers installed malware on point-of-sale systems for payment-card information. A deep investigation of the entire system may have shown the presence of the long-resident attack.

In an email to Security Now, Rich Campagna, chief marketing officer of security vendor Bitglass, noted: "Marriott is not alone in its lack of visibility over its infrastructure. Any organization that acquires another business and its IT assets will be faced with major security blind spots unless the right tools are in place. Marriott should be looking at the infrastructure affiliated with all its prior acquisitions, ensuring that the security controls in place are as effective as possible."

It's painfully obvious that cybersecurity due diligence in M&A is going to be central.

If the acquirer doesn't pay for those costs when the deal is cut, then the costs due to the lack of diligence that will show up at a later date will only make everything far more expensive.

Management has always viewed security and its associated cost as a drain on profit. They need to change their view drastically, seeing it as an insurance on making everything work out correctly.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/9/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Mobile App Fraud Jumped in Q1 as Attackers Pivot from Browsers
Jai Vijayan, Contributing Writer,  7/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-14174
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view titles of a private project via an Insecure Direct Object References (IDOR) vulnerability in the Administration Permission Helper. The affected versions are before version 7.13.6, from version 8.0.0 before 8.5....
CVE-2019-20901
PUBLISHED: 2020-07-13
The login.jsp resource in Jira before version 8.5.2, and from version 8.6.0 before version 8.6.1 allows remote attackers to redirect users to a different website which they may use as part of performing a phishing attack via an open redirect in the os_destination parameter.
CVE-2019-20898
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to access sensitive information without being authenticated in the Global permissions screen. The affected versions are before version 8.8.0.
CVE-2019-20899
PUBLISHED: 2020-07-13
The Gadget API in Atlassian Jira Server and Data Center in affected versions allows remote attackers to make Jira unresponsive via repeated requests to a certain endpoint in the Gadget API. The affected versions are before version 8.5.4, and from version 8.6.0 before 8.6.1.
CVE-2019-20900
PUBLISHED: 2020-07-13
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the Add Field module. The affected versions are before version 8.7.0.