Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

According to a report, 71% of energy industry professionals consider their organizations more vulnerable to OT cyber events than ever. These are private organizations, but the stakes are much higher for government-owned systems. Government-owned energy systems such as national grids, nuclear facilities, pipelines, and strategic reserves are foundational to national sovereignty and public welfare.

Your business depends on APIs, which are essential for contemporary digital experiences, encompassing everything from mobile applications and IoT devices to the rapidly evolving AI landscape. With more than 80% of internet traffic now routed through APIs—a number projected to rise significantly due to AI developments—their security is crucial. Unfortunately, this vital infrastructure faces growing attacks, with these threats being a real and current danger to many.

Back in 2024, Amazon Web Services (AWS) engaged Trail of Bits (ToB) to perform a comparative assessment between several authorization and access management policy languages. If you're unfamiliar with the concept of a policy engine, it's essentially a fully-featured engine that offloads authorization decisions in an application.

The cybersecurity threat landscape is constantly evolving, and Trustwave SpiderLabs has noted one of the fastest-growing threats is Phishing-as-a-Service (PhaaS). PhaaS platforms have become the go-to tool for cybercriminals to launch sophisticated phishing campaigns targeting the general public and businesses. Much like legitimate software-as-a-service platforms, PhaaS offers cybercriminals subscription-based access to powerful phishing tools—without requiring advanced technical skills.

According to the Wallarm Q1 2025 ThreatStats report, 70% of all application attacks target APIs. The industry can no longer treat API security as a sidenote; it’s time to treat it as the main event. NIST seems to be on board with this view, releasing the initial public draft of NIST SP 800-228, a set of recommendations for securing APIs.

Organizations rely on best-in-class solutions for observability and security, and various teams within an organization often have preferences for different platforms. For example, your security team may use a SIEM platform like Microsoft Sentinel and Google Security Operations (SecOps) to detect and investigate threats, while your DevOps teams use Datadog Log Management for real-time troubleshooting and monitoring.

Rate limiting plays a major role in application security, especially when it is about defending web applications from malicious bot attacks, credential stuffing, brute force attacks and excessive API calls. Rate limiting security ensures that systems function properly without overwhelming them. It controls the number of requests a client or a specific IP address can send over a specified time period.

Web and mobile application code protection is a must-have security control. Modern solutions such as application layer firewall help your organisation to keep those assets protected from threats like SQL injection, cross-site scripting and bot-driven attacks. This is where a Web Application Firewall (WAF) comes into the picture. A WAF has the capability of filtering, monitoring and blocking HTTP requests to protect the assets from malicious requests without affecting legitimate users.

The management of user access to an organization’s assets, applications, and systems is never static. Users are coming and going, different roles require different access, and for some, privileged access – elevated permissions and access capabilities granted to specific users or groups of users — is needed for mission-critical business functions.

On June 2, 2025, Hewlett Packard Enterprise (HPE) released fixes for multiple vulnerabilities affecting HPE StoreOnce VSA, an enterprise backup storage solution. The most severe of these was CVE-2025-37093, a critical authentication bypass vulnerability discovered by the Zero Day Initiative (ZDI). The flaw resides in the implementation of the machineAccountCheck method and stems from improper handling of an authentication algorithm.