Skip to content

Commit d17a5bf

Browse files
Introduction complete
1 parent 55495a2 commit d17a5bf

File tree

2 files changed

+16
-1
lines changed

2 files changed

+16
-1
lines changed

MUSESDevGuide.bib

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,8 @@ @article{deliverable21
22
title={D2.1 Architecture and Prototype Specification},
33
author={Henrik Arfwedson, Markus Burvall, Yasir Ali, Antonio Mora, Paloma de las Cuevas, Sergio Zamarripa, Jean-Marc Seigneur, Zardosht Hodaie}
44
}
5+
6+
@article{deliverable61,
7+
title={D6.1 Conceptual Model of User Observation, Application Monitoring Tools, and Context Actuators},
8+
author={Zardosht Hodaie, Natalia Mannov, Sergio Zamarripa, Yung Shin Van Der Sype, Markus Burvall, Walid Maalej}
9+
}

MUSESDevGuide.tex

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
\usepackage[T1]{fontenc}
33
\usepackage[utf8]{inputenc}
44
\usepackage{lmodern}
5+
\usepackage{url}
56
\usepackage[UKenglish]{babel}
67
\usepackage[UKenglish]{isodate}
78

@@ -20,7 +21,8 @@
2021
\maketitle
2122
\tableofcontents
2223

23-
\chapter{Preliminaries}
24+
\chapter{Introduction}
25+
\label{ch:intro}
2426

2527
This guide describes everything a developer needs to know to start developing for the MUSES system.
2628

@@ -31,16 +33,24 @@ \chapter{Preliminaries}
3133

3234
The MUSES server side is controlled by an enterprise security manager, the Chief Security Officer (CSO), who defines the security policies to be considered in the system. The security policies are used by the MUSES server to identify which behaviour is allowed and which one is not. The server then receives, stores, and processes all the gathered information from users' devices. After that, it analyses the data, performing a real-time risk and trust analysis. In addition, the system detects policy violations through event correlation techniques, adapting to changes in the environment, as well as non-secure user behaviours.
3335

36+
This guide is structured as follows. First, Chapters \label{ch:client} and \ref{ch:server} detail how to build MUSES, in order to be able to star developing and testing the system, either you want to develop for the client (Chapter \ref{ch:client}), the server (Chapter \ref{ch:server}), or both. Then, Chapter \ref{ch:sensors} specifies how to integrate new sensors to the MUSES client, for better monitoring user's actions and making the \textit{context\footnote{Any information that can be used to characterize the situation of the user.\cite{deliverable61}} observation} more complete. Finally, Chapter \ref{ch:installmuses} enumerates what are the steps to install MUSES in a real company environment.
37+
3438
\chapter{Building MUSES Client}
39+
\label{ch:client}
40+
41+
The first prototype of MUSES has been developed for Android. This chapter describes the needed tools, as well as building instructions, for developing inside the MUSES client. For instructions about how to install the whole system, please refer to Chapter \ref{ch:installmuses}.
3542

3643

3744
\chapter{Building MUSES Server}
45+
\label{ch:server}
3846

3947

4048
\chapter{Creating and integrating new sensors}
49+
\label{ch:sensors}
4150

4251

4352
\chapter{Installing MUSES}
53+
\label{ch:installmuses}
4454

4555
\bibliographystyle{abbrv}
4656
\bibliography{MUSESDevGuide}

0 commit comments

Comments
 (0)