MONARC - Method for an Optimised aNAlysis of Risks by @CASES-LU
 
 
Go to file
Cédric Bonhomme 526b54226e
Fixed conflicts.
2019-02-28 21:05:12 +01:00
INSTALL chg: added aside note 2019-01-24 13:45:40 +01:00
config Added the default value for the new 'terms' entry in the local configuration file of MONARC. 2019-02-27 10:43:26 +01:00
db-bootstrap Fixes #77 2018-03-12 10:39:14 +01:00
deliveries/cases Fix ToC for EN 3th delivery 2018-04-17 09:14:39 +02:00
public Folder for the future docs. 2017-06-21 23:02:55 +02:00
scripts Removed now useless lines. 2018-04-20 14:14:07 +02:00
vagrant Updated Changelog. 2019-02-28 21:00:41 +01:00
.gitignore Ignoring public/flags 2018-11-21 08:19:23 +01:00
.gitmodules
AUTHORS release bump 2018-08-22 14:48:39 +02:00
CHANGELOG.md Fixed conflicts. 2019-02-28 21:05:12 +01:00
LICENSE Added license file. 2017-07-10 09:11:24 +02:00
README.md Updated installation section in README. 2018-11-07 08:43:18 +01:00
VERSION.json chg: bumped version number in package.json and VERSION.json 2019-01-24 09:47:08 +01:00
composer.json Updated composer.json: ramsey/uuid is now a requirement 2018-11-21 08:14:55 +01:00
composer.phar global config 2017-01-24 09:46:23 +01:00
init_autoloader.php
package.json chg: bumped version number in package.json and VERSION.json 2019-01-24 09:47:08 +01:00
packages.json Removed build fles, behat configuration file, updated packages and README. 2018-01-25 21:38:45 +01:00

README.md

MONARC - Method for an Optimised aNAlysis of Risks by CASES

Latest Release License Contributors Stars

Introduction

Depending on its size and its security needs, organisations must react in the most appropriate manner. Adopting good practices, taking the necessary measures and adjusting them proportionally: all this is part of the process to ensure information security. Most of all, it depends on performing a risk analysis on a regular basis.

Although the profitability of the risk analysis approach is guaranteed, the investment represented by this approach in terms of the required cost and expertise is a barrier for many companies, especially SMEs.

To remedy this situation and allow all organisations, both large and small, to benefit from the advantages that a risk analysis offers, CASES has developed an optimised risk analysis method: MONARC (Optimised Risk Analysis Method), allowing precise and repeatable risk management.

The advantage of MONARC lies in the capitalisation of risk analyses already performed in similar business contexts: the same vulnerabilities regularly appear in many businesses, as they face the same threats and generate similar risks. Most companies have servers, printers, a fleet of smartphones, Wi-Fi antennas, etc. therefore the vulnerabilities and threats are the same. It is therefore sufficient to generalise risk scenarios for these assets (also called objects) by context and/or business.

Documentation

You will find a user guide and a technical guide on the MONARC website.

For installation instructions see INSTALL.

You can also use the provided Virtual Machine Virtual Machine.

Contributing

If you are interested to contribute to the MONARC project, review our community page. There are many ways to contribute and participate to the project.

Feel free to fork the code, play with it, make some patches and send us the pull requests.

There is one main branch: what we consider as stable with frequent updates as hot-fixes.

Features are developed in separated branches and then regularly merged into the master stable branch.

Please, do not open directly a GitHub issue if you think you have found a security vulnerability. See our vulnerability disclosure page.

License

This software is licensed under GNU Affero General Public License version 3

For more information, the list of authors and contributors is available.

Data provided with MONARC (threats, assets, vulnerabilities) are licensed under CC0 1.0 Universal (CC0 1.0) - Public Domain Dedication. If a specific author wants to license an object under a different license, a pull request can be requested.