MONARC - Method for an Optimised aNAlysis of Risks by @CASES-LU
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ruslan Baidan 32359aa51c
Added back the dependency pluging package and input filters.
10 hours ago
.github Trigger actions on pull request. 2 months ago
INSTALL Udpdaed install guides with references to Laminas. 1 day ago
config migrated to laminas 1 day ago
db-bootstrap updated structure dump. 5 months ago
deliveries/cases Add DE deliverables for GDPR record 6 months ago
public migrated to laminas 1 day ago
scripts Updated the release 2.9.5 related files. 2 months ago
vagrant Added symfony/console to the dependencies list to be able to execute the frontoffice command(s). 1 week ago
.gitignore Removed data folder and updated .gitignore file. 3 months ago
AUTHORS Updated copyright years. 1 month ago Uodated the version number. 1 day ago
LICENSE Added license file. 2 years ago Updated copyright years. 1 month ago Added 9 months ago
VERSION.json Uodated the version number. 1 day ago
composer.json Reverted the laminas/laminas-dependency-plugin. 1 day ago
composer.lock Added back the dependency pluging package and input filters. 10 hours ago
package.json Uodated the version number. 1 day ago

MONARC - Method for an Optimised aNAlysis of Risks by CASES

Latest Release License Contributors Stars Workflow Twitter


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.


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.


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.


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, referentials, etc.) are licensed under CC0 1.0 Universal (CC0 1.0) - Public Domain Dedication. These objects are available through the MONARC Objects Sharing Plarform. If a specific author wants to license an object under a different license, a pull request can be requested.
You can find more information about MOSP on the dedicated repository.