{"id":1474,"date":"2026-09-21T23:53:03","date_gmt":"2026-09-22T04:53:03","guid":{"rendered":"https:\/\/cmitsolutions.com\/lasvegas-nv-1206\/?p=1474"},"modified":"2026-09-21T23:53:57","modified_gmt":"2026-09-22T04:53:57","slug":"nevada-courts-vendor-data-breach-las-vegas","status":"publish","type":"post","link":"https:\/\/cmitsolutions.com\/lasvegas-nv-1206\/blog\/nevada-courts-vendor-data-breach-las-vegas\/","title":{"rendered":"Nevada Courts Data Breach: Las Vegas Business Risk"},"content":{"rendered":"
\n Las Vegas Security Brief<\/span><\/p>\n

Nevada Courts Data Breach Exposes a Bigger Risk for Las Vegas Businesses<\/h2>\n

A vendor breach at West Publishing just exposed sensitive records from Nevada’s own court system — and it’s a preview of what’s coming for any business that shares data with a third party.<\/p>\n

Published by CMIT Solutions of Las Vegas · Cybersecurity · 6 min read<\/p>\n<\/div>\n

What Happened: A Breach Nevada’s Courts Didn’t Cause<\/h2>\n

In September 2026, Nevada’s Administrative Office of the Courts confirmed a data security incident tied to a vendor, not to its own network. West Publishing Corporation<\/strong>, the Thomson Reuters subsidiary behind the widely used C-Track case management system, notified Nevada that an unauthorized party had accessed files inside West Publishing’s own IT environment.<\/p>\n

The exposure wasn’t limited to Nevada. Appellate courts in Alabama, Kentucky, Montana, North Dakota, South Carolina, Tennessee, New Hampshire, Wyoming, and the U.S. Virgin Islands were affected, along with multiple Ohio and Pennsylvania courts. West Publishing has said the intrusion actually began in March 2026<\/strong> — meaning the unauthorized party sat inside the vendor’s systems for roughly six months before any of the affected courts, or the public, knew about it.<\/p>\n

The data at risk is not minor: names, Social Security numbers, driver’s license numbers, dates of birth, medical information, and health insurance details tied to court records. West Publishing has been explicit that the incident was not caused by any court’s own network, systems, or security practices — it happened entirely on the vendor side.<\/p>\n

\n The Pattern to Notice<\/span>
\n This wasn’t a failure of Nevada’s court IT security. It was a failure of shared software running quietly in the background of dozens of government systems nationwide — the same pattern behind the MOVEit, Change Healthcare, and Snowflake breaches that have dominated headlines for two years running.<\/em>\n<\/div>\n

How a Vendor Breach Becomes Your Breach<\/h2>\n

Most Las Vegas business owners read a headline like this and assume it’s a government IT problem, not theirs. It isn’t. The mechanics of this breach are identical to the ones that hit private-sector vendors serving small and mid-sized businesses every day — payroll processors, case management tools, cloud backup providers, scheduling software. Here’s what actually happened, technically:<\/p>\n