This curriculum spans the technical and procedural rigor of a multi-workshop configuration management program, addressing the same discovery, classification, and governance challenges encountered in enterprise CMDB deployments across hybrid infrastructure and regulated environments.
Module 1: Defining Discovery Scope and Business Objectives
- Determine which business services require dependency mapping based on incident impact analysis and service ownership agreements.
- Select discovery targets by evaluating asset criticality, compliance requirements, and integration dependencies with monitoring tools.
- Negotiate access boundaries with security teams to balance network visibility with least-privilege access policies.
- Define service-aware discovery scope by aligning configuration item (CI) identification with service portfolio records.
- Establish criteria for excluding test, legacy, or decommissioned environments from automated discovery runs.
- Map discovery frequency to change velocity—daily for dynamic cloud workloads, weekly for stable on-prem systems.
- Document stakeholder expectations for CI completeness, accuracy, and relationship fidelity to set validation benchmarks.
- Integrate discovery planning into the service lifecycle by aligning with change and release management calendars.
Module 2: Network Scanning and Credential Management
- Configure segmented scanning schedules to avoid network saturation during peak business hours in global environments.
- Implement role-based credential vaulting to rotate privileged account passwords used in discovery probes.
- Select scanning protocols (SNMP, WMI, SSH, HTTP APIs) based on OS type, firewall rules, and endpoint hardening standards.
- Validate port accessibility across VLANs and firewalls using pre-scan connectivity checks before full discovery execution.
- Handle credential fallback scenarios by defining secondary authentication methods for unresponsive primary accounts.
- Mask or encrypt sensitive credential data in logs and discovery job outputs to meet audit compliance requirements.
- Test credential scope limitations to prevent unintended access to restricted systems during horizontal scans.
Module 3: CI Identification and Classification Logic
- Develop CI classification rules using heuristic patterns (e.g., hostname prefixes, MAC OUIs, API responses) to distinguish server types.
- Resolve CI duplication by defining authoritative data sources and implementing merge logic based on lifecycle state and ownership.
- Assign CI classes (e.g., virtual server, load balancer, database instance) based on observed attributes and process signatures.
- Implement custom identification scripts to detect containerized workloads in Kubernetes environments using label selectors.
- Define thresholds for distinguishing test from production CIs using tags, IP ranges, or CMDB-enriched metadata.
- Handle ambiguous devices (e.g., multi-role servers) by applying hierarchical classification rules with fallback categories.
- Integrate third-party asset data (e.g., procurement records) to enrich CI classification with financial and contractual context.
Module 4: Relationship and Dependency Mapping
- Derive host-to-application relationships using process-to-port mapping and listening socket analysis on discovered endpoints.
- Validate network flow data from NetFlow/sFlow tools against active discovery results to confirm communication paths.
- Map middleware dependencies by parsing configuration files (e.g., JDBC URLs, connection strings) from application servers.
- Identify virtualization hierarchies by correlating hypervisor API data with guest OS discovery outputs.
- Resolve circular dependency errors in service maps by applying directional precedence rules based on service ownership.
- Suppress transient relationships (e.g., short-lived batch jobs) using time-based thresholds to maintain map stability.
- Integrate APM tool data to enrich dependency maps with transaction-level call graphs for critical business services.
Module 5: Data Normalization and Reconciliation
- Define attribute transformation rules to standardize hostnames, IP formats, and vendor-specific model names across sources.
- Configure reconciliation engines to prioritize data from authoritative sources (e.g., vCenter over SNMP) during CI updates.
- Handle conflicting attribute values (e.g., OS version discrepancies) by applying timestamp and source reliability weighting.
- Implement data drift detection to flag CIs with significant attribute changes requiring manual review.
- Map raw discovery output fields to CMDB schema attributes using transformation scripts and lookup tables.
- Suppress redundant updates to prevent unnecessary audit log entries and replication traffic in distributed CMDBs.
- Validate normalization logic against edge cases such as multi-homed devices and shared storage arrays.
Module 6: Handling Cloud and Hybrid Environments
- Configure discovery jobs to authenticate with cloud provider APIs (AWS, Azure, GCP) using IAM roles and service principals.
- Differentiate between persistent and ephemeral resources by applying lifecycle tags and auto-aging policies in discovery rules.
- Map cloud resource IDs (e.g., ARN, resource group) to CMDB identifiers to maintain referential integrity across redeploys.
- Integrate with cloud configuration tools (e.g., Terraform state, CloudFormation) to supplement discovery gaps in agentless scans.
- Discover serverless components by parsing function metadata and event source mappings from cloud service APIs.
- Address multi-account and cross-tenant discovery by establishing centralized scanning roles with cross-environment access.
- Adjust discovery frequency for auto-scaled groups based on scaling policies and deployment event triggers.
Module 7: Security and Compliance Integration
- Restrict discovery access to PCI-DSS or HIPAA-regulated systems using network segmentation and access control lists.
- Tag discovered CIs with compliance domains based on data classification and regulatory scope mappings.
- Integrate vulnerability scanner outputs to enrich CIs with patch status and known exploit exposure.
- Suppress discovery of personal or shadow IT devices based on policy-defined exclusion criteria and user opt-out mechanisms.
- Log all discovery activities with immutable audit trails for forensic review and compliance reporting.
- Enforce encryption-in-transit for all discovery probes and data transfers using TLS 1.2+ configurations.
- Coordinate with GRC teams to align discovery scope with annual compliance assessment requirements.
Module 8: Performance Tuning and Error Handling
- Adjust discovery job timeouts and retry policies based on network latency and system responsiveness in remote data centers.
- Implement throttling mechanisms to prevent API rate limiting when scanning SaaS or cloud management platforms.
- Diagnose failed discovery jobs using probe-level logs and network packet captures to isolate connectivity or authentication issues.
- Optimize scan windows by staggering discovery across regions to balance CMDB write load and replication delays.
- Configure alert thresholds for discovery job duration, CI count variance, and error rate spikes.
- Design fallback discovery methods (e.g., agent-based) for systems that fail repeated agentless scan attempts.
- Archive historical discovery logs based on retention policies while preserving root cause analysis data.
Module 9: Change Integration and CMDB Governance
- Integrate discovery results with change management workflows to validate pre- and post-change CI states.
- Configure automated discovery triggers based on change request approvals for high-risk modifications.
- Enforce CMDB update policies by rejecting discovery data that violates data model constraints or naming standards.
- Assign ownership fields in discovered CIs using LDAP group mappings and service assignment rules.
- Reconcile discovery findings with configuration baselines to detect unauthorized or drift configurations.
- Implement approval workflows for automatic CI creation in controlled environments with strict governance.
- Generate reconciliation reports for audit teams showing discovery-driven updates versus manual CMDB entries.