Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The dictionary (at least the online version) defines the word trend as a general direction in which something is developing or changing. It also does have a secondary definition relating to fashion, but unless we want to cover off on some questionable choices I made when younger, we can skip that one. When does something move beyond being a trend, and create a lasting shift in behavior–or for the purposes of our discussion, technology?

In mid-May 2025, Cloudflare blocked the largest DDoS attack ever recorded: a staggering 7.3 terabits per second (Tbps). This comes shortly after the publication of our DDoS threat report for 2025 Q1 on April 27, 2025, where we highlighted attacks reaching 6.5 Tbps and 4.8 billion packets per second (pps). The 7.3 Tbps attack is 12% larger than our previous record and 1 Tbps greater than a recent attack reported by cyber security reporter Brian Krebs at KrebsOnSecurity.

For decades, the United States National Institute of Standards and Technology (NIST) has been guiding industry efforts through the many publications in its Computer Security Resource Center. NIST has played an especially important role in the adoption of Zero Trust architecture, through its series of publications that began with NIST SP 800-207: Zero Trust Architecture, released in 2020.

Over the past few years, enterprises have rapidly integrated GenAI into an increasing number of workflows and use cases. Amidst the rush and excitement to adopt a free tool that significantly boosts productivity, business leaders de-prioritized privacy, till it became a compliance issue. As privacy tools offering a quick patch quickly flooded the market, businesses ran into a new problem – which is the best tool?

Traditionally, securing APIs in AWS has involved a frustrating trade-off. Obtaining a full view of your API Fabric requires weeks or months of deploying various agents, setting up traffic analysis, and enduring lengthy professional services engagements. The outcome? An unacceptably slow time-to-value that keeps you unaware of potential risks for too long. The main issue hasn't only been locating APIs, but also the extensive wait to identify them. But what if that trade-off is no longer necessary?

Launched in 2015 by a community of security researchers and developers, MobSF has continuously evolved to meet the growing challenges in mobile security. Initially focused on static analysis for Android apps, it has since expanded to support dynamic analysis with runtime instrumentation, API fuzzing, malware detection through sandboxing, and seamless CI/CD integration.