How can Forter improve its Account Protection solution to better detect and prevent account takeover attempts?

Introduction

To improve Forter's Account Protection solution for better detection and prevention of account takeover attempts, we need to dive deep into the current product, user behavior, and emerging threats. I'll analyze key stakeholders, identify pain points, generate innovative solutions, and propose a strategic roadmap for implementation. Let's begin by clarifying some crucial aspects of the product and its ecosystem.

Step 1

Clarifying Questions (5 mins)

• Looking at Forter's position in the market, I'm thinking about the scale and diversity of their client base. Could you provide more information on the types of businesses currently using Forter's Account Protection solution? Are we primarily serving e-commerce platforms, financial institutions, or a broader range of industries?

Why it matters: This helps us understand the variety of account takeover scenarios we need to address and the potential for industry-specific solutions. Expected answer: A diverse client base across e-commerce, finance, and other digital services. Impact on approach: Would focus on developing flexible, customizable solutions that can adapt to various industry needs.

• Considering the evolving nature of cyber threats, I'm curious about the current performance metrics of the Account Protection solution. What are the current false positive and false negative rates for account takeover detection? How have these metrics changed over the past year?

Why it matters: Helps identify whether we need to focus more on improving accuracy or reducing false alarms. Expected answer: False positive rate around 2-3%, false negative rate below 1%, with a slight increase in false positives over the past year. Impact on approach: Would prioritize reducing false positives while maintaining or improving the detection rate.

• Given the importance of user experience in security solutions, I'm wondering about the level of friction currently experienced by legitimate users. What's the average additional time or steps added to the login process for a typical user due to the Account Protection measures?

Why it matters: Balancing security with user experience is crucial for adoption and retention. Expected answer: Average of 5-10 seconds added to login process for most users, with occasional additional steps for high-risk logins. Impact on approach: Would focus on streamlining the verification process while maintaining robust security.

• Considering the rapid advancement of AI and machine learning, I'm curious about the current technological stack of the Account Protection solution. To what extent are we leveraging AI/ML models in our current detection systems, and what types of data are we currently analyzing?

Why it matters: Determines the potential for advanced pattern recognition and predictive capabilities. Expected answer: Currently using some ML models for anomaly detection, primarily analyzing login patterns, device information, and basic behavioral data. Impact on approach: Would explore opportunities to expand AI/ML capabilities and incorporate more diverse data sources for improved detection.