New release
- App now ships with UBA validation data models (non-accelerated) to extend CIM validation with specific UBA product needs. Thank you @annettefo!!
- Added a filter select a "product" type to validate against, ie
Core, ES
andUBA
. - Support for district field validation regex per datamodel. This allows for different rules to apply to different datamodel schemas
- CIM Dictionary was reworked to pull information from datamodel schema, instead of relying on a static lookup that needed constant upkeep or version assumption.
- Clarified instructions on differences between
_raw
andgenerating
search type. The generating search type, formally called datamodel is for use with commands such as| datamodel
, | from,| inputlookup
, or even| makeresults
. This change will help to unlock new validation use-cases, no-matter where the data is located! - Recommended fields are now pulled from datamodel schema definition OR the recommended field lookup, allowing for additional flexibility for custom schemas.
- Fixed a bug where fields containing
_host
might be inadvertently filtered out from the Vladiator UI, for exampledest_host
,src_host
, etc.
What's Changed
- Uba support by @hire-vladimir in #35
Full Changelog: 1.8.2...2.0.0