↳ Source GitHubConnecteur

[Deprecated] Cisco Firepower eStreamer via AMA

Description

eStreamer is a Client Server API designed for the Cisco Firepower NGFW Solution. The eStreamer client requests detailed event data on behalf of the SIEM or logging solution in the Common Event Format (CEF).
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
To collect data from non-Azure VMs, they must have Azure Arc installed and enabled. [Learn more](https://docs.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-install?tabs=ARMAgentPowerShell,PowerShellWindows,PowerShellWindowsArc,CLIWindows,CLIWindowsArc)
Common Event Format (CEF) via AMA and Syslog via AMA data connectors must be installed [Learn more](https://learn.microsoft.com/azure/sentinel/connect-cef-ama#open-the-connector-page-and-create-the-dcr)

Instructions du connecteur

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

1. Kindly follow the steps to configure the data connector
Step A. Configure the Common Event Format (CEF) via AMA data connector
_Note:- CEF logs are collected only from Linux Agents_ 1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade . 2. Search for 'Common Event Format (CEF) via AMA' data connector and open it. 3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule) _Note:- It is recommended to install minimum 1.27 version of AMA agent [Learn more](https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal ) and ensure there is no duplicate DCR as it can cause log duplicacy_ 4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine
Step B. Install the Firepower eNcore client
Install and configure the Firepower eNcore eStreamer client, for more details see full install [guide](https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSentinelOperationsGuide_409.html)
1. Download the Firepower Connector from github
Download the latest version of the Firepower eNcore connector for Microsoft Sentinel [here](https://github.com/CiscoSecurity/fp-05-microsoft-sentinel-connector). If you plan on using python3 use the [python3 eStreamer connector](https://github.com/CiscoSecurity/fp-05-microsoft-sentinel-connector/tree/python3)
2. Create a pkcs12 file using the Azure/VM Ip Address
Create a pkcs12 certificate using the public IP of the VM instance in Firepower under System->Integration->eStreamer, for more information please see install [guide](https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSentinelOperationsGuide_409.html#_Toc527049443)
3. Test Connectivity between the Azure/VM Client and the FMC
Copy the pkcs12 file from the FMC to the Azure/VM instance and run the test utility (./encore.sh test) to ensure a connection can be established, for more details please see the setup [guide](https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSentinelOperationsGuide_409.html#_Toc527049430)
4. Configure encore to stream data to the agent
Configure encore to stream data via TCP to the Microsoft Agent, this should be enabled by default, however, additional ports and streaming protocols can configured depending on your network security posture, it is also possible to save the data to the file system, for more information please see [Configure Encore](https://www.cisco.com/c/en/us/td/docs/security/firepower/670/api/eStreamer_enCore/eStreamereNcoreSentinelOperationsGuide_409.html#_Toc527049433)
Step C. 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:
2. Secure your machine
Make sure to configure the machine's security according to your organization's security policy [Learn more >](https://aka.ms/SecureCEF)

Contenus associés

Liens établis à partir des identifiants déclarés et des manifests des solutions.

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
CiscoFirepowerEStreamerAma
Autres fichiers source 2Solutions/Cisco Firepower EStreamer/Data Connectors/template_CiscoFirepowerEStreamerAMA.jsonsource ↗Solutions/Cisco Firepower EStreamer/Data/Solution_Cisco Firepower EStreamer.jsonsolution-membership ↗
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.