efstratioslontzetidis/mitreattack_mapped_to_ckc_expressed_in_owl

This repository maps the ATT&CK Tactics to CKC Phases and expresses them in an OWL ontology for a research purpose.

MitreATT&CK_mapped_to_CKC_expressed_in_OWL

This repository maps the ATT&CK Tactics to CKC Phases and expresses them in an OWL ontology for a research purpose.

mitreattack_mapped_to_ckc_expressed_in_owl's Issues

Kill Chain Phases

The CKC phases needed to be created.

More hierarchies needed - between data elements

We need hierarchies between data elements as well as relationships between them.

See attached pic

Data Sources bug - they are now as data components

Check data-source, data-component and data-element classes

data-elements will not exist for now

Same name in Technique and Data Source leads to conflict

Technique T1592.003 has the same name with Data Source "Firmware". This leads to the Entity "Firmware" that is subclass of both data-source and attack-pattern.
Please see the screenshot below.
Solution: Create the hierarchy of techniques-subtechniques

Relate UCO artifacts to each technique and subtechnique

We need to relate from Protege the UCO specific artifacts needed for each technique based on MITRE ATT&CK description and data sources.

Relate data elements or data sources to uco artifacts

We need to relate data elements or data sources to uco artifacts

However, we first need to discuss if we need to relate the uco artifacts to data elements or the uco artifacts to data sources.

Tactics

Create Tactics classes and the ObjectProperties to their Techniques

We need to relate specific techniques to specific data-sources

The issue is that we relate attack-pattern entity to data-source entity.
This is not correct since this relationship is inherited by all attack-patterns and all data-sources.
We need to relate specific attack-patterns to specific data sources.
See the screenshot below

Relate Data Sources to Data Components

This relationship should be created.
So far it does not exist.