Skip to content

Commit 00f7eec

Browse files
authored
Update siem-integration-with-sentinel.md
1 parent 70548b0 commit 00f7eec

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

articles/application-gateway/for-containers/siem-integration-with-sentinel.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,9 @@ In this QuickStart guide, you set up:
6464
![A screenshot of Rule Query.](./media/siem-integration-with-sentinel/create-rule.png)
6565

6666
6. Create rule query based on your access logs:
67-
1. Example Scenario: A user sends encrypted data through a specific URL.
68-
2. Goal: Detect threats from a HostName with RequestURI **"/secret/path"**.
69-
3. Create query:
67+
- Example Scenario: A user sends encrypted data through a specific URL.
68+
- Goal: Detect threats from a HostName with RequestURI **"/secret/path"**.
69+
- Create query:
7070

7171
```bash
7272
# Example Query
@@ -76,18 +76,19 @@ In this QuickStart guide, you set up:
7676

7777
This query filters `AGCAccessLogs` based on conditions related to hostname and request URI.
7878

79-
7. Detect associated IPs by Entity Mapping:
79+
8. Detect associated IPs by Entity Mapping:
8080
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<img src="./media/siem-integration-with-sentinel/entity-mapping.png" alt="A screenshot of the entity mapping." width="80%">
8181

82-
8. Set Query Scheduling:
83-
1. Run for every 5 hours.
84-
2. Look up data for every 5 hours.
85-
9. **Review + Create**.
82+
9. Set Query Scheduling:
83+
- Run for every 5 hours.
84+
- Look up data for every 5 hours.
85+
11. **Review + Create**.
8686

8787

8888
## Test Incident
8989

90-
1. An incident occurs after the rule is active. Now we're ready to send some traffic with **/secret/path** to our sample application, via the FQDN (fully qualified domain name) assigned to the frontend. Use the following command to get the FQDN:
90+
1. Send traffic into the URL to create an incident:
91+
- Now we're ready to send some traffic with **/secret/path** to our sample application, via the FQDN (fully qualified domain name) assigned to the frontend. Use the following command to get the FQDN:
9192
9293
```bash
9394
fqdn=$(kubectl get gateway gateway-01 -n test-infra -o jsonpath='{.status.addresses[0].value}')
@@ -123,4 +124,4 @@ In this QuickStart guide, you set up:
123124
124125
[Automate Playbook and Alerts](../../azure-monitor/../sentinel/automation/automation.md) to create an alert for extra security measures and communication.
125126
126-
Congratulations, You can now create security barriers on your logs and investigate any incidents!
127+
Congratulations, you can now create security barriers on your logs and investigate any incidents!

0 commit comments

Comments
 (0)