Note: You are currently viewing documentation for Moodle 3.6. Up-to-date documentation for the latest stable version of Moodle is likely available here: Security overview report.

Security overview report: Difference between revisions

From MoodleDocs
(vendor directory (MDL-59969))
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Security}}
{{Security}}
A security overview report is available for site administrators in ''Settings > Site administration > Reports > Security overview''.
A security overview report is available via 'Security overview' in the Site administration.
 
[[Image:Security overview.png|thumb|right|Security overview]]


*[[report/security/report security check globals|Register globals]]
*[[report/security/report security check globals|Register globals]]
Line 12: Line 10:
*[[report/security/report security check displayerrors|Displaying of PHP errors]]
*[[report/security/report security check displayerrors|Displaying of PHP errors]]
:If PHP is set to display errors, then anyone can enter a faulty URL causing PHP to give up valuable information about directory structures and so on.
:If PHP is set to display errors, then anyone can enter a faulty URL causing PHP to give up valuable information about directory structures and so on.
*[[Vendor directory security check|Vendor directory]]
:The vendor directory should not be present on public sites.


*[[report/security/report security check noauth|No authentication]]
*[[report/security/report security check noauth|No authentication]]
Line 36: Line 37:
*[[report/security/report security check emailchangeconfirmation‎|Email change confirmation]]
*[[report/security/report security check emailchangeconfirmation‎|Email change confirmation]]
:You should generally always force users to confirm email address changes via an extra step where a confirmation link is sent to the user.
:You should generally always force users to confirm email address changes via an extra step where a confirmation link is sent to the user.
*[[report/security/report security check cookiesecure|Secure cookies]]
:It is recommended to use secure cookies only when serving over SSL.


*[[report/security/report security check configrw|Writable config.php]]
*[[report/security/report security check configrw|Writable config.php]]
Line 57: Line 61:
*[[report/security/report security check frontpagerole‎|Frontpage role]]
*[[report/security/report security check frontpagerole‎|Frontpage role]]
:This checks that the frontpage user role is defined with sane permissions.
:This checks that the frontpage user role is defined with sane permissions.
*[[report/security/report security check defaultcourserole|Default course role (global)]]
:This checks that the default course role globally is defined with sane permissions.
*[[report/security/report security check courserole‎|Default roles (courses)]]
:This check alerts you if any courses are using an odd default course role.


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


* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]
* [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum] on moodle.org


[[Category:Report]]
[[Category:Report]]
Line 72: Line 70:


[[de:Sicherheitsbericht]]
[[de:Sicherheitsbericht]]
[[es:Reporte Vista general de Seguridad]]
[[eu:Seguratasunaren_ikuspegi_orokorra]]
[[eu:Seguratasunaren_ikuspegi_orokorra]]
[[fr:Panorama de sécurité]]
[[fr:Panorama de sécurité]]
[[ja:セキュリティオーバービュー]]
[[ja:セキュリティオーバービュー]]

Latest revision as of 07:37, 19 September 2017

A security overview report is available via 'Security overview' in the Site administration.

register_globals is a PHP setting that must be disabled for Moodle to operate safely.
The dataroot is the directory where Moodle stores user files. It should not be directly accessible via the web.
If PHP is set to display errors, then anyone can enter a faulty URL causing PHP to give up valuable information about directory structures and so on.
The vendor directory should not be present on public sites.
Use of the "no authentication" plugin can be dangerous, allowing people to access the site without authenticating.
Allowing ordinary users to embed Flash and other media in their texts (eg forum posts) can be a problem because those rich media objects can be used to steal admin or teacher access, even if the media object is on another server.
Even the flash media filter can be abused to include malicious flash files.
User profiles should not be open to the web without authentication, both for privacy reasons and because spammers then have a platform to publish spam on your site.
Allowing Google to enter your site means that all the contents become available to the world. Don't use this unless it's a really public site.
Using a password policy will force your users to use stronger passwords that are less susceptible to being cracked by a intruder.
Setting a password salt greatly reduces the risk of password theft.
You should generally always force users to confirm email address changes via an extra step where a confirmation link is sent to the user.
It is recommended to use secure cookies only when serving over SSL.
The config.php file must not be writeable by the web server process. If it is, then it is possible for another vulnerability to allow attackers to rewrite the Moodle code and display whatever they want.
Make sure that you trust all the people on this list: they are the ones with permissions to potentially write XSS exploits in forums etc.
Review your administrator accounts and make sure you only have what you need.
Make sure that only roles that need to backup user data can do so and that all users who have the capability are trusted.
This checks that the registered user role is defined with sane permissions.
This checks that the guest role is defined with sane permissions.
This checks that the frontpage user role is defined with sane permissions.

See also