Education & EdTech

Pentesting for platforms trusted with student data.

Expert-led penetration testing for learning platforms, student data and school integrations, with validated findings and verified remediation through one connected platform.

  • CREST-Accredited Testing
  • ST4S Assurance Support
  • Privacy-Focused Testing
Trusted byStepsWebStoryparkMoneyTime
Neil Edmond
“Security is an important part of building trust in an education platform. Capture The Bug helped us approach ST4S security testing with confidence, combining technical expertise with a collaborative approach that worked well for our team. Their platform gave us visibility into findings, while direct access to the pentesters and support through remediation and retesting helped us address security risks efficiently without slowing down development.”
Neil EdmondCEO and Co-Founder, MoneyTime

Independent Assurance

Expert-led testing. Independently accredited.

  • CRESTCREST-Accredited Penetration Testing
  • CREST Security Testing of AI accreditationCREST Security Testing of AI

- EdTech Risks

Where learning platforms put student data at risk.

Four critical security risks across modern learning platforms and student data.

Student Data Across Schools

Broken tenant isolation exposing records between different schools.

Roles & Permissions

Weak authorisation allowing students to access restricted staff functions.

Single Sign-On & Identity

Authentication weaknesses across school identity providers and SSO integrations.

Plugins & Integrations

Excessive third-party permissions exposing sensitive student information.

- How We Work

From scope to verified fixes.

Expert-led penetration testing with live findings, specialist collaboration and remediation tracking through one connected platform.

  1. 01

    Scope

    Agree the systems, user roles and testing boundaries.

    Agreed scope
  2. 02

    Test

    Specialists test by hand for exploitable weaknesses.

    Live findings
  3. 03

    Report

    Each finding documented with evidence, severity and impact.

    Prioritised report
  4. 04

    Remediate

    Clear guidance and direct specialist support for your team.

    Fix guidance
  5. Retest

    Fixes retested within your engagement terms.

    Verified fix

Ready to assess your learning platform?

Discuss your testing requirements and security priorities with our specialists.

Discuss Your Testing Needs

- Assurance & Evidence

Evidence for schools, customers and your board.

  • ST4S

    ST4S

    Testing evidence supporting Safer Technologies 4 Schools assessments.

  • PRIV

    Privacy Act

    Testing evidence supporting privacy obligations and student data protection requirements.

  • ISO

    ISO 27001

    Technical evidence supporting information security management and controls.

  • SOC2

    SOC 2

    Validated findings supporting relevant security control assessments.

Validated findings and verified fixes support customer assurance and relevant security assessment requirements.

- FAQ

Education security, answered.

Ask a question +
  • EdTech platforms often handle student information, parent accounts, teacher access, administrative privileges, payments and integrations with other education systems. Testing should consider authentication, authorisation, data exposure, APIs, business logic and the separation of access between different user roles.

  • Yes. Penetration testing can support the technical assurance required as part of an ST4S security programme by independently assessing relevant applications, APIs and security controls. Scope should be agreed based on the platform and the assurance evidence required.

  • Yes. Capture The Bug works with education technology platforms and can scope testing around sensitive student data, multiple user roles, administrative access, web applications, APIs and other systems that are important to the security of an education platform.

  • Testing is scoped and coordinated with your team before it begins. We agree the target systems, testing approach, accounts, timing and any operational constraints so the assessment can be conducted safely while minimising unnecessary disruption.

  • Yes. Web applications and APIs are often closely connected, so testing them together can provide a more complete view of how authentication, authorisation, data access and business workflows behave across the platform.

  • No. Compliance can be one reason to test, but many EdTech teams also use penetration testing before important releases, when introducing new integrations or user roles, when responding to customer security requirements, or simply to gain independent assurance over the security of their platform.

Keep learning safe.

Expert-led penetration testing to protect learning platforms and student data.