Security overview report
A security overview report is available via 'Security checks' in the Site administration "Reports" section.
Some of the checks included are as follows:
- 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.
- Allowing executable paths to be set via the Admin GUI is a vector for privilege escalation. This can be prevented by setting the following config.php:
$CFG->preventexecpath = true;
- 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.
- Security and Privacy forum on moodle.org