techreport_parrend.bib

@techreport{indust2009,
  abstract = {Die Industrialisierung der Software-Entwicklung ist ein zur Zeit sehr stark diskutiertes Thema. Es geht dabei vor allem um die Efizienzsteigerung durch die Steigerung des Standardisierungsgrades, des Automatisierungsgrades sowie eine Erh\"{o}hung der Arbeitsteilung. Dies wirkt sich einerseits auf die den Software- Systemen zu Grunde liegenden Architekturen, aber auch auf die Entwicklungsprozesse aus. So sind Service-orientierte Architekturen ein Beispiel f\"{u}r eine gesteigerte Standardisierung innerhalb von Software-Systemen. Es ist zu ber\"{u}cksichtigen, dass sich die Software-Branche von den klassischen produzierenden Industriezweigen dadurch unterscheidet, dass Software ein immaterielles Produkt ist und so ohne hohe Produktionskosten beliebig oft vervielf\"{a}ltigt werden kann. Trotzdem lassen sich viele Erkenntnisse aus den klassischen Industriezweigen auf die Software-Technik \"{u}bertragen. Die Inhalte dieses Berichts stammen haupts\"{a}chlich aus dem Seminar " Software- Industrialisierung\, welches sich mit der Professionalisierung der Software- Entwi- cklung und des Software-Entwurfs besch\"{a}ftigte. W\"{a}hrend die klassische Software-Entwicklung wenig strukturiert ist und weder im Bezug auf Reproduzierbarkeit oder Qualit\"{a}tssicherung erh\"{o}hten Anforderungen gen\"{u}gt, befindet sich die Software-Entwick- lung im Rahmen der Industrialisierung in einemWandel. Dazu z\"{a}hlen arbeitsteiliges Arbeiten, die Einf\"{u}hrung von Entwicklungsprozessen mit vorhersagbaren Eigenschaften (Kosten, Zeitbedarf, ...), und in der Folge die Erstellung von Produkten mit garantierbaren Eigenschaften. Das Themenspektrum des Seminars umfasste dabei unter anderem: * Komponentenbasierte Software-Architekturen * Modellgetriebene Softwareentwicklung: Konzepte und Technologien * Industrielle Softwareentwicklungsprozesse und deren Bewertung Das Seminar wurde wie eine wissenschaftliche Konferenz organisiert: Die Einreichungen wurden in einem zweistufigen Peer-Review-Verfahren begutachtet. In der ersten Stufe wurde eine Begutachtung der studentischen Arbeiten durch Kommilitonen durchgef\"{u}hrt, in der zweiten Stufe eine Begutachtung durch die Betreuer. In verschiedenen Sessions wurden die Artikel wie bei einer Konferenz pr\"{a}sentiert. Die besten Beitr\"{a}ge wurden durch zwei Best Paper Awards ausgezeichnet. Diese gingen an Tom Beyer f\"{u}r seine Arbeit Realoptionen f\"{u}r Entscheidungen in der Software-Entwicklung, sowie an Philipp Meier f\"{u}r seine Arbeit Assessment Methods for Software Product Lines. Erg\"{a}nzt wurden die Vortr\"{a}ge der Seminarteilnehmer durch zwei eingeladene Vortr\"{a}ge: Collin Rogowski von der 1&1 Internet AG stellte den agilen Softwareentwicklungsprozess beim Mail-Produkt GMX.COM vor. Heiko Koziolek, Wolfgang Mahnke und Michaela Saeftel von ABB referierten \"{u}ber das Thema Software Product Line Engineering anhand der bei ABB entwickelten Robotik-Applikationen.},
  address = {Karlsruhe},
  author = {Brosch, Franz and Groenda, Henning and Kapova, Lucia and Krogmann, Klaus and Kuperberg, Michael and Martens, Anne and Parrend, Pierre and Reussner, Ralf and Stammel, Johannes and Taspolatoglu, Emre},
  edition = {ISSN 1432-7864},
  institution = {Fakult{\"a}t f{\"u}r Informatik, Universit{\"a}t Karlsruhe},
  note = {Interner Bericht},
  publisher = {Fakult{\"a}t f{\"u}r Informatik, Institut f{\"u}r Programmstrukturen und Datenorganisation},
  timestamp = {2009.06.29},
  title = {Software-Industrialisierung},
  url = {http://digbib.ubka.uni-karlsruhe.de/volltexte/1000010899},
  volume = {4},
  year = {2009}
}
@techreport{godary04validation,
  abstract = {In the automotive domain, the X-by-wire systems are dedicated to critical and real-time applications. These systems have specific needs that must be ful- filled, in particular in the reliability domain. Fault-tolerant architectures have been designed to fit with these requirements : TTA, FlexRay or TTCAN. This paper presents a methodology of temporal validation, and illustrates it for the validation of TTA and TTCAN services. This validation provides some temporal bounds, that can be used for the comparison of these architectures.},
  author = {Karen Godary and Pierre Parrend and Isabelle Auge-Blum},
  file = {godary04timetriggered.pdf:http\://www.rzo.free.fr/publis/godary04timetriggered.pdf:PDF},
  institution = {CITI Lab, INSA de Lyon},
  timestamp = {2005.11.07},
  title = {Comparison and temporal validation of automotive real-time architectures},
  url = {http://www.rzo.free.fr/godary04timetriggered.php},
  year = {2004}
}
@techreport{parrend04validation,
  abstract = {Cette �tude se situe dans un contexte de fort d�veloppement des applications automobiles bas�es sur l �lectronique, en vue de remplacer certaines pi�ces m�caniques, tels les syst�mes de freinage, de direction. Le protocole le plus utilis� actuellement est CAN, mais il ne suffit pas aux applications n�cessitant un haut degr� de s�curit�. D autres protocoles ont donc �t� d�velopp�s, selon le paradigme Time- Triggered (selon un ordonnancement pr�-d�fini), comme TTA, Flexray. En effet, ce type de protocoles est plus facile � valider. De la rencontre de CAN et des protocoles Time-Triggered est issu TTCAN. C est ce protocole auquel nous allons nous int�resser. Il est indispensable pour un protocole destin� � des applications � haut niveau de s�curit� de disposer d un validation formelle. Nous allons �tudier son comportement temporel � l aide de l outil UPPAAL, qui permet l analyse, � l aide d une m�thode d�velopp�e au CITI. Nous pr�sentons la mod�lisation r�alis�e � fin d analyse, ainsi que les r�sultats obtenus. Ces donn�es nous permettent une comparaison syst�matique avec le protocole TTA, ce qui offre une mise en perspective critique des deux protocoles.},
  author = {Pierre Parrend and Isabelle Auge-Blum},
  file = {parrend04TTCAN.pdf:http\://www.rzo.free.fr/publis/parrend04TTCAN.pdf:PDF},
  institution = {CITI Lab, INSA de Lyon},
  month = {July},
  number = {RR200},
  title = {Validation temporelle d'architectures embarquees pour l'automobile},
  url = {http://www.rzo.free.fr/parrend04ttcan.php},
  year = {2004}
}
@techreport{Parrend2008bundleVulnerabilities,
  abstract = {Extensible Component Platforms can discover and install code during runtime. Although this feature introduces flexibility, it also brings new security threats: malicious components can quite easily be installed and exploit the rich programming environment and interactions with other components to perform attacks against the system. One example of such environments is the Java/OSGi Platform, which widespreads in the industrial world. Attacks from one component against another can not be prevented through conventional security mechanisms, since they exploit the lack of proper isolation between them: components often share classes and objects. This reports intends to list the vulnerabilities that a component can contain, both from the literature and from our own experience. The Vulnerable Bundle catalog gathers this knowledge. It provides informations related to the characteristics of the vulnerabilities, their consequence, the security mechanisms that would help prevent their exploitation, as well as to the implementation state of the proof-of-concept bundles that are developed to prove that the vulnerability is actually exploitable. The objective of vulnerability classification is of course to provide tools for identifying and preventing them. A first assessment is performed with existing tools, such as Java Permission and FindBugs, and a specific prototype we develop, WBA ( Weak Bundle Analysis), and manual code review.},
  author = {Pierre Parrend and St\'{e}phane Fr\'{e}not},
  file = {RR-6649.pdf&docid=322138:http\://hal.inria.fr/action/open_file.php?url=http\://hal.inria.fr/docs/00/32/21/38/PDF/RR-6649.pdf&docid=322138:PDF},
  institution = {INRIA},
  keywords = {Software Security, Vulnerability Benchmarking, Code Static Analysis, Java Language, Component Platforms, OSGi},
  month = {September},
  number = {RR-6649},
  timestamp = {2008.04.14},
  title = {More Vulnerabilities in the {J}ava/{OSGi} Platform: A Focus on Bundle Interactions},
  url = {http://www.rzo.free.fr/parrend08rr6649.php},
  year = {2008}
}
@techreport{Parrend2007osgiVulnerabilities,
  abstract = {The OSGi Platform finds a growing interest in two different applications domains: embedded systems, and applications servers. However, the security properties of this platform are hardly studied, which is likely to hinder its use in production systems. This is all the more important that the dynamic aspect of OSGi-based applications, that can be extended at runtime, make them vulnerable to malicious code injection. We therefore perform a systematic audit of the OSGi platform so as to build a vulnerability catalog that intends to reference OSGi Vulnerabilities originating in the Core Specification, and in behaviors related to the use of the Java language. Standard Services are not considered. To support this audit, a Semi-formal Vulnerability Pattern is defined, that enables to uniquely characterize fundamental properties for each vulnerability, to include verbose description in the pattern, to reference known security protections, and to track the implementation status of the proof-of-concept OSGi Bundles that exploit the vulnerability. Based on the analysis of the catalog, a robust OSGi Platform is built, and recommendations are made to enhance the OSGi Specifications.},
  author = {Pierre Parrend and St\'{e}phane Fr\'{e}not},
  file = {RR-6231.pdf&docid=165712:http\://hal.inria.fr/action/open_file.php?url=http\://hal.inria.fr/docs/00/16/57/12/PDF/RR-6231.pdf&docid=165712:PDF},
  institution = {INRIA},
  keywords = {OSGi(tm), Security, Dependability, Java, Hardened Execution Platform, Vulnerability Catalog.},
  month = {June},
  number = {RR-6231},
  pages = {84 p.},
  title = {{J}ava Components Vulnerabilities - An Experimental Classification Targeted at the {OSGi} Platform},
  type = {Research Report},
  url = {http://www.rzo.free.fr/parrend07OSGivulnerabilities.php},
  year = {2007}
}
@techreport{parrend06deployment,
  abstract = {Last years have seen a dramatic increase in the use of component platforms, not only in classical application servers, but also more and more in the domain of Embedded Systems. The OSGi(tm) platform is one of these platforms dedicated to lightweight execution environments, and one of the most prominent. However, new platforms also imply new security flaws, and a lack of both knowledge and tools for protecting the exposed systems.> This technical report aims at fostering the understanding of security mechanisms in component deployment. It focuses on securing the deployment of components. It presents the cryptographic mechanisms necessary for signing OSGi(tm) bundles, as well as the detailed process of bundle signature and validation. We also present the SFelix platform, which is a secure extension to Felix OSGi(tm) framework implementation. It includes our implementation of the bundle signature process, as specified by OSGi(tm) Release 4 Security Layer. Moreover, a tool for signing and publishing bundles, SFelix JarSigner, has been developed to conveniently integrate bundle signature in the bundle deployment process.},
  author = {Pierre Parrend and St\'{e}phane Fr\'{e}not},
  file = {RT-0323.pdf&docid=86234:http\://hal.inria.fr/action/open_file.php?url=http\://hal.inria.fr/docs/00/08/62/34/PDF/RT-0323.pdf&docid=86234:PDF},
  institution = {INRIA},
  keywords = {OSGi(tm), Security, Integrity, Authentication, Jar Signature, Digital Signature, Felix},
  month = {June},
  number = {RT-0323},
  title = {Secure Component Deployment in the {OSGi}\texttrademark Release 4 Platform},
  url = {http://www.rzo.free.fr/parrend06deployment.php},
  year = {2006}
}