Prevention and recovery took center stage as major platforms rolled out new controls while urgent fixes landed elsewhere. Microsoft set out an ambient, autonomous approach to governing AI agents across its stack, and AWS introduced flat‑rate CloudFront bundles with WAF and DDoS protections turned on by default. Meanwhile, an actively exploited Chrome flaw and live attacks on Fortinet’s FortiWeb kept patching priorities high, and Cloudflare recovered from a global outage that interrupted core proxy traffic.
Autonomous defenses and fleet recovery gain ground
At Ignite, Microsoft described a broad strategy to make security ambient and autonomous across the AI stack, introducing Microsoft Agent 365 to register, govern, and quarantine agents, and positioning Microsoft Sentinel as an agentic platform that powers Security Copilot across Defender, Entra, Intune, and Purview. As part of that effort, Security Copilot agents are now included for eligible Microsoft 365 E5 customers, with rollout beginning immediately and new interactive features in public preview; early trials cited faster phishing triage and improved conditional access tuning. Details are in Security Copilot. Complementing Microsoft’s governance approach, Palo Alto Networks embedded Prisma AIRS runtime protections into Azure AI Foundry so prompts and model outputs can be scanned in real time for injection, exfiltration, malicious code, and toxic content during development and deployment, as described by Palo Alto. Together the updates target observability, policy, and runtime safeguards for agentic applications.
Microsoft also focused on resilience at the OS layer. New Windows 11 recovery features—Point‑in‑Time Restore and Cloud Rebuild—aim to shrink remediation from hours or days to minutes by taking complete snapshots and enabling Intune‑driven reinstalls that re‑enroll devices and restore policies via Autopilot; Quick Machine Recovery was updated to streamline diagnostics when WinRE launches after failures. A preview is planned in an upcoming Insider build, with integration into Intune in the first half of 2026, per BleepingComputer. In parallel, Microsoft will natively integrate Sysmon into Windows 11 and Windows Server 2025, enabling deployment through Windows Optional Features and updates via Windows Update while keeping the familiar configuration model and event coverage for threat hunting; see BleepingComputer. These additions strengthen recovery workflows and endpoint telemetry without requiring separate tools.
Cloud security and scale updates on AWS
AWS introduced flat‑rate pricing plans for CloudFront that bundle content delivery with security and edge capabilities—including AWS WAF, DDoS protections, Route 53, CloudWatch Logs ingestion, edge compute, and S3 credits—so traffic spikes or DDoS events do not automatically create overage charges. The plans come in Free, Pro, Business, and Premium tiers while pay‑as‑you‑go remains available. For secure file ingestion, AWS also published an AWS Transfer Family Terraform module that automates malware scanning of files delivered to S3 via managed transfer endpoints, routing suspicious items to quarantine and sending notifications, as outlined in AWS Transfer Family. Default‑on protections and turnkey scanning reduce operational exposure for internet‑facing workloads.
For auditability of search workloads, Amazon OpenSearch Serverless now emits detailed data‑plane events to CloudTrail, capturing reads, writes, authorization attempts, and index operations with filters to manage event volume and S3 delivery for retention, according to OpenSearch. At the infrastructure layer, AWS made Amazon EC2 P6‑B300 instances generally available, pairing eight NVIDIA Blackwell Ultra GPUs with 2.1 TB of high‑bandwidth GPU memory, higher networking bandwidth, and improved TFLOPS and memory capacity versus P6‑B200 for large‑scale training and inference; see EC2 P6‑B300. The combination supports both compliance‑driven logging and AI workload scaling.
Language platform updates also landed: AWS Lambda added support for Python 3.14 as a managed runtime and container base image across all Regions, including GovCloud and China, with automatic runtime updates; tooling compatibility spans the Lambda console, CLI, SAM, CDK, and CloudFormation. Teams should validate dependencies and recompile native extensions during migration, per AWS Lambda. Managed updates can reduce patching overhead while reinforcing the need for pre‑deployment testing.
Advisories and active exploitation
Google issued an out‑of‑band Chrome update to fix a high‑severity type confusion flaw in the V8 JavaScript engine, tracked as CVE‑2025‑13223, confirming in‑the‑wild exploitation and urging immediate updates to version 142.0.7444.175/.176 on desktop platforms; more details are in CSO. Separately, a chained design/implementation issue in Fortinet FortiWeb (CVE‑2025‑64446) enables unauthenticated admin access via path traversal and header abuse; researchers reported active exploitation and CISA added it to KEV. Fortinet released fixes and advised restricting or disabling HTTP/HTTPS on internet‑facing management interfaces when immediate upgrades aren’t possible, according to CSO. Urgent patching and interface hardening are warranted to limit exposure.
Cloudflare outage and recovery
Cloudflare experienced a global service disruption beginning around 11:20 UTC that produced elevated 5xx errors as a core proxy module failed after a metadata change in ClickHouse led to duplicate columns in a Bot Management feature file. The file exceeded the module’s preallocated feature limit, causing a Rust panic and triggering intermittent failures while different nodes alternately produced good and bad files. Impact spanned CDN and security services, Turnstile, Workers KV, and dashboard logins. Engineers halted bad file generation, injected a last‑known‑good configuration, and restarted the proxy, restoring most traffic by 14:30 UTC with full recovery at 17:06 UTC. The company emphasized the incident was not malicious and committed to hardening configuration handling, adding kill switches, and reviewing failure modes, per Cloudflare. For operators, the incident underscores how internal configuration pipelines can cascade into front‑door service failures.