Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Accurate scoping is one of the most important stages of a penetration testing engagement. It determines what will be assessed, how much testing effort is required, and whether the final results will provide meaningful assurance against the risks an organisation is trying to understand. A scope that is too narrow may exclude important systems, user roles, or integrations.

A user asks an enterprise AI assistant a normal question: “Why did we lose the Acme deal?” The agent does what agents do. It retrieves CRM notes, pricing history, discount approvals, sales leadership comments, and a couple of internal strategy docs, then combines them into one clear answer: “Acme received a 28% discount exception, well above our standard enterprise pricing.

SilverFox is expanding its toolkit. In this campaign, the group combines new vulnerable-driver abuse, newly observed abuse of legitimate applications for DLL sideloading, defense evasion, and layered recovery mechanisms to keep ValleyRAT running. We investigated an active campaign targeting a Japanese organization in the industrial manufacturing sector. The attack begins with an invoice-themed phishing lure and uses attacker-controlled content hosted through legitimate QQ and Tencent Cloud services.

New GenAI code security research shows a stubborn truth: as AI is generating more of the code entering production, secure output is not improving at the same pace. The result is a GenAI code security challenge defined by scale, model choice, and the growing need for verification. AI coding has moved past experimentation. For many teams, it is now part of how software gets built every day. That’s the opportunity. It’s also the risk.

Many organizations still rely on legacy applications to run core business processes. But that comes with limitations. According to the Workforce Agility Report, 50% of CIOs said legacy applications hold back digital transformations. More importantly, they create major security gaps. Most legacy applications, such as Oracle EBS, PeopleSoft, SAP, and JD Edwards, use authentication methods that do not fit modern identity requirements.

Software that runs inside customer-managed infrastructure creates a particular challenge at the FedRAMP High baseline. It still has to meet the applicable security and compliance requirements, even though the vendor does not control the surrounding operating system, libraries, network configuration, or maintenance practices. For Datadog, that challenge centers on the Datadog Agent, which runs directly on customer-managed hosts to collect logs, metrics, traces, and security signals.