-
Vulnerability Management System Scan Changelog
This changelog focuses on updates related to the System Scan component of WithSecure™ Elements Vulnerability Management. It includes the latest changes, improvements, and fixes affecting how system scans are performed, managed, and reported within the solution. For updates related to the portal interface or other…
-
Vulnerability Management Portal Changelog
This changelog provides updates specifically for the portal interface of WithSecure™ Elements Vulnerability Management. It includes the latest improvements, feature enhancements, and fixes related to the user experience, dashboard functionality, and overall usability of the portal. For updates related to other components…
-
Exposure Management for Cloud Changelog
This changelog is dedicated exclusively to updates for the Cloud component of WithSecure™ Elements Exposure Management. It includes the latest improvements, fixes, and new features specific to the cloud-based capabilities of the solution. Note: For updates related to Exposure Management for Business and the Frontline…
-
Exposure Management (including XM for Business and XM Frontline Add-on) Changelog
This is the primary changelog for WithSecure™ Elements Exposure Management, covering all updates related to: Exposure Management for Business Exposure Management Frontline Add-on It provides the latest enhancements, fixes, and feature updates for these components of the Exposure Management solution. Note: This changelog…
-
Vulnerability Management Scan Node Agent Changelog
This changelog provides updates for the Scan Node Agent component of WithSecure™ Elements Vulnerability Management. It includes the latest enhancements, fixes, and performance improvements related to the scan node agent, which is responsible for executing vulnerability scans within customer environments. For updates on…
-
Vulnerability Management Discovery Scan Changelog
This changelog highlights updates for the Discovery Scan component of WithSecure™ Elements Vulnerability Management. It includes the latest improvements, fixes, and feature enhancements related to asset discovery and network visibility, helping organizations identify unmanaged or unknown devices in their environments. For…
-
Vulnerability Management Web Scan Changelog
This changelog provides updates for the Web Scan component of WithSecure™ Elements Vulnerability Management. It includes the latest improvements, fixes, and new features related to scanning and assessing the security of web applications and services, helping organizations identify vulnerabilities in their online assets.…
-
Setting up authenticated scan for network devices (SNMPv3)
To set up authenticated scan, when target is a network device (Cisco, Fortigate and Palo Alto devices are currently supported). When creating a new scan, select SNMPv3 credentials as the authentication method: Next fill in the data: Enter the SNMP port number (Default:161) Enter the SNMPv3 Username Select the…
-
WithSecure™ Enhances Elements XM to Tackle Hybrid IT Risks with AI-Powered Exposure Management
WithSecure™ has released a significant upgrade to its Elements Exposure Management (Elements XM) solution, aimed at helping mid-sized organizations and service providers reduce cyber risk in increasingly complex hybrid IT environments. The update delivers expanded cloud visibility, deeper identity risk detection, and new…
-
Setting up authenticated scan for network devices (API)
To set up authenticated scan, when target is a network device (Cisco via Restconf API, Fortigate and Palo Alto devices are currently supported). When creating a new scan, select API credentials as the authentication method: Next it's important to select correct device type out of supported ones as there is no…
-
Setting up authenticated scan for network devices (SSH).
To set up authenticated scan, when target is a network device (Cisco, Fortigate and Palo Alto devices are currently supported with SSH). Create new scan following instructions for Linux machines: You can use either key or username + password credentials, but bear in mind, that your target needs to be configured…
-
XM newsletter Oct-08
Today we 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…
-
WithSecure vulnerability scan results csv export
If memory serves me correctly. There was a feature from the Elements console that allowed one to export a csv/xls file that listed all network scanned devices (Vulnerability assets), their accessable services and vulnerabilities. I just can't seem to get that option any ware. Anyone want to enlighten me? Regards, Ernest
-
EVM Authenticate scan with SNMPv3
Hi, I have tried SNMPv3 authenticate scan in Elements Vulnerability Management. I works great with FortiGate but I have tried with other kind of network devices and it's not working. Based on the information found in the scan logs, it seems that SNMPv3 authenticate scan only support Fortigate, Cisco and Paloalto. It's…
-
Having some trouble querying tags within WithSecure Vulnerability management api.
Our team has been successfully using a reporting application that queries the WithSecure Vulnerability Management API. We've been using custom tags to identify devices (e.g., Windows Server, Linux Server, Firewall). This system worked flawlessly until about a week ago. Currently, we're experiencing an issue where our API…
-
Cloud Security Posture Management and Vulnerability Management now in Exposure Management
All discussions and changelogs for Cloud Security Posture Management (CSPM) and Vulnerability Management (VM) will now be found under the Elements Exposure Management category. Consolidated Discussions: All CSPM and VM threads will now be housed in the Elements Exposure Management category. Changelog Updates: Future…
-
What are the limitations of agent-only based VM scanning?
Hi, We have a customer site where our engagement is to only scan computers for vulnerabiltities. As such, we have not deployed a scan node. WIthSecure indicated that a scan node is not needed for this purpose. However, we notice that many vulnerabilities are not caught this way. For example, deprecated TLS versions are not…