2. NETWORKED EUROPEAN SOFTWARE & SERVICES INITIATIVE NESSI: delivering building blocks for the Internet of Services New Architectures for Future Internet, Campinas, 24..09.2009. Aljosa Pasic, Atos Origin

3. Agenda The story of NESSI Future Internet (of services) Building blocks for IoS Closer look at security for IoS Conclusions

4. The story of NESSI The context - European Technology Platform Private-public partnership Industrial leadership Uniting all stakeholders Around a key, strategic area Strategic? Europes future growth Europes competitiveness Link? Requires major research and technological advances In the medium to long term NESSI aims to provide a unified view for European research in Services Architectures and Software Infrastructures Today, NESSI partners represent 1.7 Million strong workforce and 490 B in revenues NESSI has presented an initial Strategic Research Agenda that represents a global investment of 2.5 B

5. NESSIs governance 4 NESSI partners Coordinating NESSI members Actively Contributing to NEXOF to the SRA Staying Aware Committees Board Steering Committee Working Group Committees NESSI Office Research Projects NewslettersEvents Mailings

6. NESSI partners Coordinating NESSI members Actively Contributing to NEXOF to the SRA Staying Aware 400 members 12 working groups 6 NESSI Strategic Projects 5 NESSI Compliant Projects NESSIs constituency

7. ETP or JTI? ETP – European Technology Platform JTI – Joint Technology Initiative Over 30 ETPs – 6 JTIs Innovative Medicines Initiative (IMI) Embedded Computing Systems (ARTEMIS) Aeronautics and Air Transport (Clean Sky) Nanoelectronics Technologies 2020 (ENIAC) Fuel Cells and Hydrogen (FCH) Global Monitoring for Environment and Security (GMES) 6 ETPs http://cordis.europa.eu/technology-platforms/home_en.htmlhttp://cordis.europa.eu/technology-platforms/home_en.html JTI http://cordis.europa.eu/fp7/jtis/http://cordis.europa.eu/fp7/jtis/

8. NESSI at a glance 20052005 20062006 20072007 20122012 20082008

9. Agenda The story of NESSI Future Internet (of services) Building blocks for IoS Closer look at security for IoS Conclusions

10. NESSI in Future Internet Internet of things Internet of Users Internet of Contents Internet of Services Services Data & Contents Things & sensors Users & Knowledge AMBIENT NETWORKS & PERVASIVE COMPUTING REAL VIRTUAL Tomorrow the Internet will be strategic because of services

11. Future Internet Assembly 10 European Commission

12. NESSI Framework NESSI Landscape NESSI Adoption Holistic Model Core Services Business Services EU Economy NESSI Adoption

13. NESSI Framework NESSI Landscape NESSI Adoption Holistic Model Core Services Business Services EU Economy NESSI Adoption Define and implement Practices & Usages Architecture & Engineering Regulatory Governance

14. Agenda The story of NESSI Future Internet (of services) Building blocks for IoS Closer look at security for IoS Conclusions

15. The tools of NESSI The first tool of an ETP is its Strategic Research Agenda Moving from vision to definition Frame the context Refine the Technological scope

16. The tools of NESSI The first tool of an ETP is its Strategic Research Agenda Moving from vision to definition Frame the context Refine the Technological scope Enhance definition of NEXOF – the NESSI Open Service Framework Build it together 20082008 20122012

17. Contributing to NEXOF Contributing key components to NEXOF Compliant to NEXOF or Contributing to NEXOF - Open to all - Participative selection process Contributing to NEXOF – a world-wide process

18. Contributing to NEXOF Contributing to NEXOF – a world-wide process

19. System Platform Consumer Adaptation Service consumers Infrastructure Service Composition BPM view Service Platform Monitoring Service Communication Service Discovery Mediation SLA Negotiation Service Coordination Integration Services Reasoning Service Execution Lifecycle Management Service Registration Infrastructure and Data Abstraction Data Management Resources Management Business Process Execution SVN Lifecycle Management Information Services Interaction Services End user Interface Context Handling Mapping users perspectives to business/Integration Native Services External Services Knowledge Modelling Service Modelling SVN Modeling Infrastructure Modelling SBS/SBA Modelling Context Modelling Business Process Modeling Engineering tools Requirements Capture offered as services

20. System Platform Consumer Adaptation Service consumers Infrastructure Service Composition BPM view Service Platform Monitoring Service Communication Service Discovery Mediation SLA Negotiation Service Coordination Integration Services Reasoning Service Execution Lifecycle Management Service Registration Infrastructure and Data Abstraction Data Management Resources Management Business Process Execution SVN Lifecycle Management Information Services Interaction Services End user Interface Context Handling Mapping users perspectives to business/Integration Native Services External Services Knowledge Modelling Service Modelling SVN Modeling Infrastructure Modelling SBS/SBA Modelling Context Modelling Business Process Modeling Engineering tools SLA@SOI SOA4ALL MASTER EzWeb RESERVOIR

21. Agenda – The story of NESSI – Future Internet (of services) – Building blocks for IoS – Closer look at security for IoS – Conclusions

22. Service Oriented World Applications will need to utilise shared and co-owned services out of different domains of control that require to obey separate security policies and ask for diverse security and dependability qualities

23. Challenges A trustworthy Internet with services that you trust The technical base that makes the Internet a safer place Address long-term research and industry vision on trust, security and dependability in software and services

24. Coming problems For industry: Demand for Secure software is much higher than available security expertise For research/technology: New complex scenarios (e.g. ambient intelligence) introduce security issues not addressed by conventional engineering processes For market consultants: Security properties difficult to measure and it is also difficult to evaluate their compositional effects For users: Security segmentation and market definitions are blurring: service infrastructure covers network infrastructure, perimeter, desktop, server and application security For auditors and lawyers: Who is accountable and liable for what? For society: Trust becomes a key enabler for service provision and use For everyone: How much should we spend on security?

25. Some Research Topics Security Technologies Embedded in Services Services at the component level of the Service-Oriented Architecture Specialised Security Services and Properties Access control architecture and its implementation System-wide Security Characteristics Holistic implementation of the secure service eco-system. Dependability and Availability. Human/Societal/Technical Trust elements The human & machine perception of System Trustworthiness. Privacy, digital rights… Governmental and Societal Context Policy, Regulation, Certification, Awareness, Security Stakeholders Mapping…

26. TSD grey context boundaries If computing sky is getting cloudy…TSD will depend on weather conditions… Infrastructure view: Expanding boundary (include remote access PC) and/or Contracting boundary (exclude outsourcing staff PC, external B2B server…) Trust view: trust zones where a level of trust can be established and security controls can be enforced E2E Security or Dependability levels: closed, semi-open or open servicenets ?

27. Security Dimensions in Service Infrastructures Secure Services Securing Services Security as a service

28. What should it be? Dynamic Adaptable Composable Measurable Predictive Scalable Persuasive Open Trustworthy Interoperable Approaches, properties and research challenges In TSD engineering and modelling In TSD control and management In TSD level assurance

29. …which brings many trade-off issues… AvailabilityData integrity Privacy Accountability ScalabilityAssurance

30. Metrics for Trust, Security & Dependability a)b)c)

31. Biometrics Network Privacy, identity Services Secure Implementation Trusted Computing FP6FP7 Coordination Action SecurIST ESFORS THINK-TRUSTFORWARD PARSIFALAMBER

32. More on trust and trustworthiness… In a service-centric Internet: Use and adoption of services depends highly on TRUST and TRUSTWORTHINESS The trust model relies on complete requirements that include business, technical, legal, regulatory, and societal requirements PrimeLife

33. We need more than technology : an example Risk management failure; a trader (Jerome Kerviel) was able to turn off the monitoring controls which should have alerted the organization to a magnitude of risk which put the organization in danger. Governance failure; when the French Banking Commission detected Kerviel's activity and warned Societe Generale (SocGen) that its risk management regime was not working properly, SocGen management apparently failed to take effective action to fix the problem. Identifying in time both failures and who in the organization is responsible for addressing each failure is a lesson learnt for other companies which might face in the future similar problems.

34. MASTER approach: align and manage GRC tool structure should have roundtrip processes. Management at all levels should have effective tools for understanding the information and reports it receives, including the ability to drill down into information to see the details provided by staff at all levels. Compliance Management solution, such as MASTER can help implement roundtrip processes. Different interfaces for different people. Conceptual Model Methodology MASTER Architecture Online Enforcement Run-time Monitoring and Signalling Design-Time Workbench Assessement Cockpit

35. 34 Outsource people, processes, resources... Regulators Standards Bodies Best practices Offshore Outsourcing

36. 35 Compliance Management in MASTER Designing Methods and tools for selecting and integrating controls Monitoring Collecting evidence for the measurement of operation and effectiveness of controls. Assessment Evaluation of status of compliance Enforcement Ensuring controls are applied Reacting when controls fail MASTER integrated project (Feb 2008-Feb 2011) Industry Atos Origin (ES), SAP AG (DE), Engineering (IT), British Telecom (UK), IBM (CH), ANECT (CZ), Deloitte (FR) Academia Lero (IE), University of Trento (IT), ETH (CH), University of Stuttgart (DE), SINTEF ICT (NO) End user CESCE (ES), Hospital San Raffaele (IT) OrganizationOrganization Service Provision = Control process

37. Decompose compliance/control objectives Control Objectives Can be decomposed Means-end analysis Risk-assessment Control Activities Can be decomposed Process/temporal constructs Enforcement and auditing language constructs Control service Description of step-by-step control mechanisms Target/Value Goals Can be decomposed Business process engineering This is outside the MASTER process. Target Activities (business process) Can be decomposed Again outside MASTER Impact of control steps over value steps must be considered Target service Controls

38. Business Process Control Process Event going into control process Event coming out of control process Event not modified by control process

39. BP step Control step In SOA world… BP step Control step BP step Control step

40. KSI (correctness) 7,145.56 Event going into control process Event coming out of control process Event not modified by control process Compliant event (trace) Non-compliant event (trace)

41. Standardization and reusability PRM A CO 4 PRM B PRM C Control Objectives: security goals need to be satisfied to be compliant CO M CO 4 CO 8 CO 9 CO 2 CO N CO 1 Possibility to leverage on existing PRMs and re-using existing ones (or part of) in defining new PRMs Protection Model: is a set of controls whose enforcement, monitoring and assessment guarantees an experimentally and/or formally assessed level of compliance Control activities and steps: Derived from a set of required COs From specification of high level COs to operational policies

42. Key building block for FI: Identity STORK is a large scale pilot in the ICT-PSP (ICT Policy Support Programme), under the CIP (Competitiveness and Innovation Programme), and co-funded by EU. It aims at implementing an EU wide interoperable system for recognition of eID and authentication that will enable businesses, citizens and government employees to use their national electronic identities in any Member State. It will also pilot transborder eGovernment identity services and learn from practice on how to roll out such services, and to experience what benefits and challenges an EU wide interoperability system for recognition of eID will bring. The STORK interoperable solution for electronic identity (eID) is based on a distributed architecture that will pave the way towards full integration of EU e- services while taking into account specifications and infrastructures currently existing in EU Member States. The solution provided is intended to be robust, transparent, safe to use and scalable, and should be implemented in such a way that it is sustainable beyond the life of the pilot.

43. Agenda The story of NESSI Future Internet (of services) Building blocks for IoS Closer look at security for IoS Conclusions

44. The importance of the global collaboration Future Internet – an opportunity for collaboration Similar initiatives exist in several countries end-to-end location-ind. services the best of all communities optimise resources No single domain delivers end-to-end user scenarios Global convergence is only implemented by a common approach and shared process Many companies are present worldwide Many countries have specific excellence Multiple disciplines and knowledge domains are needed Validate the best competitive applications and usage scenarios worldwide Avoid reinventing the wheel ETPs

45. Conclusions We need to invest in research GLOBALLY in order to ensure continued trust by users as society increases its dependency on software services Software security engineering, in its road to maturity, could & should use lessons learned from the software engineering and from the system security, but also other disciplines and research communities

46. Thank you FACING TECHNOLOGICAL CHALLENGES TOGETHER Aljosa Pasic (Atos Origin) aljosa.pasic@atosorigin.com