Skip to content
‹ Back to IndustriesHealthcare

Making a Connection: The State of Cybersecurity for Industrial Networks

Industrial networks are under threat from cyberattacks. On Feb. 8, Oldsmar, Florida, announced a cyber intrusion into its water treatment system. They detected the attack, but only after network infiltration. David Zaveski, Product Manager at Antaira, spoke about the threats to industrial networks, what makes it easy to infiltrate them, and what IT departments…

This story was produced through MarketScale. See how Healthcare teams put it to work with Executive Thought Leadership.

·
Share
Making a Connection: The State of Cybersecurity for Industrial Networks

Free workspace

Turn your Healthcare expertise into content.

Record interviews, organize footage, and write with AI on a free trial of the MarketScale platform for qualifying companies. No demo required, no credit card.

Try it Free

Industrial networks are under threat from cyberattacks. On Feb. 8, Oldsmar, Florida, announced a cyber intrusion into its water treatment system. They detected the attack, but only after network infiltration.

David Zaveski, Product Manager at Antaira, spoke about the threats to industrial networks, what makes it easy to infiltrate them, and what IT departments can do to prevent such attacks.

Zaveski’s previous roles included working with enterprise networks, and this background gave him a lot of experience in understanding the importance of keeping networks secure. This experience is something he wants to bring to industrial networks, too.

“Industrial networks are quite different from enterprise networks,” Zaveski said. “They are required to have quicker responses across networks, but many are unprotected.”

Many industrial networks are protected from outside cyber interference through “air gapping” their networks by restricting connectivity from the outside. This provides a sense of protection from cyberthreats. And Zaveski said that does protect them. So, why are there breaches?

“What happens is, at some point, another somebody gets the idea that they want to be able to monitor the system remotely, and I want to connect that data and publish it for later planning,” he said. “As soon as they do that and attach that network to the public network, or internet, [risk is there].”

Now, a pathway to infiltrating that once-protected industrial network is created, and the cybersecurity risks begin.

Protocols and devices deployed across a network can keep them more secure. Still, any organization’s most important step is to restrict network access to just what individuals and devices need it, not carte blanche accessibility.

“Look at your network, and say, ‘I know I have A, B, C devices, and I know that A needs to communicate with B and C, but B and C never need to communicate with each other. So, I should block all traffic going from B to C.’ That’s great,” Zaveski said. “Because, now, if somebody hacks in at B, at least they can’t get to C.”

Follow us on social media for the latest updates in B2B!

Twitter – @MarketScale

Facebook – facebook.com/marketscale

LinkedIn – linkedin.com/company/marketscale

Your experts belong here

Every story in MarketScale Healthcare starts with a company putting its clinicians, service-line leaders, and field engineers on the record. Buyers are already reading this topic. The only question is whose experts they find.

Service-line buyers vet vendors quietly, and your clinicians become the proof they find while doing it.

Book DemoSee how it works15 minutes, straight to a calendar.
B2B Weekly

The week in Healthcare, and sixteen other industries, every Monday.

Ten stories, one-line takes, five minutes. Free.

Healthcare: are you visible to AI?

Before they reach out, Healthcare buyers ask AI engines which vendors to trust. Explore how your experts, customers, and partners can become useful content for buyers and AI search.

Free Trial

You just read one Healthcare expert. Your company is full of them.

This article was produced through MarketScale. The same platform turns your clinicians, service-line leaders, and field engineers into the articles, video, and social content Healthcare buyers are searching for. Start a free trial and see it with your own people. For qualifying companies, no credit card, no demo required.

NPS +73 · 1,000+ creators · 38+ countries

What your free trial includes

Hands-on access to the MarketScale platform
Media requests to your crowd, remote recording, AI writing tools
No demo required. No credit card.
For qualifying companies. Company confirmation required.

More Healthcare Insights

Denials get a queue, underpayments just look like paid claims

Denials get a queue, underpayments just look like paid claims

Underpayments in healthcare revenue cycle operations lack the visibility of denied claims because they don't trigger alerts or queue workflows. Without dedicated ownership and line-level verification against contract terms, paid claims that fall short of their contractual amount pass through undetected.

  • 01Denial workflows activate on rejection events, but underpayments produce no event, leaving paid claims unverified by default.
  • 02The speaker says many provider groups lack line-level contract intelligence to check each paid line against the applicable terms.
  • 03Payment received and payment checked are separate tasks: one verifies acceptance, the other verifies correctness—and the second often has no assigned owner.

Nov 6, 2026

A zero-paid claim line is not automatically an underpayment

A zero-paid claim line is not automatically an underpayment

A zero payment on a claim line isn't automatically an underpayment; contract terms, particularly packaging rules, determine whether zero is correct. Chasing unsupported findings damages credibility with payers and weakens the position of legitimate disputes, so revenue cycle teams must verify the full contract terms and effective dates before treating any payment difference as a finding.

  • 01When a contract packages add-ons into the primary procedure, the add-on line may legitimately show zero payment because it is folded into the primary procedure reimbursement.
  • 02Pursuing payment differences that lack contract support burns credibility with payers and can weaken the team’s position on later disputes, including valid ones.
  • 03Always verify the complete contract terms, fee schedules, carve-outs, amendments, and the specific version in effect on the date of service before treating a payment variance as a recoverable underpayment.

Nov 6, 2026

A clean, paid, closed claim can still be short of the contract

A clean, paid, closed claim can still be short of the contract

Practices can receive payment on closed, clean claims that still fall short of negotiated contract amounts because billing ends at coding, submission and posting, while no role owns checking whether payer payments match fee schedules. The speaker argues that contract-level payment review is a separate, complementary function that compares closed claims to contract terms and, run continuously, helps surface shortfalls in time to act within timely filing windows.

  • 01Correctly coded and billed healthcare claims can still result in underpayment.
  • 02Practices should review closed-claim payments against contract terms to spot underpayments.
  • 03Discrepancies in claim payments can persist despite adherence to billing protocols.

Nov 6, 2026

Explore More Healthcare Insights

Read more expert perspectives from across Healthcare.

Browse Healthcare Hub

For B2B teams

Your experts could be publishing here

Stories like this one run on content MarketScale captures from real practitioners. See how your team's expertise becomes coverage in Healthcare and beyond.

Book a Demo

Or call us. No forms required. We pick up. 214-945-2512