Homeworks and thesis subjects for the Computer Security courses - (03SGD + 02KRQ) of the Politecnico di Torino academic year 2018-2019 Prof ...

Page created by Annette Fischer
 
CONTINUE READING
Homeworks and thesis subjects for the Computer Security courses - (03SGD + 02KRQ) of the Politecnico di Torino academic year 2018-2019 Prof ...
Homeworks and thesis subjects
for the Computer Security courses
          (03SGD + 02KRQ)
     of the Politecnico di Torino
     academic year 2018-2019

          Prof. Antonio Lioy
          < lioy @ polito.it >

       version 1.0 of 10/12/2018
Homework
   max grade:
       27 for the written part
       3 for the oral presentation (optional)
   report:
       use Latex (see example at the web site)
       about 30 pages (minimum, not maximum)
       (optional) PPT slides for a brief talk (about 30’)
   can be delivered at any time but – to record the grade in a certain session –
    MUST compulsory be delivered respecting the following deadlines:
       17/2/2019 for recording the grade in February 2019
       14/7/2019 for recording the grade in July 2019
       15/9/2019 for recording the grade in September 2019

                                                                                    2
Homework outline
   meet your tutor to define your workplan
        write down your workplan and send it to
             your tutor and the teacher
             for approval
   send periodic updates to the tutor and the teacher
        brief (no more than 30 lines)
        with clear reference to the workplan (items completed, problems encountered)
        at least every 15 days
   it's possible to deliver ONE (at most TWO) draft version of the report to get
    feedback from the tutor/teacher:
        assuming that the draft is delivered well in advance of the deadline for the final
          version
        once the final report is delivered, it will be graded without any chance to further
          amend it
   please note that teacher and tutors are NOT available during August

                                                                                               3
Report skeleton
   introduction and state-of-the-art
   description of the new technique / analyzed solution
   advantages and disadvantages
   residual risks
   (when applicable) experimental performance analysis
   if the homework included the development or use of some programming code:
        user manual (how-to for installation and use)
        programmer manual (program logic, data and functions, how-to build)
   bibliography / sitography

   SHOULD DEMONSTRATE KNOWLEDGE OF COURSE'S TOPICS
      … without useless repetitions

                                                                                4
Picking up an homework
   it's NOT first-come-first-served
   contact the tutor to evaluate:
        your real understanding of the subject
        pre-requisites

   homeworks already assigned are marked with one or more X in the title (one X
    per person, up to the maximum number of people allowed for the homework)

                                                                                   5
Note about homeworks by several students
   the role of each student must be clear
        … in order to get individual evaluation
   at the same time, it must be clear the benefit of having done a joint homework
    (i.e. some common part such as a common introduction or a joint experiment)

                                                                                     6
Homework and graduation work (thesis)
   your homework may be the first part of your final graduation work (a.k.a.
    thesis)
   if you want to do your thesis in the computer security area then let the teacher
    know this before getting the homework
   in this case do NOT select a specific homework but select a thesis project and
    contact the teacher for getting a suitable subject inside the project
   thesis subjects related to EU research projects often have a possible direct
    connection with:
      a stage or job at one of the project's partners (as well as at POLITO)
      pursuing a PhD title

                                                                                       7
Final notes
   look for of updates of this document (e.g. subjects already assigned, addition
    of new subjects)
        each version is identified as X.Y (major.minor)
        the major number is changed when new subjects are added
        the minor number is changed when a subject is assigned to a student
   if you are interested in computer security but can’t find a suitable subject in
    this list (are you kidding me?) then you can propose your own subject

                                                                                      8
Elenco dei progetti di ricerca per tesi

                  /

Possible research projects for thesis

                                          9
Research projects (I)
   SHIELD project (www.shield-h2020.eu)
      EU project for using SDN, NFV, and TC to create a virtualized secure and
        trusted network infrastructure for various use cases such as:
           protection of an Intranet
           outsourced network management
      partners: POLITO, Telefonica, HP, …
      possible subjects:
           security policies (specification, management and translation)
           automatic network and system configuration of security parameters
           security optimization
           trusted network connections
           trusted execution environment (based on virtual machines)
           remote attestation
      requirements:
           C or Java programming
      environment:
           Linux (preferred) or Windows
      contact: LIOY / lioy@polito.it / 011 0907021                               10
Trusted Computing, i.e. what is my trust foundation?
   in my network are there only my computers?
   my computers are running only the sw selected by me?
   is the sw configured in the proper way?
   when I use a public network (e.g. Internet) rather than a private network, am I
    really connected to the expected node?
   when I am connected to a server, how can I verify its application sw is the
    “good” one or it has been altered?

                           TRUST & INTEGRITY

   answers: Trusted Computing (and Trusted Network Connection)
      TPM for desktop, MTM for mobile (or equivalent solutions)
      TC-enhanced Linux + trusted virtualization
      remote attestation & TLS

                                                                                      11
Components of a TC system

                                     isolation
local / remote attestation     execution in separate
  proof of configuration     domains / compartments /
    (whole sw stack)              environments

                                 protected memory
                                 hw key container
        secure I/O
                                  data encryption
     towards the user
                                    data sealing
 among various components

                                                        12
Research projects (II)
   FICEP
       project for connecting the Italian e-ID system to the EU e-ID interoperability
        architecture (eIDAS)
       possible subjects:
           digital identity (SAML, XACML, id federation)
           public-key certificates, digital signatures, PKI
           e-ID implementation (smart-card, smartphones, NFC, …)
           e-government applications
       requirements:
           Java programming
           web programming
       environment:
           Linux (preferred) or Windows

   contact: LIOY / lioy@polito.it / 011 0907021

                                                                                         13
Research projects (III)
   DeepAugur
      Smart Traffic Analyzers, for inspection of encrypted or masqueraded network
       traffic
      in collaboration with Telefonica

        possible subjects:
            network security protocols
            machine learning algorithms
        requirements:
            high-level programming language (C, Python, …)
            (desirable) knowledge of a machine-learning framework
        environment:
            Linux (preferred) or Windows

   contact: LIOY / lioy@polito.it / 011 0907021

                                                                                     15
Elenco delle tesine / tesi proposte
(in aggiunta alle tesi sui progetti di ricerca)

                      /

     Possible homeworks and thesis
    (in addition to the thesis subjects
   associated to the research projects)

                                                  16
vTPM integration in KVM hypervisor domain (H)
   tutor:
       LIOY / lioy@polito.it / 7021
       DE BENEDICTIS / marco.debenedictis@polito.it / 7192
   topic:
       the virtual Trusted Platform Module is a software implementation of a crypto
         device used to secure keys and provide evidence about platform integrity
   people: 1
       1 for homework
   example references:
       IBM vTPM 2.0 source code: https://github.com/stefanberger/swtpm/wiki
       http://www.trustedcomputinggroup.org/work-groups/trusted-platform-module/
   outline (details to be agreed with the tutor):
       analysis of the TPM 2.0 capabilities, development of a manager application to
         instantiate a vTPM within a VM, simple demo application of vTPM usage
   required skills:
       Linux system programming

                                                                                        17
Policy-based authorization in TPM 2.0 (H)
   tutor:
       LIOY / lioy@polito.it / 7021
       DE BENEDICTIS / marco.debenedictis@polito.it / 7192
   topic:
       the Trusted Platform Module 2.0 release offers an extensive support for “atomic”
         authorization policies compared to TPM 1.2
       these policies express what the TPM needs to check to validate use of a
         protected object (e.g. key, secret) and can be combined to express a complex
         authorization semantic
   people: 1
       1 for homework
   example references:
       http://www.trustedcomputinggroup.org/work-groups/trusted-platform-module/
   outline (details to be agreed with the tutor):
       analysis of the TPM 2.0 capabilities, development of simple demo applications to
         protect objects with simple and combined authorization policies
   required skills:
       Linux system programming

                                                                                           18
Hardware-bound VM attestation (T)
   tutor:
       LIOY / lioy@polito.it / 7021
       DE BENEDICTIS / marco.debenedictis@polito.it / 7192
   topic:
       the virtual Trusted Platform Module enables virtual platform attestation by
         recording platform measurements in protected Platform Configuration Registers
       securing virtual platform measures within a physical TPM to ensure tamper
         resistance
   people: 1
       1 for thesis
   example references:
       IBM vTPM 2.0 source code: https://github.com/stefanberger/swtpm/wiki
       http://www.trustedcomputinggroup.org/work-groups/trusted-platform-module/
   outline (details to be agreed with the tutor):
       analysis of the TPM 2.0 capabilities, definition of protection mechanism for virtual
         platform measures, development of a minimal remote attestation architecture
   required skills:
       Linux system programming
       client/server architectures                                                          19
Multi-factor authentication with TPM 2.0 (T)
   tutor:
       LIOY / lioy@polito.it / 7021
       DE BENEDICTIS / marco.debenedictis@polito.it / 7192
   topic:
       multi-factor authentication is a method to identify a user based on more than a
         single piece of evidence (e.g. password + biometric factor)
       the Trusted Platform Module 2.0 design allows for complex forms of
         authentication via Extended Authorization (EA) policies
   people: 1
       1 for thesis
   example references:
       https://en.wikipedia.org/wiki/Multi-factor_authentication
       http://www.trustedcomputinggroup.org/work-groups/trusted-platform-module/
   outline (details to be agreed with the tutor):
       analysis of the TPM 2.0 capabilities, development of an application for secret
         management (e.g. password manager) that exploits multi-factor authentication
   required skills:
       Linux system programming
       graphical user interfaces                                                         20
Intel SGX (H / T)
   tutor:
       LIOY / lioy@polito.it / 7021
   topic:
       SGX is an Intel technology to create a "secure enclave" to store sensitive data
         (e.g. keys) and run sensitive processes (e.g. computation on encrypted data)
   people: 2
       1 for homework
       1 for thesis = ???
   example references:
       https://en.wikipedia.org/wiki/Software_Guard_Extensions
       … and all the links mentioned in that page
       "hello world" for SGX = https://github.com/digawp/hello-enclave
   outline (details to be agreed with the tutor):
       (H) analysis of the SGX platform, development of a simple demo application
       (T) development of a full-fledged sensitive computation on SGX
   required skills:
       C/C++
       Intel architecture
                                                                                          21
Advances in TLS / HTTP security (H)
   tutor:
       LIOY / lioy@polito.it / 011 0907021
   topic:
       HTTP Strict Transport Security (HSTS), HTTP Public Key Pinning (HPKP)
       Extended Validation (EV) certificates
       TLS-1.3
   people: 2 (Enrico G. GRASSO + Mr. X)
   sample references:
       IETF TLS WG = https://datatracker.ietf.org/wg/tls/charter/
       https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
       https://blackhat.com/presentations/bh-dc-09/Marlinspike/BlackHat-DC-09-
         Marlinspike-Defeating-SSL.pdf
       https://en.wikipedia.org/wiki/Extended_Validation_Certificate
       https://en.wikipedia.org/wiki/HTTP_Public_Key_Pinning
   outline:
       read documentation, experiment (if supported by tools) and write the report
   required skills: HTTP, TLS
                                                                                      22
Security automation (H / T)
   tutor:
       LIOY / lioy@polito.it / 011 0907021
   topic:
       analyze various standards in the SCAP framework (e.g. CVE, CVSS, OVAL,
         NVD) to evaluate operational risks
       experimental evaluation of open-source tools (or development / improvement for
         thesis) to implement various SCAP components
   people: up to 2 (homework) or 1 (thesis)
   sample references:
       http://csrc.nist.gov/publications/drafts/800-126-rev3/sp800_126_r3_draft.pdf
       https://www.open-scap.org/
   outline:
       read documentation, experiment with the tools, and write the report
   required skills:
       various

                                                                                         23
IETF security (H)
   tutor:
       LIOY / lioy@polito.it / 011 0907021
   topic:
       trends on security aspects of Internet
       look at the current active security WGs at IETF and find an interesting one
            https://datatracker.ietf.org/wg/#sec
       you may look also at the other IETF areas when there is a group working on
         security aspects
   people: up to 4
   outline:
       describe the problem addressed by the WG
       describe the approach, solutions, activities
       compare to state-of-the-art
   required skills: depend upon the selected WG
   references:
       https://datatracker.ietf.org/wg/#sec
       https://datatracker.ietf.org/wg/

                                                                                      24
Key management and encryption services (T)
   tutor:
       ATZENI / shocked@polito.it / 011 0907173
   topic:
       confidentiality and integrity functions (e.g. signing, encryption, key management)
         is relevant in production environment. Hardware (HSM, NetHSM) and software
         solution (Vault, Knox) exists to cope with this problem . Both have pros and cons.
         Aim of this thesis is to critically analyze and test the options available in the field.
   people: 1
   references :
       PKCS#11 https://www.oasis-open.org/standards#pkcs11-base-v2.40
       KMIP https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=kmip
       https://www.vaultproject.io/
       https://github.com/pinterest/knox/wiki
       https://www.opendnssec.org/softhsm/
   outline:
       gathering, analysis, and critical comparison of available solutions, testing
         environment implementation, deployment in selected scenarios (e.g. eIDAS)
   preferred skills: PKCS#11, HSM, key management, Linux SysAdmin
                                                                                                    25
Automatic malware signature generation (T)
   tutor:
       ATZENI / shocked@polito.it / 011 0907173
   topic:
       up to the 2010s, the industrial standard for the detection of malicious applications
         has been mainly based on signatures; as each tiny alteration in malware make
         them ineffective, new signatures are frequently created. Recently, new
         paradigms emerged exploiting machine learning techniques to automatic derive
         new signatures. Purpose of this thesis is the evolution of current methodologies
   people: 2 (1 for Android and 1 for Win)
   example reference:
       “Countering Android Malware: a Scalable Semi-Supervised Approach for Family-
         Signature Generation” https://ieeexplore.ieee.org/document/8485352.
   outline:
       1) analysis of the state-of-the-art 2) design, implementation and testing of a
         methodology to evolve current edge solution.
   preferred skills:
       Android or Windows (app and system level), machine learning.

                                                                                               26
SSG – security serious games (T/H)
   tutor:
       ATZENI / shocked@polito.it / 011 0907173
   topic:
       serious games are a recent tendency to exploit games for specific training.
         However, only a few serious game has been developed in the field of security
         (e.g. Computer Forensics). Purpose of the thesis is to apply serious game
         methodology for evolving developed SSG on this subject
   people: up to 3 for the homework, up to 2 for the thesis
   references:
       selected document to be discussed with the tutor (past thesis and homeworks on
         the matter)
   outline:
       (H) evolution of already developed SSG (scenarios improvements)
       (T) design of the game requirements (goals, user models), game development,
         experimental evaluation
   required skills: high-level programming
   preferred skills: browser-based development, knowledge of the Unity framework

                                                                                         27
Usable security (T)
   tutor:
       ATZENI / shocked@polito.it / 011 0907173
   topic:
       Since end users are largely unaware of security principles, many security issues
         are caused by usability problems. Purpose of this thesis is to identify usability
         issues in widespread security procedures and tools, define a benchmarking
         methodology to assess usability in security, and propose policies to develop
         secure and usable products
   people: 1
   Example reference:
       http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89.6079&rep=rep1&ty
         pe=pdf (+selected documents to be discussed with the tutor)
   outline:
       Analysis of state-of-the-art in usability evaluation of security, selection of target
         security tools and procedures, analysis of selected items, synthesis and
         refinement of available evaluation methodology, definition of policy and rules to
         avoid usable security pitfalls.
   preferred skills: usability, human-computer interaction, interest in cognitive science

                                                                                                28
Security of ICS (T)
   tutor:
       LIOY / lioy@polito.it / 011 0907021
       BASILE / cataldo.basile@polito.it / 011.0907173
   topic:
       ICS (Industrial Control Systems) are at the heart of the Industry-4.0 revolution
       connecting automation equipment to LANs and Internet creates several
         vulnerabilities
   people: 2
   references:
       recommendations by NIST and other bodies about security of ICS
   outline:
       critically analyze the recommendations
       participate in the development of guidelines and a security gateway for a test-
         bed in the proiect HOME
   required skills: Linux

                                                                                           29
30
Analisi e implementazione di strumenti di protezione del dato –
Data Loss Prevention (T)

Il nuovo regolamento europeo sulla privacy (GDPR) introduce nuovi concetti e paradigmi per la protezione
dei dati personali gestiti e utilizzati dalle aziende.

All’interno del contesto aziendale Intesa Sanpaolo, per adempiere ad alcuni dei principi introdotti dal
regolamento, si è deciso di valutare e adottare una soluzione di Data Loss Prevention (DLP) per la protezione
dei dati aziendali non strutturati.

Le soluzioni di DLP valutate si compongono di due macro elementi:
• Data Classification: processi e strumenti di classificazione dei dati non strutturati che permettano
  l’identificazione del livello di riservatezza di un file;
• Data Protection: processi e tecnologie di monitoraggio e protezione che permettano di identificate come
  il dato viene utilizzato all’interno del contesto aziendale e prevenire eventuali utilizzi non autorizzati del dato
  stesso

Il candidato si affiancherà al gruppo di lavoro e potrà effettuare un’analisi delle tematiche e problematiche
tecniche/tecnologiche/sistemistiche legate all’introduzione di strumenti di questo tipo all’interno di una realtà
complessa come quella del Gruppo Intesa Sanpaolo. Nell’analisi sarà possibile anche approfondire aspetti
legate all’evoluzione dei processi e all’implementazione delle tecnologie di protezione del dato in ambito
DLP.
31
Reti neurali e Natural Language Processing: ulteriori approcci di Artificial
Intelligence per l’individuazione delle frodi sui servizi online (T)

L’uso di tecniche analitiche avanzate nell’elaborazione in tempo reale delle transazioni bancarie migliora
l’accuratezza nell’individuazione di potenziali frodi (e.g. riduzione falsi positivi) e supporta l’identificazione di
nuove tipologie di frode. L’uso congiunto di framework per Reti Neurali e algoritmi di Natural Language
Processing consentirà di intercettare i più sofisticati schemi di frode.

All’interno dell’attuale infrastruttura Big Data, alimentata in tempo reale dall’operatività di tutti i canali online,
sono in funzione motori analitici che utilizzano tecnologie di DB a grafo e modelli decisionali supervisionati. Si
vogliono ora sperimentare tecniche addizionali di Deep Learning (Reti Neurali) e Natural Language
Processing per raggiungere l’obiettivo di ridurre le frodi effettive non intercettate (obiettivo Zero Based Fraud).

Il candidato, sulla base di un background di conoscenze delle Reti Neurali e delle tecniche algoritmiche NLP,
si confronterà con dati reali, disegnerà il processo elaborativo ed implementerà i motori analitici in questione
utilizzando i linguaggi di programmazione Python e Java nello stack applicativo che comprende
Kafka/Spark/Cloudera su ambiente di Continuous Integration and Continuous Delivery (CI/CD) OpenShift.
32

Deception e la tecnologia dell'Inganno (T)

Le piattaforme di inganno distribuite (DDP) sono soluzioni che creano veri e propri insiemi di sistemi fasulli
(ovvero non realmente parte degli oggetti critici del sistema informativo), atti ad attrarre e fuorviare
l'aggressore a falsificare le risorse oggetto di attacco. Lo scopo di questi sistemi è migliorare le capacità di
detection e ritardare le azioni di hacking mentre è in corso l’attacco alle risorse create ad hoc a scopo di
inganno.

La tesi prevede l’analisi e la verifica in campo delle principali piattaforme di inganno distribuite disponibili sul
mercato tramite la definizione e l’implementazione di specifici casi d’uso.
Attraverso l’analisi dei casi d’uso sarà possibile individuare sia i limiti di questa tipologia di soluzioni sia i rischi
legati all’adozione di queste piattaforme nei vari scenari d’attacco e delle strategie ultime ottimali nell’utilizzo
di tali tecnologie.
FINE / THE END

                 33
You can also read