b80bea789d
|
||
|---|---|---|
| .github | ||
| INSTALL | ||
| config | ||
| db-bootstrap | ||
| deliveries/cases | ||
| public | ||
| scripts | ||
| tests | ||
| vagrant | ||
| wsl | ||
| .gitignore | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| VERSION.json | ||
| composer.json | ||
| composer.lock | ||
| package.json | ||
| phpunit.xml | ||
README.md
MONARC
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.
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
- Copyright (C) 2016-2024 Luxembourg House of Cybersecurity
- Copyright (C) 2016-2024 Jérôme Lombardi - https://github.com/jerolomb
- Copyright (C) 2016-2024 Juan Rocha - https://github.com/jfrocha
- Copyright (C) 2017-2024 Cédric Bonhomme - https://www.cedricbonhomme.org
- Copyright (C) 2019-2024 Ruslan Baidan - https://github.com/ruslanbaidan
- Copyright (C) 2016-2017 Guillaume Lesniak
- Copyright (C) 2016-2017 Thomas Metois
- Copyright (C) 2016-2017 Jérôme De Almeida
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.