{"id":18719484,"url":"https://github.com/center-for-threat-informed-defense/attack-sync","last_synced_at":"2025-04-12T14:08:52.120Z","repository":{"id":169474144,"uuid":"561473239","full_name":"center-for-threat-informed-defense/attack-sync","owner":"center-for-threat-informed-defense","description":"ATT\u0026CK Sync is a Center for Threat-Informed Defense project that aims to improve the ability for organizations to consume MITRE ATT\u0026CK® version updates into their internal systems and processes. ","archived":false,"fork":false,"pushed_at":"2025-04-01T04:08:21.000Z","size":21327,"stargazers_count":19,"open_issues_count":4,"forks_count":6,"subscribers_count":66,"default_branch":"main","last_synced_at":"2025-04-01T05:22:23.005Z","etag":null,"topics":["ctid","cybersecurity","mitre-attack","threat-informed-defense"],"latest_commit_sha":null,"homepage":"https://ctid.io/attack-sync","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/center-for-threat-informed-defense.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-11-03T19:12:07.000Z","updated_at":"2025-03-23T00:51:44.000Z","dependencies_parsed_at":null,"dependency_job_id":"43c43f41-631e-44d4-b11e-d4b692fa2aa2","html_url":"https://github.com/center-for-threat-informed-defense/attack-sync","commit_stats":null,"previous_names":["center-for-threat-informed-defense/attack-sync"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/center-for-threat-informed-defense%2Fattack-sync","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/center-for-threat-informed-defense%2Fattack-sync/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/center-for-threat-informed-defense%2Fattack-sync/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/center-for-threat-informed-defense%2Fattack-sync/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/center-for-threat-informed-defense","download_url":"https://codeload.github.com/center-for-threat-informed-defense/attack-sync/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248578869,"owners_count":21127713,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ctid","cybersecurity","mitre-attack","threat-informed-defense"],"created_at":"2024-11-07T13:26:17.184Z","updated_at":"2025-04-12T14:08:52.114Z","avatar_url":"https://github.com/center-for-threat-informed-defense.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"[![MITRE ATT\u0026CK® v16](https://img.shields.io/badge/MITRE%20ATT%26CK®-v16-red)](https://attack.mitre.org/versions/v16/)\n[![Build Status](https://github.com/center-for-threat-informed-defense/attack-sync/actions/workflows/build.yml/badge.svg)](https://github.com/center-for-threat-informed-defense/attack-sync/actions/workflows/build.yml)\n\n# ATT\u0026CK Sync\n\nATT\u0026CK Sync is a Center for Threat-Informed Defense project that aims to ease the\nprocess of staying in sync with MITRE ATT\u0026CK® version updates. We recognize widespread\ndifficulties keeping internal systems and date in sync with with ATT\u0026CK, so this project\nincludes tools, data, and methodology to reduce the cost and effort associated with\ntracking ATT\u0026CK releases. The Center is deploying this technology to improve our own\nprojects, and we believe it will be highly valuable to many other organizations as well.\n\n**Table Of Contents:**\n\n- [Getting Started](#getting-started)\n- [Getting Involved](#getting-involved)\n- [Questions and Feedback](#questions-and-feedback)\n- [How Do I Contribute?](#how-do-i-contribute)\n- [Notice](#notice)\n\n## Getting Started\n\nThe best way to get started is to visit the ATT\u0026CK Sync website, where you can quickly\naccess detailed changelogs that show cumulative differences between any two versions of\nATT\u0026CK from v8.0 to v16.1. The sample JSON changelog shows how the differences can be\nconsumed in machine-readable format, and the sample Excel mappings show how the\nmachine-readable data can be merged with your internal systems \u0026 data to provide\ncontextual ATT\u0026CK changes. Finally, the project wiki provides thorough documentation for\nthe project as well as a case study.\n\n| Resource                                                                                                                                       | Description                                                              |\n| ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |\n| [ATT\u0026CK Sync Website](https://center-for-threat-informed-defense.github.io/attack-sync/)                                                       | An interactive website for detailed comparisons between ATT\u0026CK versions. |\n| [Project Wiki](https://github.com/center-for-threat-informed-defense/attack-sync/wiki)                                                         | The wiki contains project documentation: goals, tools, and methodology.  |\n| [Case Study](https://github.com/center-for-threat-informed-defense/attack-sync/wiki/Case-Study:-NIST-800-53-Mappings)                          | Case study measuring efficiency gained from using ATT\u0026CK Sync.           |\n| [Sample JSON Changelog](https://github.com/center-for-threat-informed-defense/attack-sync/raw/main/samples/attack-changelog-v10.1-v12.1.json)  | A sample machine-readable ATT\u0026CK changelog.                              |\n| [Sample Excel Mappings](https://github.com/center-for-threat-informed-defense/attack-sync/raw/main/samples/nist800-53-r5-mappings-output.xlsx) | A sample mappings spreadsheet annotated with ATT\u0026CK changes.             |\n\n## Getting Involved\n\nThere are several ways that you can get involved with this project and help\nadvance threat-informed defense:\n\n- **Visit the ATT\u0026CK Sync website.** Access changelogs that detail the cumulative\n  changes between any ATT\u0026CK versions. This is especially helpful if your organization\n  is contemplating an upgrade of internal systems to a more recent version of ATT\u0026CK.\n- **Review the sample documents.** These documents will give you a better idea of how\n  ATT\u0026CK Sync can your organization major time and effort while staying in sync with\n  ATT\u0026CK.\n- **Tell us what you think.** As the project grows, we want to cover a broader set of\n  use cases. Let us know if you like this idea and how we can make it even better in\n  future releases.\n\n## Questions and Feedback\n\nPlease submit\n[issues](https://github.com/center-for-threat-informed-defense/attack-sync/issues) for\nany technical questions/concerns or contact ctid@mitre-engenuity.org directly for\ngeneral inquiries.\n\n## How Do I Contribute?\n\nWe welcome your feedback and contributions to help advance Attack Sync. Please see the\nguidance for contributors if are you interested in [contributing or simply reporting\nissues.](/CONTRIBUTING.md)\n\n## Notice\n\nCopyright 2023 MITRE Engenuity. Approved for public release. Document number CT0070.\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may not use this\nfile except in compliance with the License. You may obtain a copy of the License at\n\nhttp://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software distributed under\nthe License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied. See the License for the specific language governing\npermissions and limitations under the License.\n\nThis project makes use of MITRE ATT\u0026CK®\n\n[ATT\u0026CK Terms of Use](https://attack.mitre.org/resources/terms-of-use/)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcenter-for-threat-informed-defense%2Fattack-sync","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcenter-for-threat-informed-defense%2Fattack-sync","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcenter-for-threat-informed-defense%2Fattack-sync/lists"}