Infrastructure and Cloud Assessment
Cloud egress and data lineage audit
Quantifies hidden egress, orphaned pipelines, and PII paths across multi-account AWS and on-prem remnants.
Scope narrative
We correlated billing exports with network telemetry, traced lineage for the top twenty datasets referenced in board materials, and interviewed data platform owners about manual overrides. Pricing models stayed informational with explicit caveats where metering was incomplete.
What we examine
- Billing export normalization
- Lineage tracing for priority datasets
- PII tagging consistency checks
- Reserved capacity vs on-demand variance
- On-prem replication lag sampling
- Access pattern review for analytics sandboxes
- Executive summary with sensitivity bands
Transaction outcomes we highlight
- Egress run-rate reframed with defensible monthly bands
- Two dormant replication jobs slated for retirement pre-close
- Privacy counsel received a concise PII map for disclosures
Engagement FAQ
Yes, read-only roles scoped to agreed accounts; we document every session.
Field notes from prior sponsors
“The lineage audit for our Series D data room was blunt about blind spots. The board appreciated the honesty about metering gaps.”
“Dense but readable. We disagreed on one tagging assumption; the team revised the appendix within 48 hours after we sent logs.”