NEW INVESTMENT: Volition Capital leads $20M investment in Levanta  Read More

VOLITION NEWS: Sean Cantwell & Roger Hurwitz Named Top Software Investors of 2024  Read More

FOLLOW-ON INVESTMENT: Volition Capital Announces Meaningful Follow-On Investment in Creatio  Read More

VOLITION MEDIA: Why Hardware-Enabled SaaS is a Winning Formula  Read More

< 1 MIN READ

Ping Identity Showcases Solutions for Federated Identity and Secure Mobile Access at HIMSS 201

DENVER, Colo. — February 28, 2013 — Ping Identity®, The Identity Security Company™, today announced it will be showcasing its current and future cloud and mobile identity management solutions for healthcare organizations at the 2013 HIMSS Annual Conference & Exhibition, taking place March 3–7 in New Orleans.

“Healthcare organizations are increasingly taking advantage of the benefits of cloud resources. But managing access to these resources presents significant challenges to healthcare delivery organization’s IT staff, especially in regards to securing protected health information,” said Ping Identity Vice President of Marketing Roger Oberg. “Standards-based cloud identity management eliminates the vulnerabilities inherent in the cloud and enables healthcare organizations to remain in compliance with regulations like HIPAA.”

At HIMSS 2013, Ping Identity will address the identity security challenges that come with the increased adoption of cloud and mobile solutions, and trends such as BYOD. The company will provide demonstrations for secure workforce and customer single sign-on to cloud or internal applications from any device.

For a demonstration, or to talk to a Ping representative about our solutions, secure mobile access, cloud single sign-on and the benefits of federated identity, please stop by the Ping Identity booth (#2470). Ping Identity product demos will be available during all show floor hours.

 

ALL ARTICLES
BACK TO TOP

Consent(Required)
This field is for validation purposes and should be left unchanged.

Consent(Required)
This field is for validation purposes and should be left unchanged.

Consent(Required)
This field is for validation purposes and should be left unchanged.

Consent(Required)
This field is for validation purposes and should be left unchanged.