Hackers Target Casino Operator Boyd Gaming
Briefly

Hackers Target Casino Operator Boyd Gaming
"Boyd Gaming said in a filing with the SEC that the cybersecurity incident has not impacted its properties and business operations. The Las Vegas-based company is conducting an investigation with assistance from outside cybersecurity experts and law enforcement. The probe has shown that the hackers stole some data from its systems, including employee information and the information of "a limited number of other individuals"."
""As of the date of this filing, the Company believes that the incident will not have a material adverse effect on the Company's financial condition or results of operations," the company said. It added, "The Company maintains a comprehensive cybersecurity insurance policy, which we expect will cover costs associated with incident response and forensic investigations, as well as business interruptions, legal actions and regulatory fines, if any, subject to policy limits and deductibles.""
"It's unclear whether Boyd Gaming was targeted in a ransomware attack. No known ransomware group has taken credit for the incident, but it's not uncommon for such threat actors to target the casino industry. SecurityWeek has reached out to Boyd Gaming for comment and will update this article if the company responds."
Boyd Gaming disclosed a data breach after hackers accessed internal IT systems. The cybersecurity incident did not impact properties or business operations. An investigation is underway with outside cybersecurity experts and law enforcement. The breach resulted in theft of some data, including employee information and the information of a limited number of other individuals. Boyd Gaming believes the incident will not materially affect financial condition or results of operations. A comprehensive cybersecurity insurance policy is expected to cover incident response, forensic investigations, business interruptions, legal actions, and potential regulatory fines, subject to policy limits and deductibles.
Read at SecurityWeek
Unable to calculate read time
[
|
]