LIVE · cybersecurity feed
Live wire
patch

Three questions a hospital CISO should ask a healthcare fintech vendor

A cybersecurity expert has outlined key questions hospital CISOs should pose to healthcare fintech vendors to assess their security posture, particularly concerning patient data and financial transactions. Drew McCombs, who holds both CTO and CISO roles at Cylerity, emphasizes that security should be an integral part of development processes, not an afterthought, especially when patient data…

ZeroDay News ·

Source: Help Net Security

A cybersecurity expert has outlined key questions hospital CISOs should pose to healthcare fintech vendors to assess their security posture, particularly concerning patient data and financial transactions. Drew McCombs, who holds both CTO and CISO roles at Cylerity, emphasizes that security should be an integral part of development processes, not an afterthought, especially when patient data or funds disbursement are involved.

McCombs highlighted that his company, Cylerity, operates as a funding provider for healthcare organizations through a bank credit facility, serving businesses rather than consumers. This distinction means that while core banking regulations don't apply directly, the partner bank's expectations are conveyed through credit agreements and due diligence, covering customer types, fund movement, reporting, and audit capabilities. A critical area of focus is collateral, as Cylerity lends against healthcare claims that contain Protected Health Information (PHI). To manage this, Cylerity employs a strategy of using the minimum necessary data, providing summarized information at the payer or customer level, and creating unique identifiers for claim-level details to prevent PHI exposure to banking partners. PHI is consistently kept separate from financing data across their platform.

When it comes to artificial intelligence, McCombs insists on a strict "human-in-the-loop" control. AI models are permitted to recommend, summarize, or flag information, but a human must always be involved before any action is taken that could release funds or expose patient data. This approach integrates AI insights into underwriting and monitoring processes, providing teams with more information for decision-making without relinquishing human oversight. Explainability is crucial, with models required to show the source data for their recommendations, allowing human reviewers to verify against original sources rather than the model's self-explanation. To combat "gradual drift" where reviewers might become complacent, multiple individuals are involved in decisions, and regular post-decision reviews are conducted.

For small practices, a common and easily rectifiable weakness is the underutilization of multi-factor authentication (MFA). McCombs stresses that enabling MFA, particularly for email, is the most impactful and cost-effective fix, as it is often already included in existing email services. This measure significantly reduces the risk of account takeover and payment fraud. Furthermore, Cylerity actively monitors customer claims and funding activity for unusual patterns and confirms all deposit account changes via a pre-registered phone number, never one provided in the change request.

McCombs proposes three essential questions a hospital CISO should ask a fintech vendor. First, "Can you list every party that touches our data, including subprocessors, AI services, and any financing partners or their auditors?" A vendor's inability to quickly produce this list indicates a lack of awareness regarding data flow. Second, "How do you verify a change to where funds are sent?" The desired answer should detail an unskippable, out-of-band confirmation step, rather than a vague statement about careful review. Finally, "Walk me through the first 24 hours after you discover a breach involving our data. Who calls whom?" CISOs should seek specific names, roles, and timelines, not just a policy document.

A definitive red flag that should prompt a CISO to disengage from a vendor is the claim, "We're HIPAA certified." McCombs clarifies that no official HIPAA certification exists, indicating either a misunderstanding of the regulations or an attempt to mislead.

patchaihealthcarefinance
ShareXLinkedInWhatsAppFacebook

More News

view all →
vulnerabilitycritical

VMware patches vCenter zero-day exploited in attacks since September

Broadcom has released emergency security updates for VMware vCenter Server to address a critical authentication bypass vulnerability, identified as CVE-2026-123890. The flaw resides within the VMware Directory Service (vmdird) and allows an unauthenticated attacker with network access to the target server to bypass authentication protocols. By successfully exploiting this vulnerability, an…

vulnerabilitycritical

ASUS warns of critical hard-coded key flaw in Control Center Express

ASUS has issued urgent security updates for its Control Center Express platform to address a trio of critical vulnerabilities that could grant remote attackers full administrative control over management consoles and the hardware they monitor. The most severe of these, tracked as CVE-2026-114202, carries a maximum CVSS score of 10.0. This flaw stems from the use of a hard-coded cryptographic…

vulnerability

nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them

Five new vulnerabilities affecting the NGINX web server have been identified, prompting security teams to emphasize the importance of origin protection and timely patching. These security flaws, which vary in potential impact, highlight the ongoing risks associated with widely deployed open-source infrastructure. While the specific details of the vulnerabilities are being analyzed by the…

nation-statecritical

Sean Cairncross out as national cyber director

Sean Cairncross has departed his role as the national cyber director, marking a significant leadership transition within the Office of the National Cyber Director. The White House confirmed the change, noting that the decision to remove Cairncross was supported by President Donald Trump, who reportedly determined that Cairncross lacked the specialized technical and cybersecurity credentials…

security

Android developer verification will reach every install source, with a side door for power users

Google is set to expand its Android developer verification program to a global scale starting in January 2027. This initiative, which mandates that developers confirm their identities and register their applications, aims to standardize security protocols across the entire Android ecosystem. While the program has already been active in Brazil, Indonesia, Singapore, and Thailand since September…

ai

Qwen Incidents Show Self-Hosted AI Models Need Stronger Steering

Recent reports indicate that organizations deploying self-hosted AI models are facing significant challenges in maintaining operational control over their autonomous agents. These incidents highlight a recurring gap between the perceived level of oversight and the actual behavior of large language models when integrated into enterprise workflows. As businesses increasingly rely on these…