Multi Metrics Based Framework
Multi Metrics Based Framework for Measurable Security
|Supervisor(s)||Seraj Fayyad, Josef Noll|
|Problem description:||Embedded System (ES) becomes increasingly popular in modern times. This popularity increases the importance of the security for these systems. The reliable evaluation of the ES`s security is considered as a crucial requirement for the enhancement of its security. The evaluation of the security level for a given ES has various challenges, such as the heterogeneity among system`s components. One of the promising approaches, which considered these challenges is Multi Metrics (MM) approach. In his/her thesis, the student will investigated the applicability of MM approach on real ES use case, such as smart meter system. In his investigation, the student will identify the security level of the system and will identify the possible changes which could impact the security level of the system.|
|Methods and Tools:|| The tools and methods in this thesis are based on
|Time schedule|| The envisaged time schedule (for 4 month thesis/30 ECTS) is:
|Pre-Knowledge||This thesis includes a reasonable amount of IT security terminologies. Thus it is expected that the student has a good knowledge IT security, preferably to have also basic knowledge in J2EE and java script.|
this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Multi Metrics Based Framework
This page provides hints on what to include in your master thesis.
Title page, abstract, ...
- 1. Introduction, containing: short intro into the area, what is happening
- 1.1 Motivation, containing: what triggered me to write about what I'm writing about
- 1.2 Methods, containing: which methods are you using, how do you apply them
- 2. Scenario, optional chapter for explaining some use cases
- 2.1 user scenario, (bad name, needs something bedre)
- 2.2 Requirements/Technological challenges
- 3. State-of-the art/Analysis of technology, structure your content after hardware/SW (or other domains). Describe which technologies might be used to answer the challenges, and how they can answer the challenges
- 3.1 technology A
- 3.2 technology B
- 4. Implementation
- 4.1 Architecture, functionality
- 5. Evaluation
- 6. Conclusions
Your thesis should have a "red line", which is visible throughout the whole thesis. This means you should mention in the beginning of each chapter how the chapter contributes to the "goals of the thesis".
Use of scientific methods
A thesis follows a standard method:
- describe the problem (problemstilling)
- extract the challenges. These challenges should be measurable, e.g. method is too slow to be useful to voice handover.
- Analyse technology with respect to challenges. Don't write & repeat "everything" from a certain technology, concentrate on those parts (e.g. protocols) which are of importance for your problem
- Wikipedia is good to use to get an overview on what is happening. But there is not scientific verification of Wikipedia, thus you should use wikipedia only in the introduction of a chapter (if you use text from wikipedia). Use scientific literature for your thesis.
- Scientific library is "at your hand", you can get there directly from UiO: [[How to get access to IEEE, Springer and other scientific literature -> Unik/UiOLibrary]]
- I suggest that references to web pages, e.g. OASIS, W3C standards, are given in a footnote. Only if you find white papers or other .pdf documents on a web page then you refer to them in the reference section.
Evaluation of own work
Perform an evaluation of your own work. Revisit the challenges and discuss in how you fulfilled them. Provide alternative solution and discuss what should be done (or what could have been done).