delete docker snyk (#63)

.github/workflows/snyk-security.yml

@@ -18,14 +18,6 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       fail-fast: false
-      matrix:
-        include:
-          - dockerfile: ./Dockerfile
-            image: kennyopennix/wazuh-agent
-          - dockerfile: ./images/Dockerfie.amazonlinux
-            image: kennyopennix/wazuh-agent-amazonlinux
-          - dockerfile: ./images/Dockerfie.ubuntu
-            image: kennyopennix/wazuh-agent-ubuntu
     steps:
       - uses: actions/checkout@v3
       - name: Set up Snyk CLI to check for security issues
@@ -39,17 +31,8 @@ jobs:
         env:
           SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
 
-      - name: Build a Docker image
-        continue-on-error: true
-        run: docker build -t ${{ matrix.image }}  -f ${{ matrix.dockerfile }} .
-
-      - name: Snyk Container monitor
-        continue-on-error: true
-        run: snyk container monitor ${{ matrix.image }} --file=${{ matrix.dockerfile }}
-        env:
-          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
-
       - name: Upload result to GitHub Code Scanning
         uses: github/codeql-action/upload-sarif@v2
+        continue-on-error: true
         with:
           sarif_file: snyk-code.sarif

SECURITY.md

@@ -2,12 +2,11 @@
 
 OpenNix takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations.
 
-
 ## Reporting Security Issues
 
-**Please do not report security vulnerabilities through public GitHub issues.** Instead, please report them to the OpenNix at [[email protected]](mailto:[email protected]).  
+**Please do not report security vulnerabilities through public GitHub issues.** Instead, please report them to the OpenNix at [[email protected]](mailto:[email protected]).
 
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. 
+You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
 
 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 
@@ -20,7 +19,7 @@ Please include the requested information listed below (as much as you can provid
   * Impact of the issue, including how an attacker might exploit the issue
 
 This information will help us triage your report more quickly.
- 
+
 ## Preferred Languages
 
 We prefer all communications to be in English or Russian.