Defender for Cloud Expands Multicloud Reach with New Onboarding Process
Microsoft Defender for Cloud is expanding its reach to protect resources on Amazon Web Services (AWS) and Google Cloud Platform (GCP), in addition to Azure, as a cloud-native application protection platform.
The onboarding process has changed significantly since last year's update, with the AWS and GCP connector flows now using federated, short-lived credentials instead of long-lived secrets. The setup also includes new 'least privilege' versus 'default access' toggles that determine what gets deployed into cloud accounts.
Azure users who last set up Defender for Cloud a year ago will notice several steps have changed, including the use of workload identity federation and service account impersonation for GCP connections. Additionally, Microsoft Sentinel can now be integrated with multicloud threat detection.