We were wrapping up our interview with Tammy Buchanan about the Kido nursery breach when she said: "Actually, there were some really important points I forgot to make."
So we grabbed another cup of tea, broke out the custard creams, and kept recording.
Then, during the tea break, Graham discovered something on Twitter: VX-Underground, a credible malware research collective, had posted a screenshot of what appears to be a Kido GitHub repository containing API code. Files that typically contain system credentials. A potential smoking gun.
In Part 2, Tammy reveals what was missed in Part 1, including the game-changing fact that cybersecurity is now officially linked to safeguarding in the 2025 Keeping Children Safe in Education guidance. We examine the repository screenshot and discuss what it suggests about how breaches like this happen.
This isn't theory. This appears to be a real-world example of the vulnerability that could lead to children's data being stolen. And your child's school might have the same exposure.
Recorded in the same session as Part 1. This is what happens when cybersecurity news moves faster than podcast recording sessions.
Currently ranked in the Top 100 Apple Business Podcasts (US)
This episode is sponsored by Authentrend Biomentric Hardware
Why Listen to Part 2?
If you listened to Part 1 and thought "that's bad but it won't happen to us," Part 2 will change your mind.
The game-changer: Cybersecurity is now safeguarding, not just IT. Schools can't ignore it anymore.
The smoking gun: A screenshot showing what appears to be exposed code—the exact type of vulnerability experts warn about.
The corrections: What we got wrong in Part 1, and why the reality is even more serious.
What You'll Learn
The Major Revelations
Cyber Security = Safeguarding (2025 Guidance)First time explicitly linked in statutory guidanceChanges everything about how schools must respondMakes Kido a safeguarding failure, not just IT breachGives cyber the legal teeth it's never hadThe Repository ScreenshotVX-Underground documented what appears to be Kido's codeFiles that typically contain credentials visibleRepository has since been removedSuggests how breach may have occurredPartial MFA = No MFASchools enable MFA for head teachers but not everyoneLike "locking doors but leaving windows open"Must be ALL staff with system access or it's uselessThe Third Party IllusionSchools think IT providers handle complianceDfE Standards explicitly say schools must verifyCannot outsource responsibilityPractical Takeaways
Why phone-based MFA conflicts with safeguarding policies (and what to do)The NCSC Cyber Assessment Framework for schoolsQuestions to ask developers about code repositoriesHow to audit custom softwareWhat "Time Off In Lieu" means for trainingThe VX-Underground Discovery (Important Context)
What We Can Confirm
On 28 September 2025, VX-Underground (a credible malware research collective) posted a screenshot showing what appears to be a GitHub repository:
Repository name: kido-fullstack/mykido-apiFiles visible: Including mail.py (typically contains email credentials in Python apps)Repository stats: 2 contributors, 0 issues, 0 stars, 0 forksCurrent status: Repository has been removedVX-Underground's assessment: Called it "f**king slop piece of s**t"See: https://www.instagram.com/reel/DPUjd9mj2tG/What We Cannot Independently Verify
The actual contents of the files (repository is down)Whether repository was public or had limited visibilityThat this definitively caused the breachWhat specific credentials may have been presentWhy It Matters
This screenshot shows the exact type of vulnerability cybersecurity experts warn about:
Custom code pushed to repositories without proper security reviewFiles that typically contain credentials visible in structurePattern common in education sector (confirmed by Tammy)Explains how Famly data could be accessed without Famly infrastructure breachWe present this as a plausible explanation based on professional analysis, not as a confirmed fact.
The Safeguarding Game-Changer
2025 Keeping Children Safe in Education Guidance
For the first time, statutory safeguarding guidance for UK schools explicitly mentions taking appropriate actions to meet the Cyber Security Standard.
Cybersecurity is no longer optional IT workIt's a safeguarding responsibility with Ofsted implicationsSchools respond to safeguarding requirements (unlike IT recommendations)Governors have safeguarding oversight duties that now include cyberThe Kido breach is officially a safeguarding failureWhen it takes effect: The 2025 guidance is already in force. Schools should be implementing now.
Why schools don't know: Most haven't read the updated guidance yet. Awareness is the first problem.
Critical Corrections from Part 1
1. The MFA Misconception
What we said in Part 1: "Only 50% of schools have MFA enabled"
What Tammy clarified: That 50% is misleading because many schools have partial MFA - only for senior staff like head teachers and SENCOs.
The reality: Partial MFA = NO MFA. It's like locking your front door but leaving all the windows open. Attackers target the weakest link, not the strongest.
The phone problem: Many MFA solutions require phones for authentication, but safeguarding policies ban phones in classrooms. Schools need hardware tokens or authenticator apps on shared devices.
Where MFA works: Primarily email systems currently - but email is the gateway to everything else (password resets, system access, parent communications).
2. The Compliance Responsibility Myth
The misconception: "We pay an IT company, so they're handling DfE Digital Standards compliance for us."
The reality: DfE Standards explicitly state it's the organisation's responsibility to ask: "Are we meeting this standard? How do we meet this standard?"
What IT providers should do: Help implement technical controls
What schools must do: Verify compliance is actually happening
Who's responsible: School leadership, governors, senior management - not outsourceable
3. Training and TOIL
Correction: Staff must be given Time Off In Lieu (TOIL) for cybersecurity training. They cannot be expected to complete training unpaid outside work hours.
Why it matters: Schools operating on tight budgets must account for training time in scheduling and costs.
Resources Mentioned
Statutory Guidance and Standards
Keeping Children Safe in Education 2025
Statutory safeguarding guidance for schoolsFirst explicit link between cybersecurity and safeguardingAvailable: UK Government website / DfE publicationsACTION: Read Section on Cyber Security StandardDfE Digital Standards for Schools
Sets out cyber security requirementsSix standards schools should meet by 2030Schools must actively verify complianceACTION: Ask your school "Are we meeting these?"Free Security Resources
NCSC Cyber Assessment Framework (CAF)
Designed specifically for small businesses and schoolsWritten in accessible language (not technical jargon)Covers: access control, incident management, supply chain securityFree to useLINK: ncsc.gov.ukNCSC Early Years Settings Guidance
Bespoke guidance for nurseriesPractical steps for settings without IT expertiseLINK: ncsc.gov.ukFree for public repositoriesDetects exposed credentials in codeSchools should use if they have repositoriesACTION: Enable on all repositoriesTammy's Resources
DfE Digital Standards Webinars
Regular sessions explaining standards in simple termsHow to track progress and implementationContact Tammy for upcoming datesGuest Expert
Tammy Buchanan
Title: Senior Data Protection Consultant
Organisation: Data Protection Education
15 years in UK education sector12 years working directly in schools (8 years technician, 4 years IT manager)"Recovering Dave from IT"What makes Tammy credible: She's not a theoretical expert. She's been the person fixing school printers at 8am, dealing with budget constraints, navigating safeguarding policies. When she says "schools don't have the expertise," she's speaking from lived experience.
Data protection compliance in educationInformation security for schools and MATsDfE Digital Standards implementationGDPR for the education sectorCyber resilience on school budgetsContact Tammy
LinkedIn: Tammy Buchanan (personal) / Data Protection Education (company page)
Compliance assessmentsDfE Digital Standards webinarsData protection consultancy for schools and MATsIncident response supportQuestions Parents Should Ask Their School
Copy these questions and email them to your head teacher:
Security Basics
Do you have multi-factor authentication (MFA) enabled for ALL staff with system access (not just senior leadership)?How often do staff receive cybersecurity training, and is Time Off In Lieu provided for this training?Where is your incident response plan, and when was it last tested?Custom Software and Code
Do we have any custom-built software, integrations, or scripts?If yes: Where is the source code stored? (GitHub, GitLab, etc.)Who has access to our code repositories?Have repositories been scanned for exposed credentials?Do former developers or contractors still have access to our systems?Compliance and Governance
Are we meeting the DfE Digital Standards, and how is this verified?Who on the governing body is responsible for data protection and cyber resilience?How are you addressing cybersecurity as part of your safeguarding responsibilities under the 2025 Keeping Children Safe in Education guidance?Third Party Platforms
Which platforms hold our children's data? (Famly, Tapestry, Arbor, etc.)How do you verify these platforms are securely configured?Does our IT provider handle compliance verification, or do you verify it yourselves?Don't accept: "We have an IT company, they handle all this."
Do accept: Specific answers with evidence of verification.
Questions Schools Should Ask Developers
If you have any custom software, ask your developer:
Where is the source code stored?Is the repository public or private?Who currently has access to the repository?Are there any credentials, API keys, or connection strings in the code?How are secrets managed? (Environment variables, secret management tools?)When was the code last security reviewed?Has the repository been scanned for exposed secrets?What happens if you're not available? Who else can access/maintain this?"What do you mean by credentials in the code?""It's a private repo, it's fine.""I'll get round to moving those credentials out eventually."Cannot answer who else has accessThe Bigger Picture
Why This Matters Beyond Kido
The pattern Tammy sees constantly:
School needs custom integration between systemsHire developer (staff, parent volunteer, local contractor)Developer builds something functionalDeveloper has zero security trainingCode pushed to GitHub/GitLab for convenienceNo security review, no secrets managementRepository sits there for months/yearsFormer contractors still have accessNo documentation of what exists or whereSchool doesn't know to checkOne credential compromise = full breach
The Education Sector Reality
Constraints schools face:
No dedicated IT staff (part-time technician comes twice a week)No cybersecurity budgetVolunteer governors with no technical expertiseStaff expected to train in unpaid timeThird-party providers without clear responsibilitySafeguarding policies that conflict with security best practiceAn overwhelming number of platforms and systemsTurnover of staff and contractorsMake cyber security statutory with Ofsted oversightProvide funding for proper implementationLink explicitly to safeguarding (now happening!)Require IT providers to verify complianceTrain governors on cybersecurity oversightMake DfE Digital Standards non-negotiableThe safeguarding link is the breakthrough - schools MUST respond to safeguarding requirements.
Key Quotes
"It's like locking your front and back doors and then leaving all the downstairs windows open. I consider that to be NOT having MFA enabled."
Tammy on the safeguarding link:
"Schools can ignore IT recommendations. They can say 'no budget, we'll get to it eventually.' But you cannot ignore safeguarding. Safeguarding is non-negotiable."
"This is actually more common than people think, especially in education. Somebody builds something, pushes it to GitHub for version control, and doesn't think about security."
Tammy on compliance responsibility:
"Your IT provider should help you meet the standards, but the responsibility for checking remains with the school leadership. And most schools don't realise that."
Noel on the repository screenshot:
"The attack vector wasn't sophisticated hacking. It appears to be 'your code was accessible on the internet with the keys to the kingdom visible in the files.'"
What's Next?
If You're a Parent
Email your school the questions aboveDon't accept vague reassurancesAsk for specific evidence that they're meeting DfE Digital StandardsRemember: you're asking about safeguarding, not just ITIf You're a School Leader
Read the 2025 Keeping Children Safe in Education guidanceAudit all custom software and code repositoriesEnable MFA for ALL staff (find solutions for phone conflict)Document what you have and who has accessVerify DfE Digital Standards compliance yourselfContact Tammy or similar experts for gap analysisIf You're a Governor
Add cyber security to safeguarding oversightAsk the head teacher the same questions parents should askDon't accept "our IT company handles it"Consider appointing a digital lead on the governing bodyEnsure cyber security is a standing agenda itemSocial Media Sharing
You're a parent with kids in nursery or schoolYou're a school governor or school leaderYou work in educationYou're concerned about children's data protectionYou want schools to take cyber security seriouslyTag: #CyberSecurity #Education #Safeguarding #DataProtection #Kido #DfEDigitalStandards
Share quote: "Cyber security is now officially SAFEGUARDING in UK schools. Not optional IT. Not nice-to-have. SAFEGUARDING. This changes everything."
Connect With The Show
Website: thesmallbusinesscybersecurityguy.co.uk
Blog: Full breakdown of repository screenshot analysis
Subscribe: Available on all major podcast platforms
Review: Leave us a review and tell us what you think
Comment: What security topic should we cover next?
Currently ranked Top 100 Apple Business Podcasts (US)
Related Episodes
Part 1: The Education Data Protection Gap (listen first)
Main interview with Tammy BuchananOverview of Kido breachSystematic failures in education security35-40 minutesInitial reaction to breach announcementWhy nurseries are targetsImmediate implicationsEpisode Credits
Noel Bradford (The Veteran Solution Provider)Mauven MacLeod (The Government-Trained Practitioner)Graham Falkner (Producer/Researcher)Tammy Buchanan (Data Protection Education)Same session recording as Part 1Tea break transition editedCold open recorded post-sessionNatural conversation maintainedCustard creams (the real MVPs)VX-Underground (for documenting the repository before it vanished)Legal Disclaimer
This podcast provides general information about cybersecurity topics for educational purposes. Listeners should consult a professional for their specific situation.
Regarding the repository screenshot: We present analysis based on a screenshot from a credible source (VX-Underground). The repository has been removed and we cannot independently verify its contents. Our discussion represents a professional assessment based on typical development practices, not a confirmed fact about the specific breach mechanism.
The views expressed by guests are their own and do not necessarily reflect the views of the hosts or production team.
Transcript
Full transcript available at: thesmallbusinesscybersecurityguy.co.uk/transcripts
Accessibility: Contact us for alternative formats
Next Episode
Next time: Infosec, Cybersec, and IT security - They are the same right?? Spoiler Alert: No they are not!
Coming soon: More deep dives into small business cyber security. Subscribe so you don't miss it.
Published: 13 October 2025
Duration: ~30 minutes
Format: MP3
Copyright: © 2025 The Small Business Cyber Security Guy
License: All rights reserved
Stay safe out there. Check your repositories. Enable MFA for everyone. And remember, cybersecurity is safeguarding now.