Find your platform's weaknesses before anyone else does

We assess your Moodle's security with vulnerability scans and penetration testing (pentestingpentestingPenetration testing: a controlled attack simulation to check whether weaknesses can be exploited.), and give you a clear plan to fix what we find.

Security testing: scanning and pentesting

What you gain

The real security status of your platform, with prioritized risks and concrete recommendations.

Is it for you?

Sound familiar?

Check what's happening to you today.

0 of 8

What's included and what you can add

What the service includes

  • Scope definition Platform, server, plugins and integrations.
  • Signed authorization agreement
  • Controlled execution Without disrupting your operations.
  • Report with vulnerabilities, risk and evidence
  • Prioritized recommendations and results presentation

Two kinds of test

What it is
Vulnerability scan
An automated review of known weaknesses.
Pentesting
A controlled attack simulation by specialists.
What it answers
Vulnerability scan
What weak spots does my platform have?
Pentesting
How far could an attacker get?
Depth
Vulnerability scan
Broad and fast.
Pentesting
Deep and targeted.
Frequency
Vulnerability scan
Periodic.
Pentesting
Before launches or after major changes.

Additional services you can add Not included: you can add them with us, depending on your project

Fixing vulnerabilities If your platform is with Edu Labs, we coordinate it; otherwise it's quoted separately.

A guarantee of total security No test guarantees a platform is invulnerable.

Certification The report is evidence, not a certification.

Social engineering Not part of the standard scope.

Ask about an additional service

Phases, timelines and deliverables

Process duration

A scan is faster than a pentest. Timing depends on the systems and integrations involved.

What you get at the end

Scope and authorization agreement. Technical report with risks and evidence. Executive summary. Prioritized recommendations. Verification record, if contracted.

  1. Scope What's assessed, type of test and window.
  2. Authorization Authorization and confidentiality agreement.
  3. Execution Scanning, pentesting or both.
  4. Analysis Validated findings, no false positives.
  5. Report and presentation Technical report and executive summary.
  6. Verification (optional) We check that the vulnerabilities were closed.

What it would look like in practice

Illustrative case: hypothetical scenario
Context

An institution is preparing for an information security audit.

Challenge

An eight-year-old Moodle with more than 30 plugins and two in-house developments, never assessed.

Solution

A platform and server scan, pentesting of critical modules and verification of fixes.

Expected result

Known risks, critical issues fixed and evidence for the audit.

Frequently asked questions

Can the tests affect my platform?

They run in a controlled way within an agreed window; we explain the risks beforehand.

Scan or pentest?

A scan gives you a broad view; a pentest goes deep. Many organizations combine both.

Is the report confidential?

Yes, under a confidentiality agreement.

Have a project in mind?

Tell us about your case and we'll reply with a tailored proposal.