HackingHospitalityHospitalityStolen CredentialsSupply Chain (3P Vendor)Data ExfiltratedCustomer Data InvolvedIdentity (basic)Financial accountFinancial credentialsLowContained

The Queen Mary

bd_2f7799f24adf98f3 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 6, 2017

Filed

Aug 24, 2017

To disclose

11 weeks

Affected

1state residents only

Confidence

65%

The Queen Mary notified guests of a data breach involving its third-party reservation vendor, Sabre Hospitality Solutions. Unauthorized access to Sabre's SynXis CRS occurred between August 10, 2016, and March 9, 2017, compromising payment card data and guest PII. Sabre was notified on June 6, 2017. Forensic investigators were engaged, and law enforcement/payment brands were notified.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 300 days

discovery → filing · 11 weeks / 79 days

Aug 10, 2016

Begins

Jun 6, 2017

Discovered

Aug 24, 2017

Filed

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed1 affectedView incident

Name: The Queen Mary
norm: the queen mary

Name: The Queen Mary
norm: the queen mary
Industry: Hospitalityllm

Discovered: Jun 6, 2017
Breach occurred: Aug 10, 2016 – Mar 9, 2017
Undetected for: 300 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 22, 2017
Affected individuals: 1state-resident count only
Data types: Identity (basic)Financial accountFinancial credentials
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Sabre provided notice of this event to law enforcement and the payment card brands
Third party: via Sabre Hospitality Solutions
Initial access: valid_credentials

During the incident: Sabre worked with third-party forensic investigators
Sabre provided notice of this event to law enforcement and the payment card brands
The Queen Mary working diligently to determine the full nature and scope of this event and to identify those customers who may be impacted
Changes made: Working with our third-party vendors, to ensure the protection of data in our care
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 11 weeks(79 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/Queen-Mary-Hotel.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 24, 2017
Raw hash: cd6e9a06e6c75293c5ac66da544fae0a7c484352c0d46b4e5d17fc98aa0b6959

Reporting entityThe Queen Mary

Victim entityThe Queen Mary

Incidentdiscovered Jun 6, 2017

Stated responseSabre worked with third-party forensic investigators

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov