Defender for Cloud - AWS Compliance Controls Update Frequency

%3CLINGO-SUB%20id%3D%22lingo-sub-3061324%22%20slang%3D%22en-US%22%3EAWS%20Compliance%20Controls%20-%20Update%20Frequency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3061324%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20connected%20some%20AWS%20accounts%20and%20turned%20on%20the%20AWS%20Foundational%20Security%20Best%20Practices%20standard%20on%20them.%20To%20remediate%20some%20of%20the%20findings%2C%20I%20deleted%20the%20resources%20in%20AWS%20that%20were%20failing%20the%20control.%20It%20has%20been%20over%2048%20hours%20and%20they%20are%20still%20showing%20up%20as%20failing%20the%20control%20in%20the%20Regulatory%20Compliance%20page%20in%20Defender%20for%20Cloud.%20The%20resource%20no%20longer%20exists%20so%20I%20would%20expect%20it%20to%20no%20longer%20appear%20in%20Defender%20for%20Cloud%20and%20for%20it%20to%20no%20longer%20show%20up%20as%20failing.%20Any%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

I connected some AWS accounts and turned on the AWS Foundational Security Best Practices standard on them. To remediate some of the findings, I deleted the resources in AWS that were failing the control. It has been over 48 hours and they are still showing up as failing the control in the Regulatory Compliance page in Defender for Cloud. The resource no longer exists so I would expect it to no longer appear in Defender for Cloud and for it to no longer show up as failing. Any ideas?

2 Replies
It looks like a couple hours later after I posted this the changes were finally reflected in Defender for Cloud. It still seems like a long time to wait but I'm glad everything is in sync now.
Thank you for your feedback. This new AWS connector is currently in Preview, so minor issues or glitches are expected.