countermap 0.2.0__tar.gz

countermap-0.2.0/.claude-plugin/marketplace.json

@@ -0,0 +1,14 @@
+{
+  "name": "countermap",
+  "owner": {
+    "name": "Diego Parra"
+  },
+  "description": "Countermap for Claude Code: a cross-framework MCP server and skills for MITRE ATT&CK®, D3FEND, ATLAS and F3.",
+  "plugins": [
+    {
+      "name": "countermap",
+      "source": "./plugin",
+      "description": "Query MITRE ATT&CK®, D3FEND, ATLAS and F3 with provenance on every cross-framework link, and turn incidents into D3FEND CAD, Attack Flow, Navigator and Mermaid threat models."
+    }
+  ]
+}

countermap-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: pytest -q

countermap-0.2.0/.github/workflows/upstream-sync.yml

@@ -0,0 +1,75 @@
+name: upstream-sync
+
+# Nightly: check MITRE upstreams against sources.lock.json. When something changed,
+# build against the new data, run the tests and a live smoke test, then open a PR
+# with the new lock file and a summary of what changed. Nothing merges automatically.
+
+on:
+  schedule:
+    - cron: "17 6 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[dev]"
+
+      - name: Compare upstream to lock
+        id: check
+        run: |
+          set +e
+          countermap check-updates --lock sources.lock.json > changes.json
+          code=$?
+          cat changes.json
+          echo "code=$code" >> "$GITHUB_OUTPUT"
+          if [ "$code" != "0" ] && [ "$code" != "10" ]; then exit "$code"; fi
+
+      - name: Build and test against new upstream data
+        if: steps.check.outputs.code == '10'
+        run: |
+          cp sources.lock.json /tmp/old.lock.json
+          countermap lock -o sources.lock.json
+          countermap --db /tmp/new.db build --lock sources.lock.json
+          countermap --db /tmp/new.db info > /tmp/info.json
+          countermap --db /tmp/new.db lookup T1003.001 > /dev/null
+          pytest -q
+          pytest -q -m live
+          if countermap --db /tmp/old.db build --lock /tmp/old.lock.json; then
+            countermap diff /tmp/old.db /tmp/new.db --limit 25 > upstream-diff.json
+          else
+            echo '{"note": "previous data no longer downloadable; no diff"}' > upstream-diff.json
+          fi
+          python - <<'EOF'
+          import json
+          changes = json.load(open("changes.json"))["changes"]
+          diff = json.load(open("upstream-diff.json"))
+          warnings = json.load(open("/tmp/info.json"))["warnings"]
+          lines = ["## Upstream changes", ""]
+          lines += [f"- `{c['key']}`: {c.get('locked')} -> {c.get('latest')}" for c in changes]
+          if "added" in diff:
+              lines += ["", "## ATT&CK diff (counts)", ""]
+              for k in ("added", "removed", "newly_revoked", "newly_deprecated", "renamed", "tactic_changed"):
+                  lines.append(f"- {k}: {diff[k]['count']}")
+          lines += ["", "## Build warnings", ""] + [f"- {w}" for w in warnings]
+          open("pr-body.md", "w").write("\n".join(lines) + "\n")
+          EOF
+          rm -f changes.json upstream-diff.json
+
+      - name: Open pull request
+        if: steps.check.outputs.code == '10'
+        uses: peter-evans/create-pull-request@v8
+        with:
+          commit-message: "Update upstream sources lock"
+          branch: upstream-sync
+          title: "Upstream MITRE data changed"
+          body-path: pr-body.md
+          add-paths: sources.lock.json

countermap-0.2.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+venv/
+dist/
+build/
+.pytest_cache/
+*.db
+*.db.building
+out/
+pr-body.md

countermap-0.2.0/.vscode/mcp.json

@@ -0,0 +1,9 @@
+{
+  "servers": {
+    "countermap": {
+      "type": "stdio",
+      "command": "countermap",
+      "args": ["serve"]
+    }
+  }
+}

countermap-0.2.0/CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog
+
+Notable changes to Countermap, a local, read-only knowledge graph and MCP server for MITRE ATT&CK®, D3FEND, ATLAS and F3.
+
+## 0.2.0 (2026-10-19)
+
+The first public release.
+
+### Added
+
+- A local SQLite knowledge graph of ATT&CK (Enterprise, Mobile, ICS), D3FEND, ATLAS and F3, served read-only to AI agents over MCP (14 tools) and to people through the `countermap` CLI: search, lookup by ID, name or alias, technique context, D3FEND countermeasures with artifact paths, ATLAS and F3 crosswalks to ATT&CK, actor techniques and comparison, coverage gaps and Navigator layers.
+- Provenance on every cross-framework link: `official` when MITRE published it, `derived` when Countermap composed it at query time (with the `via` path it took), and `analyst` when a scenario asserts it. An empty D3FEND result says whether D3FEND has no mapping for the technique or predates it.
+- Upstream data checks: links that point at revoked, deprecated or missing objects are reported as build warnings and flagged in results.
+- Reproducible builds: a lock file pins each upstream release by URL and SHA-256 (`countermap lock`, `countermap build --lock`), any source can come from a mirror or a local file, and `countermap check-updates` reports when an upstream release has moved past the lock. A scheduled `upstream-sync` GitHub Actions workflow runs that check and opens a pull request with the new lock.
+- `render_scenario` (MCP) and `countermap render` (CLI): one scenario spec, checked against the loaded data, renders a D3FEND CAD graph, an Attack Flow 2.0 bundle, ATT&CK Navigator layers (including F3's Navigator domain) and a Mermaid diagram. The CAD graph and the Attack Flow bundle are validated against their published schemas. Results list the ATT&CK mitigations (`step_mitigations`) and detection strategies (`step_detections`) MITRE links to each step, and the Navigator tooltips carry them too.
+- ATT&CK's detection model: detection strategies, analytics with their log sources and tunables, and data components, through `lookup` and `technique_context`. Campaigns carry their first and last seen dates.
+- `telemetry_coverage` (MCP) and `countermap coverage` (CLI): given the log sources and data components you collect, each technique of a list, an actor or a platform is classified as covered, partial, blind, no analytic for the platform, or no detection strategy, against MITRE's analytics, with an optional Navigator layer.
+- `rule_coverage` (MCP) and `countermap rules-coverage` (CLI): given the ATT&CK IDs a ruleset maps to, each in-scope technique is classified as covered, partial or uncovered, and the gaps are ranked by how many groups ATT&CK links to them. The CLI can read the IDs from the tags of a folder of Sigma rules.
+- `version_diff` (MCP) and `countermap diff` (CLI): objects added, removed, revoked, deprecated, renamed or moved between tactics since the previous build.
+- A Claude Code plugin with two skills: `countermap` teaches the tools and the provenance rules, and `/countermap:threat-model` turns an incident or report into a mapped scenario with mitigations, detections, countermeasures, gaps and diagram files. It starts the server from PyPI with `uvx countermap@0.2.0`.
+- `docs/ARCHITECTURE.md`: the design, the provenance and coverage rules, the upstream sources and the maintenance runbook.
+
+### Notes
+
+- Built and tested against ATT&CK 20.0, F3 1.2, ATLAS 2026.09 and D3FEND 1.6.0, as pinned in `sources.lock.json`.
+- Requires Python 3.10 or newer, and installs with pip, pipx or uvx.
+- The package license is `Apache-2.0 AND BSD-3-Clause`, because the package ships 12 OASIS STIX 2.1 schemas for offline validation. `NOTICE` lists MITRE's attributions and trademarks.

countermap-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

countermap-0.2.0/LICENSES/BSD-3-Clause-OASIS.txt

@@ -0,0 +1,27 @@
+Copyright (c) [2016], OASIS Open
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+* Neither the name of the copyright holder nor the names of its
+  contributors may be used to endorse or promote products derived from
+  this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

countermap-0.2.0/NOTICE

@@ -0,0 +1,40 @@
+Countermap
+Copyright 2026 Diego Parra
+Licensed under the Apache License, Version 2.0 (see LICENSE). The vendored files
+listed below keep their own licenses.
+
+Countermap is an independent project. It is not affiliated with, sponsored by or
+endorsed by The MITRE Corporation, the MITRE Center for Threat-Informed Defense
+or the National Security Agency.
+
+MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation.
+D3FEND, ATLAS, MITRE Fight Fraud Framework and F3 are trademarks or registered
+trademarks of The MITRE Corporation.
+
+Data processed by this software (downloaded at build time, not redistributed in
+this repository or its packages):
+
+- MITRE ATT&CK (https://attack.mitre.org), (c) The MITRE Corporation. Used under
+  the ATT&CK Terms of Use:
+  https://attack.mitre.org/resources/legal-and-branding/terms-of-use/
+- MITRE D3FEND (https://d3fend.mitre.org), (c) The MITRE Corporation. MIT License;
+  the D3FEND Terms of Use also apply.
+- MITRE ATLAS (https://atlas.mitre.org), (c) The MITRE Corporation. Apache License 2.0.
+- MITRE Fight Fraud Framework (F3) (https://ctid.mitre.org/fraud/), (c) The MITRE
+  Corporation. Apache License 2.0.
+
+Files vendored in this repository and shipped in its packages:
+
+- src/countermap/emit/schemas/attack-flow-schema-2.0.0.json
+  Attack Flow 2.0 JSON schema, MITRE Center for Threat-Informed Defense,
+  https://github.com/center-for-threat-informed-defense/attack-flow, Apache License 2.0.
+- src/countermap/emit/schemas/stix2.1/common/*.json (12 files)
+  OASIS STIX 2.1 JSON schemas, https://github.com/oasis-open/cti-stix2-json-schemas
+  (stix2.1 branch), BSD 3-Clause License, (c) OASIS Open. The license text, with
+  its copyright notice, is in LICENSES/BSD-3-Clause-OASIS.txt.
+- src/countermap/emit/schemas/d3fend-cad-schema.json
+  D3FEND CAD graph schema as published at https://d3fend.mitre.org/cad/docs/schema,
+  (c) The MITRE Corporation. The schema page states no separate license; the D3FEND
+  project publishes its ontology under the MIT License and its site under the D3FEND
+  Terms of Use. Included unmodified (apart from a provenance comment) for offline
+  validation. Remove it if MITRE indicates different terms.