Seeking Advice: Technical Strategies to Automate CMDB Governance: Query 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi admins,
Part 3 of my CMDB cleanup focus is on Compliance Audits for third-party tools (Antivirus, Qualys, Airlock Digital, etc.):
1. Third-Party Tool Discovery: Can ServiceNow natively verify or discover third-party agent installations via API integrations, ITOM Discovery, or Service Graph Connectors without relying on manual record entries?
2. Exempting Non-Production Servers: Dev/Test servers shouldn't require the same strict security tools or complete asset tags as Production. What is the recommended way in ServiceNow to create Health Inclusion Rules or filter out Test/Dev CIs so they don't generate false compliance failures?
How do you keep non-prod servers from tanking your overall compliance score?