Information Security of Embedded Systems 10.2.2010: Logics and Proof Methods, Wrap-Up Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer.

Slides:



Advertisements
Similar presentations
Information Security of Embedded Systems : Design of Secure Systems Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
Advertisements

Information Security of Embedded Systems : Embedded Systems Design Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
Software Verification 2 Automated Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität and Fraunhofer Institut für.
OPERATING EFFECTIVELY AT WESD. What is Internal Control? A process designed to provide reasonable assurance the organizations objectives are achieved.
Software Verification 1 Deductive Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität und Fraunhofer Institut.
PROTOCOL VERIFICATION & PROTOCOL VALIDATION. Protocol Verification Communication Protocols should be checked for correctness, robustness and performance,
Information Security of Embedded Systems : Design of Secure Systems Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
SECURITY IN E-COMMERCE VARNA FREE UNIVERSITY Prof. Teodora Bakardjieva.
Lect. 18: Cryptographic Protocols. 2 1.Cryptographic Protocols 2.Special Signatures 3.Secret Sharing and Threshold Cryptography 4.Zero-knowledge Proofs.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
Warm-up: April 11 What’s the difference between a checking and savings account?
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt.
Information Security of Embedded Systems : Foundations of Security II Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
Formal Methods of Systems Specification Logical Specification of Hard- and Software Prof. Dr. Holger Schlingloff Institut für Informatik der.
Software Engineering COMP 201
FIT3105 Smart card based authentication and identity management Lecture 4.
Information Security of Embedded Systems : Public Key Cryptosystems, Communication Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer.
1 SWE Introduction to Software Engineering Lecture 5.
Information Security of Embedded Systems : Communication, wireless remote access Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer.
Information Security of Embedded Systems : remote access, wireless networks Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer.
Information Security of Embedded Systems : Algorithms and Measures Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
Composing Security Policies on Java Cards Michael McDougall with Rajeev Alur and Carl A. Gunter University of Pennsylvania April 26, 2004.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Information Security of Embedded Systems : BAN-Logic Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST.
Electronic Commerce. On-line ordering---an e-commerce application On-line ordering assumes that: A company publishes its catalog on the Internet; Customers.
The University of California Strengthening Business Practices: The Language of Our Control Environment Dan Sampson Assistant Vice President Financial Services.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
Programming Satan’s Computer
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Electronic Payment Systems. How do we make an electronic payment? Credit and debit cards Smart cards Electronic cash (digital cash) Electronic wallets.
General Key Management Guidance. Key Management Policy  Governs the lifecycle for the keying material  Hope to minimize additional required documentation.
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Verification 2 Automated Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität and Fraunhofer Institut für.
Software Verification 2 Automated Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität and Fraunhofer Institut für.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Clemente-Cuervo et al. A PDA Implementation of an Off-line e-Cash Protocol.
Software Verification 1 Deductive Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität und Fraunhofer Institut.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
Project co-funded by the European Commission within the 7th Framework Program (Grant Agreement No ) Business Convergence WS#2 Smart Grid Technologies.
Software Verification 1 Deductive Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität und Fraunhofer Institut.
CS Data Structures I Chapter 2 Principles of Programming & Software Engineering.
Major Disciplines in Computer Science Ken Nguyen Department of Information Technology Clayton State University.
CS453: Introduction to Information Security for E-Commerce Prof. Tom Horton.
Network Security Lecture 27 Presented by: Dr. Munam Ali Shah.
Software Verification 2 Automated Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität and Fraunhofer Institut für.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
From Hoare Logic to Matching Logic Reachability Grigore Rosu and Andrei Stefanescu University of Illinois, USA.
HACNet Simulation-based Validation of Security Protocols Vinay Venkataraghavan Advisors: S.Nair, P.-M. Seidel HACNet Lab Computer Science and Engineering.
PROGRAMMING PRE- AND POSTCONDITIONS, INVARIANTS AND METHOD CONTRACTS B MODULE 2: SOFTWARE SYSTEMS 13 NOVEMBER 2013.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
Software Verification 1 Deductive Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität und Fraunhofer Institut.
Software Verification 1 Deductive Verification Prof. Dr. Holger Schlingloff Institut für Informatik der Humboldt Universität und Fraunhofer.
Electronic Banking & Security Electronic Banking & Security.
SS 2017 Software Verification Bounded Model Checking, Outlook
SS 2017 Software Verification Software Model Checking 2 - Parallelism
SS 2018 Software Verification LTL Satisfiability applied
Software Verification 2 Automated Verification
Presentation transcript:

Information Security of Embedded Systems : Logics and Proof Methods, Wrap-Up Prof. Dr. Holger Schlingloff Institut für Informatik und Fraunhofer FIRST

Embedded Security © Prof. Dr. H. Schlingloff Structure 1. Introductory example 2. Embedded systems engineering 1.definitions and terms 2.design principles 3. Foundations of security 1.threats, attacks, measures 2.construction of safe systems 4. Design of secure systems 1.design challenges 2.safety modelling and assessment 3.cryptographic algorithms 5. Communication of embedded systems 1.remote access 2.sensor networks 6. Algorithms and measures 1.digital signatures 2.key management 3.authentication 4.authorization 7. Formal methods for security 1.protocol verification 2.logics and proof methods 8. Wrap-Up

Embedded Security © Prof. Dr. H. Schlingloff Integrated Security Design Systematic consideration of security goals  Requirements, specifications, models, code, test suites Model-based design  system model refined to implementation model  assertions as logical formulas  automated code generation  particularly well-suited for embedded systems Modelling formalisms  UML  Matlab/Simulink/Stateflow  automata

Embedded Security © Prof. Dr. H. Schlingloff Example: Security Policies Lit.: M. McDougall, R. Alur, C. Gunter: A Model-Based Approach to Integrating Security Policies for Embedded Devices  Security policies  Programmable payment cards  Policy automata, defeasible logic  Model checking and code generation

Embedded Security © Prof. Dr. H. Schlingloff Security Policies Goal: restrict permission to certain transactions  e.g. money withdrawal only if account positive Stateful: result of a request may depend on previous decisions  e.g. the amount withdrawn during the current day Various stakeholders may impose different policies  e.g. employer: withdrawal only on business trips  e.g. parent: withdrawal only up to certain amount Non-monotonic: new policy may override previous policy  e.g. withdrawal always possible for “good customers” Problem: conflicting policies? Problem: correct implementation of policy?

Embedded Security © Prof. Dr. H. Schlingloff Programmable Payment Cards Authorization of transactions according to a policy ROM, EEPROM on card, can be programmed (Java) After being issued card allows to add policies but not to remove them Policies provide boolean result, transaction is allowed iff approved by each of the policies

Embedded Security © Prof. Dr. H. Schlingloff Defeasible Logic non-monotonic logic  new axioms not necessarily increase theory  efficient proof/disproval method -> Strict rule  always (necessarily) valid (cf. modal logic!)  (penguin -> ¬fly) “penguins don’t fly” => Defeasible rule  usually valid, but can be preempted by other information  (bird => fly) “birds can fly unless we have some reason to think otherwise” ~> Defeater rule  block the tentative conclusions of defeasible rules  (injured ~> ¬fly) will block the above rule ⊢yes, ⊬ ¬ yes  approval; ⊬ yes  disapproval; ⊢yes, ⊢ ¬ yes  conflict

Embedded Security © Prof. Dr. H. Schlingloff Policy Automata Given T: transactions (e.g. ), D: votes (rules of defeasible logic) policy automaton A=(M, X, q 0, R, δ)  M: modes, X: variables, Q: states; q 0 : initial state  R: rules; R: Q x T  D  δ: transitions; δ: Q x T x {yes, no}  Q Policy model = set of policy automata  automata proceed simultaneously  depending on the approval outcome the “yes” or “no” transition is traversed  in case of conflict an error state is assumed

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy P 3 : Allow up to 3 purchases per day P E : Guarantee payment to emergency services twice P cc : A cash card: spend no more than $500 total P N : No alcohol can be purchased P t : Prevent purchases of prescription drugs which conflict with the anti-depressant Tofranil

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy (1) P 3 : Allow up to 3 purchases per day

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy (2) P E : Guarantee payment to emergency services twice

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy (3) P cc : A cash card: spend no more than $500 total

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy (4) P N : No alcohol can be purchased

Embedded Security © Prof. Dr. H. Schlingloff Example: a Payment Card Policy (5) P t : Prevent purchases of prescription drugs which conflict with the anti-depressant Tofranil

Embedded Security © Prof. Dr. H. Schlingloff Complete Model

Embedded Security © Prof. Dr. H. Schlingloff Analysis of Policy Models The following properties can be verified  reachability  conflict-freeness  redundancy of a policy Code generation is possible  translation of automata into Java card applets  adding of applets to a pre-configured card  defeasible logic engine in runtime environment Tool “Polaris”  graphical editor, analysis engine, code generator

Embedded Security © Prof. Dr. H. Schlingloff Wrap-Up: What we have learned… Systematics of security  throughout the system’s functionality  throughout the system’s design  throughout the system’s operation Assess security goals, take measures  measures must be adapted to possibilities  measures may change over time Security for embedded needs special care  processing, energy, design challenges  mass-market, price, non-revocability, … Social processes and consequences

Embedded Security © Prof. Dr. H. Schlingloff Further Topics Attacks on different levels  HW tampering, modifications  side channels Security testing  verification on all levels impossible  test case selection intrinsically hard Future: Intentious systems  autonomous agents  self-organizing systems Many things to research!

Embedded Security © Prof. Dr. H. Schlingloff Organizational Matters mündliche Prüfungen => Frau Heene  Prüfungen bitte noch in 2010! Bescheinigungen etc. => Mit ausgefülltem Formular direkt bei mir weitere Kurse  SS 2010: Grundlagen der Programmierung  WS 2010/11: Modellbasierte Entwicklung Schöne Semesterferien !!!