Skip to content

Commit f8c570a

Browse files
Adding Sergio as author
1 parent d17a5bf commit f8c570a

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

MUSESDevGuide.tex

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
\addto{\captionsspanish}{\renewcommand{\bibname}{Bibliography}}
1414

1515
\title{MUSES Developer Guide}
16-
\author{Yasir Ali, Paloma de las Cuevas Delgado, ...}
16+
\author{Yasir Ali, Sergio Zamarripa, Paloma de las Cuevas Delgado, ...}
1717
\cleanlookdateon
1818

1919
\begin{document}
@@ -33,13 +33,16 @@ \chapter{Introduction}
3333

3434
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.
3535

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.
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 the steps to install MUSES in a real company environment.
3737

3838
\chapter{Building MUSES Client}
3939
\label{ch:client}
4040

4141
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}.
4242

43+
\section{Installing Android SDK}
44+
45+
As we will use Eclipse for MUSES development, the first step is to install the Android Development Tools (ADT) plugin.
4346

4447
\chapter{Building MUSES Server}
4548
\label{ch:server}

0 commit comments

Comments
 (0)