Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Talk:Security: Difference between revisions

From MoodleDocs
(New page: 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 ...)
 
No edit summary
Line 4: Line 4:
-----------
-----------


This page describes how to write secure Moodle code, that is not vulnerable to security vulnerabilities.
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 what the danger is, and then to write Moodle code that avoids that vulnerability. Each vulnerability is described on a separate page, see the list below. This page also contains a summary of all the guidelines for writing secure code.
The page is organised around the common types of security vulnerability. For each one, it explains
# what the danger is,
# how Moodle is designed to avoid the problem, and
# what you need to do in your code to keep Moodle 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==
==Common types of security vulnerability==


* [[Security:Cross-site_request_forgery|Cross-site request forgery]]
* [[Security:Cross-site_request_forgery|Cross-site request forgery]] (XSRF)
* Cross-site scripting
* Cross-site scripting (XSS)
* SQL injection
* SQL injection
* Command-line injection
* Command-line injection
Line 30: Line 36:


* TODO
* TODO


==See also==
==See also==

Revision as of 17:58, 5 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, and
  3. what you need to do in your code to keep Moodle 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

  • Cross-site request forgery (XSRF)
  • Cross-site scripting (XSS)
  • SQL injection
  • Command-line injection
  • Confidential information leakage
  • Configuration information leakage
  • Unauthorised access
  • Unauthenticated access
  • Session fixation
  • Denial of service
  • Brute-forcing login
  • Insecure configuration management
  • Buffer overruns, and other platform weaknesses
  • Social engineering


Summary of the guidelines

  • TODO


See also

CategoryDeveloper Category:Security


End of new page contents.

Please comment below.