Ontology-Based Knowledge Representation in the IoT Cybersecurity System

Tracking #: 3523-4737

Authors: 
Anna Bryniarska
Waldemar Pokuta

Responsible editor: 
Rafael Goncalves

Submission type: 
Application Report
Abstract: 
The use of Semantic Web in cybersecurity systems is becoming more and more popular. This is an important problem, especially in times when IoT systems are developing very quickly and and their security must be maintained. Thanks to the semantic web, it is possible to store and process cybersecurity knowledge using ontology. We describe a system for analyzing the level of cybersecurity among Polish citizens, in particular Internet of Things (IoT) users. An ontology-based knowledge representation related to the security level was created for the described system. The ontology contains the information necessary to determine the security level in different locations and to conduct deeper analysis. It has been prepared for the needs of the IoT system for storing data and knowledge. The described Semantic Web application is part of a larger project that allows to determine cyber security and cyber threats of IoT devices.
Full PDF Version: 
Tags: 
Reviewed

Decision/Status: 
Major Revision

Solicited Reviews:
Click to Expand/Collapse
Review #1
Anonymous submitted on 29/Aug/2023
Suggestion:
Minor Revision
Review Comment:

This manuscript presents an 'Application Report' that focuses on the use of Semantic Web technologies in the field of IoT cybersecurity. The paper addresses the importance and relevance of this application through well-structured discussions. The authors successfully demonstrate the potential impact of ontology-based knowledge representation in enhancing the cybersecurity of IoT systems.

The clarity and readability of the paper are commendable. The key ideas regarding the application of Semantic Web technologies are effectively conveyed to the reader. The paper presents convincing evidence of the quality and impact of the described application, supported by relevant references and conceptual frameworks.

The data file provided by the authors under the "Long-term stable URL for resources" has been assessed. The provided resources are well-organized and appear to be complete for the replication of experiments. The README file enhances the accessibility and understandability of the data artifacts.

The chosen repository for the data file is appropriate for long-term repository discoverability. The authors have made adequate efforts to ensure the completeness of the provided data artifacts.

In conclusion, this 'Application Report' provides a comprehensive overview of the use of Semantic Web technologies in IoT cybersecurity. The manuscript is well-structured, clear, and impactful. The authors have successfully met the criteria outlined for the review of this application. It is recommended that the paper be accepted with minor revisions.

Review #2
By Tarek Elsaleh submitted on 31/Jul/2024
Suggestion:
Major Revision
Review Comment:

The paper presents an application for cybersecurity among citizens in the IoT domain, which relies on monitoring IoT devices in the vicinity of mobile devices hosting the application. An ontology is presented that models aspects relating to device characteristics and knowledge extracted from assessing and grouping the scanned devices. The application is quite interesting, but the justification for using Semantic Web technologies is not clear, as the application appears to be a closed system.

Paper overall is well-written, but the data (i.e. ontology) needs to be reviewed. Ontology annotations are quite minimal, which makes it harder to follow.

Ontology:
Datatype properties need to be better classified. There are too many direct sub-properties under each "Level" which should be added further down the hierarchy. Please refer to Ontology Development 101: A Guide to Creating Your First Ontology (subsection on "How many is too many and how few are too few?").

An example approach would be:

hasLevel1Score
hasCveCvssTotalScore
hasEcCouncilAttack
hasPhaseDetectedClearingTracks
hasPhaseDetectedGainingAccess
...
hasGdpr
hasBiometricDataBreachProbability
hasCrossBorderProcessingProbability
...

N.B: this is just an example.

The ontology does not reuse any vocabulary form other ontologies, which indicates there is not much effort towards interoperability.

Section 6: what are the characteristics that represent a granule? are they defined?

Line 40: (Grammar) "you can use the free OntoMetrics tool...". Please change to either "we used..." or "...was used".

In section 5, please provide a discussion or reflection on the metrics used to evaluate the ontology, not just stating them. Are there any concerns or possible improvements, or suggestions on how to evolve the ontology? What impact do these metrics have on the system when it comes to storage and querying?

Overall, what are the benefits of converting information to SW specifically for the application, sine it appears to be a closed system? This needs to be clear in the paper.