DALLAS & SAN FRANCISCO–(BUSINESS WIRE)–Jul 6, 2021–
Zimperium, the global leader in mobile security, has broadened its portfolio of mobile application protection solutions by acquiring whiteCryption, a leading provider of advanced application shielding and cryptographic key protection. Zimperium acquired whiteCryption from an investment group led by Intertrust, the pioneer in trusted computing and digital rights management (DRM) technology. Zimperium will continue to support current whiteCryption customers and will integrate whiteCryption’s solutions into Zimperium’s Mobile Application Protection Suite ( MAPS ), creating the world’s most advanced mobile application protection solution.
Zimperium MAPS helps enterprises build secure mobile apps that are natively resistant to attacks. MAPS is the only platform that protects mobile apps end-to-end, from in-development to on-device. With the addition of whiteCryption’s technologies, MAPS provides app scanning, app shielding, runtime protection, and protection of sensitive cryptographic keys in one platform. MAPS’ centralized threat management dashboard provides real-time threat visibility and the ability to respond to emerging risks and attacks detected.
“With mobile applications containing and processing an increasing amount of critical personal and business information, the risks and attacks have increased too,” said Phil Hochmuth, Program Vice President of Enterprise Mobility, IDC. “In response, organizations want to unify mobile application protection to improve visibility and prevent security gaps between point products.”
In an ever-expanding world of mobile and IoT devices, mission critical software often runs in an attacker’s back pocket or automobile. Zimperium’s solutions extend the secure perimeter from the app developer’s desktop all the way into the zero-trust environment, providing 360-degree protection.
“To provide our customers with the best security and the most value, Zimperium believes that every part of a unified mobile application protection solution should be…