Skip to content

Commit 40f1934

Browse files
committed
remove x-links; review comments
1 parent a3da303 commit 40f1934

File tree

1 file changed

+20
-17
lines changed

1 file changed

+20
-17
lines changed

articles/api-management/protect-with-defender-for-apis.md

Lines changed: 20 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,42 +6,48 @@ author: dlepow
66

77
ms.service: api-management
88
ms.topic: how-to
9-
ms.date: 04/14/2023
9+
ms.date: 04/19/2023
1010
ms.author: danlep
1111
---
1212
# Enable advanced API security features using Microsoft Defender for Cloud
1313
<!-- Update links to D4APIs docs when available -->
1414

15-
[Defender for APIs](https://aka.ms/apiSecurityOverview) (preview), a capability of [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction), offers full lifecycle protection, detection, and response coverage for APIs that are managed in Azure API Management. The service empowers security practitioners to gain visibility into their business-critical APIs, understand their security posture, prioritize vulnerability fixes, and detect active runtime threats within minutes.
15+
Defender for APIs, a capability of [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction), offers full lifecycle protection, detection, and response coverage for APIs that are managed in Azure API Management. The service empowers security practitioners to gain visibility into their business-critical APIs, understand their security posture, prioritize vulnerability fixes, and detect active runtime threats within minutes.
1616

1717
Capabilities of Defender for APIs include:
1818

19-
* Analyze for external, unused, or unauthenticated APIs
19+
* Identify external, unused, or unauthenticated APIs
2020
* Classify APIs that receive or respond with sensitive data
21-
* Detect exploits of OWASP API top 10 vulnerabilities
21+
* Apply configuration recommendations to strengthen the security posture of APIs and API Management services
22+
* Detect anomalous and suspicious API traffic patterns and exploits of OWASP API top 10 vulnerabilities
23+
* Prioritize threat remediation
2224
* Integrate with SIEM systems and Defender Cloud Security Posture Management
2325

24-
This article shows how to use the Azure portal to enable Defender for APIs from your API Management instance and view a summary of security recommendations and alerts for onboarded APIs. You can also enable Defender for APIs directly in the Microsoft Defender for Cloud console, where more API security insights and inventory experiences are available.
26+
This article shows how to use the Azure portal to enable Defender for APIs from your API Management instance and view a summary of security recommendations and alerts for onboarded APIs.
2527

2628
[!INCLUDE [api-management-availability-premium-dev-standard-basic](../../includes/api-management-availability-premium-dev-standard-basic.md)]
2729

2830
## Preview limitations
2931

3032
* Currently, Defender for APIs discovers and analyzes REST APIs only.
3133
* Defender for APIs currently doesn't onboard APIs that are exposed using the API Management [self-hosted gateway](self-hosted-gateway-overview.md) or managed using API Management [workspaces](workspaces-overview.md).
32-
* Some ML-based detections and security insights (data classification, authentication check, unused and external APIs) for API Management instances with [multi-region](api-management-howto-deploy-multi-region.md) deployments aren't supported in secondary regions. In such cases, data residency requirements are still met. 
34+
* Some ML-based detections and security insights (data classification, authentication check, unused and external APIs) aren't supported in secondary regions in [multi-region](api-management-howto-deploy-multi-region.md) deployments. Defender for APIs relies on local data pipelines to ensure regional data residency and improved performance in such deployments. 
3335

3436

3537
## Prerequisites
3638

3739
* At least one API Management instance in an Azure subscription. Defender for APIs is enabled at the level of a subscription.
3840
* One or more supported APIs must be imported to the API Management instance.
39-
* Permissions to [enable the Defender for APIs plan](/azure/defender-for-cloud/permissions).
40-
* Owner or Contributor permissions on the API Management instance.
41+
* Role to [enable the Defender for APIs plan](/azure/defender-for-cloud/permissions).
42+
* Owner or Contributor role on the API Management instance.
4143

4244
## Onboard to Defender for APIs
4345

44-
Onboarding APIs to Defender for APIs is a two-step process: enabling the Defender for APIs plan, and onboarding unprotected APIs in your API Management instances.  
46+
Onboarding APIs to Defender for APIs is a two-step process: enabling the Defender for APIs plan for the subscription, and onboarding unprotected APIs in your API Management instances.  
47+
48+
> [!TIP]
49+
> You can also onboard to Defender for APIs directly in the Defender for Cloud portal, where more API security insights and inventory experiences are available.
50+
4551

4652
### Enable the Defender for APIs plan for a subscription
4753

@@ -60,7 +66,7 @@ Onboarding APIs to Defender for APIs is a two-step process: enabling the Defende
6066
### Onboard unprotected APIs to Defender for APIs
6167

6268
> [!CAUTION]
63-
> Onboarding APIs to Defender for APIs may increase compute, memory, and network utilization of your API Management instance. Do not onboard all APIs at one time if your API Management instance is running at high utilization. Use caution by gradually onboarding APIs, while monitoring the utilization of your instance (for example, using [the capacity metric](api-management-capacity.md)) and scaling out as needed.
69+
> Onboarding APIs to Defender for APIs may increase compute, memory, and network utilization of your API Management instance, which in extreme cases may cause an outage of the API Management instance. Do not onboard all APIs at one time if your API Management instance is running at high utilization. Use caution by gradually onboarding APIs, while monitoring the utilization of your instance (for example, using [the capacity metric](api-management-capacity.md)) and scaling out as needed.
6470
6571
1. In the portal, go back to your API Management instance.
6672
1. In the left menu, select **Microsoft Defender for Cloud (preview)**.
@@ -97,14 +103,11 @@ You can view a summary of all security recommendations and alerts for onboarded
97103

98104
For the security alerts received, Defender for APIs suggests necessary steps to perform the required analysis and validate the potential exploit or anomaly associated with the APIs. Follow the steps in the security alert to fix and return the APIs to healthy status.
99105

100-
To learn more about the benefits of Defender for APIs, including additional API inventory experiences within Defender for Cloud, see [Microsoft Defender for APIs – Benefits and features](https://aka.ms/apiSecurityOverview).
106+
## Offboard protected APIs from Defender for APIs
107+
108+
You can offboard protected APIs from Defender for APIs by using the Defender for Cloud portal. For more information, see the Microsoft Defender for Cloud documentation.
101109

102110
## Next steps
103111

104-
* Learn more about Defender for APIs:
105-
* [Benefits and features](https://aka.ms/apiSecurityOverview)
106-
* [API security alerts](https://aka.ms/apiSecurityAlerts)
107-
* [API security threats](https://aka.ms/apiSecurityRecommendations)
108-
* [API security troubleshooting guide](https://aka.ms/apiSecurityTroubleshooting)
109-
* [Pricing](https://azure.microsoft.com/pricing/details/defender-for-cloud/)
112+
* Learn more about [Defender for Cloud](/azure/defender-for-cloud/defender-for-cloud-introduction)
110113
* Learn how to [upgrade and scale](upgrade-and-scale.md) an API Management instance.

0 commit comments

Comments
 (0)