ROSE: A Reference Ontology for Security Engineering

ROSE is a well-founded reference ontology, specified in OntoUML modeling language, that characterizes the concept of security mechanism and explains how this notion is related to value, risk, and prevention.

PURL: https://purl.org/security-ontology

Project Structure

• /ontouml contains files related to the conceptual version of ROSE, which is represented in OntoUML.
• /owl contains files related to the gUFO-based implementation of ROSE, represented in OWL.

Reusing .vpp files

• To open and edit .vpp files, use Visual Paradigm
• To open and edit .ttl files, use Protégé

Built with

• Visual Paradigm - a UML CASE tool that offers a free community edition version
• The OntoUML Plugin for Visual Paradigm

Video presentation

Authors

• Ítalo Oliveira - Free University of Bozen-Bolzano, Bolzano, Italy
• Tiago Prince Sales - Free University of Bozen-Bolzano, Bolzano, Italy
• Riccardo Baratella - Free University of Bozen-Bolzano, Bolzano, Italy
• Mattia Fumagalli - Free University of Bozen-Bolzano, Bolzano, Italy
• Giancarlo Guizzardi - Free University of Bozen-Bolzano, Bolzano, Italy

References

• Baratella, R., Fumagalli, M., Oliveira, Í., Guizzardi, G. (2022). Understanding and Modeling Prevention. In: Guizzardi, R., Ralyté, J., Franch, X. (eds) Research Challenges in Information Science. RCIS 2022. Lecture Notes in Business Information Processing, vol 446. Springer, Cham. https://doi.org/10.1007/978-3-031-05760-1_23
• Oliveira, Í., Sales, T.P., Baratella, R., Fumagalli, M., Guizzardi, G. (2022). An Ontology of Security from a Risk Treatment Perspective. In: Ralyté, J., Chakravarthy, S., Mohania, M., Jeusfeld, M.A., Karlapalem, K. (eds) Conceptual Modeling. ER 2022. Lecture Notes in Computer Science, vol 13607. Springer, Cham. https://doi.org/10.1007/978-3-031-17995-2_26

Errata

For questions, commentaries, or reporting mistakes, feel free to use Issues.

• In ROSE, the cardinality of << characterization >> relation between Intention and subjects (Risk Subject, Attacker, Protected Subject, and Security Designer) should be 0...1, instead of 1, as it is written in the ER paper. This repository contains the corrected version.