CIS-DF--Day16 - Service Mapping - Pattern-Based - Tag Based

✅ Day 16 Summary (CIS – Data Foundation – Discovery & Service Mapping) Based on your uploaded transcript, here is a clean and structured summary of everything covered in Day 16: 1. Discovery Overview Day 16 continues the exploration of Discovery in ServiceNow, focusing on how data is ingested into the CMDB. Types of Discovery Network Discovery – finds devices using IP ranges. CI Discovery – servers, applications, devices. Cloud Discovery – AWS, Azure, cloud-native assets. Serverless Discovery – components without a traditional host. 2. Discoverable vs Non‑discoverable Data ✔ Discoverable (via Discovery) Hardware details (CPU, memory, OS) IP, MAC address Applications Network components ✔ Non‑discoverable (manual or imported) Support groups Approval groups Business ownership Management hierarchy 3. Horizontal Discovery Process (4 Phases) Scan – ping devices via IP ranges Classification – determine device type (Windows/Linux/Network) Identification – validate and identify the CI Exploration – collect detailed attributes Each phase has its own failure type and troubleshooting category. 4. Service Mapping (Top‑Down Discovery) Service Mapping supplements Discovery by creating relationships between CIs and business services. Why Service Mapping is needed IT components alone don’t describe business services. Helps form end‑to‑end service topology (service → components → infrastructure). Aligns IT with business operations. Approaches Top‑Down (Pattern‑Based) Requires MID Server Best for mission‑critical services Tag‑Based Discovery Uses tags for categorization Good for microservices/cloud environments ML‑Powered Mapping Uses machine learning to detect patterns 5. Access, Ports & Credential Challenges Discovery requires credentials (SSH 22, WMI 135, HTTPS 443). Organizations often restrict access → causes discovery issues. Credentialless discovery is limited. ACC (Agent Client Collector) can help avoid credential challenges. 6. ACC (Agent Client Collector) Agent-based data collection. Useful when Discovery credentials/access are restricted. Works on on‑prem and cloud servers. Needs installation on target hosts. 7. Graph Connectors Pre-built connectors for integrating data from 3rd-party tools (e.g., LogicMonitor, Qualys, CrowdStrike, Azure). Plug-and-play integrations using predefined APIs. Requires separate licenses from respective vendors. 8. Licensing & Limitations Licensing depends on subscription model, usage, integrations. Token-based usage for AI/automation. Must always consult ServiceNow Sales for exact pricing.