For BOTSv3, don't hand-roll it — install the TAs from the dataset's required add-on list plus Splunk_SA_CIM. Those TAs already carry most of the field aliases. Then per sourcetype, CIM compliance is really four things Field aliases - rename source fields to CIM names (user, src, dest, action, etc.) in props.conf. Tags - the part people miss. Models constrain on tags, not sourcetypes. Add an eventtype + tag (tag=authentication, tag=network, etc.) or the model stays empty. Populate recommended fields, not just required ones. Validate with | datamodel Authentication search | search sourcetype=X. Empty result = almost always a missing tag, not a missing alias.
... View more