Skip to content

Commit 4d8f7cf

Browse files
committed
Edit of Verification doc
1 parent 94e8c9f commit 4d8f7cf

File tree

1 file changed

+15
-7
lines changed

1 file changed

+15
-7
lines changed

articles/sentinel/connect-cef-verify.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Validate connectivity to Azure Sentinel| Microsoft Docs
2+
title: Validate connectivity to Azure Sentinel | Microsoft Docs
33
description: Validate connectivity of your security solution to make sure CEF messages are being forwarded to Azure Sentinel.
44
services: sentinel
55
documentationcenter: na
@@ -13,25 +13,33 @@ ms.devlang: na
1313
ms.topic: conceptual
1414
ms.tgt_pltfrm: na
1515
ms.workload: na
16-
ms.date: 12/30/2019
16+
ms.date: 04/19/2020
1717
ms.author: yelevin
1818

1919
---
2020
# STEP 3: Validate connectivity
2121

22+
Once you have deployed your log forwarder (in Step 1) and configured your security solution to send it CEF messages (in Step 2), follow these instructions to verify connectivity between your security solution and Azure Sentinel.
2223

24+
## Prerequisites
2325

24-
After you deployed the agent and configured your security solution to forward CEF messages, use this article to understand how to verify connectivity between Azure Sentinel and your security solution.
26+
- You must have elevated permissions (sudo) on your machine.
27+
28+
- Make sure that you have Python on your machine using the following command: `python –version`
2529

2630
## How to validate connectivity
2731

28-
1. Open Log Analytics to make sure that logs are received using the CommonSecurityLog schema.<br> It may take upwards of 20 minutes until your logs start to appear in Log Analytics.
32+
1. From the Azure Sentinel navigation menu, open **Logs**. Run a query using the **CommonSecurityLog** schema to see if you are receiving logs from your security solution.<br>
33+
Be aware that it may take about 20 minutes until your logs start to appear in **Log Analytics**.
34+
35+
1. If you don't see any results from the query, verify that events are being generated from your security solution, or try generating some, and verify they are being forwarded to the Syslog forwarder machine you designated.
2936

30-
1. Before you run the script, we recommend that you send messages from your security solution to make sure they are being forwarded to the Syslog proxy machine you configured.
31-
1. You must have elevated permissions (sudo) on your machine. Make sure that you have Python on your machine using the following command: `python –version`
32-
1. Run the following script to check connectivity between the agent, Azure Sentinel, and your security solution. It checks that the daemon forwarding is properly configured, listens on the correct ports, and that nothing is blocking communication between the daemon and the Log Analytics agent. The script also sends mock messages 'TestCommonEventFormat' to check end-to-end connectivity. <br>
37+
1. Run the following script to check connectivity between your security solution, the log forwarder, and Azure Sentinel. This script checks that the daemon is listening on the correct ports, that the forwarding is properly configured, and that nothing is blocking communication between the daemon and the Log Analytics agent. It also sends mock messages 'TestCommonEventFormat' to check end-to-end connectivity. <br>
3338
`sudo wget https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/CEF/cef_troubleshoot.py&&sudo python cef_troubleshoot.py [WorkspaceID]`
3439

40+
## Validation script explained
41+
42+
3543

3644
## Next steps
3745
In this document, you learned how to connect CEF appliances to Azure Sentinel. To learn more about Azure Sentinel, see the following articles:

0 commit comments

Comments
 (0)