Microsoft Defender External Attack Surface Management finds a public storage static website that Defender Inventory never listed. What should the Azure security engineer do to close the discover-then-manage loop?
Select an answer to reveal the explanation.
Short Explanation
Finding the rogue static site is half the job. Bring it under management—or lock it down—so Inventory and Secure Score finally see it. Discovery without ownership is just a fancy bookmark.
Full Explanation
Closing the EASM loop means bringing discovered Internet-facing assets under management so they appear in Defender for Cloud Inventory and affect Secure Score, or hardening them so the exposure is removed. Leaving assets unmanaged, deleting Defender for Cloud, or only writing Sentinel rules without onboarding misses the discover-then-manage intent. Anonymous-blob hardening may follow as remediation, but the first Domain 4 answer is to manage the discovered asset.