MBA Training Data

Leaders Insights
Leaders Insights
  • 0.0 (0)
  • Management
  • Weekly

MBA Training Data. Strategy in data governance, architecture, analytics and AI, for data leaders and aspiring CDOs. New episodes every week, transcripts at mba-training.com.

  1. 2d ago

    Reddit login wall: a price tag on its AI data licensing

    Is Reddit's move to make most of the site login-only a panic response to Google AI Mode cutting search referrals, or a pricing move? The episode argues the wall matters less for casual readers than for AI companies, since it closes the free logged-out route scrapers use while Reddit renegotiates its data licensing deal with Google. The host pushes back that lurkers are the top of the funnel. You come away able to separate a vanity metric like daily active uniques from revenue, see how one archive supports two money streams (targeted ads to logged-in users and licensing to model builders, including OpenAI and Google), and weigh the flywheel risk of a stale archive and what it means for brands' SEO. 0:00 Google AI Mode cuts Reddit search traffic 1:40 Who the Reddit login wall targets 2:27 Reddit's data licensing talks with Google 4:07 Daily active uniques versus engaged users 6:13 Ads, licensing and the data flywheel 6:54 What the wall means for SEO

  2. 5d ago

    ETS data breach: one stolen SFTP login exposed student records

    How did one compromised login give an intruder nearly four months inside the SFTP server where California swapped student test data with Educational Testing Service (ETS)? The files held names, test results, disability status, Section 504 status and records on students who left as far back as 2006. The hosts split on blame: ETS for the dwell time, or the state for pooling every child's record at one vendor behind one login. You walk away able to audit your own vendor file drops: name an owner, check whether MFA is on, enforce data minimisation with a scheduled deletion job, and treat contract clauses as no substitute for controls that block a bulk download at midnight. 0:00 ETS breach via stolen SFTP login 1:29 Disability and Section 504 records exposed 2:33 Records since 2006 and data minimisation 4:03 Blame debate: ETS or state design 6:12 Notification delays, lawsuits and fallout 7:26 Unowned file drops and missing MFA

  3. Oct 20

    NAV error threshold: back-solving reconciliation tolerances

    Who pays when a fund's NAV is wrong and the manager never saw the error? Under CSSF Circular 24/856 the investment fund manager corrects and compensates, even when the administrator calculated the price. The episode argues that managers should own one position and pricing record, backed by a written pricing policy, rather than inheriting whatever the administrator used. Listeners learn to back-solve reconciliation tolerances from the 0.5% NAV materiality threshold for fixed income UCITS funds: a tenth of it per break for same-day ownership, a quarter of it in open breaks as a NAV gate. Also covered: the aggregation clause, EU T+1, Invesco's identifier consolidation, circular matching, Bloomberg pricing drift and the SEC's Madison Capital Funding settlement. 0:00 Who pays for NAV errors under CSSF 24/856 0:59 Custodian, administrator and IBOR disagree on positions 3:23 Back-solving tolerances from the NAV threshold 5:56 NAV gate versus T+1 cut-offs 7:04 Identifiers, circular matching and price challenge 9:40 Reporting breaks to the board

  4. Oct 13

    Asos hack: why marketing tools hold your Snowflake keys

    How did hackers send a ransom note through the real Asos app? Reporting points to a conned employee and, per researcher Kevin Beaumont, Simon AI, a composable customer data platform owned by Monetate that reads straight from Snowflake with MFA optional and off by default. That route is unconfirmed. The episode argues the real failure is ownership: marketing bought it, data engineering wired it to the warehouse, and nobody owned the login. You leave with a concrete audit: list every third-party tool holding warehouse credentials, check whether MFA is enforced or only available, check whether it can message customers, and fix the risky ones with mandatory MFA or single sign-on before Friday. 0:00 Asos app push notification ransom note 1:55 Social engineering and the Simon AI CDP 3:31 Optional MFA on Snowflake-connected tools 6:17 Why composable CDPs are a data leader problem 7:31 Breach scale, extortion deadline, open questions 8:28 Auditing third-party warehouse credentials this week

  5. Oct 13

    dbt State and agent-ready data: why declared meaning comes first

    Agents dominated dbt Summit, but does smart orchestration or a context layer make data agent-ready on its own? The episode argues no. Fanatics Betting and Gaming saw about 0.2% model reuse from dbt State until it declared source freshness and model-level SLAs, which raised reuse to roughly 15%. The same pattern runs through Fivetran's Context Layer, AI audit trails and token costs. Listeners learn how dbt State is billed per daily active target table, including tests, why the Context Layer's beta status needs checking in writing, how git history serves as an audit trail, and how dbt models served through the MCP server cut Gong transcript tokens by 20x or more. 0:00 Fanatics and the 0.2% dbt State reuse rate 2:21 dbt State pricing and per-test charges 3:53 Fivetran Context Layer: early access risks 6:26 Auditing AI agents without a rulebook 7:49 Why token costs belong to data teams 9:17 Declare meaning before agents act

  6. Oct 9

    ARTEX bank breaches: why side-door data access is a CDO issue

    How did an attacker using ARTEX, an open-source agentic AI penetration-testing tool, take data on more than 67,000 customers from seven South Korean firms, including Shinhan, KB Kookmin and Hana, without touching core banking? The episode argues the failure was data access design. Broker portals and employee apps returned income, loan limits and resident registration numbers to callers who did not need them, despite nearly 124 billion won in security spending. You come away knowing what the Financial Services Commission ordered, how CrowdStrike linked the attack to Claude Code and DeepSeek, and why basic cyber hygiene matters more than an AI defense product. You also get a concrete plan to inventory every externally reachable system that returns customer data and remove unneeded fields. 0:00 Shinhan breach through a loan broker portal 1:13 ARTEX agentic AI tool and the human attacker 2:38 Side-system data access as a CDO problem 4:42 FSC emergency order on exposed systems 6:06 Hygiene failure or AI-driven attack speed 8:16 Weekly task: audit customer data endpoints

  7. Oct 6

    UK GDPR Article 21: 44,000 objections hit NHS Palantir

    What happens when a data platform is legally defensible, operationally embedded and publicly distrusted at the same time? More than 44,000 people have filed Article 21 objections under UK GDPR against NHS England's Palantir-powered Federated Data Platform, live in 142 trusts, weeks before a February 2027 contract break clause comes into reach. The position here: objection handling is a throughput problem, not a policy document. You come away able to pressure-test your own platform. Check the published benefits claims, 117,000 extra operations, a 14.3% cut in discharge delays, against Foxglove FOI data showing 13 of 41 trusts doing fewer operations, and name the owner and service level for mass objections before someone else does. 0:00 44,000 Article 21 objections to NHS data 1:40 What the Federated Data Platform runs 2:31 Palantir politics versus legal mechanism 3:01 Why patients cannot opt out of FDP 4:09 Testing Palantir's NHS benefit claims 7:28 What transfers to any CDO

  8. Oct 6

    dbt State: lag_tolerance is now a budget decision

    dbt State went generally available in September 2026, so rebuilding every model on a cron schedule is now a choice rather than a default. The position here: the tool cannot tell you how stale each model is allowed to be, and the lag_tolerance config most teams set once and globally is a business decision about decision cadence, not an engineering setting. You leave with a method: meter wasted rebuilds using BigQuery INFORMATION_SCHEMA.JOBS or Snowflake credit consumption, tie tolerance to the decision each model feeds, keep source freshness checks running, read the Explain tab in audit mode, and cap agent queries with resource monitors and maximumBytesBilled. Includes the RxBenefits 59% result, dbt's 15 to 30% range, FinOps Foundation and Flexera 2026 findings. 0:00 Why 60% of scheduled model builds repeat 1:13 What dbt State GA actually changes 2:57 Metering wasted rebuilds before flipping the switch 4:18 Silent semantic drift when models are reused 5:41 Committed spend contracts hide the savings 6:57 Capping autonomous agents in the warehouse

See All (94)

About

MBA Training Data. Strategy in data governance, architecture, analytics and AI, for data leaders and aspiring CDOs. New episodes every week, transcripts at mba-training.com.

Information

More From Leaders Insights