Incident disclosureDisclosed 2024-07-25Crimson Wine Group, LtdSEC filing

Crimson Wine Group, Ltd discloses a cybersecurity incident with data taken without authorization (SEC 8-K, July 2024)

As previously disclosed on the Current Report on Form 8-K filed by Crimson Wine Group, Ltd. (the “Company”) on July 5, 2024 (the “Initial Report”), on June 30, 2024, the Company detected a cybersecurity incident in which…

What happened

  • As previously disclosed on the Current Report on Form 8-K filed by Crimson Wine Group, Ltd. (the “Company”) on July 5, 2024 (the “Initial Report”), on June 30, 2024, the Company detected a cybersecurity incident in which an unauthorized third party gained access to certain information systems of the Company.Form 8-K Item 1.05, Crimson Wine Group, Ltd, filed 2024-07-25
  • As the Company was in early stages of its investigation and assessment of the incident, it was unable to determine at the time of the Initial Report whether the incident had or will have a material impact on the Company.Form 8-K Item 1.05, Crimson Wine Group, Ltd, filed 2024-07-25
  • On July 25, 2024, the Company determined that the cybersecurity incident has likely had a material impact on the Company’s business operations.Form 8-K Item 1.05, Crimson Wine Group, Ltd, filed 2024-07-25
  • The incident consisted of the third party’s unauthorized access to a portion of the Company’s internal information systems and the exfiltration of certain files, including files potentially containing sensitive personal information.Form 8-K Item 1.05, Crimson Wine Group, Ltd, filed 2024-07-25

The failure pattern

Insufficient segmentation lets a foothold spreadOne compromised account, vendor or network segment reaches management planes, backups and everything else.How to prevent it Audit trail missing actor, target or decisionAfter something goes wrong nobody can tell who or what took the action, on which object, or why.How to prevent it
Watch the pattern: Insufficient segmentation lets a foothold spread

Related standards

CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

Building something similar?

Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

Analyze your design

Incidents with the same pattern