Blog

Credential stuffing attacks are some of the most common bot-based threats facing applications today. Virtually any site or application with a login page is a potential target for credential stuffing. In this blog, we take a look at what credential stuffing is, how it can impact your apps and users, and how you can use the ThreatX WAAP++ to keep yourself protected.  

I’m a big fan of the ThreatX agentless architecture. It simplifies many of aspects of deployment and side-steps a lot of the problems with agent-based architecture.

Most anyone who works in application security can tell you that the traditional WAF model has not aged gracefully over the past few years. Facing new challenges from bots, API-based threats, DDoS attacks, and sophisticated evasive attackers, the old guard of WAFs have bolted on module after module in an attempt to keep pace. This has, unsurprisingly, resulted in more complexity, the need for more AppSec talent, and the inability to protect an over-growing application attack surface. 

Modern AppSec and security teams face enormous challenges of scale when it comes to their daily workload. Organizations need to secure more applications and APIs than ever before, and those apps and APIs are under constant attack from increasingly sophisticated methods. Security staff has to parse and analyze an avalanche of alerts and data to stay ahead of bad actors and continuously improve the security posture of their organization. Collectively, this is a perfect storm that can put even the best security teams under intense strain.

By focusing intently on risk-based security, ThreatX delivers a truly modernized approach to AppSec that enables our clients to manage their threat posture in a fundamentally different way. It lets us consistently recognize and stop more legitimate attacks for our customers, vastly reduce false positives, and significantly reduce the fatigue and burden on staff and analysts. Let's take a closer look at what it's all about and why it matters.

Mergers and acquisitions are some of the most important, exciting, and often messy aspects of the business world. Having been through the process several times, both as an acquirer and an acquiree, I can personally attest that technology and security are areas where things can get particularly messy. Buyers and sellers will often have very different approaches to security–different levels of operational maturity, different tools, and different threat profiles. This means that many of the details about security posture and risk only become known after an acquisition is complete. Yikes!

While no technology can tame all the challenges of an acquisition, ThreatX’s web application and API protection +Bot + DDoS (WAAP++) platform can give organizations an easy, yet powerful way to wrestle control over AppSec. Because it can be up and running in just a few hours, ThreatX can help uncover problems during the due diligence process; letting security teams quickly triage and deliver core protections to newly acquired sites and apps after the merger is complete. Let’s take a closer look.

It’s been a little over two months since I joined ThreatX as CEO, and it’s already shaping up to be a fantastic ride. As a leader, these are always some of the most exciting and illuminating days as we start to get our hands dirty and chart the path forward. As always, the most important insights have come from getting to hear directly from a lot of AppSec leaders and practitioners about the real-world challenges they face on a daily basis.  

Most any organization that stores, processes, or transmits payment card data is likely well aware of the Payment Card Industry Data Security Standard (PCI DSS). For these organizations, maintaining and documenting PCI compliance is an ongoing and often laborious process. ThreatX brings a new approach to application security that not only helps address PCI requirements but does it far more consistently across many types of applications and with far less effort than traditional WAFs.