Breaking into an organisation’s IT infra doesn’t always require complex methods. Hackers often exploit normal applications and API functions in unexpected ways to access sensitive data. For example, the 2019 Venmo breach involved the exploitation of an open API to scrape millions of payment records. A design oversight in the API allowed attackers to exploit its normal functions in an unintended manner—scraping payment records without proper authorization.

Business continuity is at the forefront of most systems and process design at Indusface. In a recent blog, we discussed how Indusface follows design-for-failure principles a powerful approach that enables us to deploy faster. In this blog, I will talk about the processes we have to ensure that our code and rule deployments do not cause widespread downtime to our protected assets.

Discover the power of our new WAAP dashboard, designed to effortlessly monitor, analyze, and enhance your security posture—all in real time. The dashboard provides enhanced visibility and actionable insights to secure assets, prioritize remediation, and address critical exposures. Instantly find answers to questions such as: What is my application’s protection status? What common attacks does the WAAP protect against? Which countries are the top sources of blocked traffic?

By now, everyone is aware of the CrowdStrike Falcon update that caused major disruptions to key services such as hospitals, flights, news channels, and millions of end-user and cloud-based Windows machines worldwide. Details, including recovery options, can be found in the CrowdStrike advisory. At Indusface, designing for failure is a core tenet that we use while building all our SaaS products. After all, despite the best processes, checks, and balances, any system can fail.

Apache HugeGraph-Server, a popular open-source graph database tool, has been found to have a critical security vulnerability tracked as CVE-2024-27348. The vulnerability allows remote code execution (RCE), giving attackers the ability to execute arbitrary commands on vulnerable servers. This blog explores the details of this vulnerability, its impact, and the necessary mitigation steps to protect affected systems.

As the importance of APIs continues to grow and API traffic accelerates, ensuring their secure functionality is no longer an option—it is a necessity. Just think about recent hacks like the ones at T-Mobile and Finsify’s Money Lover app – which left millions of users exposed and vulnerable. As cyber threats evolve faster than ever, the quest for the perfect API security solution becomes a mission. With so many options, how do you know which fits your needs?

Over 100,000 websites fell victim to a recent web supply chain attack through the Polyfill JavaScript library. This incident underscores significant vulnerabilities in third-party script integration across the web. This article covers what Polyfill does, why it’s now a threat, and the steps you should take if your website relies on it.

Our latest application security report shows a significant rise in bot attacks, jumping from 59.4 million in Q1 2023 to 147 million in Q1 2024—a 147% increase. These automated programs can disrupt services, compromise sensitive data, and threaten the integrity of online operations. To effectively mitigate these risks, businesses must adopt a robust bot protection solution.

The cloud offers unparalleled flexibility and scalability, from data storage to maintaining an online presence. However, this increased reliance on cloud infrastructure also brings heightened risks, particularly from DDoS attacks. Recent incidents underscore the urgent need for robust DDoS protection. For instance, the HTTP/2-based DDoS attack peaked last August, reaching over 398 million requests per second.

An application layer DDoS attack, also known as a Layer 7 (L7) DDoS attack, targets the application layer of the OSI model. This type of DDoS attack focuses on disrupting specific functions or features of a website or online service. Layer 7 attacks leverage loopholes, vulnerabilities, or business logic flaws in the application layer to orchestrate the attacks. Here are the key characteristics and methods: Examples of L7 attacks are Slowloris, GET/POST Floods, etc.