HackingTransportation & LogisticsTransportationStolen CredentialsCapture Stored DataSupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)Financial accountLowContained

Southwest Airlines Co.

bd_ac5974af4b389039 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 22, 2018

Filed

Apr 20, 2018

To disclose

29 days

Affected

555state residents only

Linked

3 filings

Confidence

65%

Full breach record for Southwest Airlines Co. →4 incidents on file

Southwest Airlines Co. notified the Washington AG that Orbitz LLC, a third-party vendor, experienced unauthorized access to its legacy booking platform between Oct 1 and Dec 22, 2017. Access may have included names, payment card numbers, and addresses for 555 WA residents. Southwest's own systems were not affected. Orbitz engaged forensic investigators and law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 172 days

discovery → filing · 29 days

Oct 1, 2017

Begins

Mar 22, 2018

Discovered

Apr 20, 2018

Filed

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

Part of Orbitz Worldwide, LLC supply-chain incident (2018) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

New Hampshire State AGbd_092a29de743168792018-04-20Verified by operator
California State AGbd_f4cde765419b20102018-04-20Verified by operator

Name: BAKER & HOSTETLER LLP
norm: baker hostetler

Name: Southwest Airlines Co.
norm: southwest airlines
Industry: Transportation & Logisticsllm

Discovered: Mar 22, 2018
Breach occurred: Oct 1, 2017 – Dec 22, 2017
Undetected for: 172 daysoccurrence → discovery
Materiality determined: —
Notification sent: Apr 20, 2018
Affected individuals: 555state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Notified Washington Attorney General
Initial access: supply_chain

During the incident: Commenced an investigation
Began working with Orbitz to determine the scope and nature of the incident
Engaged a leading third-party forensic investigation firm and other cybersecurity experts
Began working with law enforcement
Enhanced security and monitoring of the affected platform
Remediated the issue
Took action to eliminate and prevent unauthorized access to the platform
Notified potentially impacted customers and business partners
Changes made: Enhanced security and monitoring of the affected platform
Eliminated and prevented unauthorized access to the platform
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

New Hampshire State AGApr 20 · first

California State AGApr 20 · first

Washington State AGApr 20 · 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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9564.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 20, 2018
Raw hash: fb293c5d76d0d08eb77f2f1bf67a08b323c86fccd8e7b12310a277c1fc7ad5be

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityBAKER & HOSTETLER LLP

Victim entitySouthwest Airlines Co.

Incidentdiscovered Mar 22, 2018

Stated responseCommenced an investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com