CIS-DF - Day20 - CI Reclassification - Remediation- Stale - Orphan - Upgrade - Downgrade

Day 20 – Summary (CMDB Classification & Remediation) 1. CI Classification Classification is the process of assigning a Configuration Item (CI) to the correct ServiceNow class (e.g., Server, Windows Server, Linux Server). Proper classification improves data accuracy, reporting, discovery results, and dependency mapping. Misclassification leads to poor data quality and incorrect CMDB insights. 2. Reclassification Reclassification occurs when a CI’s class changes after discovery or reconciliation. 🔁 Types of Reclassification: Upgrade Moving from generic → specific Example: Server → Windows Server ✅ Improves accuracy Downgrade Moving from specific → generic Example: Windows Server → Server ⚠️ Risk of data loss Switch Moving between peer classes Example: Windows Server → Linux Server ⚠️ Possible attribute loss Key idea: Specific classification = Upgrade Generic classification = Downgrade 3. Automation & Discovery Reclassification is primarily driven by: Discovery Identification & Reconciliation Engine (IRE) Controlled via system properties: Upgrade enabled Downgrade enabled Switch enabled If automation is disabled, ServiceNow creates a reclassification task for manual review. 4. Data Loss & Restriction Rules Downgrades and switches can cause data loss because child-class attributes may not exist in parent classes. To prevent unwanted changes, ServiceNow provides: Reclassification Restriction Rules Control using: Source inheritance Target inheritance These rules decide: Whether extended (child) classes are affected Whether reclassification is allowed or blocked ✅ Best practice: Use restriction rules to protect critical CI attributes while still allowing discovery updates. 5. CMDB Remediation CMDB Health identifies issues such as: Stale CIs Orphan CIs Required / Recommended attribute gaps Remediation process: Define Health Metrics Set thresholds Generate remediation tasks Attach flows/workflows (delete, retire, update CIs)