Healthcare Security Pros Must Speak More Like CFOs
Financial Impact of Breached Protected Health Information report helps health IT pros make the business case for patient data protection.
As the number of healthcare data breaches continues to snowball, executives put in charge of safeguarding protected health information (PHI) can't keep up with the risks inherent with increased deployment of electronic health records (EHRs) without enough financial backing to get the job done. And the only way that these PHI protectors can squeeze that juice from the C-suite is if they make themselves fluent in the language of financial justification, say authors of a new report on healthcare IT security.
A collaboration between the American National Standards Institute (ANSI), via its Identity Theft Prevention and Identity Management Standards Panel (IDSP), in partnership with the Santa Fe Group/Shared Assessments Program Healthcare Working Group, and the Internet Security Alliance (ISA), the free report, The Financial Impact of Breached Protected Health Information, took input from 100 healthcare leaders from 70 organizations. It was the culmination of a yearlong initiative called the PHI Project.
According to Rick Kam, president and co-founder of ID Experts and chair of the PHI Project, the team hopes to establish the document as the go-to resource for security and privacy officers taking a disciplined approach to assessing and mitigating risk of healthcare data breaches. He says that the state of the industry is such that those in charge of securing PHI are crying out for guidance.
"Because of the move toward electronic health records and the number of stakeholders that are now involved in handling our sensitive patient information, the PHI protectors are literally being outpaced in terms of their ability to protect our information," Kam says. "The magnitude and the frequency of healthcare breaches has increased rapidly because of the number of stakeholders and the move to electronic health records. These individuals need help."
One of the biggest ways they need help is in simply how to package PHI security issues in a way that makes sense to CEOs and CFOs. He and his co-authors found that these healthcare security initiatives are drastically underfunded and one of the main reasons is no one knows how to make a case for the cash.
"They basically put the CFO and the CEO to sleep because they're talking compliance, talking costs, and talking about things that are not that interesting to these executives," he said. "What we realized is we have to arm that chief privacy officer with the same tools and business case that speaks in investment language to help them enhance their business cases for things that would enhance privacy and security of protected health information."
Healthcare providers must collect all sorts of performance data to meet emerging standards. The new Pay For Performance issue of InformationWeek Healthcare delves into the huge task ahead. Also in this issue: Why personal health records have flopped. (Free registration required.)
Published: 2015-07-27 The kvm_apic_has_events function in arch/x86/kvm/lapic.h in the Linux kernel through 4.1.3 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging /dev/kvm access for an ioctl call.
Published: 2015-07-26 jquery_ujs.js in jquery-rails before 3.1.3 and 4.x before 4.0.4 and rails.js in jquery-ujs before 1.0.4, as used with Ruby on Rails 3.x and 4.x, allow remote attackers to bypass the Same Origin Policy, and trigger transmission of a CSRF token to a different-domain web server, via a leading space cha...
Published: 2015-07-26 The ff_mjpeg_decode_sof function in libavcodec/mjpegdec.c in FFmpeg before 2.5.4 does not validate the number of components in a JPEG-LS Start Of Frame segment, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via craft...
Published: 2015-07-26 Cross-site request forgery (CSRF) vulnerability in Honeywell Tuxedo Touch before 184.108.40.206_VA allows remote attackers to hijack the authentication of arbitrary users for requests associated with home-automation commands, as demonstrated by a door-unlock command.