SECREDAS

Product Security for Cross Domain Reliable Dependable Automated Systems

LEARN MORE CONTACT US




ABOUT SECREDAS

SECREDAS stands for “Product Security for Cross Domain Reliable Dependable Automated Systems”. It is one of the first funded ECSEL Joint Undertaking projects which looks at security, safety and privacy across multiple application domains: Road, Rail and Health. The project consortium will build a reference architecture for Secure and Safe Automated systems compliant with the new GDPR Regulation. The project started in May 2018 and will continue until April 2021. It is co-funded through the EU ECSEL Programme and a number of national funds.

ACKNOWLEDGEMENT

SECREDAS has received funding within the Electronic Components and Systems for European Leadership Joint Undertaking (ECSEL JU) in collaboration with the European Union’s H2020 Framework Programme (H2020/2014- 2020) and National Authorities, under grant agreement n° 783119.

The SECREDAS project

The SECREDAS project has been set up to maximise the available expertise and generate application-specific solutions based on common technology elements. This ensures that solutions achieve their intended security and safety targets, work on common platforms and are also cost-effective. To implement the project, €51 million, of which €XX in form of ECSEL and national co-funding grants, will be spent.

The SECREDAS project will operate through 11 interlinked Work Packages (WPs); WP11 is a combined work package on project management , dissemination and exploitation of results.

Why this project?

At this time, one in four potential buyers/users in Europe of automated driving is reluctant to do so, mainly due to a lack of trust into its security. Hence industry and research communities need to work on an answer to ensure that these concerns are no longer roadblocks for further evolutions in the transport and personal healthcare sectors. By using new design and development methodologies to integrate cross-domain cybersecurity and safety related technologies, 70 European research and industrial partners take an important step toward increasing consumer trust in Europe’s transportation (vehicles, rail and aerospace) and medical industries.

The SECREDAS project is ground-breaking because:

  • • It is the first cross-domain large-scale platform project involving key knowledgeable players and influential partners in the domains of security, safety, privacy, automotive, health and rail.
  • • It will create a cross-domain reference architecture, design patterns and common security/privacy technology components which can be embedded in-domain specific solutions and which guarantee safety and performance requirements for 2020 vehicle requirements.
  • • It will focus on multi-sector demonstrations showing how to withstand hacking & attacking of the key components and systems.
  • • It will create a new multi-stakeholder dialogue based on sound human factor surveys that will create new insights towards future legislation and societal acceptance. This is done in close cooperation with key stakeholder groups and user groups.

What will SECREDAS achieve?

The SECREDAS project consortium is in the process of developing and validating multi-domain architecting methodologies, reference architectures, components and suitable integration and verification approaches for automated systems, as well as taking into account and influencing standardization, certification and qualification in different domains, combining high security and privacy protection while preserving functional-safety and operational performance. This will ensure that European OEMs remain competitive and maintain their world-leading position. The technologies developed in this project will provide common approaches as well as domain-specific solutions that adapt to changing environments and new challenges.

The SECREDAS project will be a success if we can achieve that:

  • • Reference Architecture & Design Patterns is used by 80% of the SECREDAS partners and by interested stakeholders in at least 5 other European Cooperation Projects.
  • • The common technology elements are used in at least 3 domain-specific components developed in SECREDAS and in at least 3 other European Cooperation Projects.
  • • We have successfully introduced on the market new domain-specific components.
  • • We have had a visible impact in several standardisation committees.
    • • We have an impact on future European roadmaps as developed by EU and specific stakeholder groups. • We can showcase a successful demonstration of preventing and solving hacking experiments based on the proposed scenarios using the new components as developed in SECREDAS.

Most of all: If SECREDAS can deliver a significant contribution to the development of trust and acceptance by consumers and users of automated systems!

How is SECREDAS structured?

SECREDAS comprises 11 work packages which build upon each other’s achievements.

In the first project year, the partners focussed on:


  • • Identifying Use Cases which describe particular – realistic – situations in which a user interacts with an automated system and its outside environment. These Use Cases cover things like: the way a vehicle is accessed for use or interacts with other vehicles whilst driving or at cross roads for example, to crossings between rail and road infrastructure, sudden illness of the user or necessary technical updates or upgrades of the system.
  • • Based on the Use Cases the partners identified realistic headline threat scenarios and sub-scenarios – coincidental as well as malicious – which could affect the security or safety of the automated system and thereby endanger the user if not prevented or counteracted on time.
  • • Finally, the Threat scenarios were analysed and led to the definition of hardware and software component requirements that address each scenario and thus safeguards the autonomous system’s security and the user’s safety.

We are currently in our second project year.


The partners are working hard on the development of the hardware and software components and on validation of the effectiveness of each demonstrator against the different threat scenarios. Much emphasis is on finding common approaches for similar-type threats across the three application domains. Cross-workpackage groups have been created to ensure a smooth knowledge exchange and transfer of results between partners and work packages with a view to the integration and testing of components and systems in three main demonstrator cycles in year three. Stand-alone components developed in the different work package tasks are also being integrated in order to test and validate interconnection and overall security. Year two also sees a quick ramping up of external dissemination and commercial exploitation activities by the different partners.

In the third project year:



A selected number of components will be included in major field tests whereby autonomously moving test-vehicles will run through the Use Cases and be placed in the different threat scenario environments. This involves the simulation of external attacks on the systems internal network and interaction with other networks, sudden occurrences on/near road and rail infrastructure etc. The field tests will take place on specially prepared (not open to the public) stretches of road, as well as via drone simulations. Dissemination of the technical results to a wide audience will be a major activity in Year 3.
❮ ❯
In several iterative steps a Reference Architecture is transformed into systems for demonstration in SECREDAS.

Where are we now?

Year 1 of the project was completed in April 2019 with only minor delays in the production of technical deliverables. Use Cases and threat scenarios have been identified and solution requirements have been defined and validated. The annual review by external experts and the European Commission (June 2019) mainly showed minor improvement issues related to the transfer of results between work packages, and these are being addressed. The project started well into Year 2 of operation. Technical Progress is fast moving forward and requires more cross-work package interaction and collaboration to ensure that the results from initial demonstrators and prototypes from each work package can be used and integrated upward to systems that can be tested in the Year 3 field tests.

Why this project?

At this time, one in four potential buyers/users in Europe of automated driving is reluctant to do so, mainly due to
a lack of trust into its security. Hence industry and research communities need to work on an answer to ensure
that these concerns are no longer roadblocks for further evolutions in the transport and personal healthcare
sectors. By using new design and development methodologies to integrate cross-domain cybersecurity and safety
related technologies, 70 European research and industrial partners take an important step toward increasing
consumer trust in Europe’s transportation (vehicles, rail and aerospace) and medical industries.

The SECREDAS project is ground-breaking because:

  • • It is the first cross-domain large-scale platform project involving key knowledgeable players and influential partners in the domains of security, safety, privacy, automotive, health and rail.
  • • It will create a cross-domain reference architecture, design patterns and common security/privacy technology components which can be embedded in-domain specific solutions and which guarantee safety and performance requirements for 2020 vehicle requirements.
  • • It will focus on multi-sector demonstrations showing how to withstand hacking & attacking of the key components and systems.
  • • It will create a new multi-stakeholder dialogue based on sound human factor surveys that will create new insights towards future legislation and societal acceptance. This is done in close cooperation with key stakeholder groups and user groups.

What will SECREDAS achieve?

The SECREDAS project consortium is in the process of developing and validating multi-domain architecting
methodologies, reference architectures, components and suitable integration and verification approaches for
automated systems, as well as taking into account and influencing standardization, certification and qualification
in different domains, combining high security and privacy protection while preserving functional-safety and
operational performance.
This will ensure that European OEMs remain competitive and maintain their world-leading position. The
technologies developed in this project will provide common approaches as well as domain-specific solutions that
adapt to changing environments and new challenges.

The SECREDAS project will be a success if we can achieve that:

  • • Reference Architecture & Design Patterns is used by 80% of the SECREDAS partners and by interested stakeholders in at least 5 other European Cooperation Projects.
  • • The common technology elements are used in at least 3 domain-specific components developed in SECREDAS and in at least 3 other European Cooperation Projects.
  • • We have successfully introduced on the market new domain-specific components.
  • • We have had a visible impact in several standardisation committees.
    • • We have an impact on future European roadmaps as developed by EU and specific stakeholder groups. • We can showcase a successful demonstration of preventing and solving hacking experiments based on the proposed scenarios using the new components as developed in SECREDAS.
Most of all: If SECREDAS can deliver a significant contribution to the development of trust and acceptance by consumers and users of automated systems!

How is SECREDAS structured?

SECREDAS comprises 11 work packages which build upon each other’s achievements.

In the first project year,



The partners focussed on:
  • • Identifying Use Cases which describe particular – realistic – situations in which a user interacts with an automated system and its outside environment. These Use Cases cover things like: the way a vehicle is accessed for use or interacts with other vehicles whilst driving or at cross roads for example, to crossings between rail and road infrastructure, sudden illness of the user or necessary technical updates or upgrades of the system.
  • • Based on the Use Cases the partners identified realistic headline threat scenarios and sub-scenarios – coincidental as well as malicious – which could affect the security or safety of the automated system and thereby endanger the user if not prevented or counteracted on time.
  • • Finally, the Threat scenarios were analysed and led to the definition of hardware and software component requirements that address each scenario and thus safeguards the autonomous system’s security and the user’s safety.

We are currently in our second project year.


The partners are working hard on the development of the hardware and software components and on validation of the effectiveness of each demonstrator against the different threat scenarios. Much emphasis is on finding common approaches for similar-type threats across the three application domains. Cross-workpackage groups have been created to ensure a smooth knowledge exchange and transfer of results between partners and work packages with a view to the integration and testing of components and systems in three main demonstrator cycles in year three. Stand-alone components developed in the different work package tasks are also being integrated in order to test and validate interconnection and overall security. Year two also sees a quick ramping up of external dissemination and commercial exploitation activities by the different partners.

In the third project year:



A selected number of components will be included in major field tests whereby autonomously moving test-vehicles will run through the Use Cases and be placed in the different threat scenario environments. This involves the simulation of external attacks on the systems internal network and interaction with other networks, sudden occurrences on/near road and rail infrastructure etc. The field tests will take place on specially prepared (not open to the public) stretches of road, as well as via drone simulations. Dissemination of the technical results to a wide audience will be a major activity in Year 3.

How is SECREDAS structured?

SECREDAS comprises 11 work packages which build upon each other’s achievements.

In the first project year, the partners focussed on:


  • • Identifying Use Cases which describe particular – realistic – situations in which a user interacts with an automated system and its outside environment. These Use Cases cover things like: the way a vehicle is accessed for use or interacts with other vehicles whilst driving or at cross roads for example, to crossings between rail and road infrastructure, sudden illness of the user or necessary technical updates or upgrades of the system.
  • • Based on the Use Cases the partners identified realistic headline threat scenarios and sub-scenarios – coincidental as well as malicious – which could affect the security or safety of the automated system and thereby endanger the user if not prevented or counteracted on time.
  • • Finally, the Threat scenarios were analysed and led to the definition of hardware and software component requirements that address each scenario and thus safeguards the autonomous system’s security and the user’s safety.

We are currently in our second project year.


The partners are working hard on the development of the hardware and software components and on validation of the effectiveness of each demonstrator against the different threat scenarios. Much emphasis is on finding common approaches for similar-type threats across the three application domains. Cross-workpackage groups have been created to ensure a smooth knowledge exchange and transfer of results between partners and work packages with a view to the integration and testing of components and systems in three main demonstrator cycles in year three. Stand-alone components developed in the different work package tasks are also being integrated in order to test and validate interconnection and overall security. Year two also sees a quick ramping up of external dissemination and commercial exploitation activities by the different partners.

In the third project year:



A selected number of components will be included in major field tests whereby autonomously moving test-vehicles will run through the Use Cases and be placed in the different threat scenario environments. This involves the simulation of external attacks on the systems internal network and interaction with other networks, sudden occurrences on/near road and rail infrastructure etc. The field tests will take place on specially prepared (not open to the public) stretches of road, as well as via drone simulations. Dissemination of the technical results to a wide audience will be a major activity in Year 3.
❮ ❯

Where are we now?

Year 1 of the project was completed in April 2019 with only minor delays in the production of technical deliverables. Use Cases and threat scenarios have been identified and solution requirements have been defined and validated. The annual review by external experts and the European Commission (June 2019) mainly showed minor improvement issues related to the transfer of results between work packages, and these are being addressed. The project started well into Year 2 of operation. Technical Progress is fast moving forward and requires more cross-work package interaction and collaboration to ensure that the results from initial demonstrators and prototypes from each work package can be used and integrated upward to systems that can be tested in the Year 3 field tests.

SECREDAS Work Plan and Deliverables

IMAGE HERE

Work Package 1: User Scenarios

Coordinator: IMEC-Belgium (IMEC-B)

WP1 will study a number of user scenarios, which are relevant for SECREDAS to cover the intertwining of security, safety and privacy protection. The study will be used in order to derive future reference architectures and requirements (input to WP 2), develop common technology elements (input to WP3).
The output will be:

  • • a reference set of user scenarios for future technical developments, demonstrations and assessment/certification of new components;
  • • impact assessment of user scenarios on new components;
  • • translation of user scenarios into demonstrations;
  • • organisation of use-case workshop with other EU pilot projects.

IMAGE HERE

Work Package 2: Reference Architecture & Requirements

Coordinator: IDEMIA (IDEMIA)

WP2 will provide an analysis of the Safety, Security and Privacy requirements needed for the design, implementation and evaluation of the SECREDAS uses cases.
The output will be:

  • • identification and analysis of privacy, safety and security goals and requirements;
  • • a security model;
  • • security and privacy Reference-Architecture;
  • • supervisor Architecture for Mitigating Safety and Security Issues.

IMAGE HERE

Work Package 3: Common Technology Elements

Coordinator: IMEC-Belgium (IMEC-B)

The main objectives are to (1) develop and validate a number of common technology elements for the reference architectures and (2) develop a framework for multi-concerned security-safety verification and testing. Common technology elements will be provided/enhanced and design patterns created to support the development of technical security measures, maintaining functional safety, privacy and operational performance.
The output will be:

  • • improvement of Common Technology Elements;
  • • New design patterns, including Safety, Security and Privacy analysis;
  • • security testing framework.

IMAGE HERE

Work Package 4: Vehicle Sensing

Coordinator: IMEC-Belgium (IMEC-B)

The objective in this Work package is to design, develop and verify appropriate cyber-security and safety in sensor and pre-processing systems required in ADAS/AD/connected vehicles.
The output will be:

  • • selected sensor, components and sensor data processing algorithms and computing platforms for ADAS applications;
  • • Sensors and Components used for ADAS/AD;
  • • design and integration of the central sensor fusion system architecture;
  • • sensor System Integration and Validation.

IMAGE HERE

Work Package 5: Vehicle connectivity

Coordinator: YoGoKo

The objectives in this Work package are to integrate security building blocks necessary to protect the external interfaces linking the vehicle to the external environment. Specifically: protect the vehicle against security breaches
related to communication flows with other vehicles and the roadside infrastructure (V2X), IoT and sensor devices interacting with the vehicle.
The output will be:

  • • map of high-level security features into the ITS station reference architecture;
  • • integration of security features developed in WP3 an existing V2X communication stack complying with Cooperative ITS standards;
  • • integration of security features developed in WP3 into an existing communication stack providing extended connectivity to the cloud complying with Cooperative ITS standards;
  • • increased safety and privacy of IoT devices integrated in vehicles;
  • • a prototype of a radar/5G component capable of operating in the 76-81 GHz frequency band;
  • • security testing & performance validation.

IMAGE HERE

Work Package 6: In-vehicle networking & VCU

Coordinator: NXP Semiconductors Netherlands

This work package provides the hardware and software foundation for running
the Use Scenarios from the other WP’s in an automotive product. The work centres around the following components: data processing, In-vehicle networking devices, VCU electrical controller.
The output will be:

  • • development of data processing components that run on or with the hardware components created in Task 6.2 and Task 6.3;
  • • development of (hardware) components that take care of the networking within the car. This covers the ‘heart’ of the car networking in the car between sensors, processing units and actuators (but not networking between the car and the outside world);
  • • development of highly secured VCU electronic controller components;
  • • VCU electronic controller module development and validation.

IMAGE HERE

Work Package 7: Health

Coordinator: Philips

The objectives in this Work package are to integrate the secure architecture
and common technology elements into a personal health demonstrator using wearables. The WP will contribute to a multi domain demonstrator to enable enhanced cruise control by monitoring the driver and measure the driver performance to enhance the safety of (semi) autonomous driving.
The output will be:

  • • creation of a secure connection between wearables and via a gateway;
  • • sensing devices and algorithms for driver health monitoring;
  • • demonstrator development;
  • • user acceptance tests.

IMAGE HERE

Work Package 8: Rail

Coordinator: Thales

The objectives in this Work package are to assess cyber security and safety critical components from WP2 and WP3 for the railway domain.

The output will be:

  • • Identification of requirements for safety and security layers for the railway domain;
  • • component specification and concept development involving common security technologies and reference architectures;
  • • Component integration and validation.

IMAGE HERE

Work Package 9: Common demonstrators

Coordinator: IMEC-Belgium (IMEC-B)

The objectives in this Work package are to demonstrate software and hardware solutions on key User Scenarios. Five scenarios will undergo field-testing: Road Intersection, Automated truck with driver getting health problems, Updating the vehicle, Advanced Access to Vehicle & Rail.
The output will be three full demonstrators at selected experimentation locations on:

  • (1) Autonomous driving and infrastructure servers,
  • (2) Driver Monitoring Systems and
  • (3) Cybersecurity and connectivity.

IMAGE HERE

Work Package 10: Standardisation, Qualification & Certification

Coordinator: AIT

The objectives in this Work package are to:

  • • analyze involvement in standardization activities and current use of standards by partners;
  • • analyze the applicability of current security, safety and communication (ITS) standards and initiatives for the targeted domains;
  • • disseminate new project findings to standardization, trying to influence or initiate standards;
  • • develop guidelines for continuous multi-concern (safety and security) certification including assessment methods.

IMAGE HERE

Work Package 11: management, Dissemination & Exploitation

Coordinator: NXP Semiconductors Netherlands

The objectives in this Work package are to implement the management of the project and the communication towards the outside world and the multiple stakeholders in the outcome of the project. The work also includes the development of the strategy towards specific activities on exploitation, dissemination and risk monitoring & mitigation.
In addition to project management, the output of this work package will be:

  • • initiating and organising various multi-Stakeholder Dialogues for further commercial uptake or policy development on autonomous systems;
  • • presenting SECREDAS and partner findings at conferences, fairs and through publications and outreach activities.

SECREDAS Work Plan and Deliverables


Work Package 1: User Scenarios

Coordinator: IMEC-Belgium (IMEC-B)

WP1 will study a number of user scenarios, which are relevant for SECREDAS to cover the intertwining of security, safety and privacy protection. The study will be used in order to derive future reference architectures and requirements (input to WP 2), develop common technology elements (input to WP3).
The output will be:

  • • a reference set of user scenarios for future technical developments, demonstrations and assessment/certification of new components;
  • • impact assessment of user scenarios on new components;
  • • translation of user scenarios into demonstrations;
  • • organisation of use-case workshop with other EU pilot projects.

Work Package 2: Reference Architecture & Requirements

Coordinator: IDEMIA (IDEMIA)

WP2 will provide an analysis of the Safety, Security and Privacy requirements needed for the design, implementation and evaluation of the SECREDAS uses cases.
The output will be:

  • • identification and analysis of privacy, safety and security goals and requirements;
  • • a security model;
  • • security and privacy Reference-Architecture;
  • • supervisor Architecture for Mitigating Safety and Security Issues.

Work Package 3: Common Technology Elements

Coordinator: IMEC-Belgium (IMEC-B)

The main objectives are to (1) develop and validate a number of common technology elements for the reference architectures and (2) develop a framework for multi-concerned security-safety verification and testing. Common technology elements will be provided/enhanced and design patterns created to support the development of technical security measures, maintaining functional safety, privacy and operational performance.
The output will be:

  • • improvement of Common Technology Elements;
  • • New design patterns, including Safety, Security and Privacy analysis;
  • • security testing framework.

Work Package 4: Vehicle Sensing

Coordinator: IMEC-Belgium (IMEC-B)

The objective in this Work package is to design, develop and verify appropriate cyber-security and safety in sensor and pre-processing systems required in ADAS/AD/connected vehicles.
The output will be:

  • • selected sensor, components and sensor data processing algorithms and computing platforms for ADAS applications;
  • • Sensors and Components used for ADAS/AD;
  • • design and integration of the central sensor fusion system architecture;
  • • sensor System Integration and Validation.

Work Package 5: Vehicle connectivity

Coordinator: YoGoKo

The objectives in this Work package are to integrate security building blocks necessary to protect the external interfaces linking the vehicle to the external environment. Specifically: protect the vehicle against security breaches
related to communication flows with other vehicles and the roadside infrastructure (V2X), IoT and sensor devices interacting with the vehicle.
The output will be:

  • • map of high-level security features into the ITS station reference architecture;
  • • integration of security features developed in WP3 an existing V2X communication stack complying with Cooperative ITS standards;
  • • integration of security features developed in WP3 into an existing communication stack providing extended connectivity to the cloud complying with Cooperative ITS standards;
  • • increased safety and privacy of IoT devices integrated in vehicles;
  • • a prototype of a radar/5G component capable of operating in the 76-81 GHz frequency band;
  • • security testing & performance validation.

Work Package 6: In-vehicle networking & VCU

Coordinator: NXP Semiconductors Netherlands

This work package provides the hardware and software foundation for running
the Use Scenarios from the other WP’s in an automotive product. The work centres around the following components: data processing, In-vehicle networking devices, VCU electrical controller.
The output will be:

  • • development of data processing components that run on or with the hardware components created in Task 6.2 and Task 6.3;
  • • development of (hardware) components that take care of the networking within the car. This covers the ‘heart’ of the car networking in the car between sensors, processing units and actuators (but not networking between the car and the outside world);
  • • development of highly secured VCU electronic controller components;
  • • VCU electronic controller module development and validation.

Work Package 7: Health

Coordinator: Philips

The objectives in this Work package are to integrate the secure architecture
and common technology elements into a personal health demonstrator using wearables. The WP will contribute to a multi domain demonstrator to enable enhanced cruise control by monitoring the driver and measure the driver performance to enhance the safety of (semi) autonomous driving.
The output will be:

  • • creation of a secure connection between wearables and via a gateway;
  • • sensing devices and algorithms for driver health monitoring;
  • • demonstrator development;
  • • user acceptance tests.

Work Package 8: Rail

Coordinator: Thales

The objectives in this Work package are to assess cyber security and safety critical components from WP2 and WP3 for the railway domain.

The output will be:

  • • Identification of requirements for safety and security layers for the railway domain;
  • • component specification and concept development involving common security technologies and reference architectures;
  • • Component integration and validation.

Work Package 9: Common demonstrators

Coordinator: IMEC-Belgium (IMEC-B)

The objectives in this Work package are to demonstrate software and hardware solutions on key User Scenarios. Five scenarios will undergo field-testing: Road Intersection, Automated truck with driver getting health problems, Updating the vehicle, Advanced Access to Vehicle & Rail.
The output will be three full demonstrators at selected experimentation locations on:

  • (1) Autonomous driving and infrastructure servers,
  • (2) Driver Monitoring Systems and
  • (3) Cybersecurity and connectivity.

Work Package 10: Standardisation, Qualification & Certification

Coordinator: AIT

The objectives in this Work package are to:

  • • analyze involvement in standardization activities and current use of standards by partners;
  • • analyze the applicability of current security, safety and communication (ITS) standards and initiatives for the targeted domains;
  • • disseminate new project findings to standardization, trying to influence or initiate standards;
  • • develop guidelines for continuous multi-concern (safety and security) certification including assessment methods.

Work Package 11: management, Dissemination & Exploitation

Coordinator: NXP Semiconductors Netherlands

The objectives in this Work package are to implement the management of the project and the communication towards the outside world and the multiple stakeholders in the outcome of the project. The work also includes the development of the strategy towards specific activities on exploitation, dissemination and risk monitoring & mitigation.
In addition to project management, the output of this work package will be:

  • • initiating and organising various multi-Stakeholder Dialogues for further commercial uptake or policy development on autonomous systems;
  • • presenting SECREDAS and partner findings at conferences, fairs and through publications and outreach activities.
❮ ❯

Project Partners

The SECREDAS consortium consists of 70 partners from 16 countries. It is well balanced in terms of research – industry – public sector collaboration:
View all

Large industry: 22
SMEs: 23
Universities: 9
Research Institutes: 14
Public sector: 2

Austria
Belgium
Czech Republic
Finland
France
Germany
Greece
Hungary
Italy
Netherlands
Poland
Portugal
Romania
Spain
Sweden
Tunisia




our Latest News

Lorem ipsum dolor sit amet
20 Jan 2017

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin sed augue nulla. Maecenas sit amet ligula est. Fusce fringilla sollicitudin enim in varius. Praesent nisi neque, condimentum sit amet lacus inLorem ipsum dolor sit amet,

Read more

this is an image post
20 Jan 2017

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry’s standard dummy text

Read more

Praesent nisi neque, condimentum
20 Jan 2017

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry’s standard dummy text

Read more

get our latest news, subscribe to our newsletter!

Let us know what you think!