Microsoft has warned that Azure API Management classic-tier resources may have been accessed without corresponding log events. Where can we find the advisory, and what should we check if we use the classic tier?
How should we investigate the APIM classic-tier security advisory?
Answers
Check the Azure portal under Service Health, then Security Advisories. The notification may identify affected subscriptions. The excerpt shared in the discussion says classic tiers are affected and v2 tiers are not.
If you do not see a notice, check that you are looking at the relevant subscriptions and follow up with Microsoft support. The absence of a visible notice alone does not establish whether an instance was accessed.
Reply to this answer
Start with the secrets stored in APIM, but do not stop there. Check what the APIM system identity could read in Key Vault and what those secrets could access downstream. Rotate or otherwise remediate exposed credentials according to their scope, and investigate the systems they unlock.
Review Key Vault diagnostic logs for SecretGet activity involving that identity, particularly access outside normal patterns. Logs may help identify activity, but if the APIM access path did not generate events, a clean APIM log is not proof that nothing happened.
Reply to this answer
The configuration question deserves scrutiny. The discussion disputes whether the setup described as a security misconfiguration was also a default configuration. Check the advisory against your actual settings rather than assuming either label settles whether you are affected.
Reply to this answer
There are some serious claims about an authentication bypass and a legacy API, but the material here does not independently establish their full scope or whether every classic instance was exposed. Treat those details as leads for the investigation, not confirmed facts.
Use the subscription-specific advisory and Microsoft support to clarify exposure, affected resources and recommended remediation. Meanwhile, preserve the logs you do have and assess the potential impact of credentials reachable from APIM.
Reply to this answer
This is also a good time to review whether classic is still the right tier for your deployment. The advisory says v2 tiers are not affected by this issue, though a migration needs its own compatibility and security review and will not replace investigating possible past exposure.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_b46~quendrix.8:
The Key Vault review depends on diagnostic logging being available for the period in question. Check the identity permissions as well as the events you have.