FortiBleed Activity Continues as Healthcare Fintech Security Protocols Face Scrutiny
Help Net Security reports that the FortiBleed vulnerability remains active while hospital CISOs evaluate fintech vendor security practices for patient data and funds.
Key points
- FortiBleed vulnerability activity persists according to recent security news reviews.
- Hospital CISOs are prioritizing security questions for healthcare fintech vendors.
- Cylerity integrates security work into every software development sprint.
The FortiBleed vulnerability remains an active threat in the current security landscape, according to a weekly review by Help Net Security. Concurrently, healthcare organizations are intensifying their scrutiny of fintech partners to protect sensitive patient information and financial disbursements.
What happened
Help Net Security published a weekly review highlighting that FortiBleed activity continues without resolution in the immediate timeframe. The report also featured an interview with Drew McCombs, the CTO and CISO at Cylerity, regarding operational security. McCombs explained how his organization balances technical leadership with security responsibilities in a healthcare fintech environment. The discussion focused on specific protocols for handling sensitive data during software development and operational workflows.
Why it matters
Hospital CISOs are increasingly required to vet healthcare fintech partners for robust controls over patient data and funds. According to the Help Net Security interview, security tasks are scheduled into every software sprint at Cylerity. Issues that touch patient data or funds disbursement receive the highest priority in this workflow. This approach ensures that security is not an afterthought but a core component of development.
What to watch
- Monitor for new patches or mitigation guidance regarding FortiBleed from Fortinet.
- Review vendor security questionnaires for healthcare fintech partners.
- Verify that third-party vendors isolate protected health information from banking partners.
- Assess whether development teams integrate security checks into every sprint cycle.
What to do and how to stay safe: FortiBleed
- Audit all third-party fintech vendors to ensure they have strict data isolation protocols for patient information.
- Require vendors to demonstrate that security tasks are integrated into every software development sprint.
- Verify that any vendor handling funds disbursement has dedicated controls separate from general data processing.
- Monitor vendor communications for updates on known vulnerabilities like FortiBleed affecting their infrastructure.
General security guidance from the Firewall Chronicle newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Is FortiBleed still a threat?
Yes, Help Net Security reports that FortiBleed activity remains active in their recent security news review.
How does Cylerity handle security in development?
Cylerity schedules security work into every sprint, prioritizing issues that involve patient data or funds disbursement.
What should hospital CISOs ask fintech vendors?
CISOs should ask how vendors keep protected health information separate from bank partners and prioritize security in sprints.
