Elements Exposure Management Changelog
Elements Exposure Management feature changes will be published under this announcement thread.
Every time there is a change, an entry will be created under this announcement describing new functionalities, improvements or bug fixes.
📝 Click here to see the most recent change log and bookmark the discussion to be notified of any updates.
Comments
-
XM newsletter Week 41
We have released Exposure management with new improvements:
- AttackPath visualizer tool updated with UX improvements.
- New Recommendation score calculation is in place: Recommendations are now generated for only highly-enough risked assets. This may lead into less Recommendations provided compared to what had been recommended in the previous versions. This is considered as expected behavior while continuous improvements and tuning will be applied in the future releases to improve the quality of the recommendations.
- Several minor bug and security fixes.
0 -
XM newsletter week 42
- Added tags and affected-device columns to the Findings views for make them more self-explanatory
- AttackPath visualizer more UX improvements
- Several UX improvements and UI bug fixes including sorting bugs
- Recommendation quality improvements via several scoring logic improvements
0 -
XM newsletter week 43
- Status of a Recommendation can be set from Recommendation details page. The status is saved to the Recommendation for further tracking. e.g The status appearing on Home → Exposure widget.
- in addition to Staus, Notes can be added to each recommendation e.g to give reason about why user has decided to set a specific status to a Recommendation
In this version Recommendations that are set as "Done" or "False Positive", will disappear from Home → Exposure → Highest Impact Recommendations
1 -
XM newsletter week 44
New version released:
- Recommendations List view now supports sorting on "Related attack paths" column to make it easier find the recommendations with AttackPaths attached to them
- Recommendations List view populates "Related attack paths" much faster than beofre.
- Several UI sorting bugfixes in Recommendation and Findings views
- Cloud account removal now propagated to removal of all corresponding assets, findings and related recommendations
0 -
XM newsletter Week 45
- Status of multiple Recommendations can be now set from Recommendation List page. Multiple Recommendation selection will activate the action panel. The status will be saved to the recommendations for further tracking. e.g The status appearing on Home → Exposure widget will show only active recommendations (active recommendation = status not "Done" or "False Positive")
- "Findings in this recommendation" widget on Recommendation detail page has a new "last seen" column showing the time stamp when last time this finding has been seen. This column gives clearer idea about how fresh the scan results are.
- Improved remediation impact score precision. This will help with more accurate distinguishment of recommendations and more enhanced prioritization of them when their remediation impact scores are close to each other.
0 -
XM newsletter Week 47
- Identity audit logs when user modifies Identity properties such as importance and business context, are now available in Elements Audit Logs
- Exposure audit logs when user does actions such as elevating a recommendation to WithSecure, are now available in Elements Audit Logs
- Extended logic for checking identity’s MFA status. Correct MFA status is now shown on the Identity with traffic light colors depending on reported MFA status in O365, Portal and elsewhere by MicroSoft.
- Identity lists pagination issue correction
- Recommendation Status added to the Flyout on Finding details page when "view related recommendations" button is pressed
0 -
XM newsletter week 48
Released a new widget on Home → Exposure Widget to show the Exposure Management coverage of a selected company from different angles.
Green color in each area indicates whether the company has completed WithSecure Exposure Management onboarding successfully and scans are running perfectly on that area.
Orange Color: Indicates that the company has the proper licenses to get onboarded to the Exposure management, but not all configuration or onboarding is complete. in this case, by clicking on the area, user will be taken to a relevant view where the configuration or onboarding can be completed.
Gray Color: Indicates that the company does not have required licenses to get onboarded on the area. In this case, please reach out to the sales staff for more info on how to obtain the relevant license.
0
Categories
- All Categories
- 4.7K WithSecure Community
- 3.6K Products
- 1 Get Support