Skip to content

Commit f92901c

Browse files
authored
Renumbered numbering list
1 parent 8ab19b4 commit f92901c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CloudAppSecurityDocs/troubleshooting-siem.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,13 +42,13 @@ Use the following steps to validate your configuration:
4242

4343
1. Connect to your SIEM and check that new data is received from the new SIEM agent that you configured.
4444

45-
> [!NOTE]
46-
> The agent will only send activities in the timeframe of the issue on which you were alerted.
45+
> [!NOTE]
46+
> The agent will only send activities in the timeframe of the issue on which you were alerted.
4747
4848
1. If data isn't received by your SIEM, then on the new SIEM agent device, try listening to the port that you configured to forward activities to see if data is being sent from the agent to the SIEM. For example, run `netcat -l <port>` where `<port>` is the previously configured port number.
4949

50-
> [!NOTE]
51-
> If you're using `ncat`, make sure you specify the ipv4 flag `-4`.
50+
> [!NOTE]
51+
> If you're using `ncat`, make sure you specify the ipv4 flag `-4`.
5252
5353
1. If data is being sent by the agent but not received by your SIEM, check the SIEM agent log. If you can see "connection refused" messages, make sure that your SIEM agent is configured to use TLS 1.2 or newer.
5454

0 commit comments

Comments
 (0)