According to Gartner's March 2022 API survey, a staggering 98% of organizations currently use or plan to use internal APIs, up from 88% in 2019. Additionally, 90% of organizations utilize or have plans to utilize private APIs provided by partners, up from 68% in 2019.

Focusing solely on protecting your public-facing APIs leaves a significant blind spot in your API security posture. Our latest findings, detailed in the Q1-2023 API ThreatStats™ report infographic, confirm this fact.

In our analysis of publicly released API vulnerabilities during Q1-2023, we observe an increase in the number of vulnerabilities, with severity levels consistently in the High range. However, as past reports have revealed, it's what lies beneath the surface that can have a substantial impact.

For detailed insights, we encourage you to explore the complete report on the Wallarm blog. 

We are excited to announce the integration of Wallarm End-to-End API Security with Amazon Web Services (AWS) S3. We understand that investigating incidents can be a complex and time-consuming process. With this new integration, Wallarm can now export detected malicious requests to AWS S3 for in-depth analysis and security incident investigation. 

This integration enables security analysts to:

• Receive detected malicious requests from Wallarm to AWS S3
• Conduct detailed analysis and investigations of security incidents
• Correlate data from different sources to gain a comprehensive view of security events

By integrating Wallarm API Security with AWS S3, we are making it easier for security teams to detect and respond to security incidents quickly and effectively.

You can find more detailed information on this capability in our documentation.

Shadow APIs are undocumented or unmonitored public APIs that pose a significant security risk to an organization. These may include third-party APIs and services that the company uses but does not track, or in-house developed tools for internal or customer use. The new Wallarm API specification comparison feature allows security and operations teams to discover Shadow APIs.

Shadow APIs put businesses at risk, as attackers can exploit them to gain access to critical systems, steal valuable data, or disrupt operations, further compounded by the fact that APIs often act as gatekeepers to critical data and that a range of OWASP API vulnerabilities can be exploited to bypass API security. Recent reports highlight that the majority of businesses have Shadow APIs that are vulnerable to attacks, and cybercriminals are increasingly targeting these weaknesses.

With Wallarm's solution, SecOps and Security Analyst teams can now identify Shadow APIs, including external, internal, and 3rd party developed APIs. The solution gives security teams the ability to compare and validate their API specifications with the ones automatically built by Wallarm API Discovery. In this way, the SecOps and Security Analysts can detect any discrepancies that may indicate the presence of Shadow APIs, allowing them to quickly take action to mitigate potential security risks.

Don't wait until it's too late - start using Wallarm's new Shadow API detection feature today and safeguard your API infrastructure from potential attacks!

Wallarm, a leading provider of application security solutions, offers new integration with Jira, a popular issue and project tracking tool. With this integration, Wallarm will automatically create issues in these service for any vulnerabilities that it detects, making tracking and managing security issues easier.

By integrating Wallarm with Jira, SecOps teams can streamline their security operations and make it easier to identify and resolve vulnerabilities quickly. The automatic creation of events means that security teams no longer need to manually transfer information between services, saving time and reducing the risk of errors. This integration helps SecOps stay on top of their security posture and take action to address vulnerabilities before they can be exploited.

Wallarm is dedicated to helping customers secure their applications and data by providing tools such as the integration with Jira. Wallarm is making it easier for you to leverage the power of issue tracking tools to manage security operations, ensuring that vulnerabilities are identified and resolved quickly and efficiently.

You can find more detailed information about this integration in our documentation.

Wallarm End-to-End API Security solution provides comprehensive protection against the OWASP API Security Top-10 threats. With the new OWASP API Security Top-10 dashboards provide you with complete visibility into the security state of your APIs, easy identification of your most critical security risks, and immediate ability to apply protective measures. 

The OWASP API Security Top-10 list of most commonly seen API threats helps to assess your API infrastructure and prioritize security risks. Additionally, it contains a set of recommendations for mitigating the identified risks. The main problem for defenders is that even with this list, it's incredibly hard to build an API security program, conduct ongoing assessments of different threats, and have adequate security controls and tooling in place. Therefore, defenders must determine which risks are the most critical for their situation and what measures are needed to mitigate those risks. 

Implementing a robust API Security program becomes much easier with the new OWASP API Security Top-10 dashboards from Wallarm. The automated security report enables you to pinpoint the most critical risks in your APIs, thoroughly analyze all associated events, and effortlessly apply appropriate security controls to mitigate them. By combining the strengths of complete visibility with real-time threat prevention, this feature reduces the risk of emerging threats, your workload, and your security costs. 

The new dashboards support both the current version of the OWASP API Security Top-10 2019 as well as the upcoming OWASP API Security 2023 (RC) release, anticipated to be launched later this year. For more detailed information on protection against the OWASP API Security Top-10 threats, please refer to our documentation.

We would like to announce a change in our Wallarm API Discovery module. Previously, we used the term "Removed endpoint" to indicate that an endpoint was excluded from the API inventory because there were no more requests for it. For each endpoint, the date it was excluded from the model was calculated based on statistics showing how often the endpoint was requested.

Going forward, we will be using the term "Unused endpoint" instead of "Removed endpoint" to better reflect the status of these endpoints. An unused endpoint will now be defined as an endpoint that has not been requested in the last 7 days.

Calculating a time interval for each endpoint based on statistics could be non-obvious and difficult to analyze. By simply setting a fixed time period of 7 days, we are simplifying the process and providing a clear and consistent standard for identifying unused endpoints.

We believe that this change will improve the clarity and usefulness of our API Discovery module, making it easier for you to manage your APIs and ensure their security.

You can find more detailed information on this integration in our documentation.

We're thrilled to announce some exciting improvements to our Vulnerability section!

We have made it easier than ever to work with all your vulnerabilities in one place. The new search capabilities in the Vulnerability section will streamline your workflow and eliminate the need to switch back and forth between the Events and Vulnerabilities sections. From finding and analyzing to remediating and managing your vulnerabilities, all of your tasks can now be completed within one window. 

In addition, we moved the Vulnerability Scanner settings to the Vulnerabilities section to make it easier to configure the types of vulnerabilities that are detected.

We hope you find these improvements helpful and look forward to providing an even better experience for our users.

We're excited to announce that our platform now offers improved API token management, which provides more flexibility and control over your API access to the Wallarm platform.

This new feature allows you to set token permissions at a granular level to limit access to specific data objects that Wallarm operates with: data on attacks or vulnerabilities, or nodes or API catalog, etc. It’s also possible now to set token expiration time based on your specific needs. 

You can easily assign and manage your own tokens, ensuring that you have the precise level of access required for different integrations with Wallarm. Administrators can also create shared tokens that are accessible to other admins, and even generate tokens based on existing roles, offering even more flexibility in access control.

The new API token management feature provides new opportunities for automating the deployment of Wallarm nodes, allowing you to create node groups and manage them more conveniently. 

Note: Existing tokens will remain valid, and all integrations that use them will continue to function normally. However, we recommend that you create new tokens for any new integrations to take advantage of the new functionality.

You can find more detailed information about API tokens in our documentation.

We're excited to announce that Wallarm node 4.6 is now available!

The most important thing about this new release is the API Rate Limiting feature. The lack of proper rate limiting has been a significant problem for API security, as attackers can launch high-volume requests that can cause a denial of service (DoS) or overload the system, which hurts legitimate users. Overall, the lack of API Rate Limiting feature can result in a poor user experience, frustration, and potential security risks for both the user and the API infrastructure.

The usual way of limiting the number of requests made to an API is by blocking the IP address. However, this method can sometimes wrongly identify legitimate users as malicious and prevent them from accessing the service. Consider a SaaS application that provides an API to its customers. Each customer has their unique API key to access the service. To ensure that API consumption is fair and prevent misuse, you decide to implement rate limiting. Traditional rate limiting that relies on IP addresses would not work well in this case because multiple customers may be sharing the same IP address. For example, this can happen when customers are behind a corporate firewall or using a VPN.

With our API Rate Limiting, security teams can effectively manage the service's load and prevent false alarms, ensuring the service is always available and secure for real users. This powerful feature gives security teams more control over protection against bad bots and other bad actors. 

Security teams can now set specific parameters and session settings to apply rate limit rules based on any request parameter, including JSON fields, base64 encoded data, cookies, XML fields, and more. 

You can also adjust settings like the rate, burst, delay, and response code to fine-tune the rate limit settings and apply session settings to specific requests. Configuration is done within the Wallarm Console.

It's important to note that with version 4.6, you can only register Wallarm nodes in the Wallarm Cloud using a token. Registering with user credentials is no longer supported. If you used any user credentials to deploy the Wallarm node, you need to generate a token that will be used to register the nodes in the Wallarm Cloud. Instructions for generating a token are provided in the documentation. 

A more detailed changelog and instructions on upgrade are published in the official documentation.

If you have any questions, feel free to contact our support team at support@wallarm.com  

Wallarm is pleased to announce a new native integration of the Wallarm End-to-End API Security solution with Microsoft Azure Sentinel, a powerful combination that delivers advanced security capabilities to safeguard your API. Azure Sentinel is a cloud-based service that collects large volumes of data from various sources, including user data, cloud services, and endpoints to help security teams detect, investigate, and respond to security threats using AI and ML. This integration offers real-time reporting about detected malicious requests, vulnerabilities, changes in security settings and other important events. All of this allows security teams to respond promptly and effectively to potential threats.

The integration of Wallarm with Microsoft Azure Sentinel provides a comprehensive and holistic approach to API security. By having all relevant events in one place, security teams gain deep visibility into their API landscape, enabling analysts to detect, investigate, and respond to threats proactively, reducing the risk of data breaches and other security incidents. 

At Wallarm, we understand the importance of protecting your APIs from potential threats. Our native integration with Microsoft Azure Sentinel provides security teams with a comprehensive view of their API landscape. Take advantage of this powerful combination for best-in-class API security today.

You can find more detailed information on this integration in our documentation.