Skip to content

Commit 073aa76

Browse files
committed
another fix from email mor
1 parent 119f3c4 commit 073aa76

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/sentinel/connect-common-event-format.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.devlang: na
1313
ms.topic: conceptual
1414
ms.tgt_pltfrm: na
1515
ms.workload: na
16-
ms.date: 10/14/2019
16+
ms.date: 11/26/2019
1717
ms.author: rkarlin
1818

1919
---
@@ -77,10 +77,10 @@ Make sure your machine also meets the following requirements:
7777
- Make sure you have Python running on your machine
7878
## STEP 1: Deploy the agent
7979

80-
In this step, you need to select hte Linux machine that will act as a proxy between Azure Sentinel and your security solution. You will have to run a script on the proxy machine that:
81-
- Installs the Log Analytics agent and configures it as needed to listen for Syslog messages on port 514 over TCP and send the CEF messages to your Azure Sentinel workspace.
82-
- Configures the Syslog daemon to forward CEF messages to the Log Analytics agent using port 25226.
83-
- Sets the Syslog agent to collect the data and send it securely to Log Analytics, where it is parsed and enriched.
80+
In this step, you need to select the Linux machine that will act as a proxy between Azure Sentinel and your security solution. You will have to run a script on the proxy machine that:
81+
- Installs the Log Analytics agent and configures it as needed to listen for Syslog messages.
82+
- Configures the Syslog daemon to listen to Syslog messages using TCP port 514 and then forwards only the CEF messages to the Log Analytics agent using TCP port 25226.
83+
- Sets the Syslog agent to collect the data and send it securely to Azure Sentinel, where it is parsed and enriched.
8484

8585

8686
1. In the Azure Sentinel portal, click **Data connectors** and select **Common Event Format (CEF)** and then **Open connector page**.

articles/sentinel/roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,4 +77,4 @@ You can use the Log Analytics advanced role-based access control across the data
7777
## Next steps
7878
In this document, you learned how to work with roles for Azure Sentinel users and what each role enables users to do.
7979

80-
* [Azure Security Blog](https://blogs.msdn.com/b/azuresecurity/). Find blog posts about Azure security and compliance.
80+
* [Azure Sentinel Blog](https://aka.ms/azuresentinelblog). Find blog posts about Azure security and compliance.

0 commit comments

Comments
 (0)