Skip to content

Commit 70b232c

Browse files
authored
Merge pull request #124131 from kochavis/patch-1
Update unified-connector-cef-device.md
2 parents 02c3b5a + 482c2a5 commit 70b232c

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

articles/sentinel/unified-connector-cef-device.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,22 @@ Set your security solution to send syslog messages in CEF format to the proxy ma
182182

183183
In ForgeRock, install and configure this Common Audit (CAUD) for Microsoft Sentinel per the documentation at https://github.com/javaservlets/SentinelAuditEventHandler. Next, in Azure, follow the steps to configure the CEF via AMA data connector.
184184

185+
## Fortinet
186+
187+
Set your Fortinet to send Syslog messages in CEF format to the proxy machine. Make sure you send the logs to port 514 TCP on the machine's IP address.<br/>
188+
189+
Copy the CLI commands below and:
190+
191+
- Replace \"server &lt;ip address&gt;\" with the Syslog agent's IP address.<br/>
192+
- Set the \"&lt;facility_name&gt;\" to use the facility you configured in the Syslog agent (by default, the agent sets this to local4).<br/>
193+
- Set the Syslog port to 514, the port your agent uses.<br/>
194+
- To enable CEF format in early FortiOS versions, you may need to run the command \"set csv disable\".<br/>For more information, go to the [Fortinet Document Library](https://aka.ms/asi-syslog-fortinet-fortinetdocumentlibrary), choose your version, and use the \"Handbook\" and \"Log Message Reference\" PDFs.<br/>
195+
196+
[Learn more >](https://aka.ms/CEF-Fortinet)
197+
198+
Set up the connection using the CLI to run the following commands:
199+
`config log syslogd setting/n set status enable/nset format cef/nset port 514/nset server <ip_address_of_Receiver>/nend`
200+
185201
## iboss
186202

187203
Set your Threat Console to send syslog messages in CEF format to your Azure workspace. Make note of your **Workspace ID** and **Primary Key** within your Log Analytics workspace. Select the workspace from the Log Analytics workspaces menu in the Azure portal. Then select **Agents management** in the **Settings** section.

0 commit comments

Comments
 (0)