Detect Tactics, Techniques & Combat Threats
 
 
 
 
 
 
Go to file
Marcus Bakker 6d9aafcb68 Updated all packages 2020-05-14 15:37:04 +02:00
editor Updated all packages 2020-05-14 15:37:04 +02:00
sample-data Changed the platform and/or added some comments 2020-02-10 07:39:11 +01:00
threat-actor-data Added intel from CrowdStrike, Red Canary and Recorded Future 2020-04-07 15:03:48 +02:00
.dockerignore name change 2020-03-04 10:45:00 +01:00
.gitignore Added multiple entries for the DeTT&CT Editor 2020-03-17 14:38:05 +01:00
Dockerfile changed the base image to python:3.8-slim-buster 2020-05-12 15:37:14 +02:00
LICENSE initial commit 2019-03-29 15:26:25 +01:00
README.md Readme small update 2020-05-13 10:47:19 +02:00
constants.py Bumped the version to 1.3 2020-02-21 07:53:12 +01:00
data_source_mapping.py bugfix on filtering data sources 2020-03-16 10:29:30 +01:00
dettect.py editor rename, print message when running editor.py 2020-03-10 08:48:03 +01:00
editor.py editor rename, print message when running editor.py 2020-03-10 08:48:03 +01:00
eql_yaml.py Made the date kv-pairs compatible with the YAML GUI 2020-02-10 21:57:35 +01:00
generic.py bugfix for using lowercase platform in data source yaml file, bugfix for having empty score logbook in techniques yaml file, small code style improvement 2020-03-03 14:49:19 +01:00
group_mapping.py Another fix for when 'software_id' is not present in a group YAML file 2020-01-30 16:28:46 +01:00
health.py bug fix 2020-03-04 10:45:06 +01:00
interactive_menu.py Several small changes in some text. 2019-12-11 10:43:08 +01:00
requirements.txt new version of attackcti and taxii2-client 2020-04-03 16:27:21 +02:00
scoring_table.xlsx Several small changes in some text. 2019-12-11 10:43:08 +01:00
technique_mapping.py Mapped data sources to platforms 2020-02-10 12:17:00 +01:00
upgrade.py Added an extra check for a possible empty 'comment' key-value pair. 2019-08-20 11:13:25 +02:00

README.md

DeTT&CT

Detect Tactics, Techniques & Combat Threats

Latest version: 1.3

To get started with DeTT&CT, check out this page, our talk at hack.lu 2019 and our blog on:

DeTT&CT aims to assist blue teams using ATT&CK to score and compare data log source quality, visibility coverage, detection coverage and threat actor behaviours. All of which can help, in different ways, to get more resilient against attacks targeting your organisation. The DeTT&CT framework consists of a Python tool, YAML administration files, the DeTT&CT Editor and scoring tables for the different aspects.

DeTT&CT provides the following functionality:

  • Administrate and score the quality of your data sources.
  • Get insight on the visibility you have on for example endpoints.
  • Map your detection coverage.
  • Map threat actor behaviours.
  • Compare visibility, detections and threat actor behaviours to uncover possible improvements in detection and visibility. This can help you to prioritise your blue teaming efforts.

The coloured visualisations are created with the help of MITRE's ATT&CK™ Navigator.

Authors and contributions

This project is developed and maintained by Marcus Bakker (Twitter: @bakk3rm) and Ruben Bouman (Twitter: @rubenb_2). Feel free to contact, DMs are open.

We welcome contributions! Contributions can be both in code, as well as in ideas you might have for further development, usability improvements, etc.

Work of others

Some functionality within DeTT&CT was inspired by the work of others:

Example

YAML files are used for administrating scores and relevant metadata. All of which can be visualised by loading JSON layer files into the ATT&CK Navigator (some types of scores and metadata can also be written to Excel).

See below an example of mapping your data sources to ATT&CK, which gives you a rough overview of your visibility coverage:

DeTT&CT - Data quality

Installation and requirements

See our GitHub Wiki: Installation and requirements.

License: GPL-3.0

DeTT&CT's GNU General Public License v3.0