Skip to main content

 

 

By Len Shneyder, M3AAWG Abuse Desk SIG, Leader

One of the enduring features across any company of scale, and those that haven’t reached galactic scale, is an abuse desk. The abuse desk takes many forms, is challenged to do a wide variety of tasks from interfacing with angry customers to shutting down abusive accounts and performing complex investigations to prevent fraud, phishing, abuse and at times, much worse crimes. 

Although the roles, jobs, and missions of abuse desks, trust teams and similar constructs, may differ from company to company, the majority of them are always understaffed and underfunded. If we peel back and look at what these organizations do, their role is often preventing or minimizing the loss of revenue. Since these teams do not generate revenue they are cost centers that require personnel, technology, custom tooling and other inputs in order to save revenue, prevent negative PR, customer churn and a range of other possible risks. 

So how does an operator within one of these orgs, or a manager of a team solidly focused on preventing abuse convince their executive team to provide adequate funding for the function? How do you explain to your organization that preventing abuse isn’t a nice to have, that it isn’t a cost center but an investment worth making because critical to both the company and the internet’s long term viability?

Well to put it simply: with numbers. 

In a nut shell technical abuse professionals need to speak the same language as their executive teams. M3AAWG has traditionally focused on the technical aspects of abuse prevention. We’ve put out documents that set high bars for how email should be sent, how to mitigate malware and a myriad of other documents grounded in how you work with the tech. However, this is the first document we’ve released designed to help Abuse Desk managers and personnel structure a financial argument that takes into account the cost of non-action, the potential losses from ongoing abuse, and turn it into the kind of fiscal plan worthy of consideration and discussion by those who may not fully understand the nature of what the Abuse Desk does, and the actual real world costs of that abuse.

The M3AAWG Building a Business Case for an Abuse Desk document is arranged in a logical format that walks the reader through the various steps in building a financial argument to fulfill the needs of a technical anti-abuse function. Those steps include:

  1. The Executive Summary
  2. Defining and Building The Problem Statement: Why Action Is Needed Now
  3. Analyzing and Structuring The Cost Analysis and Return on Investment: The Financial Case
  4. Detailing and Highlighting the Operational Requirements: What’s Needed to Succeed
  5. Uncovering and Highlight the Risk Assessment: What Happens if We Don’t Act?
  6. Structuring and Providing a Conclusion and set of Recommendations Based on Data

By applying both structure and methodology, abuse desk operators can better turn their appeals into solid arguments that not only address the fight against abuse, but the real world costs of ignoring it. 

Too often money is thrown at a problem in times of crisis; Abuse Desks swell with personnel and funding in direct response to a significant incident, a spate of incidents, combatting coordinated and targeted abuse or as the result of a breach. But more often than not that funding is ephemeral and when the abuse and projected costs baseline, then the funding that actually brought that cost down is allocated elsewhere. It’s incumbent on those operators on the front lines to make informed projections about what it means to the company to underfund their abuse desk operations and offer an argument that is contextualized financially instead of simply based on the need to stop bad actors. As noble a cause as that may be, an executive far from the machinations of the Abuse Desk is forced to weigh that need against revenue producing activities that simply put, keep the lights on and the whole train moving. 

Fighting abuse is never as simple as closing an account, it is a multidisciplinary skillset that requires internal savviness to achieve external excellence. We think this document will give well meaning abuse operators a framework to improve what they do and how they do it. 

Additional Resources

You can find additional Best Practices, Best Practices in Multiple Languages and Supporting Documents at M3AAWG.org under For the Industry.

M3AAWG Upcoming Meeting Submissions 

The M3AAWG Program Committee is always looking a few meetings ahead, and we want your ideas to help shape what comes next. General Meeting Submissions are open for Upcoming General Meetings, including the 69th General Meeting in Vancouver, Canada (February 2027) and the 70th General Meeting in Dublin, Ireland (June 2027). If there’s a challenge, emerging trend, or conversation you think the M3AAWG community should be tackling, now is the time to start bringing it forward.