Webinar:Doing Multi-Factor Authentication Right the First Time: 8 Technical Requirements

There’s usually a particular risk or application that pushes management to break down and finally implement multi-factor authentication (MFA). And it’s good to begin with a use-case that provides a quick win in terms of risk reduction and ROI. But I often see organizations rush out and implement a point solution for applying MFA to a hot use case. Then what happens? You’ve brought a technology in, spent money on training, infrastructure, enrollment and gotten users accustomed to a new experience. But you’ve only solved one problem. Invariably one or more of the following happens pretty soon:

– When auditors, regulators hammer on another big risk area
– You implement a new app that also requires MFA to achieve acceptable risk
– An executive gets worked up about the latest exploit in the news and demands a wider adoption of MFA (that’s a good thing)
– A manager leaves who was standing in the way of MFA expansion to a vital business area or technology

Read more at – Doing Multi-Factor Authentication Right the First Time: 8 Technical Requirements