{"id":7238,"date":"2025-10-30T15:35:16","date_gmt":"2025-10-30T13:35:16","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=announcement&#038;p=7238"},"modified":"2026-10-19T13:10:33","modified_gmt":"2026-10-19T10:10:33","slug":"elements-vulnerability-management-feature-changes-as-end-of-life-approaches","status":"publish","type":"announcement","link":"https:\/\/support.withsecure.com\/en\/announcements\/elements-vulnerability-management-feature-changes-as-end-of-life-approaches\/","title":{"rendered":"Elements Vulnerability Management: Feature changes as End-of-Life approaches"},"content":{"rendered":"<h2 data-id=\"introduction\"><strong>Introduction<\/strong><\/h2>\n<p>We are preparing the End of Life (EOL) of WithSecure Elements Vulnerability Management (EVM), where EVM is replaced with the more comprehensive and intelligent solution &#8211; <a href=\"http:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fsolutions%2Fsoftware-and-services%2Fwithsecure-elements-exposure-management\" target=\"_blank\" rel=\"nofollow noopener ugc\">WithSecure Elements Exposure Management<\/a> (XM). <\/p>\n<p>XM includes and is not limited to<\/p>\n<ul>\n<li>From reactive and asset centric to proactive and estate-wide security.<\/li>\n<li>Gain visibility on what attackers would be able to do in your estate.<\/li>\n<li>Easier and more efficient prioritization of work.<\/li>\n<li>AI assistance for remediating and documenting your exposure.<\/li>\n<li>Expand your visibility beyond devices. E.g. EntraID, Azure and AWS.<\/li>\n<\/ul>\n<p>We are now highlighting a few fundamental changes that will impact EVM, and also when you continue using similar features in XM product.<\/p>\n<h2 data-id=\"evm-ticketing-user-interface\"><strong>EVM Ticketing User Interface<\/strong><\/h2>\n<p>We have decided to discontinue the EVM ticketing system user interface. The earliest date this will occur is 1st December-2025, and by the end of 2025 at latest. The EVM ticketing related user interface can no longer be accessed.<\/p>\n<p>While the ticketing workflow and the related history will continue to be supported via the EVM API, we recommend utilizing statuses of Exposure Management Recommendations and Findings. The recommendations are also accessible via the Elements Security Events API, which can be used to integrate to an external ticketing system. Please reach out to your WithSecure contact to get additional help for the transition.<\/p>\n<p>In case you need to access or modify the EVM ticketing data or configuration via the Elements user interface, we recommend doing it before December 2025.<\/p>\n<h2 data-id=\"evm-vulnerability-users\"><strong>EVM Vulnerability Users<\/strong><\/h2>\n<p>As <a href=\"https:\/\/community.withsecure.com\/en\/kb\/articles\/32543-upcoming-retirement-of-the-management-organization-settings-vulnerability-users-page-in-elements\" target=\"_blank\" rel=\"nofollow noopener ugc\">previously announced<\/a> we are changing the way EVM users are managed.<\/p>\n<p>We have decided to migrate Vulnerability Users as part of Elements Role Based Access Control (RBAC). The following user interface is no longer accessible, and the earliest this change will happen will be 1st December 2025:<\/p>\n<p><strong>Management \/ Organization Settings \/ Vulnerability Users<\/strong><\/p>\n<p>The roles and accesses within will continue to function.<\/p>\n<p>While the EVM API can be still used to manage the access, we recommend using the Elements level RBAC found in:<\/p>\n<p><strong>Management \/ Organization Settings \/ Security Administrators<\/strong><\/p>\n<p>This view allows managing user permissions using one of the 3 default roles: Administrator, Team member or Read-only team member. If the user was previously assigned to a custom VM role or roles, it will be represented as a single \u201cVulnerabilities:Custom\u201d role. VM custom roles can only be revoked using Security Administrators view.<\/p>\n<p>A screenshot below presents the matrix of privileges assigned to the 3 default roles that can be managed via Elements-level Security Administrators page<\/p>\n<figure class=\"entry-image display-large float-none\"><a class=\"embedImage-link\" href=\"https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5.png.webp\" rel=\"nofollow noopener ugc\" target=\"_blank\"><img decoding=\"async\" class=\"embedImage-img\" src=\"https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5.png.webp\" srcset=\"https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5.png.webp 898w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5-300x50.png.webp 300w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5-768x129.png.webp 768w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5-447x75.png.webp 447w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-acf5d7bc1e4958-5df5-868x146.png.webp 868w\" sizes=\"auto, 100vw\" alt=\"image-acf5d7bc1e4958-5df5.png\" height=\"151\" width=\"898\" loading=\"lazy\" data-display-size=\"large\" data-float=\"none\" data-type=\"image\/png\" data-embed-type=\"image\"><\/img><\/a><\/figure>\n<h2 data-id=\"further-changes\"><strong>Further changes<\/strong><\/h2>\n<p>We expect changes also to the following areas, as we start using Elements wide solutions.<\/p>\n<ul>\n<li>Environment \/ Devices \/ Device Discovery\n<ul>\n<li>The functionality is <a href=\"https:\/\/community.withsecure.com\/en\/kb\/articles\/32245-upcoming-retirement-of-the-devices-device-discovery-page-in-elements\" target=\"_blank\" rel=\"nofollow noopener ugc\">already available in the Computers view<\/a> <\/li>\n<\/ul>\n<\/li>\n<li>Environment \/ Devices \/ Vulnerability assets\n<ul>\n<li>The functionality is going to be <a href=\"https:\/\/community.withsecure.com\/en\/kb\/articles\/32679-upcoming-retirement-of-the-environments-devices-vulnerability-assets-page-in-elements\" target=\"_blank\" rel=\"nofollow noopener ugc\">available at dedicated views <\/a><\/li>\n<li>Devices \/ Computers<\/li>\n<li>Devices \/ Unmanaged soon<\/li>\n<\/ul>\n<\/li>\n<li>Environment \/ Exposure \/ Vulnerabilities\n<ul>\n<li>The functionality is going to be available at Environment \/ Exposure \/ Findings<\/li>\n<li>Further details to come<\/li>\n<\/ul>\n<\/li>\n<li>Environment \/ Exposure \/ Vulnerability coverage\n<ul>\n<li>The functionality is going to be available at Environment \/ Exposure \/ Findings definitions<\/li>\n<li>Further details to come<\/li>\n<\/ul>\n<\/li>\n<li>Home \/ Vulnerability Management Dashboard\n<ul>\n<li>The most used widgets are going to be available at Reports \/ My Report<\/li>\n<li>Further details to come<\/li>\n<\/ul>\n<\/li>\n<li>Reports \/ Vulnerability Reports\n<ul>\n<li>Will be moved under Reports \/ Email notifications and reports<\/li>\n<li>Further details to come<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>The following items will be reimplemented within Elements to become available across the whole of the Elements portfolio:<\/p>\n<ul>\n<li>Reports \/ Vulnerability Notifications<\/li>\n<li>Vulnerability Settings \/ Notification Settings<\/li>\n<li>Vulnerability Settings \/ Event Log<\/li>\n<\/ul>\n<p>We are currently evaluating how we will present the following capability to the users<\/p>\n<ul>\n<li>Security configurations \/ Scans \/ Network scans\n<ul>\n<li>Compliance (PCI)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Introduction We are preparing the End of Life (EOL) of WithSecure Elements Vulnerability Management (EVM), where EVM is replaced with the more comprehensive and intelligent solution &#8211; WithSecure Elements Exposure&hellip;<\/p>\n","protected":false},"template":"","announcement_category":[142],"class_list":["post-7238","announcement","type-announcement","status-publish","hentry"],"acf":{"source_system":"vanilla-import","import_hash":"c5b6d85dd68743867add9c4c00f3c602d5cdc821","vanilla_article_id":32681,"legacy_author":"AndyF_WS","vanilla_url":"https:\/\/community.withsecure.com\/announcements-en\/kb\/articles\/32681-elements-vulnerability-management-feature-changes-as-end-of-life-approaches","vanilla_category_id":142,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/announcement"}],"version-history":[{"count":1,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7238\/revisions"}],"predecessor-version":[{"id":8735,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7238\/revisions\/8735"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=7238"}],"wp:term":[{"taxonomy":"announcement_category","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement_category?post=7238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}