You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MUSESDevGuide.bib
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,11 @@ @article{deliverable21
3
3
author={Henrik Arfwedson, Markus Burvall, Yasir Ali, Antonio Mora, Paloma de las Cuevas, Sergio Zamarripa, Jean-Marc Seigneur, Zardosht Hodaie}
4
4
}
5
5
6
+
@article{deliverable24,
7
+
title={D2.4 MUSES Glossary of terms},
8
+
author={Anna Esparcia, Fàtima Barceló, Antonio Mora, Paloma de las Cuevas, Jean-Marc Seigneur, Marc Busch, Federica Freschi, Markus Burvall, Salvatore Piccione}
9
+
}
10
+
6
11
@article{deliverable61,
7
12
title={D6.1 Conceptual Model of User Observation, Application Monitoring Tools, and Context Actuators},
8
13
author={Zardosht Hodaie, Natalia Mannov, Sergio Zamarripa, Yung Shin Van Der Sype, Markus Burvall, Walid Maalej}
Copy file name to clipboardExpand all lines: MUSESDevGuide.tex
+21-1Lines changed: 21 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,23 @@ \chapter{Introduction}
33
33
34
34
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.
35
35
36
+
\section{MUSES on Github}
37
+
\label{sec:musesgit}
38
+
39
+
All the MUSES system code is available at \url{https://github.com/MusesProject}. That is the Github organisation page for MUSES, and it contains the following repositories:
40
+
41
+
\begin{description}
42
+
\item[Muses-Security-Quiz]
43
+
\item[MusesCommon]
44
+
\item[MusesServer] This repository contains all the files in the Java-Maven MUSES server project.
45
+
\item[MusesClient] Repository containing the first prototype of the MUSES client, developed for Android.
46
+
\item[MusesSituationPredictionStudy]
47
+
\item[MusesClientIOS] Repository containing the first prototype of the MUSES client, developed for iOS.
48
+
\item[MusesAwareLibIOS] A library that can be used by applications to retrieve information relevant for MUSES.
49
+
\item[MusesAwareApp] It contains the files of an Android project which consists of a MUSES-aware application. A MUSES-Aware application is an application that uses the MUSES API in order to notify MUSES of user interactions and adapt its behaviour based on MUSES provided commands/security decisions \cite{deliverable24}.
50
+
\item[MusesAwareAppTest] Its purpose is testing the MUSES-Aware application.
51
+
\end{description}
52
+
36
53
This guide is structured as follows. First, Chapters \ref{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.
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}.
42
59
43
60
\section{Installing Android SDK}
61
+
\label{sec:ADT}
44
62
45
63
As we will use Eclipse for MUSES development, the first step is to install the Android Development Tools (ADT) plugin. The requiremenst are \cite{adt:site}:
46
64
47
65
\begin{itemize}
48
66
\item Eclipse 3.7.2 (Indigo) or greater.
49
67
\item Java Platform (JDK) 6.
50
-
\item Eclipse Java Development Tools (JDT) plugin. This can be done in Eclipse by selecting\textit{Help > Install New Software...} and then looking at this reposiroty \url{https://dl-ssl.google.com/android/eclipse/}. After that, selecting \textit{Developer Tools} for installing it (by clicking \textit{Next} and \textit{Finish}), and then restart Eclipse.
68
+
\item Eclipse Java Development Tools (JDT) plugin. To install this pluging, in Eclipse go to\textit{Help > Install New Software...}, and make sure the \textit{Eclipse <youreclipsename> Update Site} is available by clicking in \textit{Find more software by working with the Available Software Sites preferences.}. Then select it and on the package list, look for \textit{Programming Languages > Eclipse Java Development Tools}. Finally, select Eclipse Java Development Tools and click \textit{Next} and \textit{Finish}. Eclipse will need to be restarted.
51
69
\end{itemize}
52
70
71
+
Now we can install the ADT plugin. This can be done by selecting again \textit{Help > Install New Software...} and then looking at this reposiroty \url{https://dl-ssl.google.com/android/eclipse/}. After that, selecting \textit{Developer Tools} from the package list for installing it (by clicking \textit{Next} and \textit{Finish}), and then restart Eclipse one more time.
0 commit comments