Skip to content

Commit 6672f5f

Browse files
authored
Update mde-sap-custom-detection-rules.md
1 parent 69277a8 commit 6672f5f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-endpoint/mde-sap-custom-detection-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ The SAP BASIS Team and the security team should codevelop the solution. The SAP
5151

5252
4. The SAP BASIS team briefs the security team on any "allowed" utilities, such as `BRTOOLS` (for Oracle customers), `AzCopy` (if used) or other specific utilities for printing or archiving.
5353

54-
5. The security team works with the SAP BASIS team to query SAPXPG commands and parameters. An example query to detect or block `wget` (which can be used to download malicious payloads) is as follows:
54+
5. The security team works with the SAP BASIS team to query SAPXPG commands and parameters. An example query to detect `wget` (which can be used to download malicious payloads) is as follows:
5555

5656
```kusto
5757
@@ -102,4 +102,4 @@ The SAP BASIS Team and the security team should codevelop the solution. The SAP
102102

103103
- To learn more about advanced hunting, see [Proactively hunt for threats with advanced hunting in Microsoft Defender](/defender-xdr/advanced-hunting-overview).
104104

105-
- To learn more about custom rules, see [Create custom detection rules](/defender-xdr/custom-detection-rules#2-create-new-rule-and-provide-alert-details).
105+
- To learn more about custom rules, see [Create custom detection rules](/defender-xdr/custom-detection-rules#2-create-new-rule-and-provide-alert-details).

0 commit comments

Comments
 (0)