Assisting in Secure Application Development and Testing Loukmen Regainia

Total Page:16

File Type:pdf, Size:1020Kb

Assisting in Secure Application Development and Testing Loukmen Regainia Assisting in secure application development and testing Loukmen Regainia To cite this version: Loukmen Regainia. Assisting in secure application development and testing. Cryptography and Se- curity [cs.CR]. Université Clermont Auvergne, 2018. English. NNT : 2018CLFAC018. tel-01959245 HAL Id: tel-01959245 https://tel.archives-ouvertes.fr/tel-01959245 Submitted on 18 Dec 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. UNIVERSITE CLERMONT AUVERGNE ECOLE DOCTORALE SCIENCES POUR L’INGENIEUR DE CLERMONT-FERRAND T h è s e Présentée par Loukmen REGAINIA pour obtenir le grade de D O C T E U R D’ U N I V E R S I T É SPECIALITE : INFORMATIQUE Assistance au développement et au test d’applications sécurisées Assisting in secure application development and testing Soutenue publiquement le 12/06/2018 devant le jury : Pr. Ana Rosa CAVALLI Rapporteur et examinateur Pr. Jean-Michel BRUEL Rapporteur et examinateur Pr. Michel MISSON Examinateur Dr. Barbara KORDY Examinateur Dr. Cédric BOUHOURS Encadreur Pr. Sébastien SALVA Directeur de thèse Tous les mots du monde ne sauraient exprimer l’immense amour que je vous porte, ni la profonde gratitude que je vous témoigne pour tous les efforts et les sacrifices que vous n’avez jamais cessé de consentir pour mon instruction et mon bien-être. En ce jour mémorable, pour moi ainsi que pour vous, recevez ce travail en signe de ma vive reconnaissance et mon profond estime. à mes chères parents, à ma tendre épouse, à ma petite Jana et à mes deux frères . Acknowledgements Research supported by the industrial chair on Digital Confidence Recherche prise en charge par la chaire industrielle de confiance numérique http://confiance-numerique.clermontuniversite.fr Remerciements Je voudrais tout d’abord remercier grandement mon directeur de thèse, Sébastien SALVA, pour toute son aide. Je suis ravi d’avoir travaillé en sa compagnie car outre son appui scien- tifique, il a toujours été là pour me soutenir et me conseiller au cours des années dethèse. Je tiens à remercier mon encadrant Cédric BOUHOURS, pour sa proximité, sa disponibilité permanente et pour les nombreux encouragements qu’il m’a prodiguée. Il a été pour moi un mentor dans le monde de l’enseignement et la recherche scientifique. J’adresse tous mes remerciements à Madame Ana Rosa CAVALLI, Professeur à l’institut Mines-Telecom/TELECOM SudParis, ainsi qu’à Monsieur Jean-Michel BRUEL, Professeur à l’Institut de Recherche en Informatique de Toulouse, de l’honneur qu’ils m’ont fait en acceptant d’être rapporteurs de cette thèse. J’exprime ma gratitude à Madame Barbara Kordy, Maître de conférences à l’institut National des Sciences Appliquées de Rennes et à Monsieur Michel MISSON Professeurs à l’Université Clermont-Auvergne, qui ont bien voulu être examinateurs. Il m’est impossible d’oublier toute l’équipe du département informatique: Pascale, François, Chafik, Carine, Laurent, Guenal, Abdel, Nathalie, Isabelle, pour leur accueil et toutes leschoses qu’ils m’ont appris au long de mes premières années d’expérience en enseignement. Je remercie toutes les personnes avec qui j’ai partagé ces années de thèse: Xavier, Hamadoun, Thomas, Pape, David, William, Illiot, Anne, Samir, vi Abstract Assisting in the development and testing of secure applications by Loukmen REGAINIA Ensuring the security of an application through its life cycle is a tedious task. The choice, the implementation and the evaluation of security solutions is difficult and error prone. Security skills are not common in development teams. To overcome the lack of security skills, developers and designers are provided with a plethora of documents about security problems and solutions (i.e, vulnerabilities, attacks, security principles, security patterns, etc.). Abstract and informal, these documents are provided by different sources, and their number is constantly growing. Developers are drown in a sea of documentation, which inhibits their capacity to design, implement, and the evaluate the overall application security. This thesis tackles these issues and presents a set of approaches to help designers in the choice, the implementation and the evaluation of security solutions required to overcome security problems. The problems are materialized by weaknesses, vulnerabilities, attacks, etc. and security solutions are given by security patterns. This thesis first introduces a method to guide designers implement security patterns and assess their effectiveness against vulnerabilities. Then, we present three methods associating security patterns, attacks, weaknesses, etc. in a knowledge base. This allows automated extraction of classifications and help designers quickly and accurately select security patterns required to cure a weakness or to overcome an attack. Based on this knowledge base, we detail a method to help designers in threat modeling and security test generation and execution. The method is evaluated and results show that the method enhances the comprehensibility and the accuracy of developers in the security solutions choice, threat modeling and in the writing of security test cases. Keywords. Security patterns, weaknesses, attacks, principles, life cycle, model checking, security testing. vii Résumé Assistance au développement et au test d’applications sécurisées par Loukmen REGAINIA Garantir la sécurité d’une application tout au long de son cycle de vie est une tâche fastidieuse. Le choix, l’implémentation et l’évaluation des solutions de sécurité est difficile et sujette a des erreurs. De plus, les compétences en sécurité ne sont pas répandues dans toutes les équipes de développement. Pour pallier à ces difficultés, les développeurs ont à leurs dispositions une multitude de documents décrivant des problèmes de sécurité et des solutions requises (vulnérabilités, attaques, principes de sécurité, patrons sécurité, etc.). Ces documents, proposés par des sources hétérogènes, sont souvent abstraits et informels. De plus, leur nombre est en constante croissance. Les développeurs sont noyés dans une multitude de documents ce qui fait obstruction a leur capacité à choisir, implémenter et évaluer la sécurité d’une application. Cette thèse aborde ces problématiques et propose un ensemble de méthodes pour aider les développeurs à choisir, implémenter et évaluer les solutions de sécurité face à des problèmes de sécurité. Ces derniers sont matérialisés par des vulnérabilités, des attaques, etc., et les solutions fournies par des patrons de sécurité. Cette thèse introduit en premier une méthode pour aider les développeurs dans l’instantiation de patrons de sécurité dans un modèle et l’estimation de leurs efficacités face aux vulnérabilités. Puis, elle présente trois méthodes associant patrons de sécurité, vulnérabilités et attaques au sein d’une base de connaissance. Cette dernière permet une extraction automatique de classifications de patrons et améliore la rapidité et la précision des développeurs dans le choix des patrons de sécurité. En utilisant la base de connaissance, nous présentons une méthode pour aider les développeurs dans la modélisation de menaces ainsi que la générations et l’exécution de cas de test de sécurité. L’évaluation de la méthode montre qu’elle améliore l’efficacité, la viii compréhensibilité et la précision des développeurs dans le choix des patrons de sécurité et l’écriture des cas de test de sécurité. Mots-clés. Patrons de sécurité, failles, attaques, principes de sécurité, cycle de vie, vérifica- tion des modèles, test de sécurité. ix Table of contents List of figures xv List of tables xix 1 Introduction1 1.1 General Context . .1 1.2 Open issues . .2 1.3 Contributions . .4 1.4 Overview of the thesis . .5 2 State of the art7 2.1 Introduction . .7 2.2 Security concepts and databases . .8 2.2.1 Weaknesses . .9 2.2.2 Vulnerabilities . .9 2.2.3 Threats . 10 2.2.4 Attacks . 11 2.2.5 Security principles . 11 2.2.6 Security by design . 13 2.3 Patterns . 13 2.3.1 Design patterns . 14 Table of contents 2.3.2 Patterns selection . 16 2.3.3 Patterns instantiation . 18 2.4 Security patterns and Security patterns classifications . 18 2.4.1 Security patterns . 20 2.4.2 Security pattern instantiation . 25 2.4.3 Inter-patterns relationships . 28 2.4.4 Security patterns classifications . 32 2.4.5 Classification schemes . 33 2.4.6 Classification quality criteria . 35 2.5 Security modeling . 37 2.5.1 Vulnerability Cause Graphs (VCG) . 37 2.5.2 Security Activity Graphs (SAG) . 40 2.5.3 Attack Defense Trees ADTree . 42 2.6 Chapter conclusions . 45 3 Assisting Designers in Security Pattern Integration 47 3.1 Introduction . 47 3.2 Context and Motivations . 48 3.3 Prerequisites . 50 3.4 Assisting designers in the security pattern instantiation . 52 3.5 Case study . 59 3.6 Discussion . 69 3.7 Chapter Conclusions . 72 4 Security analysis with patterns and pattern classifications 75 4.1 Introduction . 75 4.2 Context and motivations . 76 xii Table of contents 4.3 Data-stores architectures . 78 4.3.1 Data sources . 78 4.3.2 Data-stores Meta-models . 79 4.4 Data integration . 82 4.4.1 Integrating security patterns and security principles . 84 4.4.2 Integrating security patterns and weaknesses . 87 4.4.3 Attacks and security patterns integration (v1)............. 90 4.4.4 Attacks and security patterns integration (v2)............. 92 4.5 Classification extraction and SAG/ADTree generation . 96 4.5.1 Weakness Security Patterns Classification (WSPC) . 96 4.5.2 Security Activity Graph (SAGs) generation . 98 4.5.3 Attacks and Security Patterns Classification (v1)..........
Recommended publications
  • A Survey of Architectural Styles.V4
    Survey of Architectural Styles Alexander Bird, Bianca Esguerra, Jack Li Liu, Vergil Marana, Jack Kha Nguyen, Neil Oluwagbeminiyi Okikiolu, Navid Pourmantaz Department of Software Engineering University of Calgary Calgary, Canada Abstract— In software engineering, an architectural style is a and implementation; the capabilities and experience of highest-level description of an accepted solution to a common developers; and the infrastructure and organizational software problem. This paper describes and compares a selection constraints [30]. These styles are not presented as out-of-the- of nine accepted architectural styles selected by the authors and box solutions, but rather a framework within which a specific applicable in various domains. Each pattern is presented in a software design may be made. If one were to say “that cannot general sense and with a domain example, and then evaluated in be called a layered architecture because the such and such a terms of benefits and drawbacks. Then, the styles are compared layer must communicate with an object other than the layer in a condensed table of advantages and disadvantages which is above and below it” then one would have missed the point of useful both as a summary of the architectural styles as well as a architectural styles and design patterns. They are not intended tool for selecting a style to apply to a particular project. The to be definitive and final, but rather suggestive and a starting paper is written to accomplish the following purposes: (1) to give readers a general sense of several architectural styles and when point, not to be used as a rule book but rather a source of and when not to apply them, (2) to facilitate software system inspiration.
    [Show full text]
  • Diplomarbeit Im Fachbereich Elektrotechnik & Informatik an Der
    Bachelor Thesis Prannoy Mulmi Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Fakultät Technik und Informatik Faculty of Engineering and Computer Science Department Informations- und Department of Information and Elektrotechnik Electrical Engineering Prannoy Mulmi Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Bachelor Thesis based on the study regulations for the Bachelor of Engineering degree programme Information Engineering at the Department of Information and Electrical Engineering of the Faculty of Engineering and Computer Science of the Hamburg University of Applied Sciences Supervising examiner : Prof. Dr. rer. nat. Henning Dierks Second Examiner : Prof. Dr. rer. nat. Thomas Clemen Day of delivery 23. Juli 2018 Prannoy Mulmi Title of the Bachelor Thesis Design and Implementation of an Archive Microservice solution for the Multi-Agent Research and Simulation Distributed System Keywords Distributed System, Microservice, Two-Phase commit protocol, Archive, Decentrali- zed data, Multi-Agent Research and Simulation (MARS) Abstract This thesis introduces the design and implementation of an Archive Microservice in the Multi-Agent Research and Simulation (MARS) framework. Due to the distributed architecture of the system, the process of the archive and restore is complex to imple- ment and maintain as there multiple possibilities of failure. This thesis uses different strategies to
    [Show full text]
  • Methods & Tools
    METHODS & TOOLS Practical knowledge for the software developer, tester and project manager ISSN 1661-402X Spring 2011 (Volume 19 - number 1) www.methodsandtools.com The Salesmen/Developers Ratio at Software Vendors Many of us might think that software is a technological industry. Maybe. But maybe not. If you consider Oracle or Microsoft, I suppose that few of us would consider them as technology leaders, but we will all recognize their financial strength and marketing power. Long lasting organizations in the software industry might have more financial strength than technological capabilities. The recent conflict between Oracle and the creator of Hudson, an open source continuous integration server, is just another episode in the opposition between developers- and salesmen-driven software companies. On one side you have Oracle, for which Hudson is just small project inherited from the Sun buyout and that owns the "Hudson" brand. On the other side, you find Kohsuke Kawaguchi, who created Hudson and wants keep some control on its development. Hudson has been "forked", the open source code being used to start another project. You now have a Jenkins CI project that includes most of the active Hudson contributors and a Hudson CI project backed by Oracle and Sonatype, the commercial company behind the Maven project. Everything is however not black and white. Kohsuke Kawaguchi has joined Cloudbees, a company that has some management and financing coming from ex-JBoss managers, people that know how to make money with open source software. These people are not working hard for the only sake of technology evolution. You can judge the main orientation of a company looking at its salesmen/developers ratios.
    [Show full text]
  • Mutable Class Design Pattern Nikolay Malitsky Nova Southeastern University, [email protected]
    Nova Southeastern University NSUWorks CEC Theses and Dissertations College of Engineering and Computing 2016 Mutable Class Design Pattern Nikolay Malitsky Nova Southeastern University, [email protected] This document is a product of extensive research conducted at the Nova Southeastern University College of Engineering and Computing. For more information on research and degree programs at the NSU College of Engineering and Computing, please click here. Follow this and additional works at: https://nsuworks.nova.edu/gscis_etd Part of the Other Computer Sciences Commons, and the Theory and Algorithms Commons Share Feedback About This Item NSUWorks Citation Nikolay Malitsky. 2016. Mutable Class Design Pattern. Doctoral dissertation. Nova Southeastern University. Retrieved from NSUWorks, College of Engineering and Computing. (956) https://nsuworks.nova.edu/gscis_etd/956. This Dissertation is brought to you by the College of Engineering and Computing at NSUWorks. It has been accepted for inclusion in CEC Theses and Dissertations by an authorized administrator of NSUWorks. For more information, please contact [email protected]. Mutable Class Design Pattern by Nikolay Malitsky A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science Graduate School of Computer and Information Sciences Nova Southeastern University 2016 We hereby certify that this dissertation, submitted by Nikolay Malitsky, conforms to acceptable standards and is fully adequate in scope and quality to fulfill the dissertation requirements for the degree of Doctor of Philosophy. _____________________________________________ ________________ Michael J. Laszlo, Ph.D. Date Chairperson of Dissertation Committee _____________________________________________ ________________ Francisco J. Mitropoulos, Ph.D. Date Dissertation Committee Member _____________________________________________ ________________ Amon B.
    [Show full text]
  • Security Pattern Validation and Recognition
    Security-Pattern Recognition and Validation Dissertation Submitted by Michaela Bunke on 12th December 2018 to the Universit¨atBremen Faculty of Mathematics and Computer Science in partial fulfillment of the requirements for the degree of Doktor der Ingenieurwissenschaften { Dr.-Ing. { Reviewed by Prof. Dr. Hans-J¨orgKreowski Universit¨atBremen, Germany and Dr. Karsten Sohr Universit¨atBremen, Germany In Memorial of Ilse Schlamilch Karl Schlamilch Manfred Friedrichs 21 November 1924 03 March 1927 29 August 1935 09 June 2017 19 June 2018 3 July 2017 ABSTRACT The increasing and diverse number of technologies that are connected to the Internet, such as distributed enterprise systems or small electronic devices like smartphones, brings the topic IT security to the foreground. We interact daily with these technologies and spend much trust on a well-established software development process. However, security vulnerabilities appear in software on all kinds of PC(- like) platforms, and more and more vulnerabilities are published, which compromise systems and their users. Thus, software has also to be modified due to changing requirements, bugs, and security flaws and software engineers must more and more face security issues during the software design; especially maintenance programmers must deal with such use cases after a software has been released. In the domain of software development, design patterns have been proposed as the best-known solutions for recurring problems in software design. Analogously, security patterns are best practices aiming at ensuring security. This thesis develops a deeper understanding of the nature of security patterns. It focuses on their validation and detection regarding the support of reviews and maintenance activities.
    [Show full text]
  • A CASE STUDY by Siegfried Steiner ([email protected])
    BIG DATA PROCESSING THE LEAN WAY – A CASE STUDY by Siegfried Steiner ([email protected]) 19/08/14 – 17/01/21 2 Content 1.Preface.............................................................................................................3 2.Abstract...........................................................................................................3 3.The mission.....................................................................................................4 4.Terminology.....................................................................................................5 5.Constraints......................................................................................................6 6.Approach.........................................................................................................7 7.Technology stack.............................................................................................8 8.Development process....................................................................................10 Excursus: Scrum.....................................................................................10 Excursus: Test-driven development........................................................11 9.Into the cloud: Scalability..............................................................................12 Excursus: IPO Model...............................................................................13 1.Input - Receive requests (and process output)..........................................14 Excursus: Front
    [Show full text]
  • Architectural Styles and Patterns
    Architectural Styles and Patterns Wednesday 13 February 13 Architectural Patterns & Styles Consensus Controversy • Established • Philosophy (context- Solutions problem-solution vs components- Common • connections) vocabulary Granularity (vs Document • • Design patterns) Reason over quality • • Categorization Wednesday 13 February 13 Architectural Patterns (Wikipedia) • Presentation- abstraction- • Peer-to-peer control • Service-oriented • Three-tier architecture • Pipeline • Naked Objects Implicit Invocation • Model-View • Controller • Blackboard Wednesday 13 February 13 Architectural Patterns (Shaw & Garland) • Dataflow Systems -- Batch, Pipes and Filters • Call-and-return systems -- Main program and subroutines, OO systems, Hierarchical Layers • Independent components -- Communicating processes, Event systems • Virtual Machines -- Interpreters, Rule-based systems • Data-Centered Systems -- Databases, Hypertext systems Blackboards Wednesday 13 February 13 Elements of Architecture (Shaw & Garland) Components Connectors • Clients • Procedure calls • Servers • Events broadcast • Filters • Database protocols • Layers • Pipes • Databases - What are the structural patterns permitted? - What is the underlying computational model? - What are the invariants of the style? BUT ... - What are examples of its use? - What are the tradeoffs? - ... Wednesday 13 February 13 Architectural Patterns (Baas, Clements & Kazman) • Dataflow Systems -- Batch, Pipes and Filters • Data-Centered -- Repository, Blackboard • Virtual machine -- Interpreter, Rule-based
    [Show full text]
  • Microservices Antipatterns and Pitfalls
    Microservices AntiPatterns and Pitfalls Mark Richards Beijing Boston Farnham Sebastopol Tokyo Microservices Antipatterns and Pitfalls by Mark Richards Copyright © 2016 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Brian Foster Interior Designer: David Futato Production Editor: Melanie Yarbrough Cover Designer: Karen Montgomery Copyeditor: Christina Edwards Illustrator: Rebecca Demarest Proofreader: Amanda Kersey July 2016: First Edition Revision History for the First Edition 2016-07-06: First Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Microservices AntiPatterns and Pitfalls, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the author have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the author disclaim all responsibility for errors or omissions, including without limi‐ tation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsi‐ bility to ensure that your use thereof complies with such licenses and/or rights.
    [Show full text]
  • Conceptual Architecture Patterns
    HASSO - PLATTNER - INSTITUT für Softwaresystemtechnik an der Universität Potsdam Conceptual Architecture Patterns Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam 2 Conceptual Architecture Patterns: FMC-based Representations Bernhard Gröne and Frank Keller (eds.) April 2004 Bibliografische Information Der Deutschen Bibliothek Die Deutsche Bibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.ddb.de abrufbar. Die Reihe Technische Berichte des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam erscheint aperiodisch. Herausgeber: Professoren des Hasso-Plattner-Instituts für Softwaresystemtechnik an der Universität Potsdam Redaktion Bernhard Gröne und Frank Keller EMail {bernhard.groene, frank.keller}@hpi.uni-potsdam.de Vertrieb: Universitätsverlag Potsdam Postfach 60 15 53 14415 Potsdam Fon +49 (0) 331 977 4517 Fax +49 (0) 331 977 4625 e-mail: [email protected] http://info.ub.uni-potsdam.de/verlag.htm Druck allprintmedia gmbH Blomberger Weg 6a 13437 Berlin email: [email protected] © Hasso-Plattner-Institut für Softwaresystemtechnik an der Universität Potsdam, 2004 Dieses Manuskript ist urheberrechtlich geschützt. Es darf ohne vorherige Genehmigung der Herausgeber nicht vervielfältigt werden. Heft 2 (2004) ISBN 3-935024-98-3 ISSN 1613-5652 Conceptual Architecture Patterns: FMC–based Representations Bernhard Gröne and Frank Keller (editors) Research assistants of the chair “Modeling of Software–intensive Systems” Hasso–Plattner–Institute for Software Systems Engineering P.O. Box 900460, 14440 Potsdam, Germany E-mail: {bernhard.groene, frank.keller}@hpi.uni-potsdam.de Abstract This document presents the results of the seminar “Conceptual Architecture Patterns” of the winter term 2002 in the Hasso–Plattner–Institute.
    [Show full text]
  • Middleware Architecture with Patterns and Frameworks
    Middleware Architecture with Patterns and Frameworks Sacha Krakowiak Distributed under a Creative Commons license http://creativecommons.org/licenses/by-nc-nd/3.0/ February 27, 2009 Contents Preface ix References........................................ x 1 An Introduction to Middleware 1-1 1.1 Motivation for Middleware . 1-1 1.2 CategoriesofMiddleware . 1-6 1.3 A Simple Instance of Middleware: Remote Procedure Call . ......... 1-7 1.3.1 Motivations and Requirements . 1-8 1.3.2 Implementation Principles . 1-9 1.3.3 Developing Applications with RPC . 1-11 1.3.4 SummaryandConclusions. .1-13 1.4 Issues and Challenges in Middleware Design . 1-14 1.4.1 DesignIssues ...............................1-14 1.4.2 Architectural Guidelines . 1-15 1.4.3 Challenges ................................1-17 1.5 HistoricalNote .................................. 1-18 References........................................1-19 2 Middleware Principles and Basic Patterns 2-1 2.1 ServicesandInterfaces . 2-1 2.1.1 Basic Interaction Mechanisms . 2-2 2.1.2 Interfaces ................................. 2-3 2.1.3 Contracts and Interface Conformance . 2-5 2.2 ArchitecturalPatterns . 2-9 2.2.1 Multilevel Architectures . 2-9 2.2.2 DistributedObjects . .. .. .. .. .. .. .. .2-12 2.3 Patterns for Distributed Object Middleware . 2-15 2.3.1 Proxy ...................................2-15 2.3.2 Factory ..................................2-16 2.3.3 Adapter..................................2-18 2.3.4 Interceptor ................................2-19 2.3.5 Comparing and Combining Patterns . 2-20 2.4 Achieving Adaptability and Separation of Concerns . ..........2-21 2.4.1 Meta-ObjectProtocols. 2-21 2.4.2 Aspect-Oriented Programming . 2-23 ii CONTENTS 2.4.3 PragmaticApproaches. .2-25 2.4.4 ComparingApproaches .
    [Show full text]
  • Adaptivity of Business Process
    ICONS 2013 : The Eighth International Conference on Systems Adaptivity of Business Process Charif Mahmoudi Fabrice Mourlin Laboratory of Algorithms, Complexity and Logics, Laboratory of Algorithms, Complexity and Logics, Paris 12th University Paris 12th University Créteil, France Creteil, France [email protected] [email protected] Abstract— Enterprise service bus is a software architecture local services is less costly in a number of messages than a middleware used for implementing the interaction between business process using remote services. Blockings are also software applications in a Service Oriented Architecture. We less numerous, and, therefore, the execution of a business have developed a strategy to dynamically manage business process is more efficient. processes. Administrators of service bus need to reconfigure This remark highlights the dependencies between two sites where the business processes are placed. This evolution concepts, the location of business processes and its own has to be done during execution of service through the bus. We definition. The designer should not consider his work in the ensure the availability of process definition. Moreover, placement constraints. In addition, the administrator cannot business process can also be autonomous. This means a process take into account all the dependencies of a process definition which is able to move from one site to another one, where the to find a better placement. Also, our second point is: how business process engine is installed. This provides another approach to design business process. With our "mobile process separate the two. These conclusions led us to consider an migration" template, we separate two concerns, on one side initial configuration of business processes is not satisfactory.
    [Show full text]
  • 623 a Abfangen Temporärer Fehler, 479 Abgesicherter
    Index A allow_url_fopen, 510 allow_url_include, 510 Abfangen temporärer Fehler, 479 Amazon.com, 409 abgesicherter monolithischer Kernel, 135 Ambient Authority, 99, 107, 158, 416, 446 ablaufbasierte Kontrolle, 104 Ambige Interfaces, 476 Abschalten von Javascript, 503 Analysis/Paralysis Pattern, 553 Absichern von Application-Servern, 347 Anfangs- bzw. Endspanne, 571 Absicherung der Ressourcen, 350 Angriffe Absicherung der Verbindungen, 349 Klassifikation, 12 Absicherung von Servern, 169 Angriffsformen Abwehr auf der Netzwerkschicht, 39 lokale, 15 Access Control Context, 95, 203, 214 Anreicherung von Privilegien, 152 Access Control Lists, 108, 118 Antipattern, 99, 473 Access Control Markup Language, 197 API in Form paarweiser Methoden, 509 Access Control Matrix, 564 Append-Only-Recht, 152 Access Control Policies, 195 Application Integration in Acegi, 295 SSO-Infrastruktur, 285 ACL, 108, 118, 291 Application Level Security, 262 Beispiel, 119 Application Server Malware, 119 LTPA, 335 Solitaire, 119 Application Server Security, 313 Active Object, 470 Application Tower, 230 Add-Ons, 445 Application-Server, 330 Administration, 174 Architektur, 318 Administrationsfunktion, 288 Authorisierungscode in der „after the fact“-Sicherheitsmechanismen, Applikation, 329 417 Beispielarchitektur, 320 AJAX, 69 Classloader, 325 Java Script Object Notation, 75 Concurrency, 316 On-Demand JavaScript, 74 Credentials für den Zugriff auf Techniken, 72 Backends, 329 XMLHttpRequest, 72 CSIv2, 318 aktionsintegrierte Sicherheit, 554 Delegation mit Neuerzeugung Alias-Antipattern,
    [Show full text]