MONARC - Method for an Optimised aNAlysis of Risks by @CASES-LU

Go to file

YacineKhamis a4fc78feef First part of dashboard specifications Pictures need to be added, as the missing content that need to be formatted and translated		2017-07-11 18:24:02 +02:00
INSTALL	Moved instructions of deployment.	2017-06-21 22:54:16 +02:00
config	Merge branch 'master' of ssh://rhea.netlor.fr:2222/monarc/MonarcAppFO	2017-05-05 10:49:21 +02:00
data/cache	Init commit > skeleton Monarc Project	2016-04-12 14:39:18 +02:00
db-bootstrap	Fixed a typo in the path of database dump.	2017-06-21 10:30:12 +02:00
docs	Folder for the future docs.	2017-06-21 23:02:55 +02:00
public	Folder for the future docs.	2017-06-21 23:02:55 +02:00
scripts	FIX: script client-upgrade-db > test path	2017-03-17 14:37:49 +01:00
.gitignore	read me	2017-01-31 10:45:04 +01:00
.gitmodules	Init commit > skeleton Monarc Project	2016-04-12 14:39:18 +02:00
DashboardSpecs_Draft.md	First part of dashboard specifications	2017-07-11 18:24:02 +02:00
LICENSE.txt	new license	2017-02-01 16:40:23 +01:00
README.md	Removed now useless section.	2017-06-21 23:30:59 +02:00
behat.yml	Add behat tests including MonarcCore ones	2016-09-22 10:09:01 +02:00
build.properties	working on setup	2016-10-06 11:19:13 +02:00
build.xml	working on setup	2016-10-06 17:07:20 +02:00
composer.json	Fix : set the correct repository for the application	2017-03-08 15:12:21 +01:00
composer.phar	global config	2017-01-24 09:46:23 +01:00
continuous.yml	working on setup	2016-10-06 15:48:10 +02:00
init_autoloader.php	Init commit > skeleton Monarc Project	2016-04-12 14:39:18 +02:00
package.json	FIX - Package.json: Use proper branches and remotes	2017-03-10 15:41:01 +01:00
package.json.continuousphp	Package.json: We are the frontoffice	2017-01-17 09:00:33 +01:00
packages.json	packages.json: Remove more URLs	2016-09-15 14:54:44 +02:00

README.md

Skeleton Monarc Project

Disclaimer: This is a work in progress and software is still in alpha stage.

Introduction

CASES promotes information security through the use of behavioral, organizational and technical measures. Depending on its size and its security needs, organizations 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 organizations, both large and small, to benefit from the advantages that a risk analysis offers, CASES has developed an optimised risk analysis method: MONARC (Method for an Optimised aNAlysis of Risks by CASES), allowing precise and repeatable risk management.

The advantage of MONARC lies in the capitalization 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 generalize risk scenarios for these assets (also called objects) by context and/or business.

More information: [Optimised risk analysis Method] (https://www.cases.lu/index-quick.php?dims_op=doc_file_download&docfile_md5id=56ee6ff569a40a5b52bed0e526a6a77f) (pdf)

Documentation

For a general documentation see here.

For installation instructions see INSTALL.

License

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