HackingHospitalityHospitalityBackdoor / C2TargetedPCIFinancial accountIdentity (basic)LowContained

Sentinel Hotel

bd_ef822cbaf636dbd5 · schema v1 · pii pii-v1

Severity

Low

Discovered

Oct 5, 2016

Filed

Nov 4, 2016

To disclose

4 weeks

Affected

4state residents only

Linked

4 filings

Confidence

65%

Full breach record for Sentinel Hotel →

Sentinel Hotel notified guests of a payment card data breach at a front-desk terminal. An unauthorized program copied card data (names, account numbers, expiration, verification codes) from July 12 to October 3, 2016. The incident was discovered on October 5, 2016. Notifications were sent on November 4, 2016. Law enforcement and a security firm were engaged.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 85 days

discovery → filing · 4 weeks / 30 days

Jul 12, 2016

Begins

Oct 5, 2016

Discovered

Nov 4, 2016

Filed

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Massachusetts State AGbd_86cb84feddfd81e32016-11-04Verified
Oregon State AGbd_8f24a8fe27098e172016-11-04Candidate
New Hampshire State AGbd_c65a59af32eb47412016-11-04Verified

Name: Sentinel Hotel
norm: sentinel hotel
Domain: sentinelhotel.com

Name: Sentinel Hotel
norm: sentinel hotel
Domain: sentinelhotel.com
Industry: Hospitalityllm

Discovered: Oct 5, 2016
Breach occurred: Jul 12, 2016 – Oct 3, 2016
Undetected for: 85 daysoccurrence → discovery
Materiality determined: —
Notification sent: Nov 4, 2016
Affected individuals: 4state-resident count only
Data types: PCIFinancial accountIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Regulator citations: notified law enforcement
Initial access: external_remote_services

During the incident: Hired a leading computer security firm to assist
Stopped this incident
Notified law enforcement
Working closely with the payment card companies
Changes made: Work with the computer security firm to further strengthen the security of our systems
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Massachusetts State AGNov 4 · first

Oregon State AGNov 4 · first

New Hampshire State AGNov 4 · first

Montana State AGNov 4 · first · this page

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/Sentinel-Hotel.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 4, 2016
Raw hash: 99f1cee843c03f22e2031f3ea1ce9c7d0fc720e758dc9b0d45bdd9f1677ac655

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entitySentinel Hotel

Victim entitySentinel Hotel

Incidentdiscovered Oct 5, 2016

Stated responseHired a leading computer security firm to assist

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov