{"id":5189,"date":"2026-06-16T08:00:00","date_gmt":"2026-06-16T05:00:00","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=changelog&#038;p=5189"},"modified":"2026-10-19T11:42:38","modified_gmt":"2026-10-19T08:42:38","slug":"exposure-management-2026-06-16-update","status":"publish","type":"changelog","link":"https:\/\/support.withsecure.com\/en\/changelogs\/exposure-management-2026-06-16-update\/","title":{"rendered":"Exposure Management &#8211; 2026-06-16 Update"},"content":{"rendered":"<p>Vulnerability scanning now supported in OT and isolated network environments<\/p>\n<p>WithSecure Elements Vulnerability Management can now scan operational technology (OT) networks and other isolated or segmented environments by routing scan node traffic through an Elements Connector acting as a proxy.<\/p>\n<p>With this change, scan nodes deployed within isolated network segments can route all communication to the Elements backend over ports 80\/443 via a centrally deployed Elements Connector \u2014 without requiring internet access or additional firewall exceptions from within the segment.<\/p>\n<p><strong>Asset sub-type support in findings<\/strong><\/p>\n<p>Findings in Exposure Management now include asset sub-type information, giving users a more precise understanding of which type of asset a finding is associated with. <\/p>\n<p>Assets across all supported sources (Identity, ASM, VM, Cloud, and Device Service) now carry an optional sub-type property that provides a second-level classification beyond the primary asset type. For example, identity assets can be distinguished as <em>Member<\/em>, <em>Guest<\/em> while internet assets can be classified as <em>Domain<\/em>, <em>Subdomain<\/em>, or <em>IPv4 Address<\/em>.<\/p>\n<p>Asset sub-type data is now available in the Findings list (<em>Environment \u2192 Exposure \u2192 Findings<\/em>) via:<\/p>\n<ul>\n<li>A new <strong>&#8220;<\/strong>Asset sub-type<strong>&#8221; <\/strong>column (hidden by default, sortable, can be enabled via column settings)<\/li>\n<li>A new <strong>&#8220;<\/strong>Asset sub-type<strong>&#8221; <\/strong>filter to narrow findings down to a specific asset classification<\/li>\n<\/ul>\n<p>These improvements make it easier to prioritize and investigate findings based on the precise nature of the affected asset.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vulnerability scanning now supported in OT and isolated network environments WithSecure Elements Vulnerability Management can now scan operational technology (OT) networks and other isolated or segmented environments by routing scan&hellip;<\/p>\n","protected":false},"template":"","changelog_product":[119],"class_list":["post-5189","changelog","type-changelog","status-publish","hentry"],"acf":{"release_date":"20260616","version":"","source_system":"vanilla-import","source_foreign_id":"","import_hash":"ae29c4a1daf78ea24fc91e27ede087f2c89c5b36","vanilla_article_id":32968,"legacy_author":"Sandra","vanilla_url":"https:\/\/community.withsecure.com\/changelogs-en\/kb\/articles\/32968-exposure-management-2026-06-16-update","vanilla_category_id":239,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/changelog\/5189","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/changelog"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/changelog"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=5189"}],"wp:term":[{"taxonomy":"changelog_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/changelog_product?post=5189"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}