What the bank was required to demonstrate, what its existing controls could not cover, and how the gap was closed without changing the app source code.
4 pages, PDF. Opens in a new tab, no form required.
Most mobile security case studies describe a product. This one describes a compliance problem and what it took to close it.
The bank was not shopping for mobile security. It had requirements to satisfy on the mobile channel and needed to evidence how.
API gateways, fraud engines and multi-factor authentication were all in place and working. None of them observed the customer device.
The roadmap was committed. Any solution requiring source-code changes or SDK integration would have slipped past the deadline.
Detections had to be logged, exportable and readable by an auditor without a product briefing.
If you are working to a similar mandate, we will map your requirements against what this bank had to demonstrate, and tell you where we do not fit.