{"id":5221,"date":"2026-07-21T08:00:00","date_gmt":"2026-07-21T05:00:00","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=changelog&#038;p=5221"},"modified":"2026-10-19T11:40:16","modified_gmt":"2026-10-19T08:40:16","slug":"exposure-management-2026-07-21-update","status":"publish","type":"changelog","link":"https:\/\/support.withsecure.com\/de\/changelogs\/exposure-management-2026-07-21-update\/","title":{"rendered":"Exposure Management &#8211; 2026-07-21 Update"},"content":{"rendered":"<h2 data-id=\"clearer-identity-findings-and-recommendations-for-breach-exposure\"><strong>Clearer identity findings and recommendations for breach exposure<\/strong><\/h2>\n<p>We&#8217;ve renamed and updated the Identity findings and recommendations that deal with credential breaches so they&#8217;re easier to understand and act on. The names now describe exactly what each finding or recommendation covers, and for each one we&#8217;ve refreshed the supporting content &#8211; descriptions, risk explanations, details, immediate actions, and proactive actions \u2014 so the guidance is clearer and more actionable.<\/p>\n<p>Here&#8217;s what&#8217;s changed:<\/p>\n<p><strong>&#8222;User has old password&#8220; is now &#8222;Account exposed in breach after last password change&#8220;<\/strong><\/p>\n<p>The new name makes the finding&#8217;s purpose clear: it flags accounts whose credentials were exposed in a known breach and haven&#8217;t been changed since.<\/p>\n<p><strong>&#8222;Remind your users to change their password&#8220; is now &#8222;Reset passwords exposed in breaches&#8220;<\/strong><\/p>\n<p>The new name reflects the specific action that reduces risk \u2014 resetting passwords that have been exposed in breaches.<\/p>\n<p>\u00a0<\/p>\n<p><strong>&#8222;Remediate identity breach of multiple users&#8220; is now &#8222;Review identities with breaches&#8220;<\/strong><\/p>\n<p>The recommendation now includes clear guidance for addressing Identity breach findings. Since these findings belong to a unique category that can&#8217;t be resolved through standard means, they call for a different approach.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Clearer identity findings and recommendations for breach exposure We&#8217;ve renamed and updated the Identity findings and recommendations that deal with credential breaches so they&#8217;re easier to understand and act on.&hellip;<\/p>\n","protected":false},"template":"","changelog_product":[119],"class_list":["post-5221","changelog","type-changelog","status-publish","hentry"],"acf":{"release_date":"20260721","version":"","source_system":"vanilla-import","source_foreign_id":"","import_hash":"9000d4ddbf9dfac477998a1ba7fc53c51d0956a6","vanilla_article_id":33011,"legacy_author":"MagdaBB","vanilla_url":"https:\/\/community.withsecure.com\/changelogs-en\/kb\/articles\/33011-exposure-management-2026-07-21-update","vanilla_category_id":239,"machine_translated":false},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/de\/wp-json\/wp\/v2\/changelog\/5221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/de\/wp-json\/wp\/v2\/changelog"}],"about":[{"href":"https:\/\/support.withsecure.com\/de\/wp-json\/wp\/v2\/types\/changelog"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/de\/wp-json\/wp\/v2\/media?parent=5221"}],"wp:term":[{"taxonomy":"changelog_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/de\/wp-json\/wp\/v2\/changelog_product?post=5221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}