diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 0000000..4878b6e
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1,2 @@
+* @Oleksii-Klimov
+/.github/ @nepalevov @alexey-ban
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..3ba13e0
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: false
diff --git a/.github/pr-title-checker-config.json b/.github/pr-title-checker-config.json
deleted file mode 100644
index 2de82f5..0000000
--- a/.github/pr-title-checker-config.json
+++ /dev/null
@@ -1,14 +0,0 @@
-{
-  "LABEL": {
-    "name": "",
-    "color": "EEEEEE"
-  },
-  "CHECKS": {
-    "prefixes": ["fix: ", "feat: ", "feature: ", "chore: ", "hotfix: "]
-  },
-  "MESSAGES": {
-    "success": "All OK",
-    "failure": "Missing prefix",
-    "notice": ""
-  }
-}
\ No newline at end of file
diff --git a/.github/workflows/deploy_dev.yml b/.github/workflows/deploy_dev.yml
index 084e6a5..d1819d4 100644
--- a/.github/workflows/deploy_dev.yml
+++ b/.github/workflows/deploy_dev.yml
@@ -6,11 +6,11 @@ on:
 jobs:
   gitlab-dev-deploy:
     if: ${{ github.event.registry_package.package_version.container_metadata.tag.name == 'development' }}
-    uses: epam/ai-dial-ci/.github/workflows/deploy-development.yml@1.0.1
+    uses: epam/ai-dial-ci/.github/workflows/deploy-development.yml@1.3.1
     with:
-      gitlab-project-id: '1829'
-      gitlab-project-ref: 'master'
+      gitlab-project-id: "1829"
+      gitlab-project-ref: "master"
     secrets:
       DEPLOY_HOST: ${{ secrets.DEPLOY_HOST }}
       DEPLOY_ACCESS_TOKEN: ${{ secrets.DEPLOY_ACCESS_TOKEN }}
-      DEPLOY_TRIGGER_TOKEN: ${{ secrets.DEPLOY_TRIGGER_TOKEN }}
\ No newline at end of file
+      DEPLOY_TRIGGER_TOKEN: ${{ secrets.DEPLOY_TRIGGER_TOKEN }}
diff --git a/.github/workflows/pr-title-check.yml b/.github/workflows/pr-title-check.yml
new file mode 100644
index 0000000..8aef1e8
--- /dev/null
+++ b/.github/workflows/pr-title-check.yml
@@ -0,0 +1,14 @@
+name: "Validate PR title"
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+
+jobs:
+  pr-title-check:
+    uses: epam/ai-dial-ci/.github/workflows/pr-title-check.yml@1.3.1
+    secrets:
+      ACTIONS_BOT_TOKEN: ${{ secrets.ACTIONS_BOT_TOKEN }}
diff --git a/.github/workflows/pr_check_tests.yml b/.github/workflows/pr_check_tests.yml
index 4a9f029..af9a254 100644
--- a/.github/workflows/pr_check_tests.yml
+++ b/.github/workflows/pr_check_tests.yml
@@ -8,8 +8,8 @@ on:
 
 jobs:
   run_tests:
-    uses: epam/ai-dial-ci/.github/workflows/test_python_docker.yml@1.0.2
+    uses: epam/ai-dial-ci/.github/workflows/test_python_docker.yml@1.3.1
     with:
       bypass_checks: false
       python_version: 3.11
-    secrets: inherit
\ No newline at end of file
+    secrets: inherit
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 5c50d58..586f5c9 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -2,12 +2,12 @@ name: Release version
 
 on:
   push:
-    branches: [ development, release-* ]
+    branches: [development, release-*]
 
 env:
   IMAGE_NAME: ${{ github.repository }}
 
 jobs:
   release:
-    uses: epam/ai-dial-ci/.github/workflows/publish_python_docker.yml@1.0.2
-    secrets: inherit
\ No newline at end of file
+    uses: epam/ai-dial-ci/.github/workflows/publish_python_docker.yml@1.3.1
+    secrets: inherit
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..54afa27
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,11 @@
+# Reporting Security Issues
+
+We take all security reports seriously. We appreciate your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions.
+
+⚠️ Please do *not* file GitHub issues for security vulnerabilities as they are public! ⚠️
+
+To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/epam/ai-dial-assistant/security/advisories/new) tab. Tip: In this form, only the title and description are mandatory.
+
+We will send a response indicating the next steps in handling your report. After the initial reply to your report, we will keep you informed of the progress toward a fix and full announcement and may ask for additional information or guidance.
+
+When we receive such reports, we will investigate and subsequently address any potential vulnerabilities as quickly as possible.