Description

This curriculum mirrors the technical and political complexities of a multi-phase infrastructure audit conducted across hybrid environments, akin to those undertaken during enterprise advisory engagements involving inventory reconciliation, security validation, and operational risk reporting.

Module 1: Defining Scope and Stakeholder Alignment

Selecting which business units to include in the infrastructure assessment based on data sensitivity, regulatory exposure, and operational criticality.
Negotiating access to system documentation with department heads who treat architecture diagrams as proprietary or confidential.
Deciding whether to include shadow IT systems discovered during preliminary interviews or exclude them to maintain stakeholder trust.
Establishing escalation paths when infrastructure owners delay audit requests due to competing priorities or perceived risk.
Determining if legacy systems with no active support contracts should be assessed using current security baselines or historical compliance standards.
Documenting conflicting stakeholder definitions of "uptime" when aligning availability metrics across operations, finance, and legal teams.

Module 2: Inventory and Asset Discovery

Resolving discrepancies between CMDB records and active directory scans when 30% of servers are unaccounted for.
Configuring network discovery tools to avoid triggering IDS alerts during passive versus active scanning phases.
Classifying virtual machines that are powered off but retain disk images as active, decommissioned, or archived assets.
Handling asset tagging inconsistencies when subsidiaries use different naming conventions across merged organizations.
Deciding whether to include contractor-owned devices in the inventory when they access internal resources via zero-trust gateways.
Validating software license counts against actual installations when automated tools miss portable or containerized instances.

Module 3: Network Architecture Assessment

Mapping VLAN segmentation effectiveness by correlating firewall rules with observed east-west traffic patterns.
Identifying single points of failure in redundant core switches when failover testing is restricted during business hours.
Evaluating the security implications of flat network designs in development environments that share infrastructure with production.
Assessing DNS dependency risks when critical applications rely on externally hosted or third-party DNS services.
Documenting MPLS versus SD-WAN performance trade-offs at remote sites with inconsistent last-mile connectivity.
Addressing unencrypted internal traffic between microservices when mutual TLS is not enforced by default.

Module 4: Server and Data Center Operations

Assessing patch compliance across heterogeneous OS environments where patching requires vendor-certified change windows.
Measuring CPU and memory overprovisioning in virtualized environments where resource allocation exceeds actual utilization by 300%.
Identifying undocumented dependencies between batch jobs and specific physical hosts during migration planning.
Reviewing backup success rates when log entries indicate partial failures but monitoring systems report completion.
Verifying disaster recovery runbooks against recent system configurations when documentation has not been updated post-migration.
Calculating power and cooling capacity headroom when evaluating options for high-density GPU server deployment.

Module 5: Cloud and Hybrid Environment Evaluation

Mapping IAM roles across AWS accounts to detect privilege escalation paths through cross-account access.
Assessing egress cost exposure in multi-cloud architectures where data replication occurs across regions without traffic shaping.
Validating encryption at rest configurations for managed services when the cloud provider controls key management.
Identifying untagged resources in Azure subscriptions that prevent accurate cost allocation to business units.
Reviewing VPC peering and transit gateway configurations for routing loops or asymmetric traffic flows.
Documenting container image provenance in EKS clusters where developers pull from public registries without scanning.

Module 6: Security and Compliance Posture

Correlating SIEM alerts with endpoint detection logs to determine if phishing incidents led to lateral movement.
Assessing the completeness of disk encryption on laptops when pre-boot authentication is disabled for legacy application compatibility.
Reviewing firewall rulebase hygiene when 40% of rules are tagged as "temporary" but have been active for over two years.
Validating that audit logs are immutable and retained for required periods when log servers are on shared infrastructure.
Identifying systems excluded from vulnerability scans due to stability concerns and documenting compensating controls.
Mapping data flows for GDPR compliance when customer data resides in systems without data classification tagging.

Module 7: Performance and Capacity Analysis

Isolating database latency spikes to storage subsystem bottlenecks versus application-level query inefficiencies.
Forecasting storage growth based on historical trends when a new analytics initiative will increase ingestion by 20x.
Correlating application response times with network jitter metrics across WAN links during peak business hours.
Assessing the impact of anti-malware real-time scanning on file server I/O performance during business operations.
Identifying memory leaks in long-running services by analyzing trend data over 90-day observation periods.
Validating load balancer distribution algorithms when sticky sessions cause uneven backend server utilization.

Module 8: Documentation and Reporting Standards

Standardizing diagram notation across teams when network, security, and application groups use different visual conventions.
Deciding which vulnerabilities to include in executive summaries when technical reports contain hundreds of findings.
Version-controlling infrastructure diagrams in a way that supports rollback without exposing sensitive changes in Git repositories.
Redacting system credentials and IP ranges in assessment reports intended for third-party reviewers.
Aligning risk ratings with organizational thresholds when CVSS scores conflict with operational context.
Structuring findings to support remediation tracking by including system owner, SLA, and dependency information.