Description
iSID enables non-disruptive monitoring of distributed ICS networks for changes in topology and behavior, using multiple security packages, each offering a unique capability pertaining to a specific type of network activity
- Statut déclaré
- 1
- Auteur / éditeur déclaré
- Radiflow
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 [**RadiflowEvent**] which is deployed with the Microsoft Sentinel Solution.
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. Configure iSID to send logs using CEF
Configure log forwarding using CEF:
1. Navigate to the **System Notifications** section of the Configuration menu.
2. Under Syslog, select **+Add**.
3. In the **New Syslog Server** dialog specify the name, remote server **IP**, **Port**, **Transport** and select **Format** - **CEF**.
4. Press **Apply** to exit the **Add Syslog dialog**.
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
GitHubLes 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.
- Commit
9800e51↗- Identifiant source
RadiflowIsid
GSTEP / SUIVI DU CATALOGUE
Ajouté au catalogue : 16 sept. 2026 · 05:49 UTC
Dernier changement observé : 16 sept. 2026 · 05:49 UTC