Take the 2022 HIMSS Cybersecurity Survey

Between now and December 21, stakeholders are encouraged to offer their responses to help with benchmarking, assessing critical needs, tracking progress, educating federal policymakers and more.
By Mike Miliard
09:50 AM

Credit: Yuichiro Chino/Getty Images

HIMSS and Healthcare IT News are inviting our cybersecurity professional readers to take the 2022 HIMSS Cybersecurity Survey.

HIMSS is seeking stakeholder feedback about the current state of the cybersecurity industry – where it is now and where it's going. Now in its 15th year, the report has tracked the evolution and progress of healthcare privacy and security efforts amid a fast-changing landscape of risk and compliance challenges.

Individual responses will remain confidential; poll results are published in aggregate. The survey will close Dec. 21, 2022.

In early 2023, the results of the survey will be compiled in a report to assess the current cybersecurity environment in healthcare, identify critical needs and help educate policymakers on Capitol Hill and beyond.

Findings from past surveys have shown an industry evolving its response to fast-changing challenges. The 2021 edition, for instance, found most respondents (57%) saying the most significant security incidents involved phishing – not just email phishing, but spear-phishing, voice phishing/vishing, whaling, business email compromise, SMS phishing, social media phishing and more. 

Still, even as cybercriminals were targeting financial information, efforts for more robust security were often stymied by tight budgets. Other challenges included – and continue to include – legacy technology footprints, patchwork security controls and other process and technology inefficiencies.

Make your voice heard with the 2022 HIMSS Cybersecurity Survey.

Email the writer: mike.miliard@himssmedia.com
Healthcare IT News is a HIMSS publication.

Want to get more stories like this one? Get daily news updates from Healthcare IT News.
Your subscription has been saved.
Something went wrong. Please try again.