We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ontology handler - FIWARE Forge Wiki

Ontology handler

From FIWARE Forge Wiki

Jump to: navigation, search


Brief description

The ontology handler serves as a knowledge base to store information relative to IS infrastructure and their associated security data using the Security Ontology. Each ontology instance corresponds to a version of a system and the vulnerabilities, threats, and safeguards that are related to its assets. These security data are retrieved from the Vulnerability DB. Finally, the ontology repository embeds mechanisms to create, save and retrieve instances of the Security Ontology and mechanisms to add, delete, and rename individuals and to set links between the individuals with predefined properties. These functionalities are exposed in an extern interface in order for other components to remotely manipulate ontologies.

Programming artifacts

Main entities are:

- Ontology: this class represents a specific instance of the security ontology. Its content can be manipulated on memory and persistence is maintained by storing it on hard drive.

- OntologyRepository: this entity represents the database containing all the instances of the Security Ontology. Ontology instances can only be created and accessed through this class.

- OntologyRepositoryHandlerInterface: this class is the interface containing all the services provided by the component.

- OntologyRepositoryHandlerImpl: this class is the implementation of the provided services.

- OntologyRepositoryServer: this class is responsible for initializing the repository and exposing its services so they can be remotely accessible.

- VulnerabilityCollecte: this class is responsible for accessing the Vulnerability DB, interrogating it with assets & CPEs, retrieving the corresponding XML file and adding the contained security data to the ontology instance. It is also in charge of parsing Vulnerability notifications and updating the ontologies with the provided data.

Technologies Used

The ontology repository has been implemented in Java. Jena and Jess libraries were used to manipulate ontologies. Its APIs were defined in accordance with the principles of the OSS/J specification. They are available remotely by means of a Web Service.

Runtime pre-requisites

Apache CXF


To be completed.

Publicly available documentation

To be completed.

Personal tools
Create a book