Best practice for VR IP Addresses changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2024 06:32 AM - edited ‎02-27-2024 06:46 AM
Hello everyone,
We are facing the "issue" that if CI has updated IP Address, this is not reflected in VIT. VIT is still having the IP Address of CI from initial detection. I understand that this is by design, but don't really find it useful and searching for particular vulnerability means searching for IP address or CI -> IP address and this is becoming confusing for end users. Sure, we can prepare business rule to update VIT -> IP if is changed in cmdb, but not really sure if that is the best approach, or what is the intention of keeping the IP Address like this.
Thank you for you inputs
- Labels:
-
Best Practices
-
CMDB
-
Vulnerability Response