NovaGenesis: Security Aspects Requirements and Challenges


Published on

Presentation done at the BIC event at São Paulo, 2013.

As part of it’s long term strategy for building international cooperation, the BIC project is setting up an in-country Extended Working Group (EWG) in Brazil comprised of key members of the Brazilian research community engaged in research in all areas related to Trustworthy ICT and international cooperation.

The launch meeting of the Brazil EWG was held on 22nd October, 2013, at the Instituto de Tecnologia de Software (ITS) in São Paulo, Brazil.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

NovaGenesis: Security Aspects Requirements and Challenges

  1. 1. NovaGenesis: Security Aspects Requirements and Challenges Antônio Marcos Alberti Associate Professor and Researcher INATEL - Instituto Nacional de Telecomunicações October 22th, 2013.
  2. 2. Outline  Very Brief History  NovaGenesis Overview  Testing Scenario: Joint Services and Content Orchestration  Security Aspects
  3. 3. Very Brief History ‣ 2008: Started Future Internet activities @ Inatel. ‣ 2009: Studying. ‣ 2010: First NovaGenesis design principles and choices. ‣ 2011: Finished draft architecture. ‣ 2012: Started proof-of-concept implementation. Refinement of choices. ‣ 2013: Test scenario over Mobile Future Internet (MOFI) from ETRI, CNU, and KNU - South Korea.
  4. 4. NovaGenesis Overview     Entities and content naming employs natural language and selfcertifiable names (hash codes). All functionalities are seen as services, including network protocols. Name bindings are stored on distributed hash tables, representing all kind of relationships among named-things. Name bindings are published and subscribed, enabling distributed search, discovery, negotiation, and contracting of services and content.
  5. 5. NovaGenesis Overview      Substrate resources are exposed to software by proxies, which represent them regarding resource life-cycling and orchestration. All the communication is done by message scheduling and exchanging, with dynamic headers. All the service contracts can capture intrinsically the required quality, security, privacy, reputation, etc. The services will employ a decision cycle to meet objectives traced by human and machine operators. They compete each other to better satisfy contracts (evolutionary pressures) and optimize the usage of substrate resources (evolution environment).
  6. 6. NovaGenesis Overview
  7. 7. NovaGenesis Overview
  8. 8. Testing Scenario: Joint Services and Content Orchestration ‣ Clients e servers discover each other, publish SLAs and exchange named-content based on user policies. ‣ Provides check for content provenance, integrity, and coherence of content. ‣ MOFI provided transparent connectivity change.
  9. 9. Testing Scenario: Joint Services and Content Orchestration ‣ Content publishing round trip time ‣ Content subscription round trip time
  10. 10. Security Aspects  Requirements and challenges: - Message/data integrity and confidentiality. - Rendezvous among publishers and subscribers. - Security, privacy, and trust of entities/content life-cycling. - Trust network formation, assertion, and management. - Identity, privacy, and reputation management. - Unbiased contract, reputation, and trust evaluation. - Build-in police definition, enforcement, and conflict resolution. - History preservation versus cleaning. - Revoking of published bindings, data, permissions, etc.
  11. 11. Security Aspects  Requirements and challenges (continuing): - Distributed key generation and cryptography. - Voting and coordination of entities towards social security. - Distributed/hierarchical certification chains. - Management of different hash algorithms and sizes. - Deterministic building of binary executables. - Management of copies and clones. - Scalability, resilience, “on the fly” algorithm changing.
  12. 12. Of course, we are looking for collaboration to address these challenges on Future Internet! Thank you! Antônio Marcos Alberti