style: apply black changes

Author: Anthirian

.github/workflows/lint.yml

@@ -21,5 +21,12 @@ jobs:
       - name: Check files using black formatter
         uses: datadog/[email protected]
         with:
-          check_mode: true
-          additional_args: "--diff --color elkserver/docker/redelk-base/redelkinstalldata/scripts"
+          check_mode: false
+          additional_args: "-t py36 elkserver/docker/redelk-base/redelkinstalldata/scripts"
+
+      - name: Commit & Push changes
+        uses: Andro999b/[email protected]
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          message: "style: autoformatted code with black"
+          branch: "develop"

README.md

@@ -4,13 +4,17 @@
 [![Build docker kibana image (dev)](https://github.com/outflanknl/RedELK/actions/workflows/docker-build-dev-kibana.yml/badge.svg?branch=develop)](https://github.com/outflanknl/RedELK/actions/workflows/docker-build-dev-kibana.yml)
 [![Build docker logstash image (dev)](https://github.com/outflanknl/RedELK/actions/workflows/docker-build-dev-logstash.yml/badge.svg?branch=develop)](https://github.com/outflanknl/RedELK/actions/workflows/docker-build-dev-logstash.yml)
 
-Red Team's SIEM - tool for Red Teams for tracking and alarming about Blue Team activities as well as enhanced usability in long term operations.
+# RedELK
+
+The Red Team's SIEM - a tool for Red Teams for tracking and alarming about Blue Team activities as well as enhanced usability in long term operations.
 
 1. **Enhanced usability and overview** for the red team operators by creating a central location where all relevant _operational_ logs from multiple teamservers are collected and enriched. This is great for historic searching within the operation as well as giving a read-only view on the operation (e.g. for the White Team). Especially useful for multi-scenario, multi-teamserver, multi-member and multi-month operations. Also, super easy ways for viewing all screenshots, IOCs, keystrokes output, etc. \o/
 2. **Spot the Blue Team** by having a central location where all _traffic_ logs from redirectors are collected and enriched. Using specific queries its now possible to detect that the Blue Team is investigating your infrastructure.
 
-# Background info #
+# Background info
+
 Check the [wiki](https://github.com/outflanknl/RedELK/wiki) for info on usage or one the blog posts or presentations listed below:
+
 - Blog part 1: [Why we need RedELK](https://outflank.nl/blog/2019/02/14/introducing-redelk-part-1-why-we-need-it/)
 - Blog part 2: [Getting you up and running](https://outflank.nl/blog/2020/02/28/redelk-part-2-getting-you-up-and-running/)
 - Blog part 3: [Achieving operational oversight](https://outflank.nl/blog/2020/04/07/redelk-part-3-achieving-operational-oversight/)
@@ -19,8 +23,10 @@ Check the [wiki](https://github.com/outflanknl/RedELK/wiki) for info on usage or
 - x33fcon 2019 Catching Blue Team OPSEC failures [video](https://www.youtube.com/watch?v=-CNMgh0yJag) and [slides](https://github.com/outflanknl/Presentations/blob/master/x33fcon2019_OutOfTheBlue-CatchingBlueTeamOPSECFailures_publicversion.pdf)
 - BruCon 2018: Using Blue Team techniques in Red Team ops [video](https://www.youtube.com/watch?v=OjtftdPts4g) and [slides](https://github.com/outflanknl/Presentations/blob/master/MirrorOnTheWall_BruCon2018_UsingBlueTeamTechniquesinRedTeamOps_Bergman-Smeets_FINAL.pdf)
 
-# Installation #
+# Installation
+
 Check the [wiki](https://github.com/outflanknl/RedELK/wiki) for manual installation manual. There are also Ansible playbooks maintained by others:
+
 - [RedELK Server playbook](https://github.com/fastlorenzo/redelk-server) - maintained by one of RedELK's developers
 - [RedELK Client playbook](https://github.com/fastlorenzo/redelk-client) - maintained by one of RedELK's developers
 - [ansible-redelk](https://github.com/curi0usJack/ansible-redelk) - maintained by curi0usJack/TrustedSec
@@ -31,11 +37,13 @@ Here's a conceptual overview of how RedELK works.
 
 ![](./images/redelk_overview.jpg)
 
-
 # Authors and contribution #
+
 This project is developed and maintained by:
+
 - Marc Smeets (@MarcOverIP on [Github](https://github.com/MarcOverIP) and [Twitter](https://twitter.com/MarcOverIP))
 - Mark Bergman (@xychix on [Github](https://github.com/xychix) and [Twitter](https://twitter.com/xychix))
 - Lorenzo Bernardi (@fastlorenzo on [Github](https://github.com/fastlorenzo) and [Twitter](https://twitter.com/fastlorenzo))
+- Geert Smelt (@Anthirian on [GitHub](https://github.com/Anthirian), @sme.lt on [BlueSky](https://bsky.app/profile/sme.lt) and @gasmelt on [Mastodon](https://infosec.exchange/@gasmelt))
 
 We welcome contributions! Contributions can be both in code, as well as in ideas you might have for further development, alarms, usability improvements, etc.