Winlogbeat data enrich with CSV lookup adding weird field

Elastic Stack Logstash
1

Hello,

I'm currently using Winlogbeat to send logs to ELK with logstash output.
I would like to create a new field based on the winlog.event_id field.
I have a CSV field for the lookup.

This is to enrich data visualization as Event Description is present from Windows Log Viewer but not present in ELK as field/value.

  • WindowsEventID_EventDescription.csv
"EventID","EventDescription"
"21","RDP: Session Logon Succeeded"
"22","RDP: Shell Start Notification received"
"23","RDP: Session Logoff Succeeded"

Here's my filter config:

filter {
  if [winlog][event_id] {
    csv {
        autodetect_column_names => "true"
        autogenerate_column_names => "false"
        skip_header => "true"
        separator => ","
    }

    translate {
      source => "[winlog][event_id]"
      target => "[winlog][event_details]"
      dictionary_path => "/usr/share/logstash/pipeline/winlogbeat/csv/Windows-EventID-to-EventDescription.csv"
      refresh_interval => 60
      refresh_behaviour => replace
      fallback => "No Event Description Found"
    }
  }
}

It works as you can see below winlog.event_details is created with the matching CSV value.

image
image1072×171 16.7 KB

BUT i have another unknow field that is created in the same time and I think it is related because when I disable the filter, the unknow field is not present.

image
image1076×328 24.6 KB

As if it adds a new field with the value of a previous field not related to the event

  • Field/value created in addition to winlog.event_detail:

La plateforme de filtrage Windows a autorisé une connexion.": "Un nouveau processus a été créé."

event_sample.json 
{
  "_index": ".ds-winlogbeat-8.13.2-2024.04.29-000001",
  "_id": "yfRbd48BCXN4WKE6LSPb",
  "_version": 1,
  "_score": 0,
  "_ignored": [
    "event.original"
  ],
  "_source": {
    "log": {
      "level": "information"
    },
    "@version": "1",
    "winlog": {
      "keywords": [
        "Succès de l’audit"
      ],
      "record_id": 20126320401,
      "task": "Process Creation",
      "event_id": "4688",
      "provider_name": "Microsoft-Windows-Security-Auditing",
      "version": 2,
      "opcode": "Informations",
      "event_data": {
        "SubjectLogonId": "0x8b3c7",
        "SubjectUserSid": "S-1-5-21-0000000000-000000000-000000000-000",
        "TargetUserName": "-",
        "SubjectDomainName": "LAB",
        "NewProcessId": "0x2840",
        "ParentProcessName": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
        "TokenElevationType": "%%1938",
        "CommandLine": "\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1",
        "ProcessId": "0x1b90",
        "TargetDomainName": "-",
        "SubjectUserName": "username_test",
        "TargetUserSid": "S-1-0-0",
        "MandatoryLabel": "S-1-16-4096",
        "NewProcessName": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
        "TargetLogonId": "0x0"
      },
      "provider_guid": "{54849625-5478-4994-a5ba-3e3b0328c30d}",
      "computer_name": "CLI-LAB-08.lab.lan",
      "api": "wineventlog",
      "event_details": "A new process has been created.",
      "channel": "Security",
      "process": {
        "thread": {
          "id": 6824
        },
        "pid": 4
      }
    },
    "host": {
      "name": "CLI-LAB-08.lab.lan"
    },
    "event": {
      "action": "Process Creation",
      "created": "2024-05-14T13:46:54.140Z",
      "original": "Un nouveau processus a été créé.\n\nObjet créateur :\n\tID de sécurité :\t\tS-1-5-21-0000000000-000000000-000000000-000\n\tNom du compte :\t\tusername_test\n\tDomaine du compte :\t\tLAB\n\tID de connexion :\t\t0x8b3c7\n\nObjet cible :\n\tID de sécurité :\t\tS-1-0-0\n\tNom du compte :\t\t-\n\tDomaine du compte :\t\t-\n\tID de connexion :\t\t0x0\n\nInformations sur le processus :\n\tID du nouveau processus :\t\t0x2840\n\tNom du nouveau processus :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tType d'élévation du jeton :\tType d’élévation de jeton limité (3)\n\tÉtiquette obligatoire :\t\tS-1-16-4096\n\tID du processus créateur :\t0x1b90\n\tNom du processus créateur :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tLigne de commande du processus :\t\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1\n\nLe type d'élévation du jeton indique le type de jeton qui a été attribué au nouveau processus conformément à la stratégie Contrôle de compte d'utilisateur.\n\nLe type 1 est un jeton complet sans aucun privilège supprimé ni groupe désactivé. Un jeton complet est uniquement utilisé si le Contrôle de compte d'utilisateur est désactivé, ou que l'utilisateur est le compte d'administrateur intégré ou un compte de service.\n\nLe type 2 est un jeton avec élévation de privilèges sans aucun privilège supprimé ni groupe désactivé. Un jeton avec élévation de privilèges est utilisé lorsque le Contrôle de compte d'utilisateur est activé et que l'utilisateur choisit de démarrer le programme en tant qu'administrateur. Un jeton avec élévation de privilèges est également utilisé lorsqu'une application est configurée pour exiger systématiquement un privilège administratif ou le privilège maximal, et que l'utilisateur est membre du groupe Administrateurs.\n\nLe type 3 est un jeton limité dont les privilèges administratifs sont supprimés et les groupes administratifs désactivés. Le jeton limité est utilisé lorsque le Contrôle de compte d'utilisateur est activé, que l'application n'exige pas le privilège administratif et que l'utilisateur ne choisit pas de démarrer le programme en tant qu'administrateur.",
      "code": "4688",
      "provider": "Microsoft-Windows-Security-Auditing",
      "outcome": "success",
      "kind": "event"
    },
    "@timestamp": "2024-05-14T13:46:53.944Z",
    "tags": [
      "windowsprocess"
    ],
    "La plateforme de filtrage Windows a autorisé une connexion.": "Un nouveau processus a été créé.",
    "ecs": {
      "version": "8.0.0"
    },
    "message": "Un nouveau processus a été créé.\n\nObjet créateur :\n\tID de sécurité :\t\tS-1-5-21-0000000000-000000000-000000000-000\n\tNom du compte :\t\tusername_test\n\tDomaine du compte :\t\tLAB\n\tID de connexion :\t\t0x8b3c7\n\nObjet cible :\n\tID de sécurité :\t\tS-1-0-0\n\tNom du compte :\t\t-\n\tDomaine du compte :\t\t-\n\tID de connexion :\t\t0x0\n\nInformations sur le processus :\n\tID du nouveau processus :\t\t0x2840\n\tNom du nouveau processus :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tType d'élévation du jeton :\tType d’élévation de jeton limité (3)\n\tÉtiquette obligatoire :\t\tS-1-16-4096\n\tID du processus créateur :\t0x1b90\n\tNom du processus créateur :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tLigne de commande du processus :\t\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1\n\nLe type d'élévation du jeton indique le type de jeton qui a été attribué au nouveau processus conformément à la stratégie Contrôle de compte d'utilisateur.\n\nLe type 1 est un jeton complet sans aucun privilège supprimé ni groupe désactivé. Un jeton complet est uniquement utilisé si le Contrôle de compte d'utilisateur est désactivé, ou que l'utilisateur est le compte d'administrateur intégré ou un compte de service.\n\nLe type 2 est un jeton avec élévation de privilèges sans aucun privilège supprimé ni groupe désactivé. Un jeton avec élévation de privilèges est utilisé lorsque le Contrôle de compte d'utilisateur est activé et que l'utilisateur choisit de démarrer le programme en tant qu'administrateur. Un jeton avec élévation de privilèges est également utilisé lorsqu'une application est configurée pour exiger systématiquement un privilège administratif ou le privilège maximal, et que l'utilisateur est membre du groupe Administrateurs.\n\nLe type 3 est un jeton limité dont les privilèges administratifs sont supprimés et les groupes administratifs désactivés. Le jeton limité est utilisé lorsque le Contrôle de compte d'utilisateur est activé, que l'application n'exige pas le privilège administratif et que l'utilisateur ne choisit pas de démarrer le programme en tant qu'administrateur.",
    "agent": {
      "version": "8.13.2",
      "type": "winlogbeat",
      "ephemeral_id": "61d6d72d-be5d-4186-814f-e2e30ab55d75",
      "id": "7d7b46ea-dbef-4ea3-ac8c-3e1ca717e983",
      "name": "CLI-LAB-08"
    }
  },
  "fields": {
    "winlog.event_data.NewProcessName": [
      "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
    ],
    "winlog.provider_guid": [
      "{54849625-5478-4994-a5ba-3e3b0328c30d}"
    ],
    "winlog.provider_name": [
      "Microsoft-Windows-Security-Auditing"
    ],
    "winlog.event_details": [
      "A new process has been created."
    ],
    "winlog.computer_name": [
      "CLI-LAB-08.lab.lan"
    ],
    "winlog.process.pid": [
      4
    ],
    "winlog.keywords": [
      "Succès de l’audit"
    ],
    "winlog.record_id": [
      "20126320401"
    ],
    "winlog.event_data.CommandLine": [
      "\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1"
    ],
    "log.level": [
      "information"
    ],
    "agent.name": [
      "CLI-LAB-08"
    ],
    "host.name": [
      "CLI-LAB-08.lab.lan"
    ],
    "winlog.event_data.ParentProcessName": [
      "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
    ],
    "event.kind": [
      "event"
    ],
    "winlog.event_data.NewProcessId": [
      "0x2840"
    ],
    "event.outcome": [
      "success"
    ],
    "winlog.version": [
      2
    ],
    "winlog.event_data.TargetUserName": [
      "-"
    ],
    "winlog.event_data.TargetUserSid": [
      "S-1-0-0"
    ],
    "agent.hostname": [
      "CLI-LAB-08"
    ],
    "tags": [
      "windowsprocess"
    ],
    "event.provider": [
      "Microsoft-Windows-Security-Auditing"
    ],
    "event.code": [
      "4688"
    ],
    "agent.id": [
      "7d7b46ea-dbef-4ea3-ac8c-3e1ca717e983"
    ],
    "ecs.version": [
      "8.0.0"
    ],
    "winlog.event_data.TokenElevationType": [
      "%%1938"
    ],
    "event.created": [
      "2024-05-14T13:46:54.140Z"
    ],
    "agent.version": [
      "8.13.2"
    ],
    "winlog.event_data.SubjectUserSid": [
      "S-1-5-21-0000000000-000000000-000000000-000"
    ],
    "winlog.process.thread.id": [
      6824
    ],
    "agent.type": [
      "winlogbeat"
    ],
    "La plateforme de filtrage Windows a autorisé une connexion.": [
      "Un nouveau processus a été créé."
    ],
    "winlog.event_data.SubjectLogonId": [
      "0x8b3c7"
    ],
    "winlog.event_data.TargetLogonId": [
      "0x0"
    ],
    "winlog.api": [
      "wineventlog"
    ],
    "@version": [
      "1"
    ],
    "winlog.event_data.ProcessId": [
      "0x1b90"
    ],
    "winlog.task": [
      "Process Creation"
    ],
    "winlog.event_data.SubjectUserName": [
      "username_test"
    ],
    "message": [
      "Un nouveau processus a été créé.\n\nObjet créateur :\n\tID de sécurité :\t\tS-1-5-21-0000000000-000000000-000000000-000\n\tNom du compte :\t\tusername_test\n\tDomaine du compte :\t\tLAB\n\tID de connexion :\t\t0x8b3c7\n\nObjet cible :\n\tID de sécurité :\t\tS-1-0-0\n\tNom du compte :\t\t-\n\tDomaine du compte :\t\t-\n\tID de connexion :\t\t0x0\n\nInformations sur le processus :\n\tID du nouveau processus :\t\t0x2840\n\tNom du nouveau processus :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tType d'élévation du jeton :\tType d’élévation de jeton limité (3)\n\tÉtiquette obligatoire :\t\tS-1-16-4096\n\tID du processus créateur :\t0x1b90\n\tNom du processus créateur :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tLigne de commande du processus :\t\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1\n\nLe type d'élévation du jeton indique le type de jeton qui a été attribué au nouveau processus conformément à la stratégie Contrôle de compte d'utilisateur.\n\nLe type 1 est un jeton complet sans aucun privilège supprimé ni groupe désactivé. Un jeton complet est uniquement utilisé si le Contrôle de compte d'utilisateur est désactivé, ou que l'utilisateur est le compte d'administrateur intégré ou un compte de service.\n\nLe type 2 est un jeton avec élévation de privilèges sans aucun privilège supprimé ni groupe désactivé. Un jeton avec élévation de privilèges est utilisé lorsque le Contrôle de compte d'utilisateur est activé et que l'utilisateur choisit de démarrer le programme en tant qu'administrateur. Un jeton avec élévation de privilèges est également utilisé lorsqu'une application est configurée pour exiger systématiquement un privilège administratif ou le privilège maximal, et que l'utilisateur est membre du groupe Administrateurs.\n\nLe type 3 est un jeton limité dont les privilèges administratifs sont supprimés et les groupes administratifs désactivés. Le jeton limité est utilisé lorsque le Contrôle de compte d'utilisateur est activé, que l'application n'exige pas le privilège administratif et que l'utilisateur ne choisit pas de démarrer le programme en tant qu'administrateur."
    ],
    "winlog.event_id": [
      "4688"
    ],
    "event.action": [
      "Process Creation"
    ],
    "@timestamp": [
      "2024-05-14T13:46:53.944Z"
    ],
    "winlog.channel": [
      "Security"
    ],
    "winlog.event_data.MandatoryLabel": [
      "S-1-16-4096"
    ],
    "winlog.event_data.TargetDomainName": [
      "-"
    ],
    "winlog.opcode": [
      "Informations"
    ],
    "agent.ephemeral_id": [
      "61d6d72d-be5d-4186-814f-e2e30ab55d75"
    ],
    "winlog.event_data.SubjectDomainName": [
      "LAB"
    ]
  },
  "ignored_field_values": {
    "event.original": [
      "Un nouveau processus a été créé.\n\nObjet créateur :\n\tID de sécurité :\t\tS-1-5-21-0000000000-000000000-000000000-000\n\tNom du compte :\t\tusername_test\n\tDomaine du compte :\t\tLAB\n\tID de connexion :\t\t0x8b3c7\n\nObjet cible :\n\tID de sécurité :\t\tS-1-0-0\n\tNom du compte :\t\t-\n\tDomaine du compte :\t\t-\n\tID de connexion :\t\t0x0\n\nInformations sur le processus :\n\tID du nouveau processus :\t\t0x2840\n\tNom du nouveau processus :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tType d'élévation du jeton :\tType d’élévation de jeton limité (3)\n\tÉtiquette obligatoire :\t\tS-1-16-4096\n\tID du processus créateur :\t0x1b90\n\tNom du processus créateur :\tC:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\n\tLigne de commande du processus :\t\"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe\" --type=renderer --enable-dinosaur-easter-egg-alt-images --no-appcompat-clear --lang=fr --device-scale-factor=1.5 --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=655 --time-ticks-at-unix-epoch=-1715583659929242 --launch-time-ticks=110755961024 --field-trial-handle=16580,i,2479432339746349396,15067989576409705824,262144 --variations-seed-version=20240429-180218.438000 --mojo-platform-channel-handle=11388 /prefetch:1\n\nLe type d'élévation du jeton indique le type de jeton qui a été attribué au nouveau processus conformément à la stratégie Contrôle de compte d'utilisateur.\n\nLe type 1 est un jeton complet sans aucun privilège supprimé ni groupe désactivé. Un jeton complet est uniquement utilisé si le Contrôle de compte d'utilisateur est désactivé, ou que l'utilisateur est le compte d'administrateur intégré ou un compte de service.\n\nLe type 2 est un jeton avec élévation de privilèges sans aucun privilège supprimé ni groupe désactivé. Un jeton avec élévation de privilèges est utilisé lorsque le Contrôle de compte d'utilisateur est activé et que l'utilisateur choisit de démarrer le programme en tant qu'administrateur. Un jeton avec élévation de privilèges est également utilisé lorsqu'une application est configurée pour exiger systématiquement un privilège administratif ou le privilège maximal, et que l'utilisateur est membre du groupe Administrateurs.\n\nLe type 3 est un jeton limité dont les privilèges administratifs sont supprimés et les groupes administratifs désactivés. Le jeton limité est utilisé lorsque le Contrôle de compte d'utilisateur est activé, que l'application n'exige pas le privilège administratif et que l'utilisateur ne choisit pas de démarrer le programme en tant qu'administrateur."
    ]
  }
}

Is my filter incorrect or misconfigured in some ways ?

2

I think this is caused by your csv filter. Are you setting pipeline.workers to 1 and ensuring pipeline.ordered evaluates true? Suppose your events look like

Field 1, Field 2, ...
La plateforme de filtrage Windows a autorisé une connexion.,4688
Un nouveau processus a été créé.,5164

You want the first two columns to be parsed as [Field 1] and [Field 2], but if logstash processes the second line before the first it will use that to set the column names, and you will end up processing the third line as having a field called [La plateforme de filtrage Windows a autorisé une connexion.] containing "Un nouveau processus a été créé.", which is exactly what you seem to have.

3

Hi,

The pipeline setting info (which is the default one)

  • "pipeline.workers"=>8,
  • "pipeline.batch.size"=>125,
  • "pipeline.batch.delay"=>50,
  • "pipeline.max_inflight"=>1000,
  • "pipeline.sources"=>["/usr/share/logstash/pipeline/winlogbeat/01-inputs.conf", "/usr/share/logstash/pipeline/winlogbeat/10-outputs.conf", "/usr/share/logstash/pipeline/winlogbeat/30-winlog-event-desc.conf", "/usr/share/logstash/pipeline/winlogbeat/40-winlog-removetag.conf"

I will take three event.id to show you the differences, in each event, the unknow field name is always La plateforme de filtrage Windows a autorisé une connexion. but its value change for each event.id and match the Event Description that is not extracted by default in event.original or message fields.

  • event.id : 4673
Field Value
(? unknown field) La plateforme de filtrage Windows a autorisé une connexion. Un service privilégié a été appelé.
event.orignal Un service privilégié a été appelé. Sujet : ID de sécurité : S-1-5-21-0000000-00000000000000-00000000000-1125 Nom du compte : username_test Domaine du compte : LAB ID d’ouverture de session : 0x10050DD Service : Serveur : Security Nom du service : - Processus : ID du processus : 0x25c0 Nom du processus : C:\Program Files\Google\Chrome\Application\chrome.exe Informations sur la demande de service : Privilèges : SeTcbPrivilege
winlog.event_details A privileged service was called.
  • event.id : 4689
Field Value
(? unknown field) La plateforme de filtrage Windows a autorisé une connexion. Un processus est terminé.
event.original Un processus est terminé. Sujet : ID de sécurité : S-1-5-18 Nom du compte : CLI-LAB-08$ Domaine du compte : LAB ID d’ouverture de session : 0x3E7 Informations sur le processus : ID du processus : 0x18e8 Nom du processus : C:\Windows\System32\svchost.exe État de fin : 0x0
winlog.event_details A process has exited.
  • event.id : 4688
Field Value
(? unknown field) La plateforme de filtrage Windows a autorisé une connexion. Un nouveau processus a été créé.
event.original Un nouveau processus a été créé. Objet créateur : ID de sécurité : S-1-5-18 Nom du compte : CLI-LAB-08$ Domaine du compte : LAB ID de connexion : 0x3E7 Objet cible : ID de sécurité : S-1-0-0 Nom du compte : - Domaine du compte : - ID de connexion : 0x0
winlog.event_details A new process has been created.

- Here's my csv file

Windows-EventID-toEventDescription.csv 
"EventID","EventDescription"
"21","RDP: Session Logon Succeeded"
"22","RDP: Shell Start Notification received"
"23","RDP: Session Logoff Succeeded"
"24","RDP: Session has been disconnected"
"25","RDP: Session Reconnection Succeeded"
"70","DHCPv4.ScopeConfigured"
"71","DHCPv4.ScopeModified"
"72","DHCPv4.ScopeDeleted"
"73","DHCPv4.ScopeActivated"
"74","DHCPv4.ScopeDeActivated"
"75","DHCPv4.ScopeLeaseUpdate"
"76","DHCPv4.ScopeOptionUpdate"
"77","DHCPv4.ScopeDNSEnable"
"78","DHCPv4.ScopeDNSDisable"
"79","DHCPv4.ScopeDNSUpdate_Req_by_Client"
"80","DHCPv4.ScopeDNSUpdate_Always"
"81","DHCPv4.ScopeDNSEnable_Discard"
"82","DHCPv4.ScopeDNSDisable_Discard"
"83","DHCPv4.ScopeDNSEnable_Update_Client_NoReq"
"84","DHCPv4.ScopeDNSDisable_Update_Client_NoReq"
"85","DHCPv4.ScopePBA_DeActivated"
"86","DHCPv4.ScopePBA_Activated"
"87","DHCPv4.ScopeDHCIDEnable"
"88","DHCPv4.ScopeDHCIDDisable"
"89","DHCPv4.ScopeSupportType"
"90","DHCPv4.ScopeNAPEnabled"
"91","DHCPv4.ScopeNAPDisabled"
"92","DHCPv4.ScopeNAPProfileConfigured"
"93","DHCPv4.ScopeNAPProfileModified"
"94","DHCPv4.ScopeNAPProfileDeleted"
"95","DHCPv4.MulticastScopeConfigured"
"96","DHCPv4.MulticastScopeDeleted"
"98","DHCPv4.SuperScopeConfigured"
"99","DHCPv4.SuperScopeDeleted"
"100","DHCPv4.SuperScopeActivated"
"101","DHCPv4.SuperScopeDeActivated"
"102","DHCPv4.SuperScopeDeleteTemp"
"103","DHCPv4.SuperScopeDeletePerm"
"105","DHCPv4.ServerOptionUpdate"
"106","DHCPv4.ReservationConfigured"
"107","DHCPv4.ReservationDeleted"
"108","DHCPv4.ReservationDNSEnable"
"109","DHCPv4.ReservationDNSDisable"
"110","DHCPv4.ReservationDNSUpdate_Req_by_Client"
"111","DHCPv4.ReservationDNSUpdate_Always"
"112","DHCPv4.ReservationDNSEnable_Discard"
"113","DHCPv4.ReservationDNSDisable_Discard"
"114","DHCPv4.ReservationDNSEnableUpdate_No_Req_by_Client"
"115","DHCPv4.ReservationDNSDisableUpdate_No_Req_by_Client"
"116","DHCPv4.ReservationOptionUpdate"
"117","DHCPv4.ServerPBA_DeActivated"
"118","DHCPv4.ServerPBA_Activated"
"119","DHCPv4.ScopeExclusionAdded"
"120","DHCPv4.ScopeExclusionDeleted"
"121","DHCPv4.ScopeEnableAllow"
"122","DHCPv4.ScopeDisableAllow"
"123","DHCPv4.ScopeAllow_AddFilter"
"124","DHCPv4.ScopeAllow_DeleteFilter"
"125","DHCPv4.ScopeEnableDeny"
"126","DHCPv4.ScopeDisableDeny"
"127","DHCPv4.ScopeDeny_AddFilter"
"128","DHCPv4.ScopeDeny_DeleteFilter"
"130","DHCPv6.ScopeDeleted"
"131","DHCPv6.ScopeActivated"
"132","DHCPv6.ScopeDeActivated"
"133","DHCPv6.ScopeLeasePreferredUpdate"
"134","DHCPv6.ScopeLeaseValidUpdate"
"135","DHCPv6.ScopeOptionUpdate"
"136","DHCPv6.ScopeDNSEnable"
"137","DHCPv6.ScopeDNSDisable"
"138","DHCPv6.ScopeDNSUpdate_Req_by_Client"
"139","DHCPv6.ScopeDNSUpdate_Always"
"140","DHCPv6.ScopeDNSEnable_Discard"
"141","DHCPv6.ScopeDNSDisable_Discard"
"142","DHCPv6.ScopeDHCIDEnable"
"143","DHCPv6.ScopeDHCIDDisable"
"145","DHCPv6.ReservationConfigured"
"147","DHCPv6.ReservationDeleted"
"148","DHCPv6.ReservationDNSEnable"
"149","DHCPv6.ReservationDNSDisable"
"150","DHCPv6.ReservationDNSUpdate_Req_by_Client"
"151","DHCPv6.ReservationDNSUpdate_Always"
"152","DHCPv6.ReservationDNSEnable_Discard"
"153","DHCPv6.ReservationDNSDisable_Discard"
"154","DHCPv6.ReservationOptionUpdate"
"155","DHCPv6.ScopeExclusionAdded"
"156","DHCPv6.ScopeExclusionDeleted"
"157","DHCPv6.ScopeModified"
"158","DHCPv6.ScopeStatelessEnabled"
"159","DHCPv6.ScopeStatelessDisabled"
"160","DHCPv6.ServerStatelessEnabled"
"161","DHCPv6.ServerStatelessDisabled"
"162","DHCPv6.ScopeStatelessPurgeInterval"
"163","DHCPv6.ServerStatelessPurgeInterval"
"165","DHCPv4.ScopeDNSDisable_DisablePtrUpdates"
"166","DHCPv6.ServerOptionUpdate"
"513","Zone delete"
"514","Zone updated"
"515","Record create"
"516","Record delete"
"517","RRSET delete"
"518","Node delete"
"519","Record create - dynamic update"
"520","Record delete - dynamic update"
"521","Record scavenge"
"522","Zone scope create"
"523","Zone scope delete"
"525","Zone sign"
"526","Zone unsign"
"527","Zone re-sign"
"528","Key rollover start"
"529","Key rollover end"
"530","Key retire"
"531","Key rollover triggered"
"533","Key poke rollover"
"534","Export DNSSEC"
"535","Import DNSSEC"
"536","Cache purge"
"537","Forwarder reset"
"540","Root hints"
"541","Server setting"
"542","Server scope create"
"543","Server scope delete"
"544","Add trust point DNSKEY"
"545","Add trust point DS"
"546","Remove trust point"
"547","Add trust point root"
"548","Restart server"
"549","Clear debug logs"
"550","Write dirty zones"
"551","Clear statistics"
"552","Start scavenging"
"553","Enlist directory partition"
"554","Abort scavenging"
"555","Prepare for demotion"
"556","Write root hints"
"557","Listen address"
"558","Active refresh trust points"
"559","Pause zone"
"560","Resume zone"
"561","Reload zone"
"562","Refresh zone"
"563","Expire zone"
"564","Update from DS"
"565","Write and notify"
"566","Force aging"
"567","Scavenge servers"
"568","Transfer key master"
"569","Add SKD"
"570","Modify SKD"
"571","Delete SKD"
"572","Modify SKD state"
"573","Add delegation"
"574","Create client subnet record"
"575","Delete client subnet record"
"576","Update client subnet record"
"577","Create server level policy"
"578","Create zone level policy"
"579","Create forwarding policy"
"580","Delete server level policy"
"581","delete zone level policy"
"582","Delete forwarding policy"
"1006","MALWAREPROTECTION_MALWARE_DETECTED"
"1007","MALWAREPROTECTION_MALWARE_ACTION_TAKEN"
"1008","MALWAREPROTECTION_MALWARE_ACTION_FAILED"
"1009","MALWAREPROTECTION_QUARANTINE_RESTORE"
"1015","MALWAREPROTECTION_BEHAVIOR_DETECTED"
"1024","The client has initiated a multi-transport connection to the server"
"1025","RDP ClientActiveX has connected to the server"
"1026","RPP ClientActiveX has been disconnected"
"1102","The Client has initiated a multi-transport connection to the server"
"1103","The client has established a multi-transport connection to the server"
"1105","The multi-transport connection has been disconnected"
"1116","MALWAREPROTECTION_STATE_MALWARE_DETECTED"
"1117","MALWAREPROTECTION_STATE_MALWARE_ACTION_TAKEN"
"1118","MALWAREPROTECTION_STATE_MALWARE_ACTION_FAILED"
"1119","MALWAREPROTECTION_STATE_MALWARE_ACTION_CRITICALLY_FAILED"
"1401","The server is using version 0xA0502 of the RDP graphics protocol"
"4608","Windows is starting up"
"4609","Windows is shutting down."
"4610","An authentication package has been loaded by the Local Security Authority."
"4611","A trusted logon process has been registered with the Local Security Authority."
"4612","Internal resources allocated for the queuing of audit messages have been exhausted, leading to the loss of some audits."
"4614","A notification package has been loaded by the Security Account Manager."
"4615","Invalid use of LPC port."
"4616","The system time was changed."
"4618","A monitored security event pattern has occurred."
"4621","Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some auditable activity might not have been recorded."
"4622","A security package has been loaded by the Local Security Authority."
"4624","An account was successfully logged on."
"4625","An account failed to log on."
"4626","User/Device claims information."
"4627","Group membership information. "
"4634","An account was logged off."
"4646","IKE DoS-prevention mode started"
"4647","User initiated logoff."
"4648","A logon was attempted using explicit credentials."
"4649","A replay attack was detected."
"4650","An IPsec Main Mode security association was established. Extended Mode was not enabled. Certificate authentication was not used."
"4651","An IPsec Main Mode security association was established. Extended Mode was not enabled. A certificate was used for authentication."
"4652","An IPsec Main Mode negotiation failed."
"4653","An IPsec Main Mode negotiation failed."
"4654","An IPsec Quick Mode negotiation failed."
"4655","An IPsec Main Mode security association ended."
"4656","A handle to an object was requested."
"4657","A registry value was modified."
"4658","The handle to an object was closed."
"4659","A handle to an object was requested with intent to delete."
"4660","An object was deleted."
"4661","A handle to an object was requested."
"4662","An operation was performed on an object."
"4663","An attempt was made to access an object."
"4664","An attempt was made to create a hard link."
"4665","An attempt was made to create an application client context."
"4666","An application attempted an operation:"
"4667","An application client context was deleted."
"4668","An application was initialized."
"4670","Permissions on an object were changed."
"4671","An application attempted to access a blocked ordinal through the TBS."
"4672","Special privileges assigned to new logon."
"4673","A privileged service was called."
"4674","An operation was attempted on a privileged object."
"4675","SIDs were filtered."
"4688","A new process has been created."
"4689","A process has exited."
"4690","An attempt was made to duplicate a handle to an object."
"4691","Indirect access to an object was requested."
"4692","Backup of data protection master key was attempted."
"4693","Recovery of data protection master key was attempted."
"4694","Protection of auditable protected data was attempted."
"4695","Unprotection of auditable protected data was attempted."
"4696","A primary token was assigned to process."
"4697","A service was installed in the system."
"4698","A scheduled task was created."
"4699","A scheduled task was deleted."
"4700","A scheduled task was enabled."
"4701","A scheduled task was disabled."
"4702","A scheduled task was updated."
"4703","A user right was adjusted."
"4704","A user right was assigned."
"4705","A user right was removed."
"4706","A new trust was created to a domain."
"4707","A trust to a domain was removed."
"4709","IPsec Services was started."
"4710","IPsec Services was disabled."
"4711","May contain any one of the following: PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer."
"4712","IPsec Services encountered a potentially serious failure."
"4713","Kerberos policy was changed."
"4714","Encrypted data recovery policy was changed."
"4715","The audit policy (SACL) on an object was changed."
"4716","Trusted domain information was modified."
"4717","System security access was granted to an account."
"4718","System security access was removed from an account."
"4719","System audit policy was changed."
"4720","A user account was created."
"4722","A user account was enabled."
"4723","An attempt was made to change an account's password."
"4724","An attempt was made to reset an account's password."
"4725","A user account was disabled."
"4726","A user account was deleted."
"4727","A security-enabled global group was created."
"4728","A member was added to a security-enabled global group."
"4729","A member was removed from a security-enabled global group."
"4730","A security-enabled global group was deleted."
"4731","A security-enabled local group was created."
"4732","A member was added to a security-enabled local group."
"4733","A member was removed from a security-enabled local group."
"4734","A security-enabled local group was deleted."
"4735","A security-enabled local group was changed."
"4737","A security-enabled global group was changed."
"4738","A user account was changed."
"4739","Domain Policy was changed."
"4740","A user account was locked out."
"4742","A computer account was changed."
"4743","A computer account was deleted."
"4744","A security-disabled local group was created."
"4745","A security-disabled local group was changed."
"4746","A member was added to a security-disabled local group."
"4747","A member was removed from a security-disabled local group."
"4748","A security-disabled local group was deleted."
"4749","A security-disabled global group was created."
"4750","A security-disabled global group was changed."
"4751","A member was added to a security-disabled global group."
"4752","A member was removed from a security-disabled global group."
"4753","A security-disabled global group was deleted."
"4754","A security-enabled universal group was created."
"4755","A security-enabled universal group was changed."
"4756","A member was added to a security-enabled universal group."
"4757","A member was removed from a security-enabled universal group."
"4758","A security-enabled universal group was deleted."
"4759","A security-disabled universal group was created."
"4760","A security-disabled universal group was changed."
"4761","A member was added to a security-disabled universal group."
"4762","A member was removed from a security-disabled universal group."
"4764","A group’s type was changed."
"4765","SID History was added to an account."
"4766","An attempt to add SID History to an account failed."
"4767","A user account was unlocked."
"4768","A Kerberos authentication ticket (TGT) was requested."
"4769","A Kerberos service ticket was requested."
"4770","A Kerberos service ticket was renewed."
"4771","Kerberos pre-authentication failed."
"4772","A Kerberos authentication ticket request failed."
"4773","A Kerberos service ticket request failed."
"4774","An account was mapped for logon."
"4775","An account could not be mapped for logon."
"4776","The domain controller attempted to validate the credentials for an account."
"4777","The domain controller failed to validate the credentials for an account."
"4778","A session was reconnected to a Window Station."
"4779","A session was disconnected from a Window Station."
"4780","The ACL was set on accounts which are members of administrators groups."
"4781","The name of an account was changed:"
"4782","The password hash an account was accessed."
"4783","A basic application group was created."
"4784","A basic application group was changed."
"4785","A member was added to a basic application group."
"4786","A member was removed from a basic application group."
"4787","A non-member was added to a basic application group."
"4788","A non-member was removed from a basic application group."
"4789","A basic application group was deleted."
"4790","An LDAP query group was created."
"4791","A basic application group was changed."
"4792","An LDAP query group was deleted."
"4793","The Password Policy Checking API was called."
"4794","An attempt was made to set the Directory Services Restore Mode."
"4797","An attempt was made to query the existence of a blank password for an account."
"4798","A user's local group membership was enumerated. "
"4799","A security-enabled local group membership was enumerated."
"4800","The workstation was locked."
"4801","The workstation was unlocked."
"4802","The screen saver was invoked."
"4803","The screen saver was dismissed."
"4816","RPC detected an integrity violation while decrypting an incoming message."
"4817","Auditing settings on an object were changed."
"4818","Proposed Central Access Policy does not grant the same access permissions as the current Central Access Policy"
"4819","Central Access Policies on the machine have been changed."
"4820","A Kerberos Ticket-granting-ticket (TGT) was denied because the device does not meet the access control restrictions."
"4821","A Kerberos service ticket was denied because the user, device, or both does not meet the access control restrictions."
"4822","NTLM authentication failed because the account was a member of the Protected User group."
"4823","NTLM authentication failed because access control restrictions are required."
"4824","Kerberos preauthentication by using DES or RC4 failed because the account was a member of the Protected User group."
"4825","A user was denied the access to Remote Desktop."
"4826","Boot Configuration Data loaded."
"4864","A namespace collision was detected."
"4865","A trusted forest information entry was added."
"4866","A trusted forest information entry was removed."
"4867","A trusted forest information entry was modified."
"4868","The certificate manager denied a pending certificate request."
"4869","Certificate Services received a resubmitted certificate request."
"4870","Certificate Services revoked a certificate."
"4871","Certificate Services received a request to publish the certificate revocation list (CRL)."
"4872","Certificate Services published the certificate revocation list (CRL)."
"4873","A certificate request extension changed."
"4874","One or more certificate request attributes changed."
"4875","Certificate Services received a request to shut down."
"4876","Certificate Services backup started."
"4877","Certificate Services backup completed."
"4878","Certificate Services restore started."
"4879","Certificate Services restore completed."
"4880","Certificate Services started."
"4881","Certificate Services stopped."
"4882","The security permissions for Certificate Services changed."
"4883","Certificate Services retrieved an archived key."
"4884","Certificate Services imported a certificate into its database."
"4885","The audit filter for Certificate Services changed."
"4886","Certificate Services received a certificate request."
"4887","Certificate Services approved a certificate request and issued a certificate."
"4888","Certificate Services denied a certificate request."
"4889","Certificate Services set the status of a certificate request to pending."
"4890","The certificate manager settings for Certificate Services changed."
"4891","A configuration entry changed in Certificate Services."
"4892","A property of Certificate Services changed."
"4893","Certificate Services archived a key."
"4894","Certificate Services imported and archived a key."
"4895","Certificate Services published the CA certificate to Active Directory Domain Services."
"4896","One or more rows have been deleted from the certificate database."
"4897","Role separation enabled:"
"4898","Certificate Services loaded a template."
"4899","A Certificate Services template was updated."
"4900","Certificate Services template security was updated."
"4902","The Per-user audit policy table was created."
"4904","An attempt was made to register a security event source."
"4905","An attempt was made to unregister a security event source."
"4906","The CrashOnAuditFail value has changed."
"4907","Auditing settings on object were changed."
"4908","Special Groups Logon table modified."
"4909","The local policy settings for the TBS were changed."
"4910","The group policy settings for the TBS were changed."
"4911","Resource attributes of the object were changed."
"4912","Per User Audit Policy was changed."
"4913","Central Access Policy on the object was changed."
"4928","An Active Directory replica source naming context was established."
"4929","An Active Directory replica source naming context was removed."
"4930","An Active Directory replica source naming context was modified."
"4931","An Active Directory replica destination naming context was modified."
"4932","Synchronization of a replica of an Active Directory naming context has begun."
"4933","Synchronization of a replica of an Active Directory naming context has ended."
"4934","Attributes of an Active Directory object were replicated."
"4935","Replication failure begins."
"4936","Replication failure ends."
"4937","A lingering object was removed from a replica."
"4944","The following policy was active when the Windows Firewall started."
"4945","A rule was listed when the Windows Firewall started."
"4946","A change has been made to Windows Firewall exception list. A rule was added."
"4947","A change has been made to Windows Firewall exception list. A rule was modified."
"4948","A change has been made to Windows Firewall exception list. A rule was deleted."
"4949","Windows Firewall settings were restored to the default values."
"4950","A Windows Firewall setting has changed."
"4951","A rule has been ignored because its major version number was not recognized by Windows Firewall."
"4952","Parts of a rule have been ignored because its minor version number was not recognized by Windows Firewall. The other parts of the rule will be enforced."
"4953","A rule has been ignored by Windows Firewall because it could not parse the rule."
"4954","Windows Firewall Group Policy settings have changed. The new settings have been applied."
"4956","Windows Firewall has changed the active profile."
"4957","Windows Firewall did not apply the following rule:"
"4958","Windows Firewall did not apply the following rule because the rule referred to items not configured on this computer:"
"4960","IPsec dropped an inbound packet that failed an integrity check. If this problem persists, it could indicate a network issue or that packets are being modified in transit to this computer. Verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations."
"4961","IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer."
"4962","IPsec dropped an inbound packet that failed a replay check. The inbound packet had too low a sequence number to ensure it was not a replay."
"4963","IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt."
"4964","Special groups have been assigned to a new logon."
"4965","IPsec received a packet from a remote computer with an incorrect Security Parameter Index (SPI). This is usually caused by malfunctioning hardware that is corrupting packets. If these errors persist, verify that the packets sent from the remote computer are the same as those received by this computer. This error may also indicate interoperability problems with other IPsec implementations. In that case, if connectivity is not impeded, then these events can be ignored."
"4976","During Main Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation."
"4977","During Quick Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation."
"4978","During Extended Mode negotiation, IPsec received an invalid negotiation packet. If this problem persists, it could indicate a network issue or an attempt to modify or replay this negotiation."
"4979","IPsec Main Mode and Extended Mode security associations were established."
"4980","IPsec Main Mode and Extended Mode security associations were established."
"4981","IPsec Main Mode and Extended Mode security associations were established."
"4982","IPsec Main Mode and Extended Mode security associations were established."
"4983","An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted."
"4984","An IPsec Extended Mode negotiation failed. The corresponding Main Mode security association has been deleted."
"4985","The state of a transaction has changed."
"5024","The Windows Firewall Service has started successfully."
"5025","The Windows Firewall Service has been stopped."
"5027","The Windows Firewall Service was unable to retrieve the security policy from the local storage. The service will continue enforcing the current policy."
"5028","The Windows Firewall Service was unable to parse the new security policy. The service will continue with currently enforced policy."
"5029","The Windows Firewall Service failed to initialize the driver. The service will continue to enforce the current policy."
"5030","The Windows Firewall Service failed to start."
"5031","The Windows Firewall Service blocked an application from accepting incoming connections on the network."
"5032","Windows Firewall was unable to notify the user that it blocked an application from accepting incoming connections on the network."
"5033","The Windows Firewall Driver has started successfully."
"5034","The Windows Firewall Driver has been stopped."
"5035","The Windows Firewall Driver failed to start."
"5037","The Windows Firewall Driver detected critical runtime error. Terminating."
"5038","Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error."
"5039","A registry key was virtualized."
"5040","A change has been made to IPsec settings. An Authentication Set was added."
"5041","A change has been made to IPsec settings. An Authentication Set was modified."
"5042","A change has been made to IPsec settings. An Authentication Set was deleted."
"5043","A change has been made to IPsec settings. A Connection Security Rule was added."
"5044","A change has been made to IPsec settings. A Connection Security Rule was modified."
"5045","A change has been made to IPsec settings. A Connection Security Rule was deleted."
"5046","A change has been made to IPsec settings. A Crypto Set was added."
"5047","A change has been made to IPsec settings. A Crypto Set was modified."
"5048","A change has been made to IPsec settings. A Crypto Set was deleted."
"5049","An IPsec Security Association was deleted."
"5050","An attempt to programmatically disable the Windows Firewall was rejected because this API is not supported on Windows Vista."
"5051","A file was virtualized."
"5056","A cryptographic self test was performed."
"5057","A cryptographic primitive operation failed."
"5058","Key file operation."
"5059","Key migration operation."
"5060","Verification operation failed."
"5061","Cryptographic operation."
"5062","A kernel-mode cryptographic self test was performed."
"5063","A cryptographic provider operation was attempted."
"5064","A cryptographic context operation was attempted."
"5065","A cryptographic context modification was attempted."
"5066","A cryptographic function operation was attempted."
"5067","A cryptographic function modification was attempted."
"5068","A cryptographic function provider operation was attempted."
"5069","A cryptographic function property operation was attempted."
"5070","A cryptographic function property modification was attempted."
"5071","Key access denied by Microsoft key distribution service."
"5120","OCSP Responder Service Started."
"5121","OCSP Responder Service Stopped."
"5122","A Configuration entry changed in the OCSP Responder Service."
"5123","A configuration entry changed in the OCSP Responder Service."
"5124","A security setting was updated on OCSP Responder Service."
"5125","A request was submitted to OCSP Responder Service."
"5126","Signing Certificate was automatically updated by the OCSP Responder Service."
"5127","The OCSP Revocation Provider successfully updated the revocation information."
"5136","A directory service object was modified."
"5137","A directory service object was created."
"5138","A directory service object was undeleted."
"5139","A directory service object was moved."
"5140","A network share object was accessed."
"5141","A directory service object was deleted."
"5142","A network share object was added."
"5143","A network share object was modified."
"5144","A network share object was deleted."
"5145","A network share object was checked to see whether the client can be granted desired access."
"5146","The Windows Filtering Platform has blocked a packet."
"5147","A more restrictive Windows Filtering Platform filter has blocked a packet."
"5148","The Windows Filtering Platform has detected a DoS attack and entered a defensive mode; packets associated with this attack will be discarded."
"5149","The DoS attack has subsided and normal processing is being resumed."
"5150","The Windows Filtering Platform has blocked a packet."
"5151","A more restrictive Windows Filtering Platform filter has blocked a packet."
"5152","The Windows Filtering Platform blocked a packet."
"5153","A more restrictive Windows Filtering Platform filter has blocked a packet."
"5154","The Windows Filtering Platform has permitted an application or service to listen on a port for incoming connections."
"5155","The Windows Filtering Platform has blocked an application or service from listening on a port for incoming connections."
"5156","The Windows Filtering Platform has allowed a connection."
"5157","The Windows Filtering Platform has blocked a connection."
"5158","The Windows Filtering Platform has permitted a bind to a local port."
"5159","The Windows Filtering Platform has blocked a bind to a local port."
"5168","Spn check for SMB/SMB2 failed."
"5169","A directory service object was modified.     "
"5376","Credential Manager credentials were backed up."
"5377","Credential Manager credentials were restored from a backup."
"5378","The requested credentials delegation was disallowed by policy."
"5440","The following callout was present when the Windows Filtering Platform Base Filtering Engine started."
"5441","The following filter was present when the Windows Filtering Platform Base Filtering Engine started."
"5442","The following provider was present when the Windows Filtering Platform Base Filtering Engine started."
"5443","The following provider context was present when the Windows Filtering Platform Base Filtering Engine started."
"5444","The following sub-layer was present when the Windows Filtering Platform Base Filtering Engine started."
"5446","A Windows Filtering Platform callout has been changed."
"5447","A Windows Filtering Platform filter has been changed."
"5448","A Windows Filtering Platform provider has been changed."
"5449","A Windows Filtering Platform provider context has been changed."
"5450","A Windows Filtering Platform sub-layer has been changed."
"5451","An IPsec Quick Mode security association was established."
"5452","An IPsec Quick Mode security association ended."
"5453","An IPsec negotiation with a remote computer failed because the IKE and AuthIP IPsec Keying Modules (IKEEXT) service is not started."
"5456","PAStore Engine applied Active Directory storage IPsec policy on the computer."
"5457","PAStore Engine failed to apply Active Directory storage IPsec policy on the computer."
"5458","PAStore Engine applied locally cached copy of Active Directory storage IPsec policy on the computer."
"5459","PAStore Engine failed to apply locally cached copy of Active Directory storage IPsec policy on the computer."
"5460","PAStore Engine applied local registry storage IPsec policy on the computer."
"5461","PAStore Engine failed to apply local registry storage IPsec policy on the computer."
"5462","PAStore Engine failed to apply some rules of the active IPsec policy on the computer. Use the IP Security Monitor snap-in to diagnose the problem."
"5463","PAStore Engine polled for changes to the active IPsec policy and detected no changes."
"5464","PAStore Engine polled for changes to the active IPsec policy, detected changes, and applied them to IPsec Services."
"5465","PAStore Engine received a control for forced reloading of IPsec policy and processed the control successfully."
"5466","PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory cannot be reached, and will use the cached copy of the Active Directory IPsec policy instead. Any changes made to the Active Directory IPsec policy since the last poll could not be applied."
"5467","PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, and found no changes to the policy. The cached copy of the Active Directory IPsec policy is no longer being used."
"5468","PAStore Engine polled for changes to the Active Directory IPsec policy, determined that Active Directory can be reached, found changes to the policy, and applied those changes. The cached copy of the Active Directory IPsec policy is no longer being used."
"5471","PAStore Engine loaded local storage IPsec policy on the computer."
"5472","PAStore Engine failed to load local storage IPsec policy on the computer."
"5473","PAStore Engine loaded directory storage IPsec policy on the computer."
"5474","PAStore Engine failed to load directory storage IPsec policy on the computer."
"5477","PAStore Engine failed to add quick mode filter."
"5478","IPsec Services has started successfully."
"5479","IPsec Services has been shut down successfully. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks."
"5480","IPsec Services failed to get the complete list of network interfaces on the computer. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem."
"5483","IPsec Services failed to initialize RPC server. IPsec Services could not be started."
"5484","IPsec Services has experienced a critical failure and has been shut down. The shutdown of IPsec Services can put the computer at greater risk of network attack or expose the computer to potential security risks."
"5485","IPsec Services failed to process some IPsec filters on a plug-and-play event for network interfaces. This poses a potential security risk because some of the network interfaces may not get the protection provided by the applied IPsec filters. Use the IP Security Monitor snap-in to diagnose the problem."
"5632","A request was made to authenticate to a wireless network."
"5633","A request was made to authenticate to a wired network."
"5712","A Remote Procedure Call (RPC) was attempted."
"5888","An object in the COM+ Catalog was modified."
"5889","An object was deleted from the COM+ Catalog."
"5890","An object was added to the COM+ Catalog."
"6144","Security policy in the group policy objects has been applied successfully."
"6145","One or more errors occurred while processing security policy in the group policy objects."
"6272","Network Policy Server granted access to a user."
"6273","Network Policy Server denied access to a user."
"6274","Network Policy Server discarded the request for a user."
"6275","Network Policy Server discarded the accounting request for a user."
"6276","Network Policy Server quarantined a user."
"6277","Network Policy Server granted access to a user but put it on probation because the host did not meet the defined health policy."
"6278","Network Policy Server granted full access to a user because the host met the defined health policy."
"6279","Network Policy Server locked the user account due to repeated failed authentication attempts."
"6280","Network Policy Server unlocked the user account."
"6281","Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error"
"6400","BranchCache: Received an incorrectly formatted response while discovering availability of content. "
"6401","BranchCache: Received invalid data from a peer. Data discarded. "
"6402","BranchCache: The message to the hosted cache offering it data is incorrectly formatted. "
"6403","BranchCache: The hosted cache sent an incorrectly formatted response to the client."
"6404","BranchCache: Hosted cache could not be authenticated using the provisioned SSL certificate. "
"6405","BranchCache: %2 instance(s) of event id %1 occurred."
"6406","%1 registered to Windows Firewall to control filtering for the following: %2"
"6407","1%"
"6408","Registered product %1 failed and Windows Firewall is now controlling the filtering for %2"
"6409","BranchCache: A service connection point object could not be parsed."
"6410","Code integrity determined that a file does not meet the security requirements to load into a process."
"6416","A new external device was recognized by the System"
"6417","The FIPS mode crypto selftests succeeded."
"6418","The FIPS mode crypto selftests failed."
"6419","A request was made to disable a device"
"6420","A device was disabled."
"6421","A request was made to enable a device."
"6422","A device was enabled."
"6423","The installation of this device is forbidden by system policy"
"6424","The installation of this device was allowed, after having previously been forbidden by policy."
"20220","DHCPv4.UpdateServerPolicyState"
"20221","DHCPv4.UpdateScopePolicyState"
"20222","DHCPv4.UpdateServerPolicyExpr"
"20223","DHCPv4.UpdateScopePolicyExpr"
"20226","DHCPv4.DeleteServerPolicy"
"20227","DHCPv4.DeleteScopePolicy"
"20228","DHCPv4.SetScopePolicyRange"
"20229","DHCPv4.RemoveScopePolicyRange"
"20230","DHCPv4.SetServerPolicyOption"
"20231","DHCPv4.SetScopePolicyOption"
"20232","DHCPv4.UnsetServerPolicyOption"
"20233","DHCPv4.UnsetScopePolicyOption"
"20234","DHCPv4.UpdateServerPolicyName"
"20235","DHCPv4.UpdateScopePolicyName"
"20236","DHCPv4.UpdateServerPolicyDescription"
"20237","DHCPv4.UpdateScopePolicyDescription"
"20238","DHCPv4.UpdateServerPolicyProcOrder"
"20239","DHCPv4.UpdateScopePolicyProcOrder"
"20241","DHCPv4.CreateFailoverRelationshipHotStandby"
"20242","DHCPv4.DeleteFailoverRelationship"
"20243","DHCPv4.AddScopeRelationship"
"20244","DHCPv4.DeleteScopeRelationship"
"20245","DHCPv4.UpdateRelationshipParamMclt"
"20246","DHCPv4.UpdateRelationshipParamAutoSwitchOverInterval"
"20247","DHCPv4.UpdateRelationshipParamPercentageHS"
"20248","DHCPv4.UpdateRelationshipParamPercentageLB"
"20249","DHCPv4.UpdateRelationshipParamModeHStoLB"
"20250","DHCPv4.UpdateRelationshipParamModeLBtoHS"
"20311","DHCPv4.UpdateSharedSecret"
"20312","DHCPv4.EnabledSharedSecret"
"20313","DHCPv4.DisabledSharedSecret"
"20315","DHCPv4.UpdateScopePolicyDNSSuffix"
"20316","DHCPv4.UpdateServerPolicyDNSSuffix"

There is no La plateforme de filtrage Windows a autorisé une connexion. in the csv.

Additionnal info related to my previous Log solution

To be more precise with what I'm looking for, I'm currently migrating from Graylog solution, and I need to export my filter/rules/grok from Graylogs to Logstash.

In this case, the configuration in Graylog was:

  • setting up a Lookup table with key/value pairs

image
image771×735 41 KB

  • setting up a pipeline rules calling the Lookup table function to check when event.id was present, and then creating the new field Event Description with value matching the second column of the CSV.

image
image1083×315 13.2 KB

5

I've setted pipeline.worker: 1 and pipeline.ordered: true and now it is same behaviour but everytime I restart the logstash container, the unknow field switch to a new name between: La plateforme de filtrage Windows a autorisé une connexion. or Un processus est terminé. or Un service privilégié a été appelé. and its value still match the event description in the event.original value.

  • event.id: 4673
Field Value
(? Unknown field) Un processus est terminé. Un service privilégié a été appelé.
event.original Un service privilégié a été appelé. Sujet : ID de sécurité : S-1-5-21-0000810007-841596009-2815000991-1125 Nom du compte : adm.us Domaine du compte : LAB ID d’ouverture de session : 0x10050DD Service : Serveur : Security Nom du service : - Processus : ID du processus : 0x25c0 Nom du processus : C:\Program Files\Google\Chrome\Application\chrome.exe Informations sur la demande de service : Privilèges : SeTcbPrivilege
winlog.event_details A privileged service was called.

It look like the filter take the previous event or something and set as unknown field and set the value the event description but not the one from the csv but the one in the event.original.

I can't figure out what is misconfigured ?

6

Ok after I tested multiple things, except remove the CSV filter, I did comment the csv filter and the unknown field does not appear anymore...

I thought the csv filter was needed to tells logstash how to read the csv file, but it works without it :+1:

Now I wonder why it was causing this issue with csv filter, but my "issue" is resolved :slight_smile:

Thanks @Badger, your answer helped me to resolve this.