Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Most organizations treat data security and data governance as parallel tracks managed by separate teams with separate tooling. Security owns the controls; governance owns the policies. The two programs rarely share a roadmap, and the gaps between them are where data risk actually lives. Governance without security enforcement leaves policy on paper. Security without governance context produces alerts without the underlying understanding of what the data is, who owns it, or why it matters.

As organizations rush to deploy AI agents across enterprises to handle HR cases, write and execute code, and manage customer interactions, they very often need to grant them access to sensitive systems and data.

Over the years, Dynamic Application Security Testing (DAST) has helped you identify common vulnerabilities via automated scanning, fuzzing, and pattern-based detection. While valuable for baseline vulnerability discovery and compliance requirements, many security leaders, including maybe yourself, are now questioning DAST.

AWS IAM Policy Simulator is a testing tool that helps teams evaluate whether an IAM policy allows or denies specific AWS actions before those permissions are applied in production.

This year's event made it clear that as AI agents scale across enterprises, we must solve ownership, delegation, least privilege, and auditability before production risk grows.

We found 62 live PyPI tokens leaking on public sources, enough to push malicious code to 125 packages with 25,000 monthly downloads. We reported them to PyPI, which revoked every one. Here's how we decoded the macaroons and checked which still worked.

On Jun 24, 2026, the codfish/semantic-release-action GitHub Action was compromised through an imposter commit attack. An attacker force-pushed two malicious commits into the repository and repointed sixteen tags to them, including the floating major version tags v2, v3, v4, and v5. Any workflow referencing the action by one of those tags will pull and run the attacker's code on its next CI run.

In our previous article, From Vulnerability Management to Continuous Security Operations, we explored how organizations are moving beyond traditional vulnerability management toward a model built on continuous visibility, continuous prioritization, and continuous action. But that evolution raises an important question: how do security teams sustain this model at scale? For years, the cybersecurity industry focused on visibility.