GITBOOK-573: No subject

Author: Whitespots

.gitbook/assets/image (1).png

@@ -51,6 +51,9 @@
       * [SLA](appsec-portal/features/security-metrics/metrics-settings/sla.md)
     * [CVSS](appsec-portal/features/security-metrics/cvss/README.md)
       * [CVSS Rule](appsec-portal/features/security-metrics/cvss/cvss-rule.md)
+  * [Asset management](appsec-portal/features/asset-management/README.md)
+    * [How to import repositories from version control](appsec-portal/features/asset-management/how-to-import-repositories-from-version-control.md)
+    * [Default product](appsec-portal/features/asset-management/default-product.md)
 * [🎣 Auto Validator](appsec-portal/auto-validator/README.md)
   * [Rule creation](appsec-portal/auto-validator/rule-creation.md)
   * [Rules view](appsec-portal/auto-validator/rules-view.md)

.gitbook/assets/image (180).png

@@ -49,4 +49,4 @@ If you delete an Asset, the previously discovered findings from that Asset **rem
 
 You can [**create** ](auditor-settings/product-asset-setting.md)a new Asset of the appropriate type by clicking the **Create icon** in the right panel.
 
-<figure><img src="../../.gitbook/assets/image (7) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

.gitbook/assets/image (181).png

@@ -42,4 +42,4 @@ The same actions are available on the records as on the main Audits screen.
 When viewing a particular Asset, at the bottom of the screen you can also find all the audits performed on it. \
 The same actions with records are available as for the main audit screen
 
-<figure><img src="../../.gitbook/assets/image (7) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (7) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

.gitbook/assets/image (182).png

@@ -0,0 +1,16 @@
+# Asset management
+
+## General information
+
+We support 5 types of assets:
+
+<figure><img src="../../../.gitbook/assets/image.png" alt="" width="199"><figcaption></figcaption></figure>
+
+Our platform uses them to manage scans and scan results.
+
+This is how it works:
+
+1. You create/import asset (for example any repository)
+2. Portal sends this repository in `REPOSITORY` variable to auditor
+3. Auditor performs scans and calls Portal's API endpoint with REPOSITORY parameter and a report from scanner
+4. Now portal knows where to put all asset-related vulnerabilities

.gitbook/assets/image (183).png

@@ -0,0 +1,7 @@
+# Default product
+
+This is useful for all unsorted assets.
+
+We kindly suggest you to create a product called "Unsorted" and set it as default from it's options page
+
+<figure><img src="../../../.gitbook/assets/image (183).png" alt=""><figcaption></figcaption></figure>

.gitbook/assets/image (4).png

@@ -0,0 +1,16 @@
+# How to import repositories from version control
+
+1. Be sure, that you have [set up the integration with your version control system](../../general-portal-settings/version-control.md)
+2. Navigate to Assets->Repositories page and click the "Import" button
+
+<figure><img src="../../../.gitbook/assets/image (180).png" alt=""><figcaption></figcaption></figure>
+
+3. Choose your integration
+
+<figure><img src="../../../.gitbook/assets/image (181).png" alt="" width="375"><figcaption></figcaption></figure>
+
+4. Assign products for repositories (or just keep [your default one](default-product.md))
+
+<figure><img src="../../../.gitbook/assets/image (182).png" alt="" width="375"><figcaption></figcaption></figure>
+
+5. That's it. Now you can run audits&#x20;

.gitbook/assets/image (6).png

@@ -12,4 +12,4 @@ The recommendations are presented:
 * **CWE** (Common Weakness Enumerations) This section provides tailored recommendations using the top Common Weakness Enumerations (CWEs) to enhance your developer training. By focusing on these CWEs, you can guide your developers to identify and prevent critical security vulnerabilities.\
   View CWE recommendations for any product status using a simple filter
 
-<figure><img src="../../.gitbook/assets/image (6).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../.gitbook/assets/image (7).png" alt=""><figcaption></figcaption></figure>

.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1) (1) (1).png

@@ -6,7 +6,7 @@
 
  **Severity Statistic view:**
 
-<figure><img src="../../../.gitbook/assets/image (7) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (7) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 You can **customise your dashboard** based on your needs by clicking the **Metrics button** <img src="../../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1).png" alt="" data-size="line">  on the right panel:
 
@@ -49,7 +49,7 @@ Trend history section will display data for the last month
 
 <figure><img src="../../../.gitbook/assets/image (6) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
-<figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ### Mean Time of Status Change
 
@@ -73,7 +73,7 @@ Customise the view of the metric view using the Findings Status Change Time Stat
     <figure><img src="../../../.gitbook/assets/image (12) (1).png" alt=""><figcaption></figcaption></figure>
 *   **Mean Time to Rejection** (**MTR**) measures the average time it takes for a finding to be _rejected_ after _creation_. It provides insights into the speed of handling findings that are determined to be false positives.
 
-    <figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
+    <figure><img src="../../../.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
     <figure><img src="../../../.gitbook/assets/image (13) (1).png" alt=""><figcaption></figcaption></figure>
 *   **Mean Time to Remediation** (**MTTR**) calculates the average time it takes to _remediate_ vulnerabilities from the moment they are _verified_. A shorter MTTR indicates an efficient vulnerability resolution process.

.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1) (1).png

@@ -53,7 +53,7 @@ In the **Host tab** enter **host IP**, for example 83.110.124.0
 
 Click **Create**
 
-<figure><img src="../../../.gitbook/assets/image (7).png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../.gitbook/assets/image (7) (1).png" alt=""><figcaption></figcaption></figure>
 
 <figure><img src="../../../.gitbook/assets/image (8).png" alt=""><figcaption></figcaption></figure>
 

.gitbook/assets/image (7) (1) (1) (1) (1) (1) (1) (1).png

@@ -23,7 +23,7 @@ But keep in mind, that you will see only those repositories, which developers co
 
 ## Import repositories
 
-If you want to scan all repositories by manual trigger - import them using this instruction and be ready to perform scans. [This is the guide](post-install-configuration.md#import-repositories)
+If you want to scan all repositories by manual trigger - import them using this instruction and be ready to perform scans. This is[ how you can do it](features/asset-management/how-to-import-repositories-from-version-control.md)
 
 ## Perform scans