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.

Application Security //

Database Security

Starwood Breach Reaction Focuses on 4-Year Dwell

The unusually long dwell time in the Starwood breach has implications for both parent company Marriott International and the companies watching to learn from.

Four years. That's how long an attacker was in Starwood Hotels' databases. While "dwell time" — the delay between when a breach begins and when it's discovered — is an issue across cybersecurity, the unusually long dwell time in the Starwood breach has implications for both Marriott International and the companies watching to learn from.

According to Mandiant, the average dwell time for an attack is 101 days. Though there are few details about the Starwood/Marriott breach, experts say several factors might have contributed to the longer-than-usual dwell time.

According to Avivah Litan, a vice president and distinguished analyst at Gartner who has researched many large-scale breaches, the long dwell time is an indicator that the attackers were nation-state threat actors. "These guys are really good at what they do," she says. "You know, they're very stealthy — they hide in places you can't find."

In support, Litan points to details contained in the indictments for the Democratic National Convention's email server breach, which show that the DNC hired a forensic security specialist ("Company 1" in the indictment) to clean up the breach when it was discovered. Despite their efforts, the attackers maintained persistence on the servers and took files for months following the remediation efforts.

And Stephen Moore, chief security strategist at Exabeam, was part of the Anthem Healthcare security team that followed up on the insurance company's 2015 breach. He says that Starwood's 2016 purchase by Marriott could easily have increased the time the attackers had inside the network. "That's a prime moment to attack, and then it would absolutely make things more difficult," Moore explains. "I could say it would be at least twice as difficult to identify an adversary in the network because there are so many other things going on politically and otherwise."

For some professionals, the activity going on around the IT department is no excuse. "In my opinion as somebody who works in the field, a month is too long, a week is too long. You should be catching that data is being actively sent from your system to another location that you didn't authorize in a couple of days tops," says Jessica Ortega, security research analyst at Sitelock.

The Impact Spreads
Though some have focused on the financial fraud possible with stolen payment card information, Moore says other, more serious consequences are possible from this breach, or any breach in the hospitality industry. "In the past there have been travel-related incidents tied to hospitality that were for intelligence-gathering and espionage," he says. "There are at least two very heavy-handed adversaries looking to either prosper from us financially or utilize us much like a lamprey attaches to a shark to draw information about who is staying where, who is going where, and which passport numbers were included."

Moore also points out that a four-year breach isn't the result of an opportunistic hack. Litan agrees. "Nation-states are interested in hotel data because it gives them really good information on where their targets are," she says. "If they're targeting people, there are many different uses for the data, ranging from stealing money to targeting individuals to national cybersecurity implications where they want to manipulate populations for political purposes."

A Stream Of Breaches
Public response to the Starwood breach has been muted, perhaps because it's merely the latest in a long line of large data breaches. Breaches continue for a simple reason, Ortega says. "There's no accountability for these businesses that have data breaches as of right now in the US," she says. And any possible accountability is merely passed off to others, Litan adds.

"The problem is the CEOs don't really want to spend extra money on security," she says. "They want to buy cyber insurance. If you look at Equifax, like they got a $95 million payout from their insurance company. And that's the way a lot of these CEOs think." In fact, she explains, "in general, CEOs would rather spend money on cyber insurance than on security."

There is a regulatory framework that carries the possibility of serious penalty, though no one knows what impact it will have on Marriott.

"There are accountability measures built into the GDPR regulations in the European Union, but those regulations are still relatively new, and we haven't really seen a large scale or a large enterprise business like this," Ortega says. "This, if nothing else, will be an interesting test for what actually happens with a large-scale data breach under GDPR. And we'll get an idea more of future penalties from this experience than we will be able to predict what will happen to Marriott in particular."

Related Content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
12/6/2018 | 9:49:24 AM
The Ostrich Principle
If we wait long enough, maybe it will go away and nobody will notice
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
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
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...