IoT

Available (161)

Showing 25 - 36 per page



Discussion of alignment of standardisation deliverables with (EU) Common Criteria

Body

I propose to start discussing cybersecurity standardisation deliverables from the perspective of Common Criteria for Information Technology Security Evaluation (CC v3.1), in particular with respect to the EUCC - the ENISA cybersecurity certification scheme proposed for ICT products, and therefore including IoT, which is currently in preparation.

Problem definition

Given the complexity of the consumer IoT cybersecurity issue, it seems reasonable to expect different approaches that may lead to different solutions. Also considering that no overarching institution / organisation / body has authority when dealing with global IoT ecosystems, a fragmented approach is natural and probably unavoidable under the circumstances.

However, the fragmentation of the cybersecurity processes leads to inefficient use of resources and, very likely, to insufficient coverage of threatened or at risk products.

Proposed examination for a solution

It is therefore useful to analyse and align standardisation deliverables related to cybersecurity, with the aim of reducing fragmentation of the approach to cybersecurity evaluation and certification.

Background information

The EUCC is based on the Common Criteria which is an Information Technology Security evaluation method. The latest revision of the Common Criteria was published in 2017 with supporting contributions from a number of governmental organisations, representing among others EU member states like France, Germany, Netherlands, Spain, and Sweden. According to the Common Criteria Foreword version 3.1 (CC v3.1), it aims to:

  • eliminate redundant evaluation activities; reduce/eliminate activities that contribute little to the final assurance of a product;
  • clarify CC terminology to reduce misunderstanding;
  • restructure and refocus the evaluation activities to those areas where security assurance is gained; and add new CC requirements if needed.

In the EU, ENISA is responsible for the EUCC scheme (Common Criteria based European candidate cybersecurity certification scheme) which looks into the certification of ICT products cybersecurity, based on the Common Criteria, the Common Methodology for Information Technology Security Evaluation, and corresponding standards, respectively, ISO/IEC 15408 and ISO/IEC 18045.

In the document “Council of the European Union conclusions on the cybersecurity of connected devices from 2 December 2020”, it is emphasised that any certification scheme for connected devices and related services should specify how the applicable security requirements at the relevant assurance level should be met on the basis of specific European and internationally recognised standards.

Further explanation of the Common Criteria is given on their website, as follows.

The Common Criteria for Information Technology Security Evaluation (CC), and the companion Common Methodology for Information Technology Security Evaluation (CEM) are the technical basis for an international agreement, the Common Criteria Recognition Arrangement (CCRA), which ensures that:

- Products can be evaluated by competent and independent licensed laboratories so as to determine the fulfilment of particular security properties, to a certain extent or assurance;

- Supporting documents, are used within the Common Criteria certification process to define how the criteria and evaluation methods are applied when certifying specific technologies;

- The certification of the security properties of an evaluated product can be issued by a number of Certificate Authorizing Schemes, with this certification being based on the result of their evaluation;

- These certificates are recognized by all the signatories of the CCRA.

The CC is the driving force for the widest available mutual recognition of secure IT products.

 

Groups

IETF 113 Meeting Will Take Place In March 2022

Body

The Internet Engineering Task Force (IETF) is an international Standards Developing Organization that work in the development and standardization of Internet protocols. The IETF is open to any interested individual. The next IETF meeting is called IETF 113. The IETF 113 starts Saturday 19 March and runs through Friday afternoon, 25 March.

More Information, registration, agenda: https://www.ietf.org/how/meetings/113

Groups

IoT Routing at the IETF

Body

Routing Over Low power and Lossy networks (roll) working group at the IETF, is the working group in charge of developing routing standards for constrained environments, oriented to use cases such as smart home, smart cities and industry 4.0. The Working Group focus on routing issues in IPv6 for Low power and Lossy networks, maintaining and improving the protocols already developed, including RPL and MPL. The Participation is open to any individual.
Charter: https://datatracker.ietf.org/wg/roll/about/
To Subscribe: http://www.ietf.org/mailman/listinfo/roll

Groups

IETF 112 Meeting will take place in November 2021

Body

The Internet Engineering Task Force (IETF) is an international Standards Developing Organization that work in the development and standardization of Internet protocols. The IETF is open to any interested individual. The next IETF meeting is called IETF 112. The IETF 112 will start on Monday, 8 November 2021 and run through Friday afternoon, 12 November 2021. Sessions will from 12:00-18:00 UTC each day.

More Information, registration, agenda: https://www.ietf.org/how/meetings/112/

IETF 112 Newcomers: https://www.ietf.org/how/meetings/112/newcomers/

IoT in the IETF: https://www.ietf.org/topics/iot/

 

Groups

M-Sec Project Online Contest

Body

Are you a company, university student, researcher, data scientist, entrepreneur or a concerned citizen?

Do you have an innovative earlystage business idea that addresses a smartcity challenge? ?‍? Are you interested in security and privacy issues of iot devices and apps? ??

Then don't miss this chance and apply by 26 August 5pm CET to M-Sec Project Online Contest, that will run between 6-10 September ? 
https://lnkd.in/ecfRk7b

Main perks:
??‍? 1-1 Technical and business support to develop your business idea
✍? Business workshop
? Present the business idea to an international panel of experts

Top 3 winners of each challenge will also have the chance to meet city council representatives of Santander and Fujisawa #smartcities

Guidelines and more info ?‍♀️
https://lnkd.in/eXS85QN

#msecsmarthack

Groups

M-Sec EU & Japanese IoT citizens and stakeholders’ consultation preliminary results

Body

At the end of 2020, the M-Sec Project launched a survey to the European and Japanese IoT community, to better understand their experience when using IoT devices and applications and on their knowledge of EU & Japan’s data protection regulations. 6 months after, and with more than 450 answers, here are the first insights from our community: https://www.msecproject.eu/m-sec-eu-japanese-consultation-preliminary-results/  

Groups

Secure Real-time environmental data and garbage counting system – promoting environmental awareness in an urban context

Body

Dear community, the M-Sec Project is currently implementing 5 pilots to test, validate and showcase the impact of its cybersecurity solution. Learn more about M-Sec’s Use Case 3 to better understand how this Use Case is being implemented in the Japanese city of Fujisawa.

Groups

SmileCity Report platform – a secure app through which citizens can showcase affective information on a city event

Body

Dear community, the M-Sec Project is currently implementing 5 pilots to test, validate and showcase the impact of its cybersecurity solution. Learn more about M-Sec’s Use Case 4 to better understand how this Use Case is being implemented in the Japanese city of Fujisawa.

Groups

Context Information Management (CIM); NGSI-LD Testing Framework: Test Template

The Testing Framework (document format) specifies a testing framework defining a methodology for the development of the test strategies, test systems and resulting test specifications. The present document identifies the implementation under test (scope of the testing), the format for the test specification, the test architecture, the points of control and observation, the naming conventions (e.g. for test case ID and test case grouping ID), etc. It also provides the Implementation Conformance Statement which is basically a checklist for a client-owner so they know what parts of the specification will be tested and if any is optional. The ICS will be published as a separate GS.

ETSI GS CIM 016 V1.1.1