Merge pull request #460 from cobalthq/no-ticket-update-scans

Add info about failed scans

content/en/Platform Deep Dive/Scans/_index.md

@@ -55,7 +55,14 @@ We use the following IP Address to make requests to your target: **52.19.40.38**
 
     ![Scans Sample Findings Report](/deepdive/scans/6_ScansSampleFindingsReport.png "Scans Sample Findings Report")<br>
 
-6. Generate Report
+6. If the scan fails, navigate to the scans list or the scan details page to see the reason for the failed scan(s).
+
+Scan List View:
+![Scan failed](/deepdive/scans/scan-failed-01.png "Scan failed")<br>
+Scan Details View:
+![Scan failed](/deepdive/scans/scan-failed-02.png "Scan failed")<br>
+
+7. Generate Report
     1. From Targets, select the target you want to view a report for
 
     2. Select “View Report”
@@ -66,15 +73,15 @@ We use the following IP Address to make requests to your target: **52.19.40.38**
 
     ![Report](/deepdive/scans/8_Report.png "Report")<br>
 
-7. Move Finding State
+8. Move Finding State
     1. You can update the state for each finding
     2. Each finding has the following states:
         - **Pending Fix** (default): A vulnerability was found in a scan and has not been remediated
         - **Declined**: This is a false positive and not relevant to your application  (Each of these gets reviewed internally by Cobalt)
         - **Accepted Risk**: This is a known vulnerability but due to a mitigating control, the user accepts the risk.
         - **Re-test**: The user has remediated the vulnerability and is ready to retest the finding. Submitting a retest is the only way to mark a vulnerability as “fixed”.
 
-8. Retest Finding
+9. Retest Finding
     1. You can retest individual findings.
     2. Navigate to the finding you want to retest and select “retest”