HCL AppScan, previously known as IBM AppScan, is a family of desktop and web security testing and monitoring tools formerly from the Rational Software division of IBM. In July 2019, the product was acquired by HCL Technologies and currently under HCL Software, a product development division of HCL Technologies.
AppScan Standard: Dynamic application security testing (DAST) to effectively identify, understand, and remediate web application vulnerabilities.
AppScan on Cloud (ASoC): Cloud-based application security testing suite to perform static, dynamic, interactive, and open-source analysis on web, mobile, and desktop applications. (DAST, SAST, IAST, SCA)
To import your data from AppScan Standard or ASoC to the Application Security Module, you will need to leverage the AppScan XML Connector under the Dynamic Assessment tools category in the Cisco Vulnerability Management UI. Cisco Vulnerability Management requires the use of the HCL AppScan XML Connector for AppScan ASoC and AppScan Standard.
The Connector is a mandatory full run connector because it is an XML connector.
Important: There are two different AppScan Connectors: the AppScan Connector (XML) and the AppScan Enterprise Connector (API). They do not support the same tools.
- The AppScan Connector (XML) supports data from AppScan Standard and ASoC.
- The HCL AppScan Enterprise Connector supports HCL AppScan Enterprise.
What Types of AppScan Data does the AppScan XML Connector Support?
Supported:
-
Standard
-
AppScan on Cloud (ASoC)
Not Supported:
-
Enterprise
-
Source
Prerequisites
-
Given that the connector is an XML based connector, a Virtual Tunnel or Agent is not required. It will be a simple file drag-and-drop.
-
The account that you use must be able to generate XML reports in AppScan.
Important: There are 2 ways to generate XML reports in HCL AppScan Standard. One option is through the reports menu and the second option is through the File Export menu. To have your Application Identifiers appear in the Application Security Module by default, use option 2.
Use the Export menu in HCL AppScan Standard to Generate XML reports
1. In HCL AppScan, click File > Exports > Scan results as XML.
2. Click For earlier versions (legacy).
Configuring your Connector in Cisco Vulnerability Management
1. In the Cisco Vulnerability Management UI, click Connectors.
2. Click Add Connector.
3. in the Dynamic Assessment section, click HCL AppScan.
4. On the AppScan page, enter the following information:
-
Name: Enter a name for the connector, or leave it as AppScan.
-
Asset Inactivity Limit (days): Use this option if you want to set an inactivity limit for assets that this connector ingests.
- Connector-level asset inactivity limits take precedence over the global inactivity limit. If you do not set an Asset Inactivity Limit, the Global Limit will apply to data ingested by this connector. See Setting Asset Inactivity Limits.
- Cisco recommends an asset inactivity limit of 2-3x the scan cadence of your Webinspect Scans if you plan to upload regularly.
5. Click Save.
What AppScan Items does Cisco Vulnerability Management Import?
Cisco Vulnerability Management will import all of the applications associated with the user used for the connector.
|
AppScan Field |
Cisco Vulnerability Management Field |
Notes |
|---|---|---|
|
Standard: Host > :Name |
Application identifier |
Search for Application identifier in Cisco Vulnerability Management by using the custom query box and typing application:"*" |
|
Standard: Issue > Url |
URL |
|
|
source_vulnerability.issue_type_id |
Identifier |
|
|
ignored=false |
Vulnerability Status |
Vulnerability status is Open or Closed. We do not map False Positives or Triage States. Open vulnerabilities are reported in application scan reports. Closed vulns are no longer present in these reports and Cisco Vulnerability Management will auto-close the vulnerability. |
|
name |
Vulnerability Name |
|
|
severity |
scanner_score |
0-10 |
|
cwe (id) |
CWE |
|
|
{Technical Description + Causes + SecurityRisks + Affected Products} |
|
These items are combined and distilled into Vulnerability Description in Cisco Vulnerability Management. |
|
{Priority + Fix Recommendation} |
Solution |
|
|
last_found_on |
last_seen_time |
|
|
found_on |
Found Date |
|
|
{Variant + CWE + Comments + Reasoning + Test Difference} |
Details |
These items are combined and distilled into Vulnerability Details in Cisco Vulnerability Management. |
|
-N/A- |
Tags |
There are no tags returned in the XMLs, thus no tags are created for Standard or ASoC connections. |
The Connector does not import the following:
-
Custom Fields
-
Tags for the XML connector
Optional Settings
The following settings can be enabled on the backend for AppScan Connectors. To have these settings enabled, or for more information, contact Cisco Support, or your Customer Success Engineer.
Exclude Informationals
When you enable this option, Cisco Vulnerability Management will only import vulnerabilities that include a CVE, CWE, or WASC ID.
Ignore Scanner Last Seen Time
Select this setting if you do not want the asset last seen time in Cisco Vulnerability Management to be the scanner reported last seen time.
Custom Ordered Locators
Locators (such as IP, Netbios, and FQDN) can be reordered to better deduplicate vulnerabilities on the Connector level or the entire Platform level. For more information, see the help article here.
Common Reasons for AppScan Connector Run Failures
- If Cisco Vulnerability Management receives data that is not in the expected format and cannot process it, the connector will fail.
- If more than 1% of connector payloads fail to import cleanly, Cisco Vulnerability Management will auto-fail the Connector run.
Additional Assistance:
Contact Cisco Support if you require any additional assistance with the AppScan Connector.
Comments
Please sign in to leave a comment.