Formalizing an Adaptive Security Infrastructure in Mob adtl Laura Semini & Carlo Montangero dip. Informatica, Pisa Outline Mob adtl instance ASI Mob adtl.

Slides:



Advertisements
Similar presentations
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
Advertisements

Workpackage 2: Norms
Open Provenance Model Tutorial Session 2: OPM Overview and Semantics Luc Moreau University of Southampton.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
VIDE als voortzetting van Cocktail SET Seminar 11 september 2008 Dr. ir. Michael Franssen.
Towards a Logic for Wide-Area Internet Routing Nick Feamster and Hari Balakrishnan M.I.T. Computer Science and Artificial Intelligence Laboratory Kunal.
OASIS Reference Model for Service Oriented Architecture 1.0
A. Bucchiarone / Pisa/ 30 Jan 2007 Dynamic Software Architectures for Global Computing Antonio Bucchiarone PhD Student – IMT Graduate School Piazza S.
Object-Oriented Analysis and Design
Adding Organizations and Roles as Primitives to the JADE Framework NORMAS’08 Normative Multi Agent Systems, Matteo Baldoni 1, Valerio Genovese 1, Roberto.
An Application-led Approach for Security-related Research in Ubicomp Philip Robinson TecO, Karlsruhe University 11 May 2005.
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
1 Formal Models for Distributed Negotiations Description Roberto Bruni Dipartimento di Informatica Università di Pisa XVII Escuela de Ciencias Informaticas.
1 Building with Assurance CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute May 10, 2004.
1 Static vs dynamic SAGAs Ivan Lanese Computer Science Department University of Bologna/INRIA Italy.
1 Ivan Lanese Computer Science Department University of Bologna Italy Concurrent and located synchronizations in π-calculus.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
A Klaim specification of the Handover protocol: logic-based and type-based analysis Michele Loreti and Daniele Gorla Dipartimento di Sistemi e Informatica.
Course Instructor: Aisha Azeem
4.4 Naming And Directory Services Lakshmi Narayana Gupta Kollepara 09/20/2009 CSC-8320.
Secure Systems Research Group - FAU Web Services Standards Presented by Keiko Hashizume.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Cheng/Dillon-Software Engineering: Formal Methods Model Checking.
Towards a Logic for Wide- Area Internet Routing Nick Feamster Hari Balakrishnan.
Architecting Secure Mobile P2P Systems James Walkerdine, Peter Phillips, Simon Lock Lancaster University.
Introduction to MDA (Model Driven Architecture) CYT.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Benjamin Gamble. What is Time?  Can mean many different things to a computer Dynamic Equation Variable System State 2.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Proof Carrying Code Zhiwei Lin. Outline Proof-Carrying Code The Design and Implementation of a Certifying Compiler A Proof – Carrying Code Architecture.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Component frameworks Roy Kensmil. Historical trens in software development. ABSTRACT INTERACTIONS COMPONENT BUS COMPONENT GLUE THIRD-PARTY BINDING.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Lecture 7: Requirements Engineering
Formal Verification Lecture 9. Formal Verification Formal verification relies on Descriptions of the properties or requirements Descriptions of systems.
Class 5 Architecture-Based Self-Healing Systems David Garlan Carnegie Mellon University.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Introduction to WOLFASI: Workshop on Logical Foundations of an Adaptive Security Infrastructure Leo Marcus The Aerospace Corporation Los Angeles July 13,
On the Role of Abstract Platform in Model Driven Development* Marten van Sinderen Centre for Telematics and Information Technology, University of Twente,
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Chapter 2 Database System Concepts and Architecture Dr. Bernard Chen Ph.D. University of Central Arkansas.
SKOS. Ontologies Metadata –Resources marked-up with descriptions of their content. No good unless everyone speaks the same language; Terminologies –Provide.
1 Chapter 1 – Background Computer Security T/ Tyseer Alsamany - Computer Security.
Topic 1 – Introduction Huiqun Yu Information Security Principles & Applications.
A Software Framework for Distributed Services Michael M. McKerns and Michael A.G. Aivazis California Institute of Technology, Pasadena, CA Introduction.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Enabling Components Management and Dynamic Execution Semantic.
Distributed Models for Decision Support Jose Cuena & Sascha Ossowski Pesented by: Gal Moshitch & Rica Gonen.
Multiagent System Katia P. Sycara 일반대학원 GE 랩 성연식.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Lecture 13.  Failure mode: when team understands requirements but is unable to meet them.  To ensure that you are building the right system Continually.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Π-AAL: An Architecture Analysis Language for Formally Specifying and Verifying Structural and Behavioral Properties of Software Architectures Presented.
Artificial Intelligence Logical Agents Chapter 7.
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Chapter 2 Database System Concepts and Architecture
Designing Agents’ Behaviors and Interactions within ADELFE
Software Connectors.
IS 2935: Developing Secure Systems
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Formalizing an Adaptive Security Infrastructure in Mob adtl Laura Semini & Carlo Montangero dip. Informatica, Pisa Outline Mob adtl instance ASI Mob adtl formalization refinement ASI formalization

Characteristics of Mob adtl Approach to model distributed systems Focus on architectural aspects Adequate abstraction for overlay computing Accommodating mobility Temporal logic  refinement as a methodology Mechanic support to verification model logic

Mob adtl model: an intuition neighborhood Agent movement message being delivered guardian agent

The ingredients of Mob adtl Locations:  Neighbourhoods, places where computational entities live  Flat topology  Security and routing policies Agents:  Move from neighbourhood to neighbourhood  Communicate via asynchronous message passing Authorities:  Guardians monitoring agents’ activities enacting routing and security policies  No a priori choice about routing and security, freedom is given to designers Profiles:  A means to refer an entity specifying the constraints the entity must satisfy es: flightResService, name(X)

A first-order multi-modal logic to  Name components and state their properties  Relate properties of different components of a system  Describe properties of the evolution of systems  With regard to an asynchronous setting The formalism: ΔDSTL(x) Location Time

Formalizing the model: an example out(M,P) represents the will of an agent of sending a messagge M to a receiver that satisfies profile P. S (  out(M,P)  guardedby(G)) LEADS_TO G msgReq(M,S,P,i) Any message sent is first processed by the sender’s guardian out(M,P) msgReq(M,S,P,i) S G

Location layer: DSL Modalities to locate properties in the state of a component  m (p  q )  m p  n r  m s  m t (  m (s  t) !!!!) n m p, q r s t

Location layer – semantics DS =2 S Semantic domain: PowerSet (ds, ds’)  R m iff ds’ is a singleton in S m  ds ds╞ m F iff  ds’.(ds, ds’)  R m and ds’╞ F q r p n m states of m

Location layer Modalities to locate properties in the state of a component  m (p  q )  m p  n r  m s  m t (  m (s  t)) n m p, q r st

Future to be intended as the partial order of states defined by  Intra-components transitions  Inter-component communications Temporal layer: DSTL q m n o p r

q No global clock,no global knowlwdge m n o p r Valid: n q  o r  o r Non valid: n q  o r

UNITY like operators  Simplicity  Cannot be nested  + past operators F1 LEADS_TO F2 F2 BECAUSE F1 INIT F STABLE F

Events: ΔDSTL(x) Explicit event operator, ΔF  Simple events, ΔA  Composed events, Δ(A  B)  Conditioned events, ΔA  B

Rules and theorems

Outline 1. Depict a few, simple and clearly related concepts: an informal model 2. Choose a proper formalism 3. Formalize the model to get the description of a generic system 4. Instantiate the model to get the description of a particular system 5. Refine the model formalization

ASI Components in Mob adtl Detectorguardian Analyzeragent Responderguardian senses, collects, and distributes information about the security environment processes Detector data, and occasionally proposes actions to bring about a new state executes the actions as directed by the Analyzer

generic neighborhoods Analyzer ASI Components in Mob adtl Detector & Responder Detector & Responder generic agents Detector & Responder log

The threshold property agents can question the trustworthiness of a guardian. once the number of warnings reaches a given threshold, we want to consider the guardian no longer trustworthy (e.g. to route the messages).

threshold(2) generic agent Analyzer The threshold property out(demote(X,D),{sec_w}) out(demote(X,D’),{sec_w}) Detector in(demote(X,D),S) Detector in(demote(X,D’),S’)

threshold(2) Analyzer The threshold property in(demote(X,D),S) in(demote(X,D’),S’)

The threshold property Analyzer Responder out(demote(X,D),{adapt})

The threshold property ~ trusted (X) Analyzer Responders Responder Responders

The threshold property a threshold(2) /\ ag trusted(G) /\ C1  C2 C1  out(demote(X,D),{sec_w}) /\ C2  out(demote(X,D’),{sec_w}) LEADS_TO G ~ trusted (X) \/ some communication exc because of unreachablility

Conclusions ASI components: Mob adtl concepts play a central role  guardian  detection ane response  profile  adaptation ASI formalization: how should the semantics of a dynamic security policy be specified?  unify the temporal-spatial reasoning aspects  take into account the global-local (or distributed-centralized or hierarchical) nature of all components of an ASI Proof with MaRK (Mob adtl Reasoning Kit)

A support tool: MaRK MaRK = Mob adtl Reasoning Kit: a tool to support the designer while proving properties of Mob adtl systems The goal: to make the proof task as automatic as possible MaRK is based on the theorem prover Isabelle (Paulson & Nipkow)  Specialized for ΔDSTL(x)  Extended to deal with Mob adtl systems

A support tool: MaRK Why theorem proving  Need to deal with infinite states  Learning from the proof process itself  User defined logic, close to user’s knowledge  Third party checkable proofs Against:  not so automatic, often to interactive, insights on internals of provers needed But:  tactics, libraries of proofs, tailoring to a particular domain make theorem provers more usable