↳ Source GitHubConnecteur

[Deprecated] Cisco Secure Email Gateway via Legacy Agent

Description

The [Cisco Secure Email Gateway (SEG)](https://www.cisco.com/c/en/us/products/security/email-security/index.html) data connector provides the capability to ingest [Cisco SEG Consolidated Event Logs](https://www.cisco.com/c/en/us/td/docs/security/esa/esa14-0/user_guide/b_ESA_Admin_Guide_14-0/b_ESA_Admin_Guide_12_1_chapter_0100111.html#con_1061902) into Microsoft Sentinel.
Statut déclaré
1
Auteur / éditeur déclaré
Cisco

Sources déclarées

Métadonnées du fichier source. Aucune dépendance déduite du KQL.

Types de données

Permissions déclarées

read and write permissions are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace

Instructions du connecteur

Contenu publié dans le dépôt. Consultez le fichier original pour l’ensemble des paramètres.

>**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected [**CiscoSEGEvent**](https://aka.ms/sentinel-CiscoSEG-parser) which is deployed with the Microsoft Sentinel Solution.
>**NOTE:** This data connector has been developed using AsyncOS 14.0 for Cisco Secure Email Gateway
1. Linux Syslog agent configuration
Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel. > Notice that the data from all regions will be stored in the selected workspace
1.1 Select or create a Linux machine
Select or create a Linux machine that Microsoft Sentinel will use as the proxy between your security solution and Microsoft Sentinel this machine can be on your on-prem environment, Azure or other clouds.
1.2 Install the CEF collector on the Linux machine
Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Microsoft Sentinel workspace. The CEF collector collects CEF messages on port 514 TCP. > 1. Make sure that you have Python on your machine using the following command: python -version. > 2. You must have elevated permissions (sudo) on your machine.
Run the following command to install and apply the CEF collector:
2. Forward Common Event Format (CEF) logs to Syslog agent
Follow these steps to configure Cisco Secure Email Gateway to forward logs via syslog: 2.1. Configure [Log Subscription](https://www.cisco.com/c/en/us/td/docs/security/esa/esa14-0/user_guide/b_ESA_Admin_Guide_14-0/b_ESA_Admin_Guide_12_1_chapter_0100111.html#con_1134718) >**NOTE:** Select **Consolidated Event Logs** in Log Type field.
3. Validate connection
Follow the instructions to validate your connectivity: Open Log Analytics to check if the logs are received using the CommonSecurityLog schema. >It may take about 20 minutes until the connection streams data to your workspace. If the logs are not received, run the following connectivity validation script: > 1. Make sure that you have Python on your machine using the following command: python -version >2. You must have elevated permissions (sudo) on your machine
Run the following command to validate your connectivity:
4. Secure your machine
Make sure to configure the machine's security according to your organization's security policy [Learn more >](https://aka.ms/SecureCEF)

Traçabilité de la source

GitHub

Les valeurs affichées proviennent des fichiers du dépôt Azure/Azure-Sentinel. Elles décrivent le modèle publié, pas la configuration de votre workspace.

Identifiant source
CiscoSEG
Autres fichiers source 1Solutions/CiscoSEG/Data Connectors/Connector_Cisco_SEG_CEF.jsonsource ↗
GSTEP / SUIVI DU CATALOGUE

Ajouté au catalogue : 16 sept. 2026 · 05:49 UTC
Dernier changement observé : 16 sept. 2026 · 05:49 UTC

Dates de synchronisation GSTEP, distinctes des dates de publication du contenu source.