AWS Security Hub Adds Azure Integration for Cross-Cloud Attack-Path Prioritization

· Original article ↗

Summary

AWS Security Hub’s Azure connector brings Azure resources and alerts into its exposure engine, correlating ranked findings with AWS to help teams prioritize federated-identity attack paths in one console.

Key points

  • The Azure connector records and evaluates Azure resource configurations and streams Microsoft Defender for Cloud alerts and Entra ID audit logs through Azure Event Hubs.
  • Security Hub correlates reachability, effective permissions, misconfigurations, vulnerabilities, and other signals into ranked exposure findings for Azure and AWS.
  • The walkthrough illustrates potential exposures including an Entra administrator without MFA, an internet-reachable Azure VM with subscription-admin rights, and sensitive data in an AWS S3 bucket.
  • The scenario describes configuration-based risks and a possible attack path; it does not report an actual compromise.
  • Because Security Hub produces the findings, the top-level cloud provider is AWS; use resources.provider to filter for Azure resources.
  • A healthy connector status does not guarantee that resources are being recorded; confirm that Azure Activity Logs reach the event hub and create a remediation task if existing subscriptions lack the required diagnostic setting.
  • Security Hub does not raise a finding for a role trusting the organization’s own federated identity provider, so analysts must verify that cross-cloud link in AWS IAM.

Article Details

Defense Focus
Correlate cross-cloud identity, configuration, reachability, and permission exposures into ranked attack paths for unified triage.
Detection Methods
  • Correlate exposure findings across cloud environments to identify attack paths involving shared federated identities.
  • Use attack-path analysis that combines resource reachability, effective permissions, misconfigurations, and sensitive-data findings.
  • Filter findings by the evaluated resource's cloud provider to scope results to Azure resources.
  • Verify both connector health and resource-recording activity; a healthy connector does not confirm that resources are being recorded.
Data Sources
  • Azure resource configurations and network security group rules
  • Microsoft Defender for Cloud alerts
  • Entra ID audit logs and identity authorization policies
  • Azure Activity Logs exported to an event hub
  • Cloud IAM roles, role assignments, and federated SAML trust configuration
  • Vulnerability scanning findings for virtual machines, function apps, and container registry images
  • Sensitive-data findings and storage configuration, including bucket encryption, versioning, Object Lock, and MFA delete status
Platforms
  • Multicloud environment spanning AWS and Azure
Defensive Actions
  • Enable the integration across all relevant subscriptions and regions, including the global region scope needed for identity controls.
  • Confirm that subscription diagnostic settings export Activity Logs to the connector's event hub; create a remediation task if existing subscriptions are not covered.
  • Check that resources are actually being recorded, not just that the connector reports healthy status.
  • Review high-severity findings together and investigate the federated trust connecting the identity tenant to the cloud account.
  • Address exposed identity and resource conditions, including missing MFA, excessive permissions, permissive inbound network rules, and unprotected sensitive storage.
  • For virtual-machine vulnerability scanning, ensure each target VM has a system-assigned managed identity.

MITRE ATT&CK

Vendors

Products

Tools

Related Articles