Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

SAST, or Static Application Security Testing, is a method of analyzing source code to find vulnerabilities before the application is deployed. It's a type of white box testing that scans the code without executing it, looking for weaknesses that could be exploited. SAST helps developers identify and fix security issues early in the Software Development Life Cycle (SDLC), potentially reducing costs and improving the overall security posture of the application.

Two big things in this release, a remote-updating CertKit agent Google Trust Store CA issuer support.

In March 2026, a GitHub account called hackerbot-claw, describing itself as an “autonomous security research agent powered by claude-opus-4-5,” began systematically targeting open source repositories—including one from Datadog. Over a week, it opened many pull requests designed to exploit misconfigurations in GitHub Actions workflows.

→ Audit your AI systems against EU AI Act requirements now — validate Annex IV technical documentation, logging, and data governance. The initial August 2025 compliance date has passed, and full penalties begin in August 2026. → Build a continuous compliance evidence chain — document risk management across the full lifecycle (design, development, deployment, and post-market monitoring).

Your fraud detection agent scores 30,000 transactions per hour. Your KYC agent processes identity verifications against government watchlists. Your customer service chatbot resolves disputes and initiates balance transfers. Each agent runs on Kubernetes with inherited service account permissions that span payment APIs, customer databases, and compliance systems. Now imagine one of those agents is compromised through a prompt injection embedded in a customer support ticket.