AWS Security Hub Now Watches Azure As AI Workloads Become A Bigger Target

AWS Security Hub is moving beyond its home turf. Amazon Web Services has expanded the security service so it can monitor Microsoft Azure resources while also adding new AI workload protections for companies running foundation models and AI agents on AWS.

As reported by The New Stack, is less about one new dashboard and more about a shift in enterprise security. Companies no longer run neat, single-cloud environments. They run AWS, Azure, SaaS tools, endpoint systems, AI models, developer experiments and external APIs, often with security teams trying to stitch the risk picture together after the fact.

AWS says Security Hub now monitors Azure resources, including Azure Virtual Machines, Azure Container Registry images, Azure Function Apps and Azure identities. The service evaluates those resources for misconfigurations, internet exposure and software vulnerabilities, including checks aligned with the CIS Microsoft Azure Foundations Benchmark.

That means Azure findings can now appear beside AWS findings in the same prioritised view, using the same finding format, automation and response workflows. For security operations teams that already live inside AWS Security Hub, this removes some of the friction of moving between separate cloud consoles and different severity models.

The cloud-security problem is becoming more urgent as AI agents and AI workloads enter production. Recent stories around over-eager AI coding agents and context bombing as a defence against AI attackers show why security tooling now has to understand both cloud infrastructure and AI behaviour.

AWS is not pretending Azure does not exist. That is the interesting part. Most enterprises use more than one cloud because of acquisitions, regional needs, developer preference, compliance requirements or relationships with specific vendors. Security teams often inherit that complexity whether they wanted it or not.

In a multicloud environment, the risk is rarely isolated. A weak identity policy in Azure, an exposed workload in AWS, a vulnerable container image and a misused service account can belong to the same business process. If each signal lives in a different tool, analysts spend too much time reconciling alerts and too little time fixing the real exposure.

Security Hub’s Azure support is therefore AWS trying to become the operating layer for risk, not just the security console for its own cloud. Microsoft Defender for Cloud and third-party platforms such as Wiz still have strong positions, but AWS is making a clear argument: if your security centre of gravity is already AWS, Azure risk should come there too.

The Azure expansion arrived alongside a broader AWS security push around AI. In a July 14 security blog post, AWS introduced GuardDuty AI Protection, AI-powered investigations and Security Hub AI inventory.

GuardDuty AI Protection is designed to detect unusual model invocations in Amazon Bedrock and Amazon SageMaker. One of the risks AWS calls out is cost harvesting, where attackers use stolen credentials to run expensive foundation-model inference at the victim’s expense. That is a very AI-era attack: the thief is not necessarily stealing data first; they may simply be stealing compute.

AI-powered investigations, available in preview, use AI agents to analyse GuardDuty findings, related account activity, threat indicators and context so security teams can separate genuine threats from noise faster. AWS says investigations can return confidence scoring, MITRE ATT&CK classification, supporting evidence and recommendations to suppress, contain or remediate.

Security Hub AI inventory tackles a more basic problem: many organisations do not know where all their AI assets are. The inventory can discover managed AI services such as Bedrock and SageMaker workloads, and it can also identify models running on EC2, ECS and EKS or external model endpoints being called from AWS workloads.

Cost harvesting deserves attention because it is easy to underestimate. In the old cloud world, stolen credentials could mean spun-up compute, data theft or crypto mining. In the AI cloud world, stolen credentials can mean large inference bills, unauthorised model use and hidden abuse of expensive AI services.

That changes the security economics. AI workloads can burn money quickly, and abuse may look like legitimate model usage unless the organisation understands what normal invocation patterns look like. GuardDuty AI Protection is AWS saying that foundation-model usage now needs the same kind of anomaly detection that cloud accounts and workloads already require.

This also matters for finance and engineering teams. If an AI bill suddenly spikes, that may not only be a usage problem. It may be a security signal. Companies need cloud cost monitoring and security monitoring to talk to each other more closely than before.

The promise of unified security is attractive, but it comes with a warning. Security teams do not need another place where alerts go to pile up. They need better prioritisation, fewer duplicate findings, clearer ownership and faster remediation.

AWS is trying to answer that by using the same formats, workflows and automation paths across AWS and Azure findings. Its broader Security Hub Extended ecosystem also leans on the Open Cybersecurity Schema Framework so third-party tools can share security data in a more standard way.

The hard part will be correlation. It is one thing to collect findings from several clouds and vendors. It is another to understand which signals form one attack path, which assets matter most, which alerts are harmless and which remediation step should happen first.

For AWS-heavy companies with some Azure footprint, the new Security Hub support could be immediately useful. It lets teams monitor common Azure assets without building a completely separate response process for every environment. The 30-day Azure monitoring trial also makes the feature easier to test.

For Azure-first companies, this will not replace Microsoft Defender for Cloud. Microsoft will still have deeper native visibility into many Azure services. But AWS is not aiming only at Azure-first buyers. It is aiming at the messy enterprise middle, where workloads and teams are already split across providers.

The AI additions may end up being just as important as the Azure support. As AI workloads multiply across organisations, security teams need to know which models exist, which infrastructure supports them, who can call them, what normal usage looks like and how quickly abuse can be contained.

Multicloud security used to mean watching servers, identities and storage across providers. In 2026, it also means watching AI models, agents, inference costs and prompt-driven abuse. AWS Security Hub’s Azure and AI updates show how quickly the definition of cloud security is expanding.