Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On June 4, 2025, Cisco released fixes for multiple vulnerabilities, several of which were noted to have publicly available proof-of-concept (PoC) exploit code. The most severe issue, CVE-2025-20286, affects cloud deployments of Cisco Identity Services Engine (ISE) on Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI).

In a previous blog, we discussed how AI is reshaping software development at every level. This shift means developers need new skills to stay effective. In fact, Gartner predicts that generative AI will require 80% of the engineering workforce to upskill through 2027. So what can today’s developers do to stay ahead? Here are a few steps to consider.

XML external entity injection or XXE, is a type of web security vulnerability and an application-layer cybersecurity attack. This vulnerability allows the hacker to interfere with an application while it is processing XML data. The attacker can inject unsafe XML entities into the application and can interact with systems to which the application has access. The hackers can also view files on the server and even perform remote code execution (RCE).

In the last year, generative AI has dramatically accelerated how software is written. Developers can generate entire functions with a prompt, automate repetitive logic, and offload everything from boilerplate code to documentation. But with this newfound speed comes a deeper, more complex challenge: ensuring that what’s being created is secure, trustworthy, and production-ready.

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.

OWASP’s API Security Cheat Sheet is a familiar resource for many cybersecurity leaders—often bookmarked, rarely reimagined. But what if this seemingly developer-focused reference held the blueprint for executive-level strategy? For CISOs and CFOs operating in the era of digital ecosystems and financial APIs, this cheat sheet is not just tactical guidance—it’s strategic armor.

With 5+ vulnerabilities being discovered every minute, a SOC 2 (System and Organization Controls 2) compliance certificate demonstrates to customers and partners that the organization is committed to security and adheres to industry best practices for safeguarding data. Apart from customer trust, it can help organizations find and fix security vulnerabilities before attackers can exploit them.

One word defines success or failure in the race to adopt AI in security workflows: trust. While the industry moves fast toward automation and autonomy, adoption often stalls when developers and the teams supporting them can’t trust what the AI delivers. It’s not enough for a tool to explain what it did. Developers want to know: Did it actually fix the problem? Will this change break something else? Can I rely on it again next time? Nowhere is that skepticism more justified than in security.