Note: You are currently viewing documentation for Moodle 4.0. Up-to-date documentation for the latest stable version of Moodle may be available here: Security.

Development talk:Security: Difference between revisions

From MoodleDocs
No edit summary
Line 29: Line 29:
* [[Development:Security:Denial of service|Denial of service]]
* [[Development:Security:Denial of service|Denial of service]]
* [[Development:Security:Brute-forcing login|Brute-forcing login]]
* [[Development:Security:Brute-forcing login|Brute-forcing login]]
* Insecure configuration management
* [[Development:Security:Insecure configuration management|Insecure configuration management]]
* Buffer overruns, and other platform weaknesses
* [[Development:Security:Buffer overruns, and other platform weaknesses|Buffer overruns, and other platform weaknesses]]
* Social engineering
* [[Development:Security:Social engineering|Social engineering]]





Revision as of 12:26, 6 November 2009

I am working on a revision of these guidelines. I am going to hack around on this talk page before copying the result to the main page.

Start of new page contents.


This page describes how to write secure Moodle code that is not vulnerable to anything that evil people my try to throw at it.

The page is organised around the common types of security vulnerability. For each one, it explains

  1. what the danger is,
  2. how Moodle is designed to avoid the problem,
  3. what you need to do as a Moodle developer to keep your code secure, and
  4. what you can do as an administrator, to make your Moodle more secure.

The explanation of each vulnerability is on a separate page, linked to in the list below.

This page also summarises all the key guidelines.


Common types of security vulnerability


Summary of the guidelines

  • TODO


See also

CategoryDeveloper Category:Security


End of new page contents.

Please comment below.