diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
index 8d0969c706..95b812ab11 100644
--- a/docs/SUMMARY.md
+++ b/docs/SUMMARY.md
@@ -99,6 +99,8 @@
* [Deploying MongoDB Helm Chart](user-guide/deploy-chart/examples/deploying-mongodb-helm-chart.md)
* [Chart Group](user-guide/deploy-chart/chart-group.md)
* [Security](user-guide/security-features.md)
+ * [Security Scans](user-guide/security-features/security-scans.md)
+ * [Security Policies](user-guide/security-features/security-policies.md)
* [Clusters](user-guide/clusters.md)
* [Bulk Edit](user-guide/bulk-update.md)
* [Integrations](user-guide/integrations/README.md)
diff --git a/docs/user-guide/security-features.md b/docs/user-guide/security-features.md
index b8df3bf7fe..0f4d0ade55 100644
--- a/docs/user-guide/security-features.md
+++ b/docs/user-guide/security-features.md
@@ -1,156 +1,20 @@
# Security Features
-Devtron provides strong security features that help identify vulnerabilities in container images. The system scans container images thoroughly and generates reports if any vulnerabilities are found.
+{% hint style="info" %}
+### Prerequisite
-Within the CI pipeline of Devtron, there is an option called [**Scan for vulnerabilities**](creating-application/workflow/ci-pipeline.md#scan-for-vulnerabilities).
+Install any one of the following integrations for scanning vulnerabilities:
+* [Clair](../user-guide/integrations/clair.md)
+* Trivy
+{% endhint %}
-
+Devtron's security feature consists of two primary components:
-By enabling this option, the system automatically scans the container image after the image build stage. It then generates a report that highlights all the vulnerabilities present within the image. To access the scan report of all builds with vulnerability scans enabled, simply navigate to the 'Security' tab on the dashboard. There you can conveniently view the build history and all the vulnerabilities detected in the build image.
+1. [Security Scans](./security-features/security-scans.md) - This allows you to identify and address potential security risks effectively. By leveraging this feature, you can ensure that your containerized applications are safeguarded against known vulnerabilities.
-
-
-The scan report provides a comprehensive overview of any vulnerabilities present in the image. This allows you to identify and address potential security risks effectively. By leveraging this feature, you can ensure that your containerized applications are safeguarded against known vulnerabilities.
-
-Devtron's Security Feature consists of two primary components:
-
-1. **Security Scans**
-2. **Security Policies**
-
-## Security Scans
-
-Devtron's security scans provide comprehensive scan reports for all applications that have undergone vulnerability scanning. These reports offer a detailed overview of the security status of each scanned application.
-
-These comprehensive scan reports provide valuable insights, including information about identified vulnerabilities, their severity levels, and any corresponding Common Vulnerabilities and Exposures (CVE) entries.
-
-## Security Policies
-
-Devtron's Security Policies feature allows users to define policies based on the severity levels of vulnerabilities, which include `Critical`, `Moderate`, and `Low`. Users have the flexibility to set policies that either block the deployment of container images with vulnerabilities or allow their deployment.
-
-With this feature, users can specify their desired actions for each severity level. For example, they can choose to block any container image with `Critical` vulnerabilities, while allowing container images with `Moderate` or `Low` vulnerabilities to be deployed.
-
-### Checking Comprehensive Vulnerability Scan Report
-
-To access the comprehensive security scan reports, follow these steps:
-
-1. Navigate to the `Security` tab within Devtron.
-2. Select the desired application from the available list.
-
-
-
-This action will provide detailed information regarding the security scan of the application, including the CVE, Severity of the identified vulnerabilities, as you can see in the image below.
-
-
-
-Each vulnerability is identified by a **CVE ID** and categorized based on **Severity**, **Package**, **Current Version**, and **Fixed In Version**.
-
-* **`CVE ID`** refers to the Common Vulnerability ID assigned to each vulnerability.
-* **`Severity`** indicates the severity of the vulnerability and can be classified as Critical, Medium, or Low.
-* The **`Package`** column contains metadata associated with the vulnerability. The current Version refers to the specific version of the vulnerability.
-* The **`Fixed In Version`** column displays the version name if the vulnerability has been addressed in a subsequent release; otherwise, it remains blank.
-
-### Discover Vulnerabilities on the Trigger Page
-
-Devtron provides the capability to identify vulnerabilities before image deployment in the Continuous Deployment (CD) pipeline. This ensures that potential vulnerabilities are detected and addressed early in the deployment process.
-
-To access security vulnerability details during image deployment in Devtron, follow these steps:
-
-1. Click on the `Show source info` option for the desired image during the deployment process.
-2. Navigate to the `Security` tab.
-
-
-
-In the `Security` tab, you will find the security vulnerability details associated with the image.
-
-**NOTE**: Vulnerabilities will only be displayed if a vulnerability scan has been enabled for that specific image. If no vulnerabilities are visible, it indicates that a vulnerability scan has not been performed for the image.
-
-### Accessing Vulnerability Information on the App Details Page
-
-Devtron offers the capability to identify vulnerabilities even after an image has been deployed. By navigating to the `app details` page, you can find comprehensive details about the vulnerabilities associated with the deployed image.
-
-With this capability, Devtron empowers users to stay informed about the security vulnerabilities present in their deployed images.
-
-
-
-By clicking on the 'Details' link in the security vulnerabilities report, you can access detailed information about the security vulnerabilities present inside the deployed image.
-
-
-
-## Configuring Security Policies
-
-You can establish security policies for their vulnerabilities through the `Security Policies` tab, which can be accessed from the left pane by navigating to `Security` and selecting `Security Policies`. Policies are implemented in a hierarchical order, following a specific sequence. The order of implementation is as follows, starting from the highest level:
-
-* **Global**
-* **Cluster**
-* **Environment**
-* **Application**
-
-Policies are implemented in a hierarchical order, with the following sequence: Global, Cluster, Environment, and Application. Higher-level policies take precedence over lower-level policies, ensuring a systematic and structured enforcement of security measures.
-
-
-
-**Some examples of how policies can be defined**
-
-Users can block all the critical vulnerabilities and allow the moderate and low vulnerabilities
-or
-Users can block all vulnerabilities
-or
-Users can block all vulnerabilities for one application and can block only critical vulnerabilities for other applications
-
-## Configure Global Security Policy
-
-Within the `Global Security Policies`, there are two options available: Block and Allow.
-If critical severity levels are blocked in the `Global Security Policy`, the same blocking will be applied to the `Cluster Security Policy`. Similarly, if the global policy is modified to allow critical levels, it will also allow them in `Cluster Security Policies`.
-However, users have the flexibility to explicitly modify these policies as desired.
-
-
-
-## Configure Cluster Security Policy
-
-
-In `Global Security Policies`, there are two options: `Block` and `Allow`. `Cluster Security Policies` have an additional option called `Inherit`.
-
-When `Inherit` is selected, the policy adopts settings from higher-level options. For example, if critical severity levels are blocked globally, they will also be blocked in `Cluster Security Policies`. Changing the global policy to allow critical levels will also allow them in `Cluster Security Policies`. Explicit changes can be made to these policies.
-
-To block critical vulnerabilities globally but allow them in specific clusters:
-
-1. Select the desired cluster.
-2. Change the critical setting to allow.
-3. This change only affects the policy of the selected cluster without impacting others or the global policy.
-
-
-
-## Configure Environment Security Policy
-
-Environment Security Policies, like Cluster Security Policies, offer three options: Block, Allow, and Inherit.
-
-The `Environment Security Policy` inherits its settings from the `Cluster Security Policy`, following a hierarchical structure where each level inherits the policy from its upper level.
-
-When you select an environment, it automatically adopts the policy of the associated cluster. For example, if critical-level vulnerabilities are blocked globally but allowed in the `Cluster Security Policy`, the `Environment Security Policy` will inherit this allowance. Consequently, critical-level vulnerabilities will also be allowed in the `Environment Security Policy`.
-
-However, you have the flexibility to make explicit changes to the policy if needed. This empowers you to customize the policy to align with specific requirements or preferences.
-
-
-
-## Configure Application Security Policy
-
-The `Application Security Policy` operates on a similar principle as other policies. However, in the `Application Security Policy`, the policy is determined by both the Environment option and the Application option.
-
-When modifying the policy within a development environment, the changes will be applied to all applications within that specific development environment. This means that any adjustments made to the policy settings will be consistently applied across all applications associated with that particular development environment.
-
-This approach ensures uniformity and streamlined management of security policies within specific environments and their corresponding applications.
-
-
-
-## Block or Allow Specific CVE Policies.
-
-To block or allow specific Common Vulnerabilities and Exposures (CVE) policies, simply click `Add CVE Policy`.
-
-
-
-A window will appear where you can enter the CVE ID and select whether to allow or block it.
-
-
-
-This action will determine whether image deployment is allowed or blocked based on the presence of vulnerabilities matching that particular CVE ID. Any other deployment decisions will be made according to the policies set previously.
+2. [Security Policies](./security-features/security-policies.md) - This allows you to define policies to block or allow the deployment of container images depending on the vulnerabilities detected.
+{% hint style="warning" %}
+### Who Can Perform This Action?
+Users need to have super-admin permission to enable vulnerability scanning and to define security policies in Devtron.
+{% endhint %}
\ No newline at end of file
diff --git a/docs/user-guide/security-features/security-policies.md b/docs/user-guide/security-features/security-policies.md
new file mode 100644
index 0000000000..d099fee551
--- /dev/null
+++ b/docs/user-guide/security-features/security-policies.md
@@ -0,0 +1,161 @@
+# Security Policies
+
+{% hint style="info" %}
+### Prerequisite
+
+Install any one of the following integrations for scanning vulnerabilities:
+* [Clair](../user-guide/integrations/clair.md)
+* Trivy
+{% endhint %}
+
+Devtron's Security Policies feature allows users to define policies based on the severity levels of vulnerabilities, which include `Critical`, `Moderate`, and `Low`. Users have the flexibility to set policies that either block the deployment of container images with vulnerabilities or allow their deployment.
+
+With this feature, users can specify their desired actions for each severity level. For example, they can choose to block any container image with `Critical` vulnerabilities, while allowing container images with `Moderate` or `Low` vulnerabilities to be deployed.
+
+For in-depth instructions, refer to the [Configure Security Policies](#configuring-security-policies) section.
+
+{% hint style="warning" %}
+### Who Can Perform This Action?
+Users need to have super-admin permission to define or modify security policies.
+{% endhint %}
+
+---
+
+## Configuring Security Policies
+
+You can establish security policies for their vulnerabilities through the `Security Policies` tab, which can be accessed from the left pane by navigating to `Security` and selecting `Security Policies`.
+
+You can define policies at the following levels:
+
+* [Global](#configure-global-security-policy)
+* [Cluster](#configure-cluster-security-policy)
+* [Environment](#configure-environment-security-policy)
+* [Application](#configure-application-security-policy)
+
+
+
+However, if you define policies at more than one level, the order of precedence would be as follows:
+
+* Application + Environment (highest priority)
+* Environment
+* Cluster
+* Global
+
+### Examples of Defining a Policy
+
+* Users can block all vulnerabilities
+* Users can block critical vulnerabilities and allow moderate and low vulnerabilities
+* Users can block all vulnerabilities for one application and can block only critical vulnerabilities for other applications
+* Users can block those vulnerabilities for which a fix is already available
+
+---
+
+## Configure Global Security Policy
+
+Within the Global Security Policies, there are three options available:
+
+| Option | Description |
+| ------------------------- | ---------------------------------------------------------------------------------------------------|
+| Block always | Images containing vulnerabilities will be blocked from deployment |
+| Block if fix is available | Images containing vulnerabilities will be blocked if a fix is available and has not been applied |
+| Allow | Images containing vulnerabilities will be allowed to be deployed regardless of whether a fix is available or not |
+
+
+
+If critical severity levels are blocked in the Global Security Policy, the same blocking will be applied to the Cluster Security Policy. Likewise, allowing critical levels in the global policy automatically allows them in Cluster Security Policies.
+
+However, users have the flexibility to explicitly modify these policies as desired.
+
+---
+
+## Configure Cluster Security Policy
+
+Cluster Security Policies offer the same three options as [Global Security Policies](#configure-global-security-policy) for handling vulnerabilities. However, an extra option called `Inherit` is available too.
+
+
+
+When `Inherit` is selected, the policy adopts settings from higher-level options. For example, if critical severity levels are blocked globally, they will also be blocked in Cluster Security Policies. Changing the global policy to allow critical levels will also allow them in Cluster Security Policies. Explicit changes can be made to these policies.
+
+To block critical vulnerabilities globally but allow them in specific clusters:
+
+1. Select the desired cluster.
+2. Change the critical setting to allow.
+3. This change only affects the policy of the selected cluster without impacting others or the global policy.
+
+---
+
+## Configure Environment Security Policy
+
+Environment Security Policies, like [Cluster Security Policies](#configure-cluster-security-policy), offer four options:
+
+* Block always
+* Block if fix is available
+* Allow
+* Inherit
+
+
+
+The Environment Security Policy inherits its settings from the Cluster Security Policy, following a hierarchical structure where each level inherits the policy from its upper level.
+
+When you select an environment, it automatically adopts the policy of the associated cluster. For example, if critical-level vulnerabilities are blocked globally but allowed in the Cluster Security Policy, the Environment Security Policy will inherit this allowance. Consequently, critical-level vulnerabilities will also be allowed in the Environment Security Policy.
+
+However, you have the flexibility to make explicit changes to the policy if needed. This empowers you to customize the policy to align with specific requirements or preferences. Any adjustments made to the environment policy settings will be consistently applied across all applications associated with that environment.
+
+---
+
+## Configure Application Security Policy
+
+The Application Security Policy operates on a similar principle as other policies and offers four options:
+
+* Block always
+* Block if fix is available
+* Allow
+* Inherit
+
+However, in the Application Security Policy, the policy is determined by both: Application and Environment
+
+First, choose an application from the list.
+
+
+
+Next, configure a security policy for that application in the intended environment.
+
+
+
+---
+
+## Example
+
+1. Let's say, you have defined a policy to block the deployment if critical vulnerabilities are found in a given application.
+
+ 
+
+2. Now, go to the **Build & Deploy** tab of that application to select an image.
+
+ 
+
+3. As you can see, security issues were found in the scanned image, hence it is not available for selection. Click **Show Source Info**.
+
+ 
+
+4. The `Security` tab shows the critical vulnerabilities and the policy enforced to prevent deployment.
+
+ 
+
+---
+
+## Block or Allow Specific CVE Policies
+
+To block or allow specific Common Vulnerabilities and Exposures (CVE) policies, simply click **Add CVE Policy**.
+
+
+
+A window will appear where you can enter the CVE ID and select whether to allow or block it.
+
+
+
+This action will determine whether image deployment is allowed or blocked based on the presence of vulnerabilities matching that particular CVE ID. Any other deployment decisions will be made according to the policies set previously.
+
+
+
+
diff --git a/docs/user-guide/security-features/security-scans.md b/docs/user-guide/security-features/security-scans.md
new file mode 100644
index 0000000000..e96e962141
--- /dev/null
+++ b/docs/user-guide/security-features/security-scans.md
@@ -0,0 +1,80 @@
+# Security Scans
+
+{% hint style="info" %}
+### Prerequisite
+
+Install any one of the following integrations for scanning vulnerabilities:
+* [Clair](../user-guide/integrations/clair.md)
+* Trivy
+{% endhint %}
+
+Devtron's CI pipeline provides a [**Scan for vulnerabilities**](creating-application/workflow/ci-pipeline.md#scan-for-vulnerabilities) option as shown below. Once you enable this option, it will automatically scan the image for vulnerabilities.
+
+
+
+{% hint style="warning" %}
+### Who Can Perform This Action?
+Users need to have Admin permission or above (along with access to the environment and application) to enable the **Scan for vulnerabilities** option.
+{% endhint %}
+
+---
+
+## Checking Comprehensive Vulnerability Scan Report
+
+To access the comprehensive security scan reports, follow these steps:
+
+1. In the left sidebar, click **Security** and go to the `Security Scans` tab.
+
+ {% hint style="warning" %}
+ ### Who Can Perform This Action?
+ Users need to have super-admin permission to view the 'Security Scans' page.
+ {% endhint %}
+
+2. Select the desired application from the available list.
+
+ 
+
+ This action provides a detailed overview of the application's security scan, including CVE IDs, severity levels of vulnerabilities, and more, as shown below.
+
+ 
+
+Each vulnerability is identified by a **CVE ID** and categorized based on **Severity**, **Package**, **Current Version**, and **Fixed In Version**.
+
+* **CVE ID** - Refers to the Common Vulnerability ID assigned to each vulnerability.
+* **Severity** - Indicates the severity of the vulnerability and can be classified as Critical, Medium, or Low.
+* **Package** - Contains metadata associated with the vulnerability. The `CURRENT VERSION` refers to the specific version of the vulnerability.
+* **Fixed In Version** - Displays the version name if the vulnerability has been addressed in a subsequent release; otherwise, it remains blank.
+
+---
+
+## Discover Vulnerabilities on the Trigger Page
+
+Devtron provides the capability to identify vulnerabilities before image deployment in the Continuous Deployment (CD) pipeline. This ensures that potential vulnerabilities are detected and addressed early in the deployment process.
+
+To access security vulnerability details during image deployment in Devtron, follow these steps:
+
+1. Click **Show Source Info** option for the desired image during the deployment process.
+2. Navigate to the `Security` tab.
+
+
+
+In the `Security` tab, you will find the security vulnerability details associated with the image.
+
+{% hint style="info" %}
+Vulnerability information will only be displayed for images that have undergone vulnerability scanning. If no vulnerabilities were identified during the scan, the **Security** tab will display a zero count, indicating **Security (0)**.
+{% endhint %}
+
+---
+
+## Accessing Vulnerability Information on the App Details Page
+
+Devtron offers the capability to identify vulnerabilities even after an image has been deployed. By navigating to the `App Details` page, you can find comprehensive details about the vulnerabilities associated with the deployed image.
+
+With this capability, Devtron empowers users to stay informed about the security vulnerabilities present in their deployed images.
+
+
+
+Clicking the 'Details' link in the security vulnerabilities report (shown above) reveals detailed information about those found within the deployed image.
+
+
+