Skip to content

Commit 5776a20

Browse files
committed
fixed links
1 parent f6abd3a commit 5776a20

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/connect-data-sources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,11 +60,11 @@ The following data connection methods are supported by Azure Sentinel:
6060
- [Barracuda](connect-barracuda.md)
6161
- [Barracuda CloudGen Firewall](connect-barracuda-cloudgen-firewall.md)
6262
- [Citrix Analytics (Security)](connect-citrix-analytics.md)
63-
- [F5 BIG-IP](connect-f3-big-ip.md)
63+
- [F5 BIG-IP](connect-f5-big-ip.md)
6464
- [Forcepoint DLP](connect-forcepoint-dlp.md)
6565
- [Squadra Technologies secRMM](connect-squadra-secrmm.md)
6666
- [Symantec ICDX](connect-symantec.md)
67-
- [Zimperium](connect-zimperium.md)
67+
- [Zimperium](connect-zimperium-mtd.md)
6868

6969

7070
- **External solutions via agent**: Azure Sentinel can be connected to all other data sources that can perform real-time log streaming using the Syslog protocol, via an agent. <br>Most appliances use the Syslog protocol to send event messages that include the log itself and data about the log. The format of the logs varies, but most appliances support the Common Event Format (CEF) based formatting for logs data. <br>The Azure Sentinel agent, which is based on the Log Analytics agent, converts CEF formatted logs into a format that can be ingested by Log Analytics. Depending on the appliance type, the agent is installed either directly on the appliance, or on a dedicated Linux server. The agent for Linux receives events from the Syslog daemon over UDP, but if a Linux machine is expected to collect a high volume of Syslog events, they are sent over TCP from the Syslog daemon to the agent and from there to Log Analytics.

0 commit comments

Comments
 (0)