Vulnerability Management and CI ownership
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-27-2024 05:41 AM
Hello All,
Need help on understanding the ownership management on CIs when it comes to managing VR/ OR how are you managing it.
Our SN instance is integrated with Tenable for vulnerability management.
How tenable works is clear to us:
- If the scanned CI is not available in CMDB, it creates in one of the below classes
- Unclassed
- Unmatched
- Incomplete IP Identified Devices
However, I see that the vulnerabilities are getting created for the component level as well ( IP Address, DNS etc).
There are various reasons where the mains CIs will not get discovered in CMDB (WIP for fixing these issues).
In that case, it creating vulnerabilities at components the level.
The important thing here is for Vulnerability is to have the CI ownership.
Need suggestion:
Is it okay to populate the Ownership details at component level?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 09:52 AM
Hi, did you find solution for this?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2025 03:14 AM
Not yet. Kindly let me know if you have suggestion