nano SIEM
Reference

Migrating from UDM

Map retired UDM field names to OCSF 1.9 paths when you port saved searches, detection rules, dashboards and parsers.

Map retired UDM names to OCSF 1.9 paths when you port saved searches, detection rules, dashboard panels, notebook queries, and parsers.

Older nano installs used the Unified Data Model (UDM), with flat columns such as src_ip, process_name, and file_hash and source-specific extras in an ext JSON column. New installs store and query OCSF in the ClickHouse table ocsf_logs; see OCSF schema. The UDM profile (NANO_SCHEMA_PROFILE=udm) can still be chosen at install, and an existing install keeps the profile it was installed with, but UDM is being retired.

Old forms on the OCSF profile

Old formWhat happensUse instead
ext.fooResolves to unmapped.foounmapped.foo
source_typeResolves to the log source routing keymetadata.log_source
file_hash, process_hashResolve to the derived SHA-256 columnsfile.hashes.value / process.file.hashes.value (every algorithm), or file.hashes.sha256
src_ip, user, src_host and other UDM namesResolve to their OCSF column (class-split names such as user read a unified column) while the compatibility window lastsThe OCSF path from the tables below

file.hashes.sha256, process.file.hashes.sha256 and actor.process.file.hashes.sha256 are nano-derived columns: the SHA-256 element of each hashes[] list, lowercased.

Field map

Each UDM name maps to one canonical OCSF 1.9 path. Where OCSF splits a concept by event class, both paths are listed; see Paths depend on the class.

Event identity

UDMOCSF 1.9Notes
timestamptime
idmetadata.uid
source_typemetadata.log_source
messagemessageUnchanged
_rawraw_data
event_bytesraw_data_size
severityseverity_id (number) or severity (label)Values change, see below
event_type, actionclass_uid + activity_idValues change, see below
ext.<key>unmapped.<key>Keys are flattened to dotted snake_case
tagsunmapped.tags

Network

UDMOCSF 1.9Notes
src_ipsrc_endpoint.ip
dest_ipdst_endpoint.ipdst_, not dest_
src_portsrc_endpoint.port
dest_portdst_endpoint.port
src_hostsrc_endpoint.hostname (network classes), device.hostname (endpoint classes)Class-dependent
dest_hostdst_endpoint.hostname
src_mac, dest_macsrc_endpoint.mac, dst_endpoint.mac
protocolconnection_info.protocol_num (6)IANA number. connection_info.protocol_name (tcp) exists too, but many sources fill only the number
bytes_in, bytes_outtraffic.bytes_in, traffic.bytes_outOCSF: bytes_in is destination→source, bytes_out is source→destination
packets_in, packets_outtraffic.packets_in, traffic.packets_out
bytestraffic.bytes
response_timeduration

Hosts and users

UDMOCSF 1.9Notes
host, hostnamedevice.hostname
useruser.name or actor.user.nameClass-dependent: the account acted on vs the account acting
src_useractor.user.nameThe initiating account
user_domainuser.domain
user_iduser.uid
emailuser.email_addr
display_nameuser.display_name
auth_typeauth_protocol_id (number) or auth_protocol (label)
auth_resultstatus_id (1 Success, 2 Failure) or status (label)
mfa_usedis_mfa
session_idsession.uid
user_identity_*unmapped.user_identity_*Directory enrichment fields

Process

UDMOCSF 1.9Notes
process_nameprocess.name (Process Activity) or actor.process.name (other classes)Class-dependent
command_lineprocess.cmd_line or actor.process.cmd_lineClass-dependent
process_idprocess.pid or actor.process.pid
process_guidprocess.uid or actor.process.uid
process_pathprocess.file.path or actor.process.file.path
process_hashprocess.file.hashes.value or actor.process.file.hashes.value
parent_process_nameactor.process.nameOn Process Activity the parent is the actor
parent_command_lineactor.process.cmd_line
parent_process_pathactor.process.file.path

File

UDMOCSF 1.9Notes
file_pathfile.path
file_namefile.name
file_hashfile.hashes.valueNever file.hashes.sha256
file_actionactivity_id (number) or activity_name (label)Activity numbers depend on the class

Web, DNS and email

UDMOCSF 1.9Notes
urlhttp_request.url.url_string (HTTP) or url.url_string (other classes)Class-dependent
url_domainhttp_request.url.hostname or url.hostname
uri_pathhttp_request.url.path
http_method, methodhttp_request.http_method
http_status_code, http_statushttp_response.code
status_codehttp_response.code for HTTP statusOn OCSF, a bare status_code is the event's own status code, not the HTTP code
status (as HTTP status)http_response.codeOn OCSF, status is the event outcome label
http_user_agent, user_agenthttp_request.user_agent
http_referrer, referrerhttp_request.referrer
query, dns_queryquery.hostname
answeranswers.rdataA list
senderemail.from
recipientemail.toA list
subjectemail.subject
message_idemail.message_uid

Cloud

UDMOCSF 1.9
cloud_providercloud.provider
cloud_regioncloud.region
cloud_account_idcloud.account.uid
cloud_account_namecloud.account.name
cloud_serviceapi.service.name
resource_id, resource_name, resource_typeresources.uid, resources.name, resources.type (lists)
cvevulnerabilities.cve.uid (a list)
error_code, error_messageunmapped.error_code, unmapped.error_message

Enrichment, risk and prevalence

UDM had one column per enrichment. On the OCSF profile, geolocation fills standard endpoint attributes, and the other enrichments are nano-derived columns written at ingest.

UDMOCSF profile
enriched_src_country_code, enriched_dest_country_codesrc_endpoint.location.country, dst_endpoint.location.country
enriched_src_asn, enriched_src_as_namesrc_endpoint.autonomous_system.number, src_endpoint.autonomous_system.name (and dst_endpoint equivalents)
ioc_src_ip_threat_type, ioc_dest_ip_threat_type, ioc_domain_threat_type, ioc_hash_threat_typeenrichments.ioc_src_ip_threat_type, enrichments.ioc_dest_ip_threat_type, enrichments.ioc_domain_threat_type, enrichments.ioc_hash_threat_type
src_is_tor, dest_is_torenrichments.ioc_src_ip_threat_type="tor_exit", enrichments.ioc_dest_ip_threat_type="tor_exit"
custom_src_ip_tags, custom_dest_ip_tagsenrichments.custom_src_ip_tags, enrichments.custom_dest_ip_tags
prevalence_*prevalence_file_hash, prevalence_process_hash, prevalence_dest_domain, prevalence_dest_ip (same names)
risk_scorerisk_score (also risk_level) on Detection Findings, owned by risk-based alerting

Per-feed details: Enrichment field reference.

Values change too

For some filters the field name and the values both change. A find-and-replace on the name alone gives a query that matches nothing.

UDM filterOCSF 1.9 filterWhat changed
source_type=sysmonmetadata.log_source=windows_sysmon, or by kind: class_uid=1007Use the log source slug, or a numeric class
event_type=loginclass_uid=3002 activity_id=1String event type → class + activity numbers
auth_result=failurestatus_id=2String → number
action="created" (file)class_uid=1001 activity_id=1String → class + activity
severity=highseverity_id=4String → normalized number (0–6)
protocol=tcpconnection_info.protocol_num=6Name → IANA number (6 TCP, 17 UDP). Many sources leave connection_info.protocol_name empty

Where OCSF has both a number and a label (status_id / status, auth_protocol_id / auth_protocol, activity_id / activity_name), filter on the number. Label filters such as status="failure" also work and are case-insensitive. Don't rely on the old names: during the compatibility window some map to number paths (for example auth_type to auth_protocol_id), so an old string value can match nothing.

Before and after

Failed logons by user, legacy form:

event_type=login auth_result=failure | stats count by user, src_ip

OCSF 1.9:

class_uid=3002 activity_id=1 status_id=2 | stats count by user.name, src_endpoint.ip

Encoded PowerShell launched by Office, legacy form:

process_name="powershell.exe" parent_process_name="winword.exe" command_line="*-enc*"

OCSF 1.9:

class_uid=1007 process.name="powershell.exe" actor.process.name="winword.exe" process.cmd_line="*-enc*"

Known-bad hash anywhere, legacy form:

file_hash="44d88612fea8a8f36de82e1278abb02f" OR process_hash="44d88612fea8a8f36de82e1278abb02f"

OCSF 1.9:

file.hashes.value="44d88612fea8a8f36de82e1278abb02f" OR process.file.hashes.value="44d88612fea8a8f36de82e1278abb02f" OR actor.process.file.hashes.value="44d88612fea8a8f36de82e1278abb02f"

A source-specific extra field, legacy form:

source_type=json_generic ext.tenant_tier="gold"

OCSF 1.9:

metadata.log_source=json_generic unmapped.tenant_tier="gold"

Parsers

UDM parsers wrote .udm.* fields. OCSF parsers build the whole OCSF event on the event root, set class_uid, activity_id, type_uid and metadata.*, keep the original line in raw_data, and let unmapped source fields spill to unmapped. A parser must not write .udm.* or a top-level source_type. See Parser extensions.

UDM-profile installs

An install on the UDM profile keeps its logs table and flat field names; the profile is fixed at install and isn't converted in place. To move to OCSF, install a new deployment on the OCSF profile and point your senders at it, then port saved searches and rules with the tables above. See Deployment models.

What's next

On this page