MITRE EMB3D: Library & CLI for working with the MITRE EMB3D framework.
Project description
MITRE EMB3D
A CLI, TUI & MCP Server for https://emb3d.mitre.org/
Run
Via uvx
uvx mitre-emb3d --help
or
uvx --from mitre-emb3d med --help
uvx --from mitre-emb3d med --pprint properties Networking --level 3
Add to your project
The project can be used both as a tool & library
uv add mitre-emb3d
Features
4 MITRE EMB3D Categories -
- Hardware
- System Software
- Application Software
- Networking
What you can do (via library, CLI and MCP Server)
- List device properties for a given category
- List threats for a given category
- List mitigations for a given threat
- Get detailed information about a threat
- Get detailed information about a mitigation
- A CLI - AI Agent first (returns JSON output) / For humans add
--pprintto see beautiful ouput - A TUI - Heatmap creation, reading & update (See TUI section below for screenshots)
- An MCP Server
- ... more coming
CLI Interface
Example -
$ uv run med --pprint list-threats-for-category "Networking"
- TID-221: Authentication Bypass By Message Replay
- TID-222: Critical System Service May Be Disabled
- TID-310: Remotely Accessible Unauthenticated Services
- TID-316: Incorrect Certificate Verification Allows Authentication Bypass
- TID-317: Predictable Cryptographic Key
- TID-318: Insecure Cryptographic Implementation
- TID-401: Undocumented Protocol Features
- TID-404: Remotely Triggerable Deadlock/DoS
- TID-405: Network Stack Resource Exhaustion
- TID-406: Unauthorized Messages or Connections
- TID-407: Missing Message Replay Protection
- TID-408: Unencrypted Sensitive Data Communication
- TID-410: Cryptographic Protocol Side Channel
- TID-411: Weak/Insecure Cryptographic Protocol
- TID-412: Network Routing Capability Abuse
Note --pprint (default is OFF, default output is JSON) for display
Explore other commands using the CLI help
Usage: med [OPTIONS] COMMAND [ARGS]...
╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --release TEXT 2.0.1, 2.0 ... [default: 2.0.1] │
│ --heatmap-storage [json] Storage type for heatmaps (e.g. json) [default: json] │
│ --loglevel -l TEXT Set the logging level (debug, info, warning, error, critical) [default: warning] │
│ --pprint --no-pprint Whether to pretty-print the output (e.g. JSON lists) [default: no-pprint] │
│ --install-completion Install completion for the current shell. │
│ --show-completion Show completion for the current shell, to copy it or customize the installation. │
│ --help Show this message and exit. │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ list-categories List the categories │
│ list-properties List properties for a certain category │
│ list-threats-for-category List threats for a certain category │
│ list-threats-for-property List threats for a certain device property │
│ list-mitigations List mitigations for a certain threat │
│ threat Threat Information │
│ mitigation Mitigation Information │
│ mcp Launch the MCP server │
│ heatmap HeatMap related commands │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Heatmap TUI
You can use TUI to inspect & edit the Heatmap
# Make sure to initialize the heatmap
uvx mitre-emb3d heatmap init "Project Name" "Description of Project" --output-dir .
- Above command will create
mitre-emb3d-heatmap.jsonfile in the specified output directory - All the entries in the heatmap are set to NOT_INVESTIGATED
# Show the current state (and edit) using TUI
uvx mitre-emb3d heatmap tui mitr-emb3d-heatmap.json
Clicking on Threat Entry will open a screen that presents a Form, Information about Threat & Mitigations
MCP Server
At the moment only STDIO is supported
For your mcp.json add the server like this
{
"servers": {
"mitre-emb3d": {
"command": "uvx",
"args": ["mitre-emb3d", "mcp"]
}
}
}
Use mcp inspector to play with the MCP Server
npx -y @modelcontextprotocol/inspector uvx mitre-emb3d mcp
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file mitre_emb3d-0.3.2.tar.gz.
File metadata
- Download URL: mitre_emb3d-0.3.2.tar.gz
- Upload date:
- Size: 192.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6cef3cbdbb1c67be95fdcd0219146a2ae5f4814720f6cd13fac667fca83da5ee
|
|
| MD5 |
b06ca747ae46428491ff9d9260828bc2
|
|
| BLAKE2b-256 |
72efb9d40cf90c710e263d6480bcdaad7340ae8f0a7a6d596e93e9dbe20241a8
|
Provenance
The following attestation bundles were made for mitre_emb3d-0.3.2.tar.gz:
Publisher:
publish.yaml on ksachdeva/mitre-emb3d
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
mitre_emb3d-0.3.2.tar.gz -
Subject digest:
6cef3cbdbb1c67be95fdcd0219146a2ae5f4814720f6cd13fac667fca83da5ee - Sigstore transparency entry: 1092036679
- Sigstore integration time:
-
Permalink:
ksachdeva/mitre-emb3d@ed4395a37d534e26964dd372075f0cfd9abc1c79 -
Branch / Tag:
refs/tags/0.3.2 - Owner: https://github.com/ksachdeva
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yaml@ed4395a37d534e26964dd372075f0cfd9abc1c79 -
Trigger Event:
release
-
Statement type:
File details
Details for the file mitre_emb3d-0.3.2-py3-none-any.whl.
File metadata
- Download URL: mitre_emb3d-0.3.2-py3-none-any.whl
- Upload date:
- Size: 29.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.7
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
7f43cf53673afe458d236b86dad2047e58bb1fefba61a1ea8abb51f61b36e87f
|
|
| MD5 |
6d07b2c37192e969d0ff2cc0fe324432
|
|
| BLAKE2b-256 |
6f844ddb75d4d65be89aa77cb943a43e95d66be7ce403f9c98765fd0d5227a2d
|
Provenance
The following attestation bundles were made for mitre_emb3d-0.3.2-py3-none-any.whl:
Publisher:
publish.yaml on ksachdeva/mitre-emb3d
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
mitre_emb3d-0.3.2-py3-none-any.whl -
Subject digest:
7f43cf53673afe458d236b86dad2047e58bb1fefba61a1ea8abb51f61b36e87f - Sigstore transparency entry: 1092036684
- Sigstore integration time:
-
Permalink:
ksachdeva/mitre-emb3d@ed4395a37d534e26964dd372075f0cfd9abc1c79 -
Branch / Tag:
refs/tags/0.3.2 - Owner: https://github.com/ksachdeva
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yaml@ed4395a37d534e26964dd372075f0cfd9abc1c79 -
Trigger Event:
release
-
Statement type: