Skip to main content

MITRE DASH-board🏄🏽‍♂️

Update the MiTRE dashboard provided by HELK.

TLDR

This package loads the most recent data from the MITRE ATT&CK® framework and and converts it to parsable csv files.

In a second step the data can be parsed by logstash and imported into your elasticsearch instance. This step should be repeated in an interval of 3 month to keep your CTI up to date!

Additionally, you can upload the metadata of the HELK dashboard to your Kibana endpoint. This step is necessary only once and if the dashboard wasn't imported previously.

helkDashAll helkDashApt

Usage

Package installation

pip install mitre-dash

Get and process the latest Mitre data

attack_fetch

Optional flags:

  • --matrix_name to specify the matrix. Options are enterprise-attack, mobile-attack and ics-attack.
  • --include_subtechniques to include sub_techniques. This will result in a factor 10 increase in data size (20GB).
  • --include_detection to include detection methods. This is very verbose, will increase log size and might break logstash parsing due to special characters.
  • --include_descriptions to include descriptions of techniques, software, groups, etc. Same as above ⬆️.
  • --output_dir to specify the output directory. Default is ./output.
  • --help or -h to get help.

Import dashboard to Kibana

In total you will import:

  • 1 index pattern
  • 2 dashboards
  • a bunch of custom visualizations

Run:

attack_dash_up

Next you will be prompted to enter your Kibana host-address and credentials. We use the same script as the HELK to import the metadata.

⚠️ This step is only necessary once and if the dashboard wasn't imported previously!!!

Parse data with logstash

Now upload the new data to your elasticsearch instance:

attack_parse

Next you will be prompted to enter your elasticsearch host-address and credentials.

This will create a 'logstash' folder in your current directory with:

  • logstash.conf to parse the csv data.
  • docker-compose.yml to run logstash as a contained service.
  • .env to facilitate the provided credentials.

Finally two parallel processes will be started:

  • docker-compose up to run logstash.
  • nc <logstash-host> 32173 -q 11 < output/<attack-matrix>.csv to send the data to logstash.

The second process is repeated for every attack matrix csv file in the output folder.

⚠️ Prepare for a long ride. Get some popcorn while 13M logs are ingested 🍿

Metadata

Release files for attack-dashboard 0.11.11

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for attack-dashboard 0.11.11
File Size Uploaded Provenance Actions
attack_dashboard-0.11.11.tar.gz 19.5 kB Without provenance Details for attack_dashboard-0.11.11.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for attack-dashboard 0.11.11
File Interpreter ABI Platform Actions
attack_dashboard-0.11.11-py3-none-any.whl Python 3 none any Details for attack_dashboard-0.11.11-py3-none-any.whl

Total release size: 56.6 kB

Release files / attack_dashboard-0.11.11.tar.gz

Download URL attack_dashboard-0.11.11.tar.gz
Size 19.5 kB
Tags Source
SHA-256 checksum
How to use checksums
e24fa811d5f5d36bf4cbf6b22c5cb5fabeec24b239a6b10e20ed41c564b30da3
BLAKE2b-256 checksum
How to use checksums
ee46e5e82e620f9f615d52df066ac82d72937ccf8b648a7020a1d164fdcf24c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Linux/5.15.90.1-microsoft-standard-WSL2

Release files / attack_dashboard-0.11.11-py3-none-any.whl

Download URL attack_dashboard-0.11.11-py3-none-any.whl
Size 37.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6d4c710f9fbec654f6a572bb74227bebc646d3adfb361cadea99c49b3e28fee7
BLAKE2b-256 checksum
How to use checksums
f982ac8ec7683926ea9e3b44e1fa267a08a9242d75d3263e08be0c2a84fa4407
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.11.3 Linux/5.15.90.1-microsoft-standard-WSL2

Security for attack-dashboard 0.11.11

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page