diff --git a/.github/workflows/api-security.yml b/.github/workflows/api-security.yml
new file mode 100644
index 00000000..07ca9f2c
--- /dev/null
+++ b/.github/workflows/api-security.yml
@@ -0,0 +1,69 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# APIsec addresses the critical need to secure APIs before they reach production.
+# APIsec provides the industry’s only automated and continuous API testing platform that uncovers security vulnerabilities and logic flaws in APIs.
+# Clients rely on APIsec to evaluate every update and release, ensuring that no APIs go to production with vulnerabilities.
+
+# How to Get Started with APIsec.ai
+# 1. Schedule a demo at https://www.apisec.ai/request-a-demo .
+#
+# 2. Register your account at https://cloud.apisec.ai/#/signup .
+#
+# 3. Register your API . See the video (https://www.youtube.com/watch?v=MK3Xo9Dbvac) to get up and running with APIsec quickly.
+#
+# 4. Get GitHub Actions scan attributes from APIsec Project -> Configurations -> Integrations -> CI-CD -> GitHub Actions
+#
+# apisec-run-scan
+#
+# This action triggers the on-demand scans for projects registered in APIsec.
+# If your GitHub account allows code scanning alerts, you can then upload the sarif file generated by this action to show the scan findings.
+# Else you can view the scan results from the project home page in APIsec Platform.
+# The link to view the scan results is also displayed on the console on successful completion of action.
+
+# This is a starter workflow to help you get started with APIsec-Scan Actions
+
+name: APIsec
+
+# Controls when the workflow will run
+on:
+    # Triggers the workflow on push or pull request events but only for the "main" branch
+    # Customize trigger events based on your DevSecOps processes.
+    push:
+        branches: ["main"]
+    pull_request:
+        branches: ["main"]
+    schedule:
+        - cron: "38 15 * * 1"
+
+    # Allows you to run this workflow manually from the Actions tab
+    workflow_dispatch:
+
+permissions:
+    contents: read
+
+jobs:
+    Trigger_APIsec_scan:
+        permissions:
+            security-events: write # for github/codeql-action/upload-sarif to upload SARIF results
+            actions: read # only required for a private repository by github/codeql-action/upload-sarif to get the Action run status
+        runs-on: ubuntu-latest
+
+        steps:
+            - name: APIsec scan
+              uses: apisec-inc/apisec-run-scan@025432089674a28ba8fb55f8ab06c10215e772ea
+              with:
+                  # The APIsec username with which the scans will be executed
+                  apisec-username: ${{ secrets.apisec_username }}
+                  # The Password of the APIsec user with which the scans will be executed
+                  apisec-password: ${{ secrets.apisec_password}}
+                  # The name of the project for security scan
+                  apisec-project: "VAmPI"
+                  # The name of the sarif format result file The file is written only if this property is provided.
+                  sarif-result-file: "apisec-results.sarif"
+            - name: Import results
+              uses: github/codeql-action/upload-sarif@v3
+              with:
+                  sarif_file: ./apisec-results.sarif
diff --git a/.github/workflows/sonar.yml b/.github/workflows/sonar.yml
new file mode 100644
index 00000000..0fba2300
--- /dev/null
+++ b/.github/workflows/sonar.yml
@@ -0,0 +1,67 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow helps you trigger a SonarCloud analysis of your code and populates
+# GitHub Code Scanning alerts with the vulnerabilities found.
+# Free for open source project.
+
+# 1. Login to SonarCloud.io using your GitHub account
+
+# 2. Import your project on SonarCloud
+#     * Add your GitHub organization first, then add your repository as a new project.
+#     * Please note that many languages are eligible for automatic analysis,
+#       which means that the analysis will start automatically without the need to set up GitHub Actions.
+#     * This behavior can be changed in Administration > Analysis Method.
+#
+# 3. Follow the SonarCloud in-product tutorial
+#     * a. Copy/paste the Project Key and the Organization Key into the args parameter below
+#          (You'll find this information in SonarCloud. Click on "Information" at the bottom left)
+#
+#     * b. Generate a new token and add it to your Github repository's secrets using the name SONAR_TOKEN
+#          (On SonarCloud, click on your avatar on top-right > My account > Security
+#           or go directly to https://sonarcloud.io/account/security/)
+
+# Feel free to take a look at our documentation (https://docs.sonarcloud.io/getting-started/github/)
+# or reach out to our community forum if you need some help (https://community.sonarsource.com/c/help/sc/9)
+
+name: SonarCloud analysis
+
+on:
+    push:
+        branches: ["main"]
+    pull_request:
+        branches: ["main"]
+    workflow_dispatch:
+
+permissions:
+    pull-requests: read # allows SonarCloud to decorate PRs with analysis results
+
+jobs:
+    Analysis:
+        runs-on: ubuntu-latest
+
+        steps:
+            - name: Analyze with SonarCloud
+
+              # You can pin the exact commit or the version.
+              # uses: SonarSource/sonarcloud-github-action@v2.2.0
+              uses: SonarSource/sonarcloud-github-action@4006f663ecaf1f8093e8e4abb9227f6041f52216
+              env:
+                  SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Generate a token on Sonarcloud.io, add it to the secrets of this repo with the name SONAR_TOKEN (Settings > Secrets > Actions > add new repository secret)
+              with:
+                  # Additional arguments for the SonarScanner CLI
+                  args:
+                      # Unique keys of your project and organization. You can find them in SonarCloud > Information (bottom-left menu)
+                      # mandatory
+                      -Dsonar.projectKey=
+                      -Dsonar.organization=
+                      # Comma-separated paths to directories containing main source files.
+                      #-Dsonar.sources= # optional, default is project base directory
+                      # Comma-separated paths to directories containing test source files.
+                      #-Dsonar.tests= # optional. For more info about Code Coverage, please refer to https://docs.sonarcloud.io/enriching/test-coverage/overview/
+                      # Adds more detail to both client and server-side analysis logs, activating DEBUG mode for the scanner, and adding client-side environment variables and system properties to the server-side log of analysis report processing.
+                      #-Dsonar.verbose= # optional, default is false
+                  # When you need the analysis to take place in a directory other than the one from which it was launched, default is .
+                  projectBaseDir: .