Istlab - User contributions [en]

FP7 Call 5

2009-09-11T11:20:16Z

Louridas:

Publication date 30/07/2009, deadline 26/10/2009.

== Material ==
* [http://cordis.europa.eu/fp7/ict/ssai/objectives-1-2_en.html Objectives 1.2.: Internet of Services, Software and Virtualisation]
* [http://www.slideshare.net/azwegers/20090327-csmr-kaiserslautern-1217914 Arian Zwegers CMSR talk]

== Partners ==
* [http://www.sig.nl Software Improvement Group] NL
* [http://www.kdab.net KDAB] D/SE
* [http://seal.ifi.uzh.ch/ SEAL team] CH, Harald Gall
* [http://www.singularlogic.eu SingularLogic] GR, Pantelopoulos Stelios
* Possibly Sun, waiting response from Stelios Pantelopoulos

== Topic ==

* Make OSS data computable in a way similar to that of WolframAlpha. (Panos) and open SQO-OSS allowing researchers to submit plugins. Use VMs and sandboxing to make this safe to execute. (dds) [[Brief Description]]

FP7 Call 5

2009-09-11T11:18:34Z

Louridas:

Publication date 30/07/2009, deadline 03/11/2009.

== Material ==
* [http://cordis.europa.eu/fp7/ict/ssai/objectives-1-2_en.html Objectives 1.2.: Internet of Services, Software and Virtualisation]
* [http://www.slideshare.net/azwegers/20090327-csmr-kaiserslautern-1217914 Arian Zwegers CMSR talk]

== Partners ==
* [http://www.sig.nl Software Improvement Group] NL
* [http://www.kdab.net KDAB] D/SE
* [http://seal.ifi.uzh.ch/ SEAL team] CH, Harald Gall
* [http://www.singularlogic.eu SingularLogic] GR, Pantelopoulos Stelios
* Possibly Sun, waiting response from Stelios Pantelopoulos

== Topic ==

* Make OSS data computable in a way similar to that of WolframAlpha. (Panos) and open SQO-OSS allowing researchers to submit plugins. Use VMs and sandboxing to make this safe to execute. (dds) [[Brief Description]]

Brief Description

2009-06-25T18:05:46Z

Louridas:

Our goal is to provide a tool that will enable other researchers and
practitioners to conduct Software Engineering research and practice in
a far more innovative and efficient way. To do what, we want to make
Open Source Software (OSS) computable.

There is a very large (and growing) amount of OSS on the web right
now. This software can be used for all kinds of empirical analyses,
quality assessments, testing of hypotheses on Software Engineering
theories and methods. This potential is hampered by two factors:

* Although OSS code is available, those wishing to analyse it have to download the code from the primary repository; then they typically have to write code that analyses it, for instance by computing some metrics on it; and then they have to run it.

* The above steps are usually repeated as often as somebody else wants to analyse the same piece of software. That is, a metric calculator for a certain OSS project is not usually available (or known) to other people wishing to do research on the same project. One may wonder how different wc implementations for different OSS projects have been written the last few years.

Moreover, people developing metric measuring tools are often the same
people who will use the metrics. This is not necessary. We propose to
separate the two concerns: having the ability to ask questions on a
piece of software is an enabler for research and innovation on
Software Engineering. We also want to go one step further: asking
questions should be so easy that researchers should be able to do it
interactively in an exploratory manner.

WolframAlpha is an interesting example of what can be achieved by
making information executable. In the same vein, we want to make
Software Engineering knowledge, taken from OSS repositories,
executable. Researchers should be able to ask questions like:

* What is the metric X for project P?

* How does metric X for project P correlate with metric Y for project P?

* How does metric X for project P correlate with metric Y for project P?

* Where does metric X in project P exceed value V?

and so on.

To make such a tool meaningful, the set of metrics that could be
calculated should be open-ended. In fact, the tool should be developed
in such a way that interested researchers could easily create their
own metrics and offer them to the tool, so that the set of metrics
offered by the tool will be increasing with the number of people using
and contributing to it. At the same time, the execution of contributed
metrics should take into account security issues. Virtual machines and
sandboxing should be employed to make them safe to execute.

Brief Description

2009-06-25T14:21:00Z

Louridas: New page: One page description to be written here.

One page description to be written here.

FP7 Call 5

2009-06-25T14:17:18Z

Louridas: /* Preliminary topics */

Publication date 30/07/2009, deadline 03/11/2009.

== Material ==
* [http://www.slideshare.net/azwegers/20090327-csmr-kaiserslautern-1217914 Arian Zwegers CMSR talk]

== Candidate partners ==
* [http://www.sig.nl Software Improvement Group] NL
* [http://www.frontendart.com/about_us.php FrontEndART Software Ltd.] HU

== Preliminary topics ==
According to Zwegers' presentation and based on a discussion he had afterward with Giannis Kanellopoulos, the following issues are relevant to software quality:
*Issues with very large, dynamic, open service networks:*
** From design-time to run-time.
** Quality of open systems without fixed boundaries.
** Opportunities with open source software and service engineering.
* Ways to address these issues: Highly Innovative Service / Software Engineering*
** Service / Software engineering methods and tools.
** Verification and validation methods, tools and techniques.
** Methods, tools and approaches specifically supporting the development, deployment and evolution of open source platforms.

Neat ideas (not sure where they fit)
* Make OSS data computable in a way similar to that of WolframAlpha. (Panos) and open SQO-OSS allowing researchers to submit plugins. Use VMs and sandboxing to make this safe to execute. (dds) [[Brief Description]]

FP7 Call 5

2009-06-25T14:12:38Z

Louridas: /* Preliminary topics */

FP7 Call 5

2009-06-25T14:09:50Z

Louridas: /* Preliminary topics */

FP7: Capacities

2008-07-01T10:41:11Z

Louridas: /* TODO */

== Summary ==
OSSLab aims to provide a laboratory where researchers will be able to run large-scale studies on the source code of thousands of real-world software systems and the data of the processes used to build them. Many important results in software engineering have come from empirical studies. Yet the difficulty of setting up realistic experiments often results in studies of a small number of high-profile systems or toy-problems programmed by students. This need not be so. The open source software movement has provided us with a goldmine of thousands of software systems whose code and process data are freely available. Studying these systems is easy in theory, but difficult in practice, as their data is scattered around in various repositories, formats, databases, and applications. Based on work performed in the highly-successful IST project Software Quality Observatory for Open Source Software (SQO-OSS) we propose to gather code and process data in an open virtual laboratory, OSSLab. Researchers will be able to use OSSLab by uploading their programs related to the studies they want to perform, execute them on the laboratory’s huge data assets, and download and share the corresponding results. OSSLab will serve not only the software engineering community, but also the increasing number of researchers from other disciplines, like sociology, economics, management science, and psychology, who utilize in their studies empirical data from open source software projects.

The main tasks associated with setting up OSSLab include the gathering and normalization of the data, the creation of an infrastructure that will allow researchers to run their code while taking into account fair resource allocation and security, facilities for sharing the data and building on each others results, and pilot studies demonstrating the utility of OSSLab to a wide scientific community.

== TODO ==
* Write to Pires
* Gather partners
** Korfiatis? Constantiou?
* Get LoS from IDABC
* Write proposal

== Call information ==
* [http://cordis.europa.eu/fp7/dc/index.cfm?fuseaction=usersite.FP7DetailsCallPage&CALL_ID=122 FP7-INFRASTRUCTURES-2008-2: Call documents]
* [http://cordis.europa.eu/fp7/ict/e-infrastructure/events-20080418_en.html Information Event on the fourth Call for proposals under the e-Infrastructures Activity of the 'Capacities' Specific Programme, FP7]
* [http://cordis.europa.eu/fp7/ict/e-infrastructure/networking_en.html Networking Sessions of the FP7 'Capacities' Information Events]
* Contact person: [http://cordis.europa.eu/ist/rn/ri-cnd/whoswho.htm Carlos Morais Pires]

== Partners ==
* AUEB
* GRNET
* [http://www.sig.nl/ SIG]
* SINTEF - confirmed
* [http://www.kdab.net KDAB] - confirmed

FP7: Capacities

2008-07-01T10:40:13Z

Louridas: /* Partners */

== Summary ==
OSSLab aims to provide a laboratory where researchers will be able to run large-scale studies on the source code of thousands of real-world software systems and the data of the processes used to build them. Many important results in software engineering have come from empirical studies. Yet the difficulty of setting up realistic experiments often results in studies of a small number of high-profile systems or toy-problems programmed by students. This need not be so. The open source software movement has provided us with a goldmine of thousands of software systems whose code and process data are freely available. Studying these systems is easy in theory, but difficult in practice, as their data is scattered around in various repositories, formats, databases, and applications. Based on work performed in the highly-successful IST project Software Quality Observatory for Open Source Software (SQO-OSS) we propose to gather code and process data in an open virtual laboratory, OSSLab. Researchers will be able to use OSSLab by uploading their programs related to the studies they want to perform, execute them on the laboratory’s huge data assets, and download and share the corresponding results. OSSLab will serve not only the software engineering community, but also the increasing number of researchers from other disciplines, like sociology, economics, management science, and psychology, who utilize in their studies empirical data from open source software projects.

The main tasks associated with setting up OSSLab include the gathering and normalization of the data, the creation of an infrastructure that will allow researchers to run their code while taking into account fair resource allocation and security, facilities for sharing the data and building on each others results, and pilot studies demonstrating the utility of OSSLab to a wide scientific community.

== TODO ==
* Write to Pires
* Gather partners
** SINTEF?
** Korfiatis? Constantiou?
* Write proposal

== Call information ==
* [http://cordis.europa.eu/fp7/dc/index.cfm?fuseaction=usersite.FP7DetailsCallPage&CALL_ID=122 FP7-INFRASTRUCTURES-2008-2: Call documents]
* [http://cordis.europa.eu/fp7/ict/e-infrastructure/events-20080418_en.html Information Event on the fourth Call for proposals under the e-Infrastructures Activity of the 'Capacities' Specific Programme, FP7]
* [http://cordis.europa.eu/fp7/ict/e-infrastructure/networking_en.html Networking Sessions of the FP7 'Capacities' Information Events]
* Contact person: [http://cordis.europa.eu/ist/rn/ri-cnd/whoswho.htm Carlos Morais Pires]

== Partners ==
* AUEB
* GRNET
* [http://www.sig.nl/ SIG]
* SINTEF - confirmed
* [http://www.kdab.net KDAB] - confirmed

SENSE book wishlist

2008-05-05T09:29:39Z

Louridas:

*[http://www.amazon.com/Programming-Python-Prentice-Software-Development/dp/0132354187 Rapid GUI Programming with Python and Qt The Definitive Guide to PyQt Programming]

*Karl Fogel [http://www.amazon.co.uk/Producing-Open-Source-Software-Fogel/dp/0596007590/ref=sr_1_1/203-2032591-8741518?ie=UTF8&s=books&qid=1173340467&sr=8-1 Producing Open Source Software]

*John R. Levine [http://www.amazon.co.uk/Linkers-Kaufmann-Software-Engineering-Programming/dp/1558604960/ref=pd_luc_0180305960075901558604960/203-2032591-8741518 Linkers and Loaders]

*Hans Petter Langtangen [http://www.amazon.co.uk/Python-Scripting-Computational-Science-Engineering/dp/3540294155/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173357421&sr=8-1 Python Scripting for Computational Science]

* Benjamin C. Pierce [http://www.amazon.co.uk/Types-Programming-Languages-Benjamin-Pierce/dp/0262162091/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375705&sr=8-1 Types and Programming Languages]

* R.W. Hamming [http://www.amazon.co.uk/Numerical-Methods-Scientists-Engineers-Richard/dp/0486652416/ref=sr_1_2/202-3585720-0642223?ie=UTF8&s=books&qid=1173375899&sr=8-2 Numerical Methods for Scientists and Engineers]

* Henry S. Warren Jr. [http://www.amazon.co.uk/Hackers-Delight-Henry-S-Warren/dp/0201914654/ref=sr_1_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375969&sr=1-1 Hacker's Delight]

* Joel Spolsky. [http://www.amazon.com/Best-Software-Writing-Selected-Introduced/dp/1590595009 The Best Software Writing I]

* Stephen Wilbers. [http://www.amazon.com/Keys-Great-Writing-Stephen-Wilbers/dp/0898799325 Keys to Great Writing]

* Mortimer J. Adler. [http://www.amazon.com/How-Read-Book-Touchstone/dp/0671212095 How to Read a Book]

* Robert Mecklenburg. [http://www.amazon.co.uk/Managing-Projects-Make-Building-Handbooks/dp/0596006101/ Managing Projects with GNU Make]

* Martin Fowler [http://www.amazon.co.uk/Enterprise-Application-Architecture-Addison-Wesley-Signature/dp/0321127420/ Patterns of Enterprise Application Architecture]

* Andres Andreu [http://www.amazon.com/Professional-Pen-Testing-Applications-Programmer/dp/0471789666/ref=pd_sim_b_1/103-9938800-8237415?ie=UTF8&qid=1170769149&sr=1-1 Professional Pen Testing for Web Applications (Programmer to Programmer)]

* Mark G. Graff [http://www.amazon.com/gp/product/0596002424 Secure Coding: Principles and Practices]

* Joel Scambray [http://www.amazon.com/Hacking-Exposed-Web-Applications-Second/dp/0072262990/sr=1-1/qid=1171651524?ie=UTF8&s=books Hacking Exposed Windows, 2nd Ed. (Hacking Exposed)]

* Seth Fogie [http://www.amazon.com/Cross-Site-Scripting-Attacks-Exploits/dp/1597491543/sr=1-1/qid=1170769149?ie=UTF8&s=books Cross Site Scripting Attacks: Xss Exploits and Defense ]

* Kate L. Turabian [http://www.amazon.co.uk/Manual-Writers-Research-Papers-Dissertations/dp/0226823377/ref=sr_1_1/026-8892653-7930013?ie=UTF8&s=books&qid=1184508531&sr=8-1 A Manual for Writers of Research Papers, Theses, and Dissertations]

* William Strunk Jr. and E.B.White [http://www.amazon.co.uk/Elements-Style-William-I-Strunk/dp/020530902X/ref=pd_sim_b_5/026-8892653-7930013?ie=UTF8&qid=1184508531&sr=8-1 The Elements of Style]

* Ronald L. Graham, Donald E. Knuth and Oren Patashnik [http://www.amazon.co.uk/Concrete-Mathematics-Foundation-Computer-Science/dp/0201558025/ref=pd_bbs_sr_1/026-8892653-7930013?ie=UTF8&s=books&qid=1185030033&sr=8-1 Concrete Mathematics: A Foundation for computer science]

* Tom DeMarco and Timothy Lister [http://www.amazon.co.uk/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439/ref=pd_bbs_sr_1/202-6651186-7291039?ie=UTF8&s=books&qid=1187972200&sr=8-1 Peopleware: Productive Projects and Teams]

* Adobe Systems Incorporated [http://www.amazon.co.uk/Postscript-Language-Reference-CD-ROM-Systems/dp/0201379228/ref=sr_1_2/202-6651186-7291039?ie=UTF8&s=books&qid=1187972791&sr=1-2 PostScript Language Reference 3rd edition]

* George W. Snedecor and William G. Cochran [http://www.amazon.com/Statistical-Methods-George-W-Snedecor/dp/0813815614/ref=sr_1_1/002-8692953-8561655?ie=UTF8&s=books&qid=1191253322&sr=1-1 Statistical Methods]

* Scott Berkun [http://www.amazon.com/Myths-Innovation-Scott-Berkun/dp/0596527055 Myths of Innovation]

* John Viega and Gary McGraw [http://www.amazon.com/exec/obidos/ASIN/020172152X Building Secure Software: How to Avoid Security Problems the Right Way]

* Gary McGraw [http://www.amazon.com/Software-Security-Building-Addison-Wesley/dp/0321356705/ref=pd_sim_b_2 Software Security: Building Security In]

* Dorothy Elizabeth Robling Denning [http://www.amazon.com/exec/obidos/ASIN/0201101505 Cryptography and Data Security]

* Donald A. Norman [http://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_2?ie=UTF8&s=books&qid=1209977401&sr=8-2 The Design of Everyday Things]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Display-Quantitative-Information/dp/0961392142/ref=sr_1_1?ie=UTF8&s=books&qid=1209977565&sr=1-1 The Visual Display of Quantitative Information]

* Edward R. Tufte [http://www.amazon.co.uk/Envisioning-Information-Edward-R-Tufte/dp/0961392118/ref=sr_1_2?ie=UTF8&s=books&qid=1209977710&sr=1-2 Envisioning Information]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Visual Explanations: Images and Quantities, Evidence and Narrative]

* Edward R. Tufte [http://www.amazon.co.uk/Beautiful-Evidence-Edward-R-Tufte/dp/0961392177/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Beautiful Evidence ]

* Robert L. Glass [http://www.amazon.co.uk/Facts-Fallacies-Software-Engineering-Development/dp/0321117425/ref=sr_1_1?ie=UTF8&s=books&qid=1209977897&sr=1-1 Facts and Fallacies of Software Engineering ]

* Steve Krug [http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1209978195&sr=8-1 Don't Make Me Think]

* Richard J. Larsen, Morris L. Marx [http://www.amazon.co.uk/Introduction-Mathematical-Statistics-Its-Applications/dp/0132018136/ref=sr_1_2?ie=UTF8&s=books&qid=1209978238&sr=1-2 An Introduction to Mathematical Statistics and Its Applications]

* Terry Winograd, C.F. Flores [http://www.amazon.co.uk/Understanding-Computers-Cognition-Foundation-Language/dp/0893910503/ref=sr_1_10?ie=UTF8&s=books&qid=1209978295&sr=1-10 Understanding Computers and Cognition: A New Foundation for Design]

* S. Weber [http://www.amazon.co.uk/Success-Open-Source-S-Weber/dp/0674018583/ref=sr_1_1?ie=UTF8&s=books&qid=1209978674&sr=1-1 The Success of Open Source]

* Karl E. Wiegers [http://www.amazon.co.uk/Software-Requirements-Second-Pro-Best-Practices/dp/0735618798/ref=sr_1_1?ie=UTF8&s=books&qid=1209978762&sr=1-1 Software Requirements]

* Sven Birkerts [http://www.amazon.co.uk/Gutenberg-Elegies-Fate-Reading-Electronic/dp/0865479577/ref=sr_1_1?ie=UTF8&s=books&qid=1209979722&sr=1-1 The Gutenberg Elegies: The Fate of Reading in an Electronic Age]

[[Category:SENSE]]

SENSE book wishlist

2008-05-05T09:21:55Z

Louridas:

SENSE book wishlist

2008-05-05T09:12:14Z

Louridas:

SENSE book wishlist

2008-05-05T09:10:27Z

Louridas:

SENSE book wishlist

2008-05-05T09:10:05Z

Louridas:

*[http://www.amazon.com/Programming-Python-Prentice-Software-Development/dp/0132354187 Rapid GUI Programming with Python and Qt The Definitive Guide to PyQt Programming]

*Karl Fogel [http://www.amazon.co.uk/Producing-Open-Source-Software-Fogel/dp/0596007590/ref=sr_1_1/203-2032591-8741518?ie=UTF8&s=books&qid=1173340467&sr=8-1 Producing Open Source Software]

*John R. Levine [http://www.amazon.co.uk/Linkers-Kaufmann-Software-Engineering-Programming/dp/1558604960/ref=pd_luc_0180305960075901558604960/203-2032591-8741518 Linkers and Loaders]

*Hans Petter Langtangen [http://www.amazon.co.uk/Python-Scripting-Computational-Science-Engineering/dp/3540294155/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173357421&sr=8-1 Python Scripting for Computational Science]

* Benjamin C. Pierce [http://www.amazon.co.uk/Types-Programming-Languages-Benjamin-Pierce/dp/0262162091/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375705&sr=8-1 Types and Programming Languages]

* R.W. Hamming [http://www.amazon.co.uk/Numerical-Methods-Scientists-Engineers-Richard/dp/0486652416/ref=sr_1_2/202-3585720-0642223?ie=UTF8&s=books&qid=1173375899&sr=8-2 Numerical Methods for Scientists and Engineers]

* Henry S. Warren Jr. [http://www.amazon.co.uk/Hackers-Delight-Henry-S-Warren/dp/0201914654/ref=sr_1_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375969&sr=1-1 Hacker's Delight]

* Joel Spolsky. [http://www.amazon.com/Best-Software-Writing-Selected-Introduced/dp/1590595009 The Best Software Writing I]

* Stephen Wilbers. [http://www.amazon.com/Keys-Great-Writing-Stephen-Wilbers/dp/0898799325 Keys to Great Writing]

* Mortimer J. Adler. [http://www.amazon.com/How-Read-Book-Touchstone/dp/0671212095 How to Read a Book]

* Robert Mecklenburg. [http://www.amazon.co.uk/Managing-Projects-Make-Building-Handbooks/dp/0596006101/ Managing Projects with GNU Make]

* Martin Fowler [http://www.amazon.co.uk/Enterprise-Application-Architecture-Addison-Wesley-Signature/dp/0321127420/ Patterns of Enterprise Application Architecture]

* Andres Andreu [http://www.amazon.com/Professional-Pen-Testing-Applications-Programmer/dp/0471789666/ref=pd_sim_b_1/103-9938800-8237415?ie=UTF8&qid=1170769149&sr=1-1 Professional Pen Testing for Web Applications (Programmer to Programmer)]

* Mark G. Graff [http://www.amazon.com/gp/product/0596002424 Secure Coding: Principles and Practices]

* Joel Scambray [http://www.amazon.com/Hacking-Exposed-Web-Applications-Second/dp/0072262990/sr=1-1/qid=1171651524?ie=UTF8&s=books Hacking Exposed Windows, 2nd Ed. (Hacking Exposed)]

* Seth Fogie [http://www.amazon.com/Cross-Site-Scripting-Attacks-Exploits/dp/1597491543/sr=1-1/qid=1170769149?ie=UTF8&s=books Cross Site Scripting Attacks: Xss Exploits and Defense ]

* Kate L. Turabian [http://www.amazon.co.uk/Manual-Writers-Research-Papers-Dissertations/dp/0226823377/ref=sr_1_1/026-8892653-7930013?ie=UTF8&s=books&qid=1184508531&sr=8-1 A Manual for Writers of Research Papers, Theses, and Dissertations]

* William Strunk Jr. and E.B.White [http://www.amazon.co.uk/Elements-Style-William-I-Strunk/dp/020530902X/ref=pd_sim_b_5/026-8892653-7930013?ie=UTF8&qid=1184508531&sr=8-1 The Elements of Style]

* Ronald L. Graham, Donald E. Knuth and Oren Patashnik [http://www.amazon.co.uk/Concrete-Mathematics-Foundation-Computer-Science/dp/0201558025/ref=pd_bbs_sr_1/026-8892653-7930013?ie=UTF8&s=books&qid=1185030033&sr=8-1 Concrete Mathematics: A Foundation for computer science]

* Tom DeMarco and Timothy Lister [http://www.amazon.co.uk/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439/ref=pd_bbs_sr_1/202-6651186-7291039?ie=UTF8&s=books&qid=1187972200&sr=8-1 Peopleware: Productive Projects and Teams]

* Adobe Systems Incorporated [http://www.amazon.co.uk/Postscript-Language-Reference-CD-ROM-Systems/dp/0201379228/ref=sr_1_2/202-6651186-7291039?ie=UTF8&s=books&qid=1187972791&sr=1-2 PostScript Language Reference 3rd edition]

* George W. Snedecor and William G. Cochran [http://www.amazon.com/Statistical-Methods-George-W-Snedecor/dp/0813815614/ref=sr_1_1/002-8692953-8561655?ie=UTF8&s=books&qid=1191253322&sr=1-1 Statistical Methods]

* Scott Berkun [http://www.amazon.com/Myths-Innovation-Scott-Berkun/dp/0596527055 Myths of Innovation]

* John Viega and Gary McGraw [http://www.amazon.com/exec/obidos/ASIN/020172152X Building Secure Software: How to Avoid Security Problems the Right Way]

* Gary McGraw [http://www.amazon.com/Software-Security-Building-Addison-Wesley/dp/0321356705/ref=pd_sim_b_2 Software Security: Building Security In]

* Dorothy Elizabeth Robling Denning [http://www.amazon.com/exec/obidos/ASIN/0201101505 Cryptography and Data Security]

* Donald A. Norman [http://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_2?ie=UTF8&s=books&qid=1209977401&sr=8-2 The Design of Everyday Things]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Display-Quantitative-Information/dp/0961392142/ref=sr_1_1?ie=UTF8&s=books&qid=1209977565&sr=1-1 The Visual Display of Quantitative Information]

* Edward R. Tufte [http://www.amazon.co.uk/Envisioning-Information-Edward-R-Tufte/dp/0961392118/ref=sr_1_2?ie=UTF8&s=books&qid=1209977710&sr=1-2 Envisioning Information]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Visual Explanations: Images and Quantities, Evidence and Narrative]

* Edward R. Tufte [http://www.amazon.co.uk/Beautiful-Evidence-Edward-R-Tufte/dp/0961392177/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Beautiful Evidence ]

* Robert L. Glass [http://www.amazon.co.uk/Facts-Fallacies-Software-Engineering-Development/dp/0321117425/ref=sr_1_1?ie=UTF8&s=books&qid=1209977897&sr=1-1 Facts and Fallacies of Software Engineering ]

* Steve Krug [http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1209978195&sr=8-1 Don't Make Me Think]

* Richard J. Larsen, Morris L. Marx [ http://www.amazon.co.uk/Introduction-Mathematical-Statistics-Its-Applications/dp/0132018136/ref=sr_1_2?ie=UTF8&s=books&qid=1209978238&sr=1-2 An Introduction to Mathematical Statistics and Its Applications]

* Terry Winograd, C.F. Flores [ http://www.amazon.co.uk/Understanding-Computers-Cognition-Foundation-Language/dp/0893910503/ref=sr_1_10?ie=UTF8&s=books&qid=1209978295&sr=1-10 Understanding Computers and Cognition: A New Foundation for Design]
[[Category:SENSE]]

SENSE book wishlist

2008-05-05T09:09:37Z

Louridas:

*[http://www.amazon.com/Programming-Python-Prentice-Software-Development/dp/0132354187 Rapid GUI Programming with Python and Qt The Definitive Guide to PyQt Programming]

*Karl Fogel [http://www.amazon.co.uk/Producing-Open-Source-Software-Fogel/dp/0596007590/ref=sr_1_1/203-2032591-8741518?ie=UTF8&s=books&qid=1173340467&sr=8-1 Producing Open Source Software]

*John R. Levine [http://www.amazon.co.uk/Linkers-Kaufmann-Software-Engineering-Programming/dp/1558604960/ref=pd_luc_0180305960075901558604960/203-2032591-8741518 Linkers and Loaders]

*Hans Petter Langtangen [http://www.amazon.co.uk/Python-Scripting-Computational-Science-Engineering/dp/3540294155/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173357421&sr=8-1 Python Scripting for Computational Science]

* Benjamin C. Pierce [http://www.amazon.co.uk/Types-Programming-Languages-Benjamin-Pierce/dp/0262162091/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375705&sr=8-1 Types and Programming Languages]

* R.W. Hamming [http://www.amazon.co.uk/Numerical-Methods-Scientists-Engineers-Richard/dp/0486652416/ref=sr_1_2/202-3585720-0642223?ie=UTF8&s=books&qid=1173375899&sr=8-2 Numerical Methods for Scientists and Engineers]

* Henry S. Warren Jr. [http://www.amazon.co.uk/Hackers-Delight-Henry-S-Warren/dp/0201914654/ref=sr_1_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375969&sr=1-1 Hacker's Delight]

* Joel Spolsky. [http://www.amazon.com/Best-Software-Writing-Selected-Introduced/dp/1590595009 The Best Software Writing I]

* Stephen Wilbers. [http://www.amazon.com/Keys-Great-Writing-Stephen-Wilbers/dp/0898799325 Keys to Great Writing]

* Mortimer J. Adler. [http://www.amazon.com/How-Read-Book-Touchstone/dp/0671212095 How to Read a Book]

* Robert Mecklenburg. [http://www.amazon.co.uk/Managing-Projects-Make-Building-Handbooks/dp/0596006101/ Managing Projects with GNU Make]

* Martin Fowler [http://www.amazon.co.uk/Enterprise-Application-Architecture-Addison-Wesley-Signature/dp/0321127420/ Patterns of Enterprise Application Architecture]

* Andres Andreu [http://www.amazon.com/Professional-Pen-Testing-Applications-Programmer/dp/0471789666/ref=pd_sim_b_1/103-9938800-8237415?ie=UTF8&qid=1170769149&sr=1-1 Professional Pen Testing for Web Applications (Programmer to Programmer)]

* Mark G. Graff [http://www.amazon.com/gp/product/0596002424 Secure Coding: Principles and Practices]

* Joel Scambray [http://www.amazon.com/Hacking-Exposed-Web-Applications-Second/dp/0072262990/sr=1-1/qid=1171651524?ie=UTF8&s=books Hacking Exposed Windows, 2nd Ed. (Hacking Exposed)]

* Seth Fogie [http://www.amazon.com/Cross-Site-Scripting-Attacks-Exploits/dp/1597491543/sr=1-1/qid=1170769149?ie=UTF8&s=books Cross Site Scripting Attacks: Xss Exploits and Defense ]

* Kate L. Turabian [http://www.amazon.co.uk/Manual-Writers-Research-Papers-Dissertations/dp/0226823377/ref=sr_1_1/026-8892653-7930013?ie=UTF8&s=books&qid=1184508531&sr=8-1 A Manual for Writers of Research Papers, Theses, and Dissertations]

* William Strunk Jr. and E.B.White [http://www.amazon.co.uk/Elements-Style-William-I-Strunk/dp/020530902X/ref=pd_sim_b_5/026-8892653-7930013?ie=UTF8&qid=1184508531&sr=8-1 The Elements of Style]

* Ronald L. Graham, Donald E. Knuth and Oren Patashnik [http://www.amazon.co.uk/Concrete-Mathematics-Foundation-Computer-Science/dp/0201558025/ref=pd_bbs_sr_1/026-8892653-7930013?ie=UTF8&s=books&qid=1185030033&sr=8-1 Concrete Mathematics: A Foundation for computer science]

* Tom DeMarco and Timothy Lister [http://www.amazon.co.uk/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439/ref=pd_bbs_sr_1/202-6651186-7291039?ie=UTF8&s=books&qid=1187972200&sr=8-1 Peopleware: Productive Projects and Teams]

* Adobe Systems Incorporated [http://www.amazon.co.uk/Postscript-Language-Reference-CD-ROM-Systems/dp/0201379228/ref=sr_1_2/202-6651186-7291039?ie=UTF8&s=books&qid=1187972791&sr=1-2 PostScript Language Reference 3rd edition]

* George W. Snedecor and William G. Cochran [http://www.amazon.com/Statistical-Methods-George-W-Snedecor/dp/0813815614/ref=sr_1_1/002-8692953-8561655?ie=UTF8&s=books&qid=1191253322&sr=1-1 Statistical Methods]

* Scott Berkun [http://www.amazon.com/Myths-Innovation-Scott-Berkun/dp/0596527055 Myths of Innovation]

* John Viega and Gary McGraw [http://www.amazon.com/exec/obidos/ASIN/020172152X Building Secure Software: How to Avoid Security Problems the Right Way]

* Gary McGraw [http://www.amazon.com/Software-Security-Building-Addison-Wesley/dp/0321356705/ref=pd_sim_b_2 Software Security: Building Security In]

* Dorothy Elizabeth Robling Denning [http://www.amazon.com/exec/obidos/ASIN/0201101505 Cryptography and Data Security]

* Donald A. Norman [http://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_2?ie=UTF8&s=books&qid=1209977401&sr=8-2 The Design of Everyday Things]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Display-Quantitative-Information/dp/0961392142/ref=sr_1_1?ie=UTF8&s=books&qid=1209977565&sr=1-1 The Visual Display of Quantitative Information]

* Edward R. Tufte
[http://www.amazon.co.uk/Envisioning-Information-Edward-R-Tufte/dp/0961392118/ref=sr_1_2?ie=UTF8&s=books&qid=1209977710&sr=1-2 Envisioning Information]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Visual Explanations: Images and Quantities, Evidence and Narrative]

* Edward R. Tufte [http://www.amazon.co.uk/Beautiful-Evidence-Edward-R-Tufte/dp/0961392177/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Beautiful Evidence ]

* Robert L. Glass [http://www.amazon.co.uk/Facts-Fallacies-Software-Engineering-Development/dp/0321117425/ref=sr_1_1?ie=UTF8&s=books&qid=1209977897&sr=1-1 Facts and Fallacies of Software Engineering ]

* Steve Krug [http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1209978195&sr=8-1 Don't Make Me Think]

* Richard J. Larsen, Morris L. Marx [ http://www.amazon.co.uk/Introduction-Mathematical-Statistics-Its-Applications/dp/0132018136/ref=sr_1_2?ie=UTF8&s=books&qid=1209978238&sr=1-2 An Introduction to Mathematical Statistics and Its Applications]

* Terry Winograd, C.F. Flores [ http://www.amazon.co.uk/Understanding-Computers-Cognition-Foundation-Language/dp/0893910503/ref=sr_1_10?ie=UTF8&s=books&qid=1209978295&sr=1-10 Understanding Computers and Cognition: A New Foundation for Design]
[[Category:SENSE]]

SENSE book wishlist

2008-05-05T09:09:08Z

Louridas:

*[http://www.amazon.com/Programming-Python-Prentice-Software-Development/dp/0132354187 Rapid GUI Programming with Python and Qt The Definitive Guide to PyQt Programming]

*Karl Fogel [http://www.amazon.co.uk/Producing-Open-Source-Software-Fogel/dp/0596007590/ref=sr_1_1/203-2032591-8741518?ie=UTF8&s=books&qid=1173340467&sr=8-1 Producing Open Source Software]

*John R. Levine [http://www.amazon.co.uk/Linkers-Kaufmann-Software-Engineering-Programming/dp/1558604960/ref=pd_luc_0180305960075901558604960/203-2032591-8741518 Linkers and Loaders]

*Hans Petter Langtangen [http://www.amazon.co.uk/Python-Scripting-Computational-Science-Engineering/dp/3540294155/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173357421&sr=8-1 Python Scripting for Computational Science]

* Benjamin C. Pierce [http://www.amazon.co.uk/Types-Programming-Languages-Benjamin-Pierce/dp/0262162091/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375705&sr=8-1 Types and Programming Languages]

* R.W. Hamming [http://www.amazon.co.uk/Numerical-Methods-Scientists-Engineers-Richard/dp/0486652416/ref=sr_1_2/202-3585720-0642223?ie=UTF8&s=books&qid=1173375899&sr=8-2 Numerical Methods for Scientists and Engineers]

* Henry S. Warren Jr. [http://www.amazon.co.uk/Hackers-Delight-Henry-S-Warren/dp/0201914654/ref=sr_1_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375969&sr=1-1 Hacker's Delight]

* Joel Spolsky. [http://www.amazon.com/Best-Software-Writing-Selected-Introduced/dp/1590595009 The Best Software Writing I]

* Stephen Wilbers. [http://www.amazon.com/Keys-Great-Writing-Stephen-Wilbers/dp/0898799325 Keys to Great Writing]

* Mortimer J. Adler. [http://www.amazon.com/How-Read-Book-Touchstone/dp/0671212095 How to Read a Book]

* Robert Mecklenburg. [http://www.amazon.co.uk/Managing-Projects-Make-Building-Handbooks/dp/0596006101/ Managing Projects with GNU Make]

* Martin Fowler [http://www.amazon.co.uk/Enterprise-Application-Architecture-Addison-Wesley-Signature/dp/0321127420/ Patterns of Enterprise Application Architecture]

* Andres Andreu [http://www.amazon.com/Professional-Pen-Testing-Applications-Programmer/dp/0471789666/ref=pd_sim_b_1/103-9938800-8237415?ie=UTF8&qid=1170769149&sr=1-1 Professional Pen Testing for Web Applications (Programmer to Programmer)]

* Mark G. Graff [http://www.amazon.com/gp/product/0596002424 Secure Coding: Principles and Practices]

* Joel Scambray [http://www.amazon.com/Hacking-Exposed-Web-Applications-Second/dp/0072262990/sr=1-1/qid=1171651524?ie=UTF8&s=books Hacking Exposed Windows, 2nd Ed. (Hacking Exposed)]

* Seth Fogie [http://www.amazon.com/Cross-Site-Scripting-Attacks-Exploits/dp/1597491543/sr=1-1/qid=1170769149?ie=UTF8&s=books Cross Site Scripting Attacks: Xss Exploits and Defense ]

* Kate L. Turabian [http://www.amazon.co.uk/Manual-Writers-Research-Papers-Dissertations/dp/0226823377/ref=sr_1_1/026-8892653-7930013?ie=UTF8&s=books&qid=1184508531&sr=8-1 A Manual for Writers of Research Papers, Theses, and Dissertations]

* William Strunk Jr. and E.B.White [http://www.amazon.co.uk/Elements-Style-William-I-Strunk/dp/020530902X/ref=pd_sim_b_5/026-8892653-7930013?ie=UTF8&qid=1184508531&sr=8-1 The Elements of Style]

* Ronald L. Graham, Donald E. Knuth and Oren Patashnik [http://www.amazon.co.uk/Concrete-Mathematics-Foundation-Computer-Science/dp/0201558025/ref=pd_bbs_sr_1/026-8892653-7930013?ie=UTF8&s=books&qid=1185030033&sr=8-1 Concrete Mathematics: A Foundation for computer science]

* Tom DeMarco and Timothy Lister [http://www.amazon.co.uk/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439/ref=pd_bbs_sr_1/202-6651186-7291039?ie=UTF8&s=books&qid=1187972200&sr=8-1 Peopleware: Productive Projects and Teams]

* Adobe Systems Incorporated [http://www.amazon.co.uk/Postscript-Language-Reference-CD-ROM-Systems/dp/0201379228/ref=sr_1_2/202-6651186-7291039?ie=UTF8&s=books&qid=1187972791&sr=1-2 PostScript Language Reference 3rd edition]

* George W. Snedecor and William G. Cochran [http://www.amazon.com/Statistical-Methods-George-W-Snedecor/dp/0813815614/ref=sr_1_1/002-8692953-8561655?ie=UTF8&s=books&qid=1191253322&sr=1-1 Statistical Methods]

* Scott Berkun [http://www.amazon.com/Myths-Innovation-Scott-Berkun/dp/0596527055 Myths of Innovation]

* John Viega and Gary McGraw [http://www.amazon.com/exec/obidos/ASIN/020172152X Building Secure Software: How to Avoid Security Problems the Right Way]

* Gary McGraw [http://www.amazon.com/Software-Security-Building-Addison-Wesley/dp/0321356705/ref=pd_sim_b_2 Software Security: Building Security In]

* Dorothy Elizabeth Robling Denning [http://www.amazon.com/exec/obidos/ASIN/0201101505 Cryptography and Data Security]

* Donald A. Norman [http://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_2?ie=UTF8&s=books&qid=1209977401&sr=8-2 The Design of Everyday Things]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Display-Quantitative-Information/dp/0961392142/ref=sr_1_1?ie=UTF8&s=books&qid=1209977565&sr=1-1 The Visual Display of Quantitative Information]

* Edward R. Tufte
[http://www.amazon.co.uk/Envisioning-Information-Edward-R-Tufte/dp/0961392118/ref=sr_1_2?ie=UTF8&s=books&qid=1209977710&sr=1-2 Envisioning Information]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Visual Explanations: Images and Quantities, Evidence and Narrative]

* Edward R. Tufte [http://www.amazon.co.uk/Beautiful-Evidence-Edward-R-Tufte/dp/0961392177/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Beautiful Evidence ]

* Robert L. Glass [http://www.amazon.co.uk/Facts-Fallacies-Software-Engineering-Development/dp/0321117425/ref=sr_1_1?ie=UTF8&s=books&qid=1209977897&sr=1-1 Facts and Fallacies of Software Engineering ]

* Steve Krug [ http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1209978195&sr=8-1 Don't Make Me Think]

* Richard J. Larsen, Morris L. Marx [ http://www.amazon.co.uk/Introduction-Mathematical-Statistics-Its-Applications/dp/0132018136/ref=sr_1_2?ie=UTF8&s=books&qid=1209978238&sr=1-2 An Introduction to Mathematical Statistics and Its Applications]

* Terry Winograd, C.F. Flores [ http://www.amazon.co.uk/Understanding-Computers-Cognition-Foundation-Language/dp/0893910503/ref=sr_1_10?ie=UTF8&s=books&qid=1209978295&sr=1-10 Understanding Computers and Cognition: A New Foundation for Design]
[[Category:SENSE]]

SENSE book wishlist

2008-05-05T09:08:21Z

Louridas:

*[http://www.amazon.com/Programming-Python-Prentice-Software-Development/dp/0132354187 Rapid GUI Programming with Python and Qt The Definitive Guide to PyQt Programming]

*Karl Fogel [http://www.amazon.co.uk/Producing-Open-Source-Software-Fogel/dp/0596007590/ref=sr_1_1/203-2032591-8741518?ie=UTF8&s=books&qid=1173340467&sr=8-1 Producing Open Source Software]

*John R. Levine [http://www.amazon.co.uk/Linkers-Kaufmann-Software-Engineering-Programming/dp/1558604960/ref=pd_luc_0180305960075901558604960/203-2032591-8741518 Linkers and Loaders]

*Hans Petter Langtangen [http://www.amazon.co.uk/Python-Scripting-Computational-Science-Engineering/dp/3540294155/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173357421&sr=8-1 Python Scripting for Computational Science]

* Benjamin C. Pierce [http://www.amazon.co.uk/Types-Programming-Languages-Benjamin-Pierce/dp/0262162091/ref=pd_ka_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375705&sr=8-1 Types and Programming Languages]

* R.W. Hamming [http://www.amazon.co.uk/Numerical-Methods-Scientists-Engineers-Richard/dp/0486652416/ref=sr_1_2/202-3585720-0642223?ie=UTF8&s=books&qid=1173375899&sr=8-2 Numerical Methods for Scientists and Engineers]

* Henry S. Warren Jr. [http://www.amazon.co.uk/Hackers-Delight-Henry-S-Warren/dp/0201914654/ref=sr_1_1/202-3585720-0642223?ie=UTF8&s=books&qid=1173375969&sr=1-1 Hacker's Delight]

* Joel Spolsky. [http://www.amazon.com/Best-Software-Writing-Selected-Introduced/dp/1590595009 The Best Software Writing I]

* Stephen Wilbers. [http://www.amazon.com/Keys-Great-Writing-Stephen-Wilbers/dp/0898799325 Keys to Great Writing]

* Mortimer J. Adler. [http://www.amazon.com/How-Read-Book-Touchstone/dp/0671212095 How to Read a Book]

* Robert Mecklenburg. [http://www.amazon.co.uk/Managing-Projects-Make-Building-Handbooks/dp/0596006101/ Managing Projects with GNU Make]

* Martin Fowler [http://www.amazon.co.uk/Enterprise-Application-Architecture-Addison-Wesley-Signature/dp/0321127420/ Patterns of Enterprise Application Architecture]

* Andres Andreu [http://www.amazon.com/Professional-Pen-Testing-Applications-Programmer/dp/0471789666/ref=pd_sim_b_1/103-9938800-8237415?ie=UTF8&qid=1170769149&sr=1-1 Professional Pen Testing for Web Applications (Programmer to Programmer)]

* Mark G. Graff [http://www.amazon.com/gp/product/0596002424 Secure Coding: Principles and Practices]

* Joel Scambray [http://www.amazon.com/Hacking-Exposed-Web-Applications-Second/dp/0072262990/sr=1-1/qid=1171651524?ie=UTF8&s=books Hacking Exposed Windows, 2nd Ed. (Hacking Exposed)]

* Seth Fogie [http://www.amazon.com/Cross-Site-Scripting-Attacks-Exploits/dp/1597491543/sr=1-1/qid=1170769149?ie=UTF8&s=books Cross Site Scripting Attacks: Xss Exploits and Defense ]

* Kate L. Turabian [http://www.amazon.co.uk/Manual-Writers-Research-Papers-Dissertations/dp/0226823377/ref=sr_1_1/026-8892653-7930013?ie=UTF8&s=books&qid=1184508531&sr=8-1 A Manual for Writers of Research Papers, Theses, and Dissertations]

* William Strunk Jr. and E.B.White [http://www.amazon.co.uk/Elements-Style-William-I-Strunk/dp/020530902X/ref=pd_sim_b_5/026-8892653-7930013?ie=UTF8&qid=1184508531&sr=8-1 The Elements of Style]

* Ronald L. Graham, Donald E. Knuth and Oren Patashnik [http://www.amazon.co.uk/Concrete-Mathematics-Foundation-Computer-Science/dp/0201558025/ref=pd_bbs_sr_1/026-8892653-7930013?ie=UTF8&s=books&qid=1185030033&sr=8-1 Concrete Mathematics: A Foundation for computer science]

* Tom DeMarco and Timothy Lister [http://www.amazon.co.uk/Peopleware-Productive-Projects-Tom-DeMarco/dp/0932633439/ref=pd_bbs_sr_1/202-6651186-7291039?ie=UTF8&s=books&qid=1187972200&sr=8-1 Peopleware: Productive Projects and Teams]

* Adobe Systems Incorporated [http://www.amazon.co.uk/Postscript-Language-Reference-CD-ROM-Systems/dp/0201379228/ref=sr_1_2/202-6651186-7291039?ie=UTF8&s=books&qid=1187972791&sr=1-2 PostScript Language Reference 3rd edition]

* George W. Snedecor and William G. Cochran [http://www.amazon.com/Statistical-Methods-George-W-Snedecor/dp/0813815614/ref=sr_1_1/002-8692953-8561655?ie=UTF8&s=books&qid=1191253322&sr=1-1 Statistical Methods]

* Scott Berkun [http://www.amazon.com/Myths-Innovation-Scott-Berkun/dp/0596527055 Myths of Innovation]

* John Viega and Gary McGraw [http://www.amazon.com/exec/obidos/ASIN/020172152X Building Secure Software: How to Avoid Security Problems the Right Way]

* Gary McGraw [http://www.amazon.com/Software-Security-Building-Addison-Wesley/dp/0321356705/ref=pd_sim_b_2 Software Security: Building Security In]

* Dorothy Elizabeth Robling Denning [http://www.amazon.com/exec/obidos/ASIN/0201101505 Cryptography and Data Security]

* Donald A. Norman [http://www.amazon.co.uk/Design-Everyday-Things-Donald-Norman/dp/0465067107/ref=sr_1_2?ie=UTF8&s=books&qid=1209977401&sr=8-2 The Design of Everyday Things]

* Edward R. Tufte [http://www.amazon.co.uk/Visual-Display-Quantitative-Information/dp/0961392142/ref=sr_1_1?ie=UTF8&s=books&qid=1209977565&sr=1-1 The Visual Display of Quantitative Information]

* Edward R. Tufte
[ http://www.amazon.co.uk/Envisioning-Information-Edward-R-Tufte/dp/0961392118/ref=sr_1_2?ie=UTF8&s=books&qid=1209977710&sr=1-2 Envisioning Information]

* Edward R. Tufte [ http://www.amazon.co.uk/Visual-Explanations-Quantities-Evidence-Narrative/dp/0961392126/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Visual Explanations: Images and Quantities, Evidence and Narrative]

* Edward R. Tufte [ http://www.amazon.co.uk/Beautiful-Evidence-Edward-R-Tufte/dp/0961392177/ref=pd_sim_b?ie=UTF8&qid=1209977710&sr=1-2 Beautiful Evidence ]

* Robert L. Glass [ http://www.amazon.co.uk/Facts-Fallacies-Software-Engineering-Development/dp/0321117425/ref=sr_1_1?ie=UTF8&s=books&qid=1209977897&sr=1-1 Facts and Fallacies of Software Engineering ]

* Steve Krug [ http://www.amazon.co.uk/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?ie=UTF8&s=books&qid=1209978195&sr=8-1 Don't Make Me Think]

* Richard J. Larsen, Morris L. Marx [ http://www.amazon.co.uk/Introduction-Mathematical-Statistics-Its-Applications/dp/0132018136/ref=sr_1_2?ie=UTF8&s=books&qid=1209978238&sr=1-2 An Introduction to Mathematical Statistics and Its Applications]

* Terry Winograd, C.F. Flores [ http://www.amazon.co.uk/Understanding-Computers-Cognition-Foundation-Language/dp/0893910503/ref=sr_1_10?ie=UTF8&s=books&qid=1209978295&sr=1-10 Understanding Computers and Cognition: A New Foundation for Design]
[[Category:SENSE]]

ICT-SEC-2007.1.7 Partners Table

2007-10-03T17:52:43Z

Louridas:

{| class="wikitable" border="1"
|-
! Partner name !! URL !! Contact !! Previous Experience !! Current Call !! Status
|-
| Cyprus Telecommunications Authority || http://www.cyta.com.cy/ || CHRYSOCHOS, Ioannis (Dr) || || [[RedZone]] || Use as a last resort
|-
| Polska Telefonia Cyfrowa Sp. z o.o. || http://www.era.pl/ || BRZOZOWY, Miroslaw (Dr.) || || [[RedZone]] || Sent cover letter
|-
| University of Oulu - Department of Electrical and Information Engineering || || RÖNING, Juha (Professor) || || [[RedZone]] || Sent cover letter, apparent lack of response
|-
| Siemens PSE TR || http://www.pse.siemens.at/ || CEBECI, Onur (Mr.) || || [[RedZone]] || There can be one partner from TR; wait feedback from other contacts
|-
| RedHat EMEA || http://www.europe.redhat.com/about/ || Sacha Labourey || || [[RedZone]] || Sent e-mail
|-
| Distributed Systems Group RWTH Aachen University || http://ds.informatik.rwth-aachen.de/ || Klaus Wehrle Prof. Dr.-Ing.|| || [[RedZone]] || Sent cover letter, they cannot participate due to large number of projects
|-
| Next Generation Security Software || http://www.ngssoftware.com/ || research@ngssofware.com|| || [[RedZone]] || Sent cover letter
|-
| Hasso-Plattner Institute, OS and Middleware Group|| http://www.hpi.uni-potsdam.de/forschung/fachgebiete/betriebssysteme.html?L=1 || Prof. Dr. Andreas Polze || || [[RedZone]] || Sent cover letter, they are waiting for further info
|-
| SINTEF, Software Engineering, Safety and Security Research Group || http://www.sintef.no/content/page3____6456.aspx || Eldfrid Øfsti Øvstedal || || [[RedZone]] || Sent cover letter, they are waiting for further info
|-
| ERICSSON TURKEY || http://www.ericsson.com/ || GOKCEK, Muge || || [[RedZone]] || Sent cover letter
|-
| University of Cambridge Computer Laboratory, Systems Research Group, NetOS Group || http://www.cl.cam.ac.uk/research/srg/ || ??? These are the guys behind Xen, but there is no contact person, if anybody knows somebody... (gousiosg: actually, Xen was the byproduct of a competing project they are developing, XenoServers)|| || [[RedZone]] ||
|-
| Athens University of Economics and Business, CiS Group || http://www.cis.aueb.gr/ || Dimitrios Gritzalis || || [[PROMIS]] || Use as last resort
|-
| KEMEA, Center for Security Studies || http://www.kemea.gr/ || ??? we have a contact, vbill knows more about him || || [[PROMIS]] || Use as last resort
|-
| F-Secure || http://www.f-secure.co.uk/enterprises/ || uk@f-secure.co.uk || || [[PROMIS]] || Sent cover letter
|-
| PANDA || http://www.pandasecurity.com/ [http://www.pandasecurity.com/img/sob/cf11c.gif] || info@pandasecurity.com or marketing.greece@pandasecurity.com || || [[PROMIS]] || Sent cover letter
|-
| ASTARO || http://www.astaro.com/company/offices || salesuk@astaro.com || || [[PROMIS]] ||Sent cover letter
|-
| Avira || http://www.avira.com/en/company/contact.html || info@avira.com || || [[PROMIS]] ||Sent cover letter
|-
| AVG || http://www.avguk.com/ || ?? no contact found || || [[PROMIS]] ||
|-
| Kaspersky || http://www.kaspersky.com/contacts || onlinesales@kaspersky.com || || [[PROMIS]] || Sent cover letter
|-
| THUS plc || http://www.thus.net/ || Phil Male || || [[PROMIS]] || Sent cover letter (generic)
|-
| Universitat Politècnica de Catalunya || http://www-fen.upc.es/~romu/ || Romualdo Pastor-Satorras || || [[PROMIS]] || Sent cover letter
|-
| Complexity Group, BT Research || http://nekovee.info || Maziar Nekovee || || [[PROMIS]] || Sent cover letter
|-
| nixu || http://www.nixu.com/index_en.html || info@nixu.com || || [[PROMIS]] || Sent cover letter
|}

ICT-SEC-2007.1.7 Partners Table

2007-09-27T21:19:46Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-27T21:10:16Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-27T15:27:37Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-27T15:18:38Z

Louridas:

PROMIS Letter of Interest

2007-09-26T20:03:37Z

Louridas: /* Description */

'''ACRONYM''' PROMIS

'''NAME''' A PROactive Malware Identification System based on Peer-to-Peer Networks

[http://gaijin.dmst.aueb.gr/repository/promis/partner-invitation/promis.pdf pdf version here] (needs authentication)

==Description==

'''STREP proposal (FP7/ICT)'''

'''Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)'''

Recent worm epidemics showed that the existing centralized worm containment mechanisms are no longer
adequate to protect vulnerable systems. Although the homogeneity of computer systems offers some significant benefits,
e.g., portability and the standardisation of software development, highly homogeneous environments
make easy for malcode to propagate in less time than any traditional reaction is possible.
This has resulted to a shift towards distributed
cooperative systems that aim to safeguard and immunise the susceptible population by automatically
vaccinating them.

At the same time, there is a more balanced choice of software and hardware in critical infrastructures. In
that case a system that is not vulnerable to a specific type of malware can extract valuable information
regarding the mechanisms of the specific attack and pass them to rest of the systems, before these
systems get compromised. The systems, which will participate in a proposed Peer-to-Peer (P2P) network can thereafter
apply automatically some predefined countermeasures in order to avoid the consequences of
a forthcoming malware epidemic. Our approach is based on the principles of hygiene:
taking the basic precautions to avoid infection when an epidemic is on the rise.

Based on these principles, to alleviate the effects of rapid malcode we propose a cooperative containment
algorithm called PROactive Malware Identification System – PROMIS,
based on a P2P architecture, which provides timely information to the
members of a specially crafted P2P group. Members of the group then automatically adjust their security level.

Theoretical research regarding our approach has already been published in

* Vasileios Vlachos and Diomidis Spinellis. A PRoactive malware identification system based on the computer hygiene principles. ''Information Management and Computer Security'', 15(4):295–312, 2007 [http://dx.doi.org/10.1108/09685220710817815]

The simulations we performed in conjunction with two early prototypes produced
positive results. We are planning to build a stable PROMIS system using the
experience gained from our attempts and the experimental results of the
simulation. This project aims to:

* Conduct research, extending the findings of the PROMIS algorithm, discovering innovative methods to identify malware and to protect critical infrastructures

* Design and build a fully functional PROMIS system running in the MS-Windows and GNU/Linux operating systems

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

==What we need from you==

The PROMIS project is a research proposal being submitted for the first time. We plan to carry out
the major parts of the write-up using our own resources, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas of their particular expertise
and to formally review the proposal before it is being submitted.

==Further information and communication==

This proposal is initiated by the Software Engineering and Security Group of the Department of Management
Science and Technology of the Athens University of Economics and Business, directed by Diomidis
Spinellis [http://www.dmst.aueb.gr/dds]. 
 
Our web site: [http://istlab.dmst.aueb.gr/sense] 
Contact us by email at bkarak@aueb.gr.

PROMIS Letter of Interest

2007-09-26T20:00:55Z

Louridas: /* Description */

'''ACRONYM''' PROMIS

'''NAME''' A PROactive Malware Identification System based on Peer-to-Peer Networks

[http://gaijin.dmst.aueb.gr/repository/promis/partner-invitation/promis.pdf pdf version here] (needs authentication)

==Description==

'''STREP proposal (FP7/ICT)'''

'''Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)'''

Recent worm epidemics showed that the existing centralized worm containment mechanisms are no longer
adequate to protect vulnerable systems. Although the homogeneity of computer systems offers some significant benefits,
e.g., portability and the standardisation of software development, highly homogeneous environments
make easy for malcode to propagate in less time than any traditional reaction is possible.
This has resulted to a shift towards distributed
cooperative systems that aim to safeguard and immunise the susceptible population by automatically
vaccinating them.

At the same time, there is a more balanced choice of software and hardware in critical infrastructures. In
that case a system that is not vulnerable to a specific type of malware can extract valuable information
regarding the mechanisms of the specific attack and pass them to rest of the systems, before these
systems get compromised. The systems, which will participate in a proposed P2P network can thereafter
apply automatically some predefined countermeasures in order to avoid the consequences of
a forthcoming malware epidemic. Our approach is based on the principles of hygiene:
taking the basic precautions to avoid infection when an epidemic is on the rise.

Based on these principles, to alleviate the effects of rapid malcode we propose a cooperative containment
algorithm called PRoactive malware Identification System – PROMIS,
based on a peer-to-peer (P2P) architecture, which provides timely information to the
members of a specially crafted P2P group. Members of the group then automatically adjust their security level.

Theoretical research regarding our approach has already been published in

* Vasileios Vlachos and Diomidis Spinellis. A PRoactive malware identification system based on the computer hygiene principles. ''Information Management and Computer Security'', 15(4):295–312, 2007 [http://dx.doi.org/10.1108/09685220710817815]

The simulations we performed in conjunction with two early prototypes produced
positive results. We are planning to build a stable PROMIS system using the
experience gained from our past attempts and the experimental results of the
simulation. This project aims to:

* Conduct research, extending the findings of PROMIS algorithm, discovering innovative methods to identify malware and to protect critical infrastructures
* Design and build a fully functional PROMIS system running in windows and linux operating system

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

==What we need from you==

The PROMIS project is a research proposal being submitted for the first time. We plan to carry out
the major parts of the write-up using our own resources, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas of their particular expertise
and to formally review the proposal before it is being submitted.

==Further information and communication==

This proposal is initiated by the Software Engineering and Security Group of the Department of Management
Science and Technology of the Athens University of Economics and Business, directed by Diomidis
Spinellis [http://www.dmst.aueb.gr/dds]. 
 
Our web site: [http://istlab.dmst.aueb.gr/sense] 
Contact us by email at bkarak@aueb.gr.

PROMIS Letter of Interest

2007-09-26T19:52:32Z

Louridas: /* Description */

'''ACRONYM''' PROMIS

'''NAME''' A PROactive Malware Identification System based on Peer-to-Peer Networks

[http://gaijin.dmst.aueb.gr/repository/promis/partner-invitation/promis.pdf pdf version here] (needs authentication)

==Description==

'''STREP proposal (FP7/ICT)'''

'''Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)''' 

Recent worm epidemics showed that the existing centralized worm containment mechanisms are no longer
adequate to protect vulnerable systems. This in turn has resulted to a shift towards distributed
cooperative systems that aim to safeguard and immunise the susceptible population by automatically
vaccinating them. We present PROMIS, a P2P based algorithm that provides its participants with
early information regarding the existence of a worm epidemic and lets them automatically adjust their
security level. We argue that our approach is based on the principles of hygiene: taking the basic
precautions to avoid infection when an epidemic is on the rise.

The homogeneity of most computer systems offers some significant benefits, regarding portability
and the standardization of software development. On the other hand highly homogenous environments
make easy for rapid malcode to propagate in less time than any traditional reaction is possible. Probably
we should pay more attention to the security disadvantages of that approach and start looking for other
means to diminish these effects.

Fortunately, we see a more balanced choice of software and hardware in critical infrastructures. In
that case a system that is not vulnerable to a specific type of malware, can extract valuable information
regarding the mechanisms of the specific attack and pass them to rest of the systems, before these
systems get compromised. The systems, which participate in our proposed P2P network can thereafter,
apply automatically, some predefined countermeasures, (disabling the HTML preview in their e-mail
clients or increasing the security settings of their browser etc) in order to avoid the consequences of
a forthcoming malware epidemic. We argue that our approach is based on the principles of hygiene:
taking the basic precautions to avoid infection when an epidemic is on the rise.

To alleviate the effects of rapid malcode we propose a cooperative containment
algorithm PRoactive malware Identification System – PROMIS and is
based on a peer-to-peer (P2P) architecture to provide timely information to the
members of a specially crafted P2P group.

Theoretical research regarding our approach have already been published in

* Vasileios Vlachos and Diomidis Spinellis. A PRoactive malware identification system based on the computer hygiene principles. ''Information Management and Computer Security'', 15(4):295–312, 2007 [http://dx.doi.org/10.1108/09685220710817815]

The simulations we performed in conjunction with the two early prototypes produced
positive results. We are planning to build a stable PROMIS system using the
experience gained from our past attempts and the experimental results of the
simulation. This project aims to:

* Conduct research, extending the findings of PROMIS algorithm, discovering innovative methods to identify malware and to protect critical infrastructures
* Design and build a fully functional PROMIS system running in windows and linux operating system

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

==What we need from you==

The PROMIS project is a research proposal being submitted for the first time. We plan to carry out
the major parts of the write-up using our own resources, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas of their particular expertise
and to formally review the proposal before it is being submitted.

==Further information and communication==

This proposal is initiated by the Software Engineering and Security Group of the Department of Management
Science and Technology of the Athens University of Economics and Business, directed by Diomidis
Spinellis [http://www.dmst.aueb.gr/dds]. 
 
Our web site: [http://istlab.dmst.aueb.gr/sense] 
Contact us by email at bkarak@aueb.gr.

ICT-SEC-2007.1.7 Partners Table

2007-09-21T15:57:25Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T15:55:30Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T15:20:50Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T14:31:58Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T14:25:34Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T14:25:02Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-21T14:23:39Z

Louridas:

{| class="wikitable" border="1"

|-

! Partner name !! URL !! Contact !! Previous Experience !! Current Call

|-

| Cyprus Telecommunications Authority || http://www.cyta.com.cy/ || CHRYSOCHOS, Ioannis (Dr) || || [[RedZone]]

|-

| Polska Telefonia Cyfrowa Sp. z o.o. || http://www.era.pl/ || BRZOZOWY, Miroslaw (Dr.) || || [[RedZone]]

|-
| University of Oulu - Department of Electrical and Information Engineering || || RÖNING, Juha (Professor) || || [[RedZone]]
|-
| Siemens PSE TR || http://www.pse.siemens.at/ || CEBECI, Onur (Mr.) || || [[RedZone]]

|-

| ERICSSON TURKEY || http://www.ericsson.com/ || GOKCEK, Muge || || [[RedZone]]

|-

| University of Cambridge Computer Laboratory, Systems Research Group, NetOS Group || http://www.cl.cam.ac.uk/research/srg/ || ??? These are the guys behind Xen, but there is no contact person, if anybody knows somebody... || || [[RedZone]]
|-
| Athens University of Economics and Business, CiS Group || http://www.cis.aueb.gr/ || Dimitrios Gritzalis || || [[PROMIS]]
|-
| KEMEA, Center for Security Studies || http://www.kemea.gr/ || ??? we have a contact, vbill knows more about him || || [[PROMIS]]
|-
| F-Secure || http://www.f-secure.co.uk/enterprises/ || ??? no contact here || || [[PROMIS]]
|}

ICT-SEC-2007.1.7 Partners Table

2007-09-19T15:07:48Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-19T14:53:49Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-19T14:52:31Z

Louridas:

ICT-SEC-2007.1.7 Partners Table

2007-09-19T14:31:42Z

Louridas: New page: {| class="wikitable" border="1" |- ! Partner name !! URL !! Contact !! Previous Experience !! Current Call |- | row 1, cell 1 || row 1, cell 2 || row 1, cell 3 || row 1, cell 4 || row...

{| class="wikitable" border="1"

|-

! Partner name !! URL !! Contact !! Previous Experience !! Current Call

|-

| row 1, cell 1 || row 1, cell 2 || row 1, cell 3 || row 1, cell 4 || row 1, cell 5

|-

| row 2, cell 1 || row 2, cell 2 || row 2, cell 3 || row 1, cell 4 || row 1, cell 5

|}

FP7: Critical Infrastructure Protection

2007-09-19T14:21:56Z

Louridas:

Reliability Evaluation of Free / Open Source / Libre Software

2007-09-19T14:02:12Z

Louridas: New page: The interoperability and inter-connectivity of communication networks are is one of the cornerstones of our society. All workings of today's society, be them financial transactions, inter...

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T14:02:02Z

Louridas: /* Reliability Evaluation of Free / Open Source / Libre Software */

FP7: Critical Infrastructure Protection

2007-09-19T14:01:53Z

Louridas: /* Project Proposals */

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[Telemonitoring System for Remote Power Plants]]
* [[Reliability Evaluation of Free / Open Source / Libre Software]]

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T14:01:35Z

Louridas:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[Telemonitoring System for Remote Power Plants]]
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

Telemonitoring System for Remote Power Plants

2007-09-19T14:00:41Z

Louridas: New page: There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something al...

There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something along the lines of a telemonitoring system for remote power plants. I very briefly looked in the internet, and there is some information, relevant projects and systems etc. I could not, by myself, undertake the preparation of such a proposal, but if I had some help from someone else in the group, we could go for it, it would be interesting. Bare in mind (i've been following this a little), that a great "boom" in renewable energy investments is expected soon, and it could very well be that the outcome of such a project could be a very interesting commercial project (don't laugh, i'm the first to criticize the outcome of all EU funded projects, but this time it's really well positioned in time and geographically). So if there is interest in this, and someone is willing to start right away working on consortium and proposal preparation with me, let me know. We are talking about a STREP, so I guess 5-6 partners (we already have AUEB, SINGULAR, and ENOLIA, this company I've mentioned from Greece, so I think everyone else should be from Europe, I have a couple of potential contacts already), and about 2MEuros or so... Perhaps we can make Singular coordinators and avoid some of the accounting hussle

===Possible Partners===

* SINGULAR
* ENOLIA
* http://www.solarsat.eu/
* Fraunhofer ISE - Fraunhofer Institute for Solar Energy Systems ( http://www.ise.fhg.de/ )
* www.flyby.it

FP7: Critical Infrastructure Protection

2007-09-19T14:00:29Z

Louridas: /* Telemonitoring system for remote power plants (need work). Call Details: Objective ICT-2007.6.3: ICT for Environmental Management and Energy Efficiency) */

ideas we have:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[Telemonitoring System for Remote Power Plants]]
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T14:00:15Z

Louridas: /* Project Proposals */

ideas we have:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[Telemonitoring System for Remote Power Plants]]
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==Telemonitoring system for remote power plants (need work). Call Details: Objective ICT-2007.6.3: ICT for Environmental Management and Energy Efficiency)==

There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something along the lines of a telemonitoring system for remote power plants. I very briefly looked in the internet, and there is some information, relevant projects and systems etc. I could not, by myself, undertake the preparation of such a proposal, but if I had some help from someone else in the group, we could go for it, it would be interesting. Bare in mind (i've been following this a little), that a great "boom" in renewable energy investments is expected soon, and it could very well be that the outcome of such a project could be a very interesting commercial project (don't laugh, i'm the first to criticize the outcome of all EU funded projects, but this time it's really well positioned in time and geographically). So if there is interest in this, and someone is willing to start right away working on consortium and proposal preparation with me, let me know. We are talking about a STREP, so I guess 5-6 partners (we already have AUEB, SINGULAR, and ENOLIA, this company I've mentioned from Greece, so I think everyone else should be from Europe, I have a couple of potential contacts already), and about 2MEuros or so... Perhaps we can make Singular coordinators and avoid some of the accounting hussle

===Possible Partners===

* SINGULAR
* ENOLIA
* http://www.solarsat.eu/
* Fraunhofer ISE - Fraunhofer Institute for Solar Energy Systems ( http://www.ise.fhg.de/ )
* www.flyby.it

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T13:59:30Z

Louridas: /* A PROactive Malware Identification System (PROMIS) based on Peer-to-Peer Networks */

ideas we have:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[SENSE]]: Software Engineering and Security
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==Telemonitoring system for remote power plants (need work). Call Details: Objective ICT-2007.6.3: ICT for Environmental Management and Energy Efficiency)==

There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something along the lines of a telemonitoring system for remote power plants. I very briefly looked in the internet, and there is some information, relevant projects and systems etc. I could not, by myself, undertake the preparation of such a proposal, but if I had some help from someone else in the group, we could go for it, it would be interesting. Bare in mind (i've been following this a little), that a great "boom" in renewable energy investments is expected soon, and it could very well be that the outcome of such a project could be a very interesting commercial project (don't laugh, i'm the first to criticize the outcome of all EU funded projects, but this time it's really well positioned in time and geographically). So if there is interest in this, and someone is willing to start right away working on consortium and proposal preparation with me, let me know. We are talking about a STREP, so I guess 5-6 partners (we already have AUEB, SINGULAR, and ENOLIA, this company I've mentioned from Greece, so I think everyone else should be from Europe, I have a couple of potential contacts already), and about 2MEuros or so... Perhaps we can make Singular coordinators and avoid some of the accounting hussle

===Possible Partners===

* SINGULAR
* ENOLIA
* http://www.solarsat.eu/
* Fraunhofer ISE - Fraunhofer Institute for Solar Energy Systems ( http://www.ise.fhg.de/ )
* www.flyby.it

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T13:59:07Z

Louridas: /* Project Proposals */

ideas we have:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[PROMIS]]
* [[SENSE]]: Software Engineering and Security
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==A PROactive Malware Identification System (PROMIS) based on Peer-to-Peer Networks==

The promis project has moved. [[PROMIS]]

==Telemonitoring system for remote power plants (need work). Call Details: Objective ICT-2007.6.3: ICT for Environmental Management and Energy Efficiency)==

There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something along the lines of a telemonitoring system for remote power plants. I very briefly looked in the internet, and there is some information, relevant projects and systems etc. I could not, by myself, undertake the preparation of such a proposal, but if I had some help from someone else in the group, we could go for it, it would be interesting. Bare in mind (i've been following this a little), that a great "boom" in renewable energy investments is expected soon, and it could very well be that the outcome of such a project could be a very interesting commercial project (don't laugh, i'm the first to criticize the outcome of all EU funded projects, but this time it's really well positioned in time and geographically). So if there is interest in this, and someone is willing to start right away working on consortium and proposal preparation with me, let me know. We are talking about a STREP, so I guess 5-6 partners (we already have AUEB, SINGULAR, and ENOLIA, this company I've mentioned from Greece, so I think everyone else should be from Europe, I have a couple of potential contacts already), and about 2MEuros or so... Perhaps we can make Singular coordinators and avoid some of the accounting hussle

===Possible Partners===

* SINGULAR
* ENOLIA
* http://www.solarsat.eu/
* Fraunhofer ISE - Fraunhofer Institute for Solar Energy Systems ( http://www.ise.fhg.de/ )
* www.flyby.it

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

FP7: Critical Infrastructure Protection

2007-09-19T13:58:37Z

Louridas: /* Web Applications Security */

ideas we have:

== Project Proposals ==
* [[RedZone]]
* [[Mapping Critical IT Infrastructures]]
* [[OIS]]: Organizational Information Systems
* [[SENSE]]: Software Engineering and Security
* [[WRC]]: Wireless Research Center

== Call ==

* [[CallDetails-ICT-SEC-2007.1.7]]: Call details

==A PROactive Malware Identification System (PROMIS) based on Peer-to-Peer Networks==

The promis project has moved. [[PROMIS]]

==Telemonitoring system for remote power plants (need work). Call Details: Objective ICT-2007.6.3: ICT for Environmental Management and Energy Efficiency)==

There is the ICT Call 2 for Environment with deadline October 9th. There is interest from a Greek company involved with solar plants and stuff, as well as SINGULAR, to propose something along the lines of a telemonitoring system for remote power plants. I very briefly looked in the internet, and there is some information, relevant projects and systems etc. I could not, by myself, undertake the preparation of such a proposal, but if I had some help from someone else in the group, we could go for it, it would be interesting. Bare in mind (i've been following this a little), that a great "boom" in renewable energy investments is expected soon, and it could very well be that the outcome of such a project could be a very interesting commercial project (don't laugh, i'm the first to criticize the outcome of all EU funded projects, but this time it's really well positioned in time and geographically). So if there is interest in this, and someone is willing to start right away working on consortium and proposal preparation with me, let me know. We are talking about a STREP, so I guess 5-6 partners (we already have AUEB, SINGULAR, and ENOLIA, this company I've mentioned from Greece, so I think everyone else should be from Europe, I have a couple of potential contacts already), and about 2MEuros or so... Perhaps we can make Singular coordinators and avoid some of the accounting hussle

===Possible Partners===

* SINGULAR
* ENOLIA
* http://www.solarsat.eu/
* Fraunhofer ISE - Fraunhofer Institute for Solar Energy Systems ( http://www.ise.fhg.de/ )
* www.flyby.it

==Reliability Evaluation of Free / Open Source / Libre Software==

The interoperability and inter-connectivity of communication networks are is
one of the cornerstones of our society. All workings of today's society, be
them financial transactions, interpersonal communications, health care provision or
knowledge acquisition, are heavily dependent on telecommunications network
meshes, able to transfer information in real time. As control of those
infrastructures is increasingly left over to complex software systems, our
society is increasingly dependent on the security and quality of the
construction of this software.

On the other hand, FLOSS (free / libre / open source software) is quickly
becoming a key component of critical infrastructures and therefore an
important factor of the ICT sector in the EU. FLOSS is expected to be present
in many different products and systems in the EU in the near future.
However, while some well known FLOSS packages, such as the Apache web
server and the Linux kernel, have a proved security record, a great number of
other FLOSS programs is in use, without their users knowing their security
properties. This situation is even more pronounced in the case of proprietary software.
Large scale users base their IT decisions for critical infrastructures on
word-of-mouth recommendations and have trust software houses based on their
reputation, rather than utilising independent and objective security evaluations.

The scientific community has long been studying the issue of
software security. Tools to detect common problems in both code and program
runtime are widely available, both as FLOSS and as commercial products.
Also, a number of security provisioning method are available and cover
all the phases of the development of information systems.

The <PROJECT_ACRONYM> project aims to bridge the gap between the availability
of tools and methodologies and the absence of their application on the
field of critical information systems. Our goal is to build a platform that
integrates existing security-related tools and using well established
methodologies it will allow for the scientific evaluation of the security
of critical software. Our particular focus will be the field of FLOSS,
as the availability of the source code will allow us to develop in-depth
evaluation methods.

More specifically, we plan to develop:

* Integrated tools that assess the security of software projects
* A classification of security-evaluated projects
* An integrated method for performing security evaluations of software

Using a large set of projects, of a different kind (operating systems, web
servers etc), the security of different products
will be measured. Those products will be classified by field of application,
and by their security metrics. Depending on the field of application, the risk
associated to each possible security flaw will be evaluated. The consequences
of that flaw will be evaluated as well. With that information, a ranking of
products will be made. This ranking will be useful to certificate FLOSS
products for different fields of application, and also as a roadmap in order to
fix those products that are the least secure.
For the measurement system, existing tools will be evaluated, and when the
needs of the system may not be covered with existing alternatives, new tools
will be developed.

Our proposed work will build upon two currently running,
FP6-funded projects, FLOSSMETRICS and SQO-OSS. FLOSSMETRICS [1] has
build a comprehensive database of software quality related metrics for
a great number of projects and will function as our source of raw data.
On the other hand, the SQO-OSS plug-in based software evaluation
platform [2] will be the basis for the software we are planning to develop.
The integration of the quality metrics tools from FLOSSMETRICS project and the
security tools that will be developed for <PROJECT_ACRONYM> on the SQO-OSS
tool, will effectively create a tool for the holistic evaluation of software
quality and security, which will allow critical IS implementers to choose
from the best available projects.

All the software produced by this research
project will be released in the public domain under the European Public License (EUPL).

'''What we need from you'''

The <PROJECT_ACRONYM> project is a research proposal being submitted
for the first time. We plan to carry out the major parts of the write-up
using the resources of URJC and AUEB, although help from partners will be greatly
appreciated. We expect our partners to contribute their opinions in areas
of their particular expertise and to formally review the proposal before it
is being submitted.

'''Further information and communication'''
This proposal is co-ordinated by the <LAB> of the <UNI>, directed by Jesus Gonzalez Barajona
<MAIL>, <TEL>, <WEB> etc. The Information Systems Laboratory of the Department of the Athens
University of Economics and Business, directed by Diomidis Spinellis, will be participating
in the proposal preparation.

[1] - Flossmetrics: http://www.flossmetrics.org
[2] - SQO-OSS: http://www.sqo-oss.eu

RedZone

2007-09-19T13:58:03Z

Louridas: /* Recovery Oriented Computing, Virtualization, and Secutity */

Assume that attacks and breaches are unavoidable; focus on how to
make systems resilient in spite of them. For instance, extend Recovery
Oriented Computing (ROC) ideas to apply to the security infrastructure. What
if instead of a company or country running services on servers, having
them run on virtual machines (cf. what Amazon offers with its EC2
service) that run on farms and can be brought up and down at will? If
something is attacked, we just bring it down and spawn another
pre-configured virtual machine hosting exactly the same services... In
sort, combine virtualisation and ROC for security infrastructure.

Recent moves in security infrastructure could already be interpreted under this light.
DNS root servers have started adopting anycast, in which case traffic from a compromised
server will automatically switch to a standby server via BGP.

Coming back to virtualisation, imagine we have an infrastructure that can host
fully configured services; e.g., an image of a DNS server, or e-mail server, etc.
The server itself runs as an instance of that image. When the image is attacked or
compromised, you just bring up another image. This requires:

* A substrate on which the virtual machines will run
* A way to configure virtual machines and package them, so as to be ready for deployment
* A way to interact with the substrate and the virtual machines in order to control their operation

==Cons==

The marriage of virtualisation and security is not exactly new, see [http://www.virtualization.info/2006/07/security-by-virtualization.html] and [http://en.wikipedia.org/wiki/Bitfrost Bitfrost].

== Cover Letter==

'''ACRONYM'''

'''NAME'''

===Description===

'''STREP proposal (FP7/ICT)'''

'''Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)'''

Critical infrastructures comprise a large number of complex, interconnected systems, where software plays an important role. Failures of critical infrastructure software components can have far-reaching impact; such failures may be the result of malicious intent (i.e., attacks, viruses, etc.) or they may be the result of lurking software bugs. For certain critical components, shutting down the malfunctioning part is not an option, as even decreased quality of service is better than complete service disruption – consider air traffic control systems, or even an online auction site. This has led to an increased interest in the area of self-adapted and self-healing systems. At the same time, legal frameworks, security and auditing concerns, demand that, especially in malfunctions, data is captured and made available for security forensics.

The proposed project aims at self-adaptability, self-healing, and security forensics enablers. Specifically, we plan to develop techniques that will allow systems to continue running even in the presence of faults (accidental or malicious). These techniques will reduce the likelihood of unnecessary infrastructure service termination, and provide a better understanding of the infrastructure failure, or the factors that led to that failure. In order to do that, we will pursue research in the following areas:

* ''Profiling critical infrastructure software components'': In order to diagnose a malfunction, we need to be able to distinguish normal from abnormal behaviour. We will investigate methods that will allow us to derive and specify the normal behaviour of software components. If, later, during operation a software infrastructure component deviates from the expected behaviour, we will be alerted that it has moved beyond its accepted operational parameters, its ''normal operational envelope''.

* ''Allow controlled execution outside the operational envelope'': We define an area outside the normal operational envelope, which we call the ''red zone''. If a software component enters the red zone, we know that it has moved beyond its normal behaviour, but we do not know the cause and the severity of the problem. Rather than terminating or suspending the component, we place it into an appropriate container and we enter an increased state of readiness. We allow the component to continue to run, taking actions to limit the damage caused. In parallel, we collect any data that may be of use in tracing the origin of the malfunction.

The software component profiling, and the controlled execution in the red zone, will be performed in the context of properly adapted virtual machines that will host the critical components. The proposed project will therefore build on the latest trends in virtualisation, and we will research on using virtual machines as an important component for building reliable, resilient, and always available information infrastructures.

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

===What we need from you===

This project is a research proposal being submitted for the first time. We plan to carry out the major parts of the write-up using our own resources, although help from partners will be greatly appreciated. We expect our partners to contribute their opinions in areas of their particular expertise and to formally review the proposal before it is submitted.

===Further information and communication===

This proposal is initiated by the Software Engineering and Security Group of the Information Systems Technology Laboratory, directed by Diomidis Spinellis (http://www.dmst.aueb.gr/dds/), hosted by the Department of Management Science and Technology at the Athens University of Economics and Business.

Our website: http://istlab.dmst.aueb.gr.

Contact us by email at louridas@aueb.gr .

==Possible Partners==

* Ericsson

* University of Cambridge (if we use VMs and specifically Xen)

* Cyprus Telecommunication Authority (but we may end up Eurovision-style)

Mapping Critical IT Infrastructures

2007-09-19T13:57:38Z

Louridas: /* Mapping Critical IT Infrastructures */

Develop a way to map critical IT infrastructures. The
dependencies are very complex, and therefore you need tools and data
to explore what is really critical. Is Vodafone part of Greece's
critical infrastructure? Linux? Solaris? MS-DOS? Postgres? So we do a
kind of service and artefact dependency analysis, mapping dependencies
and criticality indicators/measures not only software but telecom
links, hardware facilities, etc. We develop the software and then run
a pilot study. Our proposed approach differs from automatic vulnerability analysis, because we follow and explore the effect of dependencies, rather than primary vulnerabilities.

How do we measure criticality? I can come up with two dimensions:

# The amount of infrastructure affected. If we map the infrastructure on a graph, it is clear that some nodes are more central than others. This has been explored at length in scale-free networks research, providing grounding why the internet is vulnerable to targeted attacks.
# The exact effects on the affected infrastructure. A slight performance degradation is not the same as a crash.

In software, it has long since been observed that not all bugs are worth fixing, as they
may never produce a failure. This observations may extend to whole security infrastructures,
and perhaps this is what we are aiming at here?

==Cons==
The importance of this proposal is, at least to me, self-evident, but I was wondering if this information should be made public. Identifying the most critical nodes in every complex system, is like pinpointing the most valuable targets for adversaries wanting to wreck havoc. Nonetheless I would love to work in that proposal…

==Possible Partners==

==Cover Letter==

'''Mapping Critical IT Infrastructures and their Dependencies'''

Department of Management Science and Technology
Athens University of Economics and Business

STREP proposal (FP7/ICT)
Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)

Communication systems, supply systems, services, form complex interconnected infrastructure networks whose functioning is fundamental for our
society. Infrastructure networks are vulnerable both to malicious attacks and to accidental malfunction; in recent years, in various countries, we have seen examples of commodity infrastructures such as telecommunications, transportation, or power supply networks that were attacked or failed accidentally leading to loss of their availability. In several of these cases large parts of the attacked systems were adversely affected due to domino-like effects: failure in a system component had far reaching rippling effects that had not been predicted, as the criticality of infrastructure components, and the possibilities for damage propagation had not been assessed.

Information and Communication Technology (ICT) infrastructures are becoming more and more complex, not only because their size grows daily but also (mostly) due to their interconnected nature and the fact that we are moving towards the unification of such networks (e.g., data and voice networks). It is therefore becoming more difficult to efficiently monitor their operation, master their vulnerabilities, prevent against the cascading effects of failures and provide recovery and continuity in critical scenarios. Tools are needed in order to explore and map the dependencies between the parts of these systems in order to identify the ones that are critical. If failures are inevitable, it is necessary to know the extent of the expected damage, in order to prepare the most adequate reaction.

The proposed project aims to deliver algorithms and tools for mapping and exploring dependencies between the different artefacts and components that ICT infrastructures are made of and identifying/examining criticality measures for each one. This includes not just hardware or software but also service provisioning (e.g., power supply, telecommunication links, Web Services). The project's macro level goal is not to create a tool that automatically detects vulnerabilities and proposes countermeasures, but to follow and explore the effect of dependencies between the various components of a system that is geographically dispersed and relies on the availability of various service providers in order to operate. In this way we will be able to predict the extent of the damage that may result from a malfunctioning component in an infrastructure network. The dependencies and probabilities about the spread of damage will be visualised to aid decision making; for instance, our tools will produce graphical overlays on infrastructure maps.

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

'''What we need from you'''

This project is a research proposal being submitted for the first time. We plan to carry out the major parts of the write-up using our own resources, although help from partners will be greatly appreciated. We expect our partners to contribute their opinions in areas of their particular expertise and to formally review the proposal before it is submitted.

Further information and communication

This proposal is initiated by the Software Engineering and Security Group of the Information Systems Technology Laboratory, directed by Diomidis Spinellis (http://www.dmst.aueb.gr/dds/), hosted by the Department of Management Science and Technology at the Athens University of Economics and Business.

Our website: http://istlab.dmst.aueb.gr.

Contact us by email at circular@aueb.gr .

Mapping Critical IT Infrastructures

2007-09-19T13:57:16Z

Louridas: New page: =Mapping Critical IT Infrastructures= Develop a way to map critical IT infrastructures. The dependencies are very complex, and therefore you need tools and data to explore what is really...

=Mapping Critical IT Infrastructures=

Develop a way to map critical IT infrastructures. The
dependencies are very complex, and therefore you need tools and data
to explore what is really critical. Is Vodafone part of Greece's
critical infrastructure? Linux? Solaris? MS-DOS? Postgres? So we do a
kind of service and artefact dependency analysis, mapping dependencies
and criticality indicators/measures not only software but telecom
links, hardware facilities, etc. We develop the software and then run
a pilot study. Our proposed approach differs from automatic vulnerability analysis, because we follow and explore the effect of dependencies, rather than primary vulnerabilities.

How do we measure criticality? I can come up with two dimensions:

# The amount of infrastructure affected. If we map the infrastructure on a graph, it is clear that some nodes are more central than others. This has been explored at length in scale-free networks research, providing grounding why the internet is vulnerable to targeted attacks.
# The exact effects on the affected infrastructure. A slight performance degradation is not the same as a crash.

In software, it has long since been observed that not all bugs are worth fixing, as they
may never produce a failure. This observations may extend to whole security infrastructures,
and perhaps this is what we are aiming at here?

==Cons==
The importance of this proposal is, at least to me, self-evident, but I was wondering if this information should be made public. Identifying the most critical nodes in every complex system, is like pinpointing the most valuable targets for adversaries wanting to wreck havoc. Nonetheless I would love to work in that proposal…

==Possible Partners==

==Cover Letter==

'''Mapping Critical IT Infrastructures and their Dependencies'''

Department of Management Science and Technology
Athens University of Economics and Business

STREP proposal (FP7/ICT)
Strategic Objective: ICT-SEC-2007.1.7: Critical Infrastructure Protection (Joint Call between ICT and Security Themes FP7-ICT-SEC-2007-1)

Communication systems, supply systems, services, form complex interconnected infrastructure networks whose functioning is fundamental for our
society. Infrastructure networks are vulnerable both to malicious attacks and to accidental malfunction; in recent years, in various countries, we have seen examples of commodity infrastructures such as telecommunications, transportation, or power supply networks that were attacked or failed accidentally leading to loss of their availability. In several of these cases large parts of the attacked systems were adversely affected due to domino-like effects: failure in a system component had far reaching rippling effects that had not been predicted, as the criticality of infrastructure components, and the possibilities for damage propagation had not been assessed.

Information and Communication Technology (ICT) infrastructures are becoming more and more complex, not only because their size grows daily but also (mostly) due to their interconnected nature and the fact that we are moving towards the unification of such networks (e.g., data and voice networks). It is therefore becoming more difficult to efficiently monitor their operation, master their vulnerabilities, prevent against the cascading effects of failures and provide recovery and continuity in critical scenarios. Tools are needed in order to explore and map the dependencies between the parts of these systems in order to identify the ones that are critical. If failures are inevitable, it is necessary to know the extent of the expected damage, in order to prepare the most adequate reaction.

The proposed project aims to deliver algorithms and tools for mapping and exploring dependencies between the different artefacts and components that ICT infrastructures are made of and identifying/examining criticality measures for each one. This includes not just hardware or software but also service provisioning (e.g., power supply, telecommunication links, Web Services). The project's macro level goal is not to create a tool that automatically detects vulnerabilities and proposes countermeasures, but to follow and explore the effect of dependencies between the various components of a system that is geographically dispersed and relies on the availability of various service providers in order to operate. In this way we will be able to predict the extent of the damage that may result from a malfunctioning component in an infrastructure network. The dependencies and probabilities about the spread of damage will be visualised to aid decision making; for instance, our tools will produce graphical overlays on infrastructure maps.

The project's software deliverables will be available for internal use by the project's partners and in the future could become part of or form the basis of novel products and business solutions. Scientific contributions will be exploited by means of journal articles and conference publications. Licensing and commercial exploitation of research results will be discussed during the proposal preparation phase.

'''What we need from you'''

This project is a research proposal being submitted for the first time. We plan to carry out the major parts of the write-up using our own resources, although help from partners will be greatly appreciated. We expect our partners to contribute their opinions in areas of their particular expertise and to formally review the proposal before it is submitted.

Further information and communication

This proposal is initiated by the Software Engineering and Security Group of the Information Systems Technology Laboratory, directed by Diomidis Spinellis (http://www.dmst.aueb.gr/dds/), hosted by the Department of Management Science and Technology at the Athens University of Economics and Business.

Our website: http://istlab.dmst.aueb.gr.

Contact us by email at circular@aueb.gr .