↳ GitHub sourceConnector

[Deprecated] Symantec ProxySG

An inconsistency was detected in the sources: variants or an invalid file. Check the files and commit shown below.

Description

The [Symantec ProxySG](https://www.broadcom.com/products/cyber-security/network/gateway/proxy-sg-and-advanced-secure-gateway) allows you to easily connect your Symantec ProxySG logs with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigations. Integrating Symantec ProxySG with Microsoft Sentinel provides more visibility into your organization's network proxy traffic and will enhance security monitoring capabilities.
Declared status
1
Declared author / publisher
Symantec

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

Declared permissions

write permission is required.
Workspace
Workspace
Symantec ProxySG
must be configured to export logs via Syslog

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

>**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias Symantec Proxy SG and load the function code or click [here](https://aka.ms/sentinel-SymantecProxySG-parser), on the second line of the query, enter the hostname(s) of your Symantec Proxy SG device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.
1. Install and onboard the agent for Linux
Typically, you should install the agent on a different computer from the one on which the logs are generated. > Syslog logs are collected only from **Linux** agents.
Choose where to install the agent:
Install agent on Azure Linux Virtual Machine
Select the machine to install the agent on and then click **Connect**.
Install agent on a non-Azure Linux Machine
Download the agent on the relevant machine and follow the instructions.
2. Configure the logs to be collected
Configure the facilities you want to collect and their severities. 1. Under workspace advanced settings **Configuration**, select **Data** and then **Syslog**. 2. Select **Apply below configuration to my machines** and select the facilities and severities. 3. Click **Save**.
3. Configure and connect the Symantec ProxySG
1. Log in to the Blue Coat Management Console . 2. Select Configuration > Access Logging > Formats. 3. Select New. 4. Enter a unique name in the Format Name field. 5. Click the radio button for **Custom format string** and paste the following string into the field. <p><code>1 $(date) $(time) $(time-taken) $(c-ip) $(cs-userdn) $(cs-auth-groups) $(x-exception-id) $(sc-filter-result) $(cs-categories) $(quot)$(cs(Referer))$(quot) $(sc-status) $(s-action) $(cs-method) $(quot)$(rs(Content-Type))$(quot) $(cs-uri-scheme) $(cs-host) $(cs-uri-port) $(cs-uri-path) $(cs-uri-query) $(cs-uri-extension) $(quot)$(cs(User-Agent))$(quot) $(s-ip) $(sr-bytes) $(rs-bytes) $(x-virus-id) $(x-bluecoat-application-name) $(x-bluecoat-application-operation) $(cs-uri-port) $(x-cs-client-ip-country) $(cs-threat-risk)</code></p> 6. Click the **OK** button. 7. Click the **Apply** button. 8. [Follow these instructions](https://knowledge.broadcom.com/external/article/166529/sending-access-logs-to-a-syslog-server.html) to enable syslog streaming of **Access** Logs. Use the IP address or hostname for the Linux device with the Linux agent installed as the Destination IP address

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

Source identifier
SymantecProxySG
Additional source files 1Solutions/SymantecProxySG/Data Connectors/Connector_Syslog_SymantecProxySG.jsonsource ↗
GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.