Flagship course
Fintech Pipeline Audit Lab
A six-module working lab for teams that need to examine secure data pipelines in fintech—collect evidence, sample controls, and write findings that survive challenge.
Request a seatLearning outcomes
Map sensitive flows
Produce lineage diagrams covering ingest, transform, store, and vendor egress paths.
Sample with intent
Design control samples that match pipeline volume and risk—not arbitrary percentages.
Write usable findings
Draft issues with impact, evidence, owners, and honest scope limits.
Brief stakeholders
Present a short assurance memo suitable for risk committees.
Modules
- 01Scope & system context
Define in-scope systems, data classes, and regulatory triggers for the lab case.
- 02Flow mapping workshop
Trace PII and payment events across brokers, warehouses, and APIs.
- 03Access & ACL evidence
Inventory principals, compare to registers, and sample produce/consume logs.
- 04Retention & encryption checks
Validate lifecycle rules, encryption claims, and orphaned temporary stores.
- 05Vendor handoffs
Review contracts against actual data paths and logging behavior.
- 06Finding clinic & memo
Peer-review drafts and assemble a final assurance brief.
Instructor
Yoon Seo-jin
Former second-line auditor for a Korea-licensed payments firm and later a data platform lead. Seo-jin designs Syncdatanet labs around artifacts she once demanded from engineering—short, evidence-heavy, and free of decorative risk language.
Informational pricing
Listed at ₩890,000 per learner for open cohorts. Private team pricing and Standing Watch retainers are scoped on Pricing. This site does not collect payment.
FAQ
Do I need Kafka experience?
Helpful but not required. We provide a pre-read on broker concepts and focus labs on audit technique rather than cluster administration.
Is this a certification exam?
No. You receive a Syncdatanet certificate of completion after graded labs. It is not a regulatory license.
What is a real limitation of this course?
We do not deep-dive multi-cloud IAM topology for every vendor. Teams with complex landing-zone designs should bring internal reference diagrams; the lab time is reserved for pipeline evidence and findings.
Can we use our own pipeline?
Yes for private cohorts. Open cohorts use a shared fictional fintech case to protect confidentiality.
Course reviews
“Module 5’s vendor handoff checklist caught a logging partner we had never listed in our DPIA.”
The pacing in week three was dense. I needed the weekend to finish the ACL sample—but the annotated solution made the miss obvious.