Skip to content
Skills Library
Security · Building & coding

field-normalization

/field-normalization

Design and validate field normalization across security data models — Splunk CIM, Microsoft ASIM, Elastic ECS, OCSF, Google UDM — including mapping tables, value normalization (action/outcome, user/host formats), and parser testing. Use when building parsers, writing cross-source detections, or debugging rules that miss data due to field differences.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design and validate field normalization across security data models — Splunk CIM, Microsoft ASIM, Elastic ECS, OCSF, Google UDM — including mapping tables, value normalization (action/outcome, user/host formats), and parser testing. Use when building parsers, writing cross-source detections, or debugging rules that miss data due to field differences.

Original author description

Design and validate field normalization across security data models — Splunk CIM, Microsoft ASIM, Elastic ECS, OCSF, Google UDM — including mapping tables, value normalization (action/outcome, user/host formats), and parser testing. Use when building parsers, writing cross-source detections, or debugging rules that miss data due to field differences.

How it works

  1. Crosswalk (common fields)
  2. Value normalization rules
  3. Parser test
  4. Detection impact
  5. Related skills
  6. References
Original SKILL.md headings · 46 lines, 311 words
SKILL.md preview
---
name: field-normalization
description: Design and validate field normalization across security data models — Splunk CIM, Microsoft ASIM, Elastic ECS, OCSF, Google UDM — including mapping tables, value normalization (action/outcome, user/host formats), and parser testing. Use when building parsers, writing cross-source detections, or debugging rules that miss data due to field differences.
license: MIT
metadata:
  category: siem-engineering
  version: "2.0.0"
  verification: documented
---

# Field Normalization

## Crosswalk (common fields)

| Concept | Splunk CIM | Microsoft ASIM | Elastic ECS | OCSF |
|---|---|---|---|---|
| Source IP | `src` / `src_ip` | `SrcIpAddr` | `source.ip` | `src_endpoint.ip` |
| Destination IP | `dest` / `dest_ip` | `DstIpAddr` | `destination.ip` | `dst_endpoint.ip` |
| User | `user` | `TargetUsername` / `ActorUsername` | `user.name` | `user.name` / `actor.user.name` |
| Host | `dest` / `dvc` | `DvcHostname` | `host.name` | `device.hostname` |
| Process path | `process_path` | `TargetProcessName` | `process.executable` | `process.file.path` |
| Command line | `process` | `TargetProcessCommandLine` | `process.command_line` | `process.cmd_line` |
| Parent process | `parent_process_name` | `ActingProcessName` | `process.parent.name` | `process.parent_process.name` |
| Outcome | `action` (success/failure) | `EventResult` (Success/Failure/Partial/NA) | `event.outcome` | `status_id` / `status` |
| File hash | `file_hash` | `TargetFileSHA256` | `file.hash.sha256` | `file.hashes[]` |

Verify against the current schema versions; names above are the commonly used ones.

## Value normalization rules

- Users: decide canonical form (UPN lowercase; `DOMAIN\user` → `user@domain`) and keep original in a separate field.
- Hosts: short name vs. FQDN — keep both; lowercase.
- IPs: separate IPv4/IPv6 handling, strip ports into their own field.
- Time: UTC ISO-8601; keep source timezone.
- Outcome: map vendor codes (e.g. 4625 → failure; `ResultType != "0"` → failure) to a fixed vocabulary.

## Parser test

For each parser keep sample raw events and expected normalized output; run in CI (`detection-as-code`). Spot-check live data: `fieldsummary` (Splunk), `getschema`/`summarize count() by isempty(field)` (KQL), field statistics in Discover (Elastic).

## Detection impact

Write detections against normalized fields **only** when the fields are reliably populated for all relevant sources; otherwise the rule silently misses sources. Document per-rule which sources the normalized view includes.

## Related skills

`log-source-onboarding`, `sigma-conversion`, `correlation-rule-design`

## References

- Splunk CIM: https://docs.splunk.com/Documentation/CIM/latest/User/Overview
- Microsoft ASIM: https://learn.microsoft.com/en-us/azure/sentinel/normalization
- Elastic ECS: https://www.elastic.co/guide/en/ecs/current/index.html
- OCSF schema: https://schema.ocsf.io/

Versions

The database has no other skills named field-normalization.

Database snapshot: 13.11.2026 · package version 926c3a3e000c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100splunk
    Splunk as a SIEM/security platform across all versions (9.x-10.x): SPL query development for security detection, indexer/search head architecture, forwarder management, SmartStore, CIM normalization for security data models, knowledge objects, and deployment at scale. WHEN:…
  • 100siem-edr-connector
    Collect, normalize and correlate security alerts from SIEM and EDR platforms (Splunk SPL and REST search jobs, Elastic Security KQL/EQL/ES|QL and detection rules API, Microsoft Sentinel and Defender for Endpoint KQL, Wazuh API and indexer, CrowdStrike Falcon FQL detects and…
  • 100performing-log-source-onboarding-in-siem
    Perform structured log source onboarding into SIEM platforms (Splunk, Elastic, Sentinel, QRadar, or similar) by prioritizing sources with a tiered value framework, configuring collectors, building parsers, normalizing fields to a common schema (e.g. CIM), and validating data…
  • 95ecs-field-mappings
    Use when defining field mappings for data streams, populating ecs.yml with ECS field references, selecting ECS categorization values, choosing custom field types, or troubleshooting mapping validation failures.
  • 100elastic-investigation
    Investigate and hunt in Elastic Security using ES|QL, EQL sequences, KQL/Lucene and ECS field names — process lineage, sequences across hosts, aggregations and timeline — with performance and mapping caveats. Use when querying Elasticsearch/Elastic Security or OpenSearch security data.
  • 95azure-sentinel
    Expert knowledge for Azure Sentinel development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when configuring Sentinel data connectors,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.