diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 457b0c1..c728f9d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,13 +2,13 @@ First, please refer to [contribution-guide.org](http://www.contribution-guide.org/) for the steps we expect from contributors before submitting an issue or bug report. Be as concrete as possible, include relevant logs, package versions etc. -Also, please check our [FAQ](https://github.com/krakow2600/atomic-threat-coverage#faq). +Also, please check our [FAQ](https://github.com/atomic-threat-coverage/atomic-threat-coverage#faq). The proper place for open-ended questions is [Slack](https://join.slack.com/t/atomicthreatcoverage/shared_invite/enQtNTMwNDUyMjY2MTE5LTk1ZTY4NTBhYjFjNjhmN2E3OTMwYzc4MTEyNTVlMTVjMDZmMDg2OWYzMWRhMmViMjM5YmM1MjhkOWFmYjE5MjA) or [Telegram](https://t.me/atomic_threat_coverage). # How to add a new feature or create a pull request? -1. Fork the [ATC repository](https://github.com/krakow2600/atomic-threat-coverage) +1. Fork the [ATC repository](https://github.com/atomic-threat-coverage/atomic-threat-coverage) 2. Clone your fork: `git clone git clone https://gitlab.com//atomic-threat-coverage.git` 3. Create a new branch based on `develop`: `git checkout -b my-feature develop` 4. Setup your Python enviroment @@ -27,6 +27,6 @@ The proper place for open-ended questions is [Slack](https://join.slack.com/t/at - Any other useful information: links to other related Github or mailing list issues and discussions, benchmark graphs, academic papers… - Note that your Pull Request should be into **develop** branch, **not master** -P.S. for developers: see our [Developer Page](https://gitlab.com/krakow2600/atomic-threat-coverage/wikis/Developer-guide) for details on the code style, CI, testing and similar. + **Thanks and let's improve the open source world together!** \ No newline at end of file diff --git a/DEVELOP.md b/DEVELOP.md index 6ede0a1..1fda149 100644 --- a/DEVELOP.md +++ b/DEVELOP.md @@ -1,6 +1,6 @@ -The code for Atomic Threat Coverage is hosted on GitHub. [Pull requests](https://help.github.com/articles/about-pull-requests/) are welcome, for both code or documentation. You may also report an issue or bug [here](https://github.com/krakow2600/atomic-threat-coverage/issues). +The code for Atomic Threat Coverage is hosted on GitHub. [Pull requests](https://help.github.com/articles/about-pull-requests/) are welcome, for both code or documentation. You may also report an issue or bug [here](https://github.com/atomic-threat-coverage/atomic-threat-coverage/issues). -If you don't feel confident in your Git and/or Python skills, you can get up-to-speed with [these tutorials](http://matthew-brett.github.com/pydagogue/). If you would like to share an idea for improvement you can create [issue](https://github.com/krakow2600/atomic-threat-coverage/issues) or contact us in [Slack](https://join.slack.com/t/atomicthreatcoverage/shared_invite/enQtNTMwNDUyMjY2MTE5LTk1ZTY4NTBhYjFjNjhmN2E3OTMwYzc4MTEyNTVlMTVjMDZmMDg2OWYzMWRhMmViMjM5YmM1MjhkOWFmYjE5MjA) or [Telegram](https://t.me/atomic_threat_coverage) to discuss it. +If you don't feel confident in your Git and/or Python skills, you can get up-to-speed with [these tutorials](http://matthew-brett.github.com/pydagogue/). If you would like to share an idea for improvement you can create [issue](https://github.com/atomic-threat-coverage/atomic-threat-coverage/issues) or contact us in [Slack](https://join.slack.com/t/atomicthreatcoverage/shared_invite/enQtNTMwNDUyMjY2MTE5LTk1ZTY4NTBhYjFjNjhmN2E3OTMwYzc4MTEyNTVlMTVjMDZmMDg2OWYzMWRhMmViMjM5YmM1MjhkOWFmYjE5MjA) or [Telegram](https://t.me/atomic_threat_coverage) to discuss it. # Documentation @@ -84,4 +84,4 @@ git merge --no-ff master git push origin develop ``` -Add text description in [Tags](https://github.com/krakow2600/atomic-threat-coverage/tags). +Add text description in [Tags](https://github.com/atomic-threat-coverage/atomic-threat-coverage/tags). diff --git a/README.md b/README.md index 8486acd..ea05dee 100644 --- a/README.md +++ b/README.md @@ -443,7 +443,7 @@ At the same time it highlights which fields could be found only with specific en If you just want to try it with default dataset, you can use docker: -1. Clone the repository or download an [archive](https://github.com/krakow2600/atomic-threat-coverage/archive/master.zip) with it +1. Clone the repository or download an [archive](https://github.com/atomic-threat-coverage/atomic-threat-coverage/archive/master.zip) with it 2. Go to the project directory 3. Download and update Sigma and Atomic Red Team projects using git submodules: ```bash diff --git a/README_RU.md b/README_RU.md index b3ffd05..dd30c94 100644 --- a/README_RU.md +++ b/README_RU.md @@ -452,7 +452,7 @@ Atomic Threat Coverage генерирует [pivoting.csv](pivoting.csv) — с Вы можете использовать Docker для того, чтобы посмотреть, как ATC работает с данными из открытых источников. Для этого нужно выполнить следующее: -1. Клонируйте репозиторий или скачайте [архив](https://github.com/krakow2600/atomic-threat-coverage/archive/master.zip) с ним +1. Клонируйте репозиторий или скачайте [архив](https://github.com/atomic-threat-coverage/atomic-threat-coverage/archive/master.zip) с ним 2. Перейдите в директорию проекта 3. Скачайте и обновите репозитории Sigma и Atomic Red Team c помощью git submodules: ```bash diff --git a/analytics/predefined/atc-analytics-dashboard.json b/analytics/predefined/atc-analytics-dashboard.json index c60e93c..b89abef 100644 --- a/analytics/predefined/atc-analytics-dashboard.json +++ b/analytics/predefined/atc-analytics-dashboard.json @@ -248,7 +248,7 @@ "version": 9, "attributes": { "title": "ATC Analytics Dashboard legend", - "visState": "{\"title\":\"ATC Analytics Dashboard legend\",\"type\":\"markdown\",\"params\":{\"fontSize\":12,\"openLinksInNewTab\":true,\"markdown\":\"ATC Analytics Dashboard was built upon 223 (all for 26 of July 2019) public [Sigma](https://github.com/Neo23x0/sigma) rules for Windows OS.\\n\\nInformation about data source has been automatically calculated by Atomic Threat Coverage project upon [Data Needed](https://github.com/krakow2600/atomic-threat-coverage/tree/master#data-needed) entities.\\n\\nInformation about Detection Rules implementation for specific customers has been built upon demo [Customers](https://github.com/krakow2600/atomic-threat-coverage/tree/master#customers) entities.\\n\\nYou can build the same dashboard for your own analytics following [this](https://github.com/krakow2600/atomic-threat-coverage/tree/master#setting-up-kibana-dashboard) guideline.\"},\"aggs\":[]}", + "visState": "{\"title\":\"ATC Analytics Dashboard legend\",\"type\":\"markdown\",\"params\":{\"fontSize\":12,\"openLinksInNewTab\":true,\"markdown\":\"ATC Analytics Dashboard was built upon 223 (all for 26 of July 2019) public [Sigma](https://github.com/Neo23x0/sigma) rules for Windows OS.\\n\\nInformation about data source has been automatically calculated by Atomic Threat Coverage project upon [Data Needed](https://github.com/atomic-threat-coverage/atomic-threat-coverage/tree/master#data-needed) entities.\\n\\nInformation about Detection Rules implementation for specific customers has been built upon demo [Customers](https://github.com/atomic-threat-coverage/atomic-threat-coverage/tree/master#customers) entities.\\n\\nYou can build the same dashboard for your own analytics following [this](https://github.com/atomic-threat-coverage/atomic-threat-coverage/tree/master#setting-up-kibana-dashboard) guideline.\"},\"aggs\":[]}", "uiStateJSON": "{}", "description": "", "version": 1,