{"id":33276,"date":"2024-05-21T20:24:15","date_gmt":"2024-05-21T18:24:15","guid":{"rendered":"https:\/\/www.kaspersky.co.za\/blog\/siem-platform-ux-updates\/33276\/"},"modified":"2024-05-21T20:24:27","modified_gmt":"2024-05-21T18:24:27","slug":"siem-platform-ux-updates","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.za\/blog\/siem-platform-ux-updates\/33276\/","title":{"rendered":"How to increase the efficiency of SIEM"},"content":{"rendered":"

For many InfoSec teams, security information and event management (SIEM) is at the heart of what they do. A company\u2019s security depends to a large extent on how well its SIEM system allows experts to focus directly on combating threats and avoid routine tasks. That\u2019s why almost every update of our Kaspersky Unified Monitoring and Analysis Platform is aimed at improving the user interface, automating routine processes and adding features to make the work of security teams easier. Many of the improvements are based on feedback from our customers\u2019 InfoSec experts. In particular, the latest version of the platform (3.0.3) introduces the following features and improvements.<\/p>\n

Writing filter conditions and correlation rules as code<\/h2>\n

\nPreviously, analysts had to set filters and write correlation rules by clicking the conditions they needed. In this update, the redesigned interface now allows advanced users to write rules and conditions as code. Builder mode remains: filter and selector conditions are automatically translated between builder and code modes.<\/p>\n

\"Same<\/a>

Same rule condition in builder and code modes<\/p><\/div>\n

What\u2019s more, builder mode also lets you write conditions using the keyboard. As soon as you start entering a filter condition, Kaspersky Unified Monitoring and Analysis Platform will suggest suitable options from event fields, dictionaries, active sheets, etc. To narrow down the range of options, simply enter the appropriate prefix. For your convenience, condition types are highlighted in different colors.<\/p>\n

Code mode lets you quickly edit correlation rule conditions, as well as select and copy conditions as code and easily transfer them between different rules or different selectors within a rule. The same code blocks can also be moved to filters (a separate system resource), which greatly simplifies their creation.<\/p>\n

Extended event schema<\/h2>\n

\nKaspersky Unified Monitoring and Analysis Platform retains Common Event Format (CEF) as the basis for the event schema, but we have added the ability to create custom fields, which means you can now implement any taxonomy. No more being limited to vendor-defined fields, you can name event fields anything you want to make it easier to write search queries. Custom fields are typed and must begin with a prefix that determines both its type and the array type. Fields with arrays can only be used in JSON and KV normalizers.<\/p>\n

\"Example<\/a>

Example of normalization using CEF fields and custom fields<\/p><\/div>\n

Automatic identification of event source<\/h2>\n

\nKaspersky Unified Monitoring and Analysis Platform administrators no longer need to set up a separate collector for each event type or open ports for each collector on the firewall\u00a0\u2013 in the new version we have implemented the ability to collect events of different formats with a single collector. The collector selects the correct normalizer based on the source IP address. Using a chain of normalizers is permitted. For example, the [OOTB] Syslog header<\/strong> normalizer accepts events from multiple servers and allows you to define a DeviceProcessName and direct bind events to the [OOTB] BIND Syslog<\/strong> normalizer and squid events to the [OOTB] Squid access Syslog<\/strong> normalizer.<\/p>\n

\"Kaspersky<\/a>

Kaspersky Unified Monitoring and Analysis Platform: Event parsing<\/p><\/div>\n

The following event normalization options are now available:<\/p>\n

1 collector\u00a0\u2013 1 normalizer. <\/strong>We recommend using this method if you have many events of the same type or many IP addresses from which events of the same type may originate. In terms of SIEM performance, configuring a collector with only one normalizer would be optimal.<\/p>\n

1 collector\u00a0\u2013 multiple normalizers, based on IP addresses. <\/strong>This method is available for collectors with a UDP, TCP or HTTP connector. If a UDP, TCP or HTTP connector is specified in the collector at the Transport<\/strong> step, then at the Event Parsing<\/strong> step, on the Parsing settings<\/strong> tab, you can specify multiple IP addresses and select which normalizer to use for events arriving from those addresses. The following types of normalizers are available: JSON, CEF, regexp, Syslog, CSV, KV, XML. For Syslog or regexp normalizers, you can specify additional normalization conditions depending on the value of the DeviceProcessName field.<\/p>\n

These are by no means the only updates to Kaspersky Unified Monitoring and Analysis Platform. There are also changes related to context tables, simplified binding of rules to correlators and other improvements. All of them are designed to improve the user experience for InfoSec professionals\u00a0\u2013 see the full list here<\/a>. To learn more about our SIEM system, Kaspersky Unified Monitoring and Analysis Platform, please visit the official product page<\/a>.<\/p>\n\n","protected":false},"excerpt":{"rendered":"

What\u2019s new in Kaspersky Unified Monitoring and Analysis Platform 3.0.3.<\/p>\n","protected":false},"author":2757,"featured_media":33279,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,3020],"tags":[2464,3731],"class_list":{"0":"post-33276","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"tag-siem","10":"tag-ux"},"hreflang":[{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/siem-platform-ux-updates\/33276\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/siem-platform-ux-updates\/27465\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/siem-platform-ux-updates\/22783\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/siem-platform-ux-updates\/27615\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/siem-platform-ux-updates\/37195\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/siem-platform-ux-updates\/51275\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/siem-platform-ux-updates\/33612\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.za\/blog\/tag\/siem\/","name":"SIEM"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/33276","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/users\/2757"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/comments?post=33276"}],"version-history":[{"count":1,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/33276\/revisions"}],"predecessor-version":[{"id":33278,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/33276\/revisions\/33278"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media\/33279"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media?parent=33276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/categories?post=33276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/tags?post=33276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}