{"id":7254,"date":"2025-12-08T14:24:48","date_gmt":"2025-12-08T12:24:48","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=announcement&#038;p=7254"},"modified":"2026-10-19T13:10:53","modified_gmt":"2026-10-19T10:10:53","slug":"elements-vulnerability-management-changes-to-features","status":"publish","type":"announcement","link":"https:\/\/support.withsecure.com\/en\/announcements\/elements-vulnerability-management-changes-to-features\/","title":{"rendered":"Elements Vulnerability Management: changes to features"},"content":{"rendered":"<p><strong>EDIT January 15, 2026: <\/strong><\/p>\n<p><strong>Update\u00a0on\u00a0feature\u00a0changes\u00a0and known\u00a0issues\u00a0(January 15, 2026)<\/strong>\u00a0<\/p>\n<p>This is an update on changes to the Vulnerability assets list that was discontinued at the end of December 2025, since the changes have caused the following known issues that will be addressed shortly:\u00a0<\/p>\n<ul>\n<li><strong>Device Details Page for Unmanaged Devices: <\/strong>Links\u00a0from\u00a0Elements\u00a0Exposure\u00a0Management (XM)\u00a0views to device details\u00a0may\u00a0lead to a\u00a0page not found\u00a0error\u00a0(404)\u00a0if the device is unmanaged.\u00a0Also,\u00a0linkage from Scan pages to the device details\u00a0might be broken for some devices.\u00a0\n<ul>\n<li><strong>UPDATE 15.1.2026<\/strong>: This now works for most devices, but may still happen in extremely rare cases. This is being worked on to resolve the remaining cases.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Software List Visibility:<\/strong>\u00a0The\u00a0software\u00a0list on\u00a0some\u00a0unmanaged devices cannot be viewed at this time.\u00a0\n<ul>\n<li><strong>UPDATE 15.1.2026<\/strong>: This now works for most devices, but may still happen in extremely rare cases. This is being worked on to resolve the remaining cases.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Asset Properties Editing:<\/strong>\u00a0Importance, tags, and other asset properties previously managed by\u00a0EVM\u00a0are temporarily not editable until data import is completed.\n<ul>\n<li><strong>UPDATE 15.1.2026<\/strong>:\u00a0All of the properties referred to can be edited via the Elements Security Center. However the API for editing device labels is still being worked on.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Impact<\/strong>\u00a0<\/p>\n<ul>\n<li>Some device\u00a0properties\u00a0such as\u00a0importance\u00a0and\u00a0business context\u00a0may be\u00a0not\u00a0editable\u00a0\n<ul>\n<li><strong>UPDATE 15.1.2026: T<\/strong>his issue is now fixed<\/li>\n<\/ul>\n<\/li>\n<li>Some workflows involving unmanaged devices may be disrupted.\u00a0\n<ul>\n<li><strong>UPDATE 15.1.2026:<\/strong> This issue is now fixed<\/li>\n<\/ul>\n<\/li>\n<li>Customers may experience broken links and limited visibility of device details.\u00a0\n<ul>\n<li><strong>UPDATE 15.1.2026: <\/strong>Most links and device details show now be fixed. For a limited number of devices, a &#8220;Device UUID not found&#8221; message may be displayed.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>Mitigation Plan<\/strong>\u00a0<\/p>\n<p>The\u00a0known\u00a0issues\u00a0will\u00a0be resolved by\u00a0<strong>January 12, 2026, at the latest<\/strong>.\u00a0\u00a0<\/p>\n<p>In the meantime:\u00a0You can continue using the\u00a0<strong>Findings<\/strong>\u00a0and\u00a0<strong>Findings Definitions<\/strong>\u00a0views under the Environment menu in Elements as substitutes for the old Vulnerabilities views.\u00a0You can\u00a0also\u00a0navigate\u00a0from\u00a0Security configurations\u00a0to\u00a0Scans\u00a0view to\u00a0see\u00a0a\u00a0list of vulnerabilities\u00a0from\u00a0a specific scan,\u00a0organized\u00a0by device.\u00a0If you\u00a0encounter\u00a0issues, please reach out to our support team for\u00a0assistance.\u00a0<\/p>\n<p>We\u00a0appreciate\u00a0your\u00a0patience\u00a0and\u00a0understanding\u00a0as\u00a0we\u00a0complete\u00a0these\u00a0updates\u00a0to\u00a0transition\u00a0from\u00a0EVM\u00a0to\u00a0the\u00a0more\u00a0comprehensive and intelligent solution &#8211;\u00a0<a href=\"https:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwithsecure.com%2Fxm\" target=\"_blank\" rel=\"nofollow noopener ugc\">WithSecure Elements Exposure Management<\/a>\u00a0(XM).\u00a0<\/p>\n<p>&#8211; &#8211; <\/p>\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=\"https:\/\/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>As part of our efforts to provide a unified user experience across Elements, we are improving our user interface related to Elements Vulnerability Management. This operation also means decommissioning a few Vulnerability Management features that were either inconsistent or not widely adopted nowadays<\/p>\n<p>We are now highlighting these changes that will impact EVM, and also when you continue using similar features in the XM product.<\/p>\n<h2 data-id=\"evm-assets-management\">EVM assets management<\/h2>\n<ul>\n<li><em>Vulnerability assets list<\/em> page will be discontinued by the end of December 2025. From now on, EVM assets can be accessed using <em>Devices &gt; Computers<\/em> and <em>Devices &gt; Unmanaged<\/em> pages <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\">as communicated earlier<\/a> and by selecting \u201cVulnerability management\u201d from the View drop down .<\/li>\n<li>API for EVM assets management will become read-only for all properties that can be managed using Devices pages. This includes fields like alias, importance and note\/business context.<\/li>\n<li>Although EVM API for assets will still work in read-only mode, we encourage to migrate any integrations to use the <a href=\"https:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fconnect.withsecure.com%2Fapi-reference%2Felements%2F\" rel=\"nofollow noopener ugc\" target=\"_blank\">Elements API<\/a>.<\/li>\n<li>Environment \/ Devices \/ Device Discovery will be decommissioned as 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<h2 data-id=\"evm-user-management\">EVM user management<\/h2>\n<ul>\n<li>The old user interface for managing EVM users, groups and roles will be discontinued by the end of December 2025 and Elements-wide \u201cSecurity groups\u201d feature will fully replace it in early 2026.<\/li>\n<li>EVM User management API is expected to be decommissioned <\/li>\n<li>Access management can be carried out using the Elements-wide <em>Organization settings &gt; Security administrator<\/em> page.<\/li>\n<\/ul>\n<h2 data-id=\"evm-dashboard\">EVM Dashboard<\/h2>\n<ul>\n<li>The most used widgets are available at <em>Reports \/ My Report (Circle and Gauge widgets are not going to be back ported due to miniscule usage)<\/em><\/li>\n<li>Existing EVM Dashboard page will be discontinued by the end of December 2025.<\/li>\n<li>All custom VM dashboards need to be re-created by the customer. Should you need any assistance, please log a support case with us.<\/li>\n<\/ul>\n<h2 data-id=\"evm-summary-reports\">EVM Summary reports<\/h2>\n<ul>\n<li>All EVM Summary reports are available on <em>Reports \/ Email notifications and reports<\/em> page. New reports can also be configured there, and the old page will be discontinued by the end of December 2025.<\/li>\n<li>There will be no changes to reports-related part of EVM API.<\/li>\n<li>Although there is no decommission regarding EVM summary reports, they are considered legacy and we plan to extend only XM reporting capabilities.<\/li>\n<\/ul>\n<h2 data-id=\"evm-vulnerabilities\">EVM Vulnerabilities<\/h2>\n<ul>\n<li><em>Exposure &gt; Findings<\/em> and <em>Exposure Findings definitions<\/em> pages are addressing the same needs as <em>Vulnerabilities<\/em> and <em>Vulnerability coverage<\/em> pages do in EVM, but the new views contain more data and of higher quality. Hence, <em>Vulnerabilities<\/em> and <em>Vulnerability coverage<\/em> pages became redundant and will be disabled soon.<\/li>\n<li>There will be no changes to vulnerabilities-related part of EVM API.<\/li>\n<li>Recommendation is to switch to Findings and Findings definitions views under Environment mega menu in Elements as a substitute for Vulnerabilities and Vulnerability coverage views<\/li>\n<\/ul>\n<h2 data-id=\"evm-internet-discovery\">EVM Internet Discovery<\/h2>\n<ul>\n<li>EVM Internet discovery page has undergone a visual update, but with no changes from the usability perspective.<\/li>\n<li><em>External assets<\/em> page has become a default landing page for Environment -&gt; <em>Network<\/em> menu, whereas the <em>Internet discovery<\/em> has become a secondary tab.<\/li>\n<\/ul>\n<h2 data-id=\"evm-ticketing\">EVM Ticketing<\/h2>\n<ul>\n<li>The feature is in sunsetting phase already now, meaning that it\u2019s only available for customers and partners who have already used it in the past.<\/li>\n<li>The user interface will be disabled by the end of December 2025.<\/li>\n<li>EVM ticketing API will be maintained as operational to keep the existing integrations operational as well. Meanwhile we recommend using the Elements level API for the same outcome.<\/li>\n<\/ul>\n<h2 data-id=\"security-configurations-scans-network-scans\">Security configurations \/ Scans \/ Network scans<\/h2>\n<ul>\n<li>All scans-related pages are undergoing a visual update.<\/li>\n<li>Compliance (PCI) column will be removed from Network scans page by the end of December 2025. The related functionality will continue to be supported.<\/li>\n<\/ul>\n<h2 data-id=\"management-vulnerability-settings\">Management \/ Vulnerability Settings<\/h2>\n<ul>\n<li>The page will undergo a visual update. \u201cGeneral settings\u201d and \u201cSecurity settings\u201d tabs will get merged into a single view, as part of the simplification.<\/li>\n<li>The following settings will get decommissioned from user interface:\n<ul>\n<li>Contact details, as they are not in use.<\/li>\n<li>Subscriptions, which are also available in Management &gt; Subscriptions<\/li>\n<li>\u201cCustomization settings\u201d, which are also available in \u201cMANAGEMENT &gt; Organization Settings &gt; Customization\u201d with following caveats:\n<ul>\n<li>Existing VM settings will not be migrated. However, they have always only applied to VM scope and have never affected other parts of Elements.<\/li>\n<li>VM reports are currently using VM settings, but will start using Elements customization settings by the end of January 2026 (<a href=\"https:\/\/community.withsecure.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwithsecure.atlassian.net%2Fbrowse%2FRADAR-32889\" target=\"_blank\" rel=\"nofollow noopener ugc\">RADAR-32889<\/a>)<\/li>\n<li>This will no longer be supported on company-level, but only for partners.<\/li>\n<\/ul>\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-51c821d15c6168-db42.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-51c821d15c6168-db42.png.webp\" srcset=\"https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-51c821d15c6168-db42.png.webp 937w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-51c821d15c6168-db42-300x177.png.webp 300w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-51c821d15c6168-db42-768x452.png.webp 768w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-51c821d15c6168-db42-447x263.png.webp 447w, https:\/\/support.withsecure.com\/wp-content\/smush-webp\/2026\/10\/image-51c821d15c6168-db42-248x146.png.webp 248w\" sizes=\"auto, 100vw\" alt=\"image-51c821d15c6168-db42.png\" height=\"552\" width=\"937\" loading=\"lazy\" data-display-size=\"large\" data-float=\"none\" data-type=\"image\/png\" data-embed-type=\"image\"><\/img><\/a><\/figure>\n<\/li>\n<li>Vulnerability statuses and workflow, as they are on their way to be superseded by XM statuses<\/li>\n<li>Assets archiving, as this will no longer be controlled by EVM. Automated assets clean-up will be performed with \u201cAutomated deletion\u201d feature on Devices page.<\/li>\n<li>Restrict login based on IP address will not be available any longer as we are aligning authentication &amp; authorization throughout the Elements.<\/li>\n<li>Force two-factor authentication, as this is already forced on Elements level.<\/li>\n<\/ul>\n<\/li>\n<li>EVM API keys definition should be done via Vulnerability settings page, as they will cease to show on Elements user profile page.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>EDIT January 15, 2026: Update\u00a0on\u00a0feature\u00a0changes\u00a0and known\u00a0issues\u00a0(January 15, 2026)\u00a0 This is an update on changes to the Vulnerability assets list that was discontinued at the end of December 2025, since the&hellip;<\/p>\n","protected":false},"template":"","announcement_category":[142],"class_list":["post-7254","announcement","type-announcement","status-publish","hentry"],"acf":{"source_system":"vanilla-import","import_hash":"83f4c984efd5c4de61bb5dd81ae54a8a77462869","vanilla_article_id":32770,"legacy_author":"AndyF_WS","vanilla_url":"https:\/\/community.withsecure.com\/announcements-en\/kb\/articles\/32770-elements-vulnerability-management-changes-to-features","vanilla_category_id":142,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7254","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\/7254\/revisions"}],"predecessor-version":[{"id":8781,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement\/7254\/revisions\/8781"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=7254"}],"wp:term":[{"taxonomy":"announcement_category","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/announcement_category?post=7254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}