Skip to content

Commit 8e43cab

Browse files
Merge pull request #280955 from dcurwin/remove-postman-containers-july16-2024
Remove mention of Postman
2 parents bf2ced6 + 76edc2d commit 8e43cab

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

articles/defender-for-cloud/includes/defender-for-containers-enable-plan-arc.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -134,10 +134,7 @@ You can use the **azure-defender-extension-arm-template.json** Resource Manager
134134
135135
To use the REST API to deploy the Defender sensor, you'll need a Log Analytics workspace on your subscription. Learn more in [Log Analytics workspaces](../../azure-monitor/logs/log-analytics-workspace-overview.md).
136136
137-
> [!TIP]
138-
> The simplest way to use the API to deploy the Defender sensor is with the supplied **Postman Collection JSON** example from Defender for Cloud's [installation examples](https://aka.ms/kubernetes-extension-installation-examples).
139-
140-
- To modify the Postman Collection JSON, or to manually deploy the sensor with the REST API, run the following PUT command:
137+
- To manually deploy the sensor with the REST API, run the following PUT command:
141138
142139
```rest
143140
PUT https://management.azure.com/subscriptions/{{Subscription Id}}/resourcegroups/{{Resource Group}}/providers/Microsoft.Kubernetes/connectedClusters/{{Cluster Name}}/providers/Microsoft.KubernetesConfiguration/extensions/microsoft.azuredefender.kubernetes?api-version=2020-07-01-preview

articles/defender-for-cloud/onboarding-guide-bright.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The solution is both developer and AppSec friendly and has unique capabilities i
1919

2020
Bright API security validation is based on three main phases:
2121

22-
1. Map the API attack surface. Bright can parse and learn the exact valid structure of REST and GraphQL APIs, from an OAS file (swagger) or an Introspection (GraphQL schema description). In addition, Bright can learn API content from Postman collections and HAR files. These methods provide a comprehensive way to visualize the attack surface.
22+
1. Map the API attack surface. Bright can parse and learn the exact valid structure of REST and GraphQL APIs, from an OAS file (swagger) or an Introspection (GraphQL schema description). In addition, Bright can learn API content from HAR files. These methods provide a comprehensive way to visualize the attack surface.
2323
1. Conduct an attack simulation on the discovered APIs. Once the baseline of the API behavior is known (in step 1), Bright manipulates the requests (payloads, endpoint parameters, and so on) and automatically analyzes the response, verifying the correct response code and the content of the response payload to ensure no vulnerability exists. The attack simulations include OWASP API top 10, NIST, business logic tests, and more.
2424
1. Bright provides a clear indication of any found vulnerability, including screenshots to ease the triage and investigation of the issue and suggestions on how to remediate that vulnerability.
2525

0 commit comments

Comments
 (0)