Home
Developing
Learn how to develop by using the product.
AppScan® Source for Analysis and defect tracking
AppScan® Source for Analysis integrates with defect tracking systemsIBM® Rational Team Concert™ to deliver confirmed software vulnerabilities directly to the developer desktop. Defect submission to a defect tracking system contains a textual description of the bug and a file that contains only the findings submitted with the defect.
Integrating HP Quality Center and AppScan® Source for Analysis
The HP Quality Center integration with AppScan® Source for Analysis requires a Quality Center client installation on the local computer. The Quality Center client application is downloaded and installed on the local computer the first time you log in to Quality Center through the Quality Center browser-based client interface.
Tracking findings submitted to Quality Center

Developing
Learn how to develop by using the product.
- Scanning source code and managing assessments
  This section explains how to scan your source code and manage assessments.
- Triage and analysis
  Grouping similar findings allows security analysts or IT auditors to segment and triage source code problems. This section explains how to triage AppScan® Source assessments and analyze results.
- AppScan® Source trace
  With AppScan® Source trace, you can verify input validation and encoding that meets your software security policies. You can look at the findings that produce input/output traces and mark methods as validation and encoding routines, sources or sinks, callbacks, or taint propagators.
- AppScan® Source for Analysis and defect tracking
  AppScan® Source for Analysis integrates with defect tracking systemsIBM® Rational Team Concert™ to deliver confirmed software vulnerabilities directly to the developer desktop. Defect submission to a defect tracking system contains a textual description of the bug and a file that contains only the findings submitted with the defect.
  - Enabling defect tracking with preferences
    Defect Tracking System preferences allow you to enable the submission of findings to a defect tracking system - and determine how defects are submitted.
  - Integrating HP Quality Center and AppScan® Source for Analysis
    The HP Quality Center integration with AppScan® Source for Analysis requires a Quality Center client installation on the local computer. The Quality Center client application is downloaded and installed on the local computer the first time you log in to Quality Center through the Quality Center browser-based client interface.
    - Submitting findings to Quality Center
      Findings are submitted to Quality Center through any AppScan® Source for Analysis Findings view.
    - Tracking findings submitted to Quality Center
    - AppScan® Source finding information in Quality Center
  - Integrating Rational® ClearQuest® and AppScan® Source for Analysis
    The Rational® ClearQuest® integration with AppScan® Source for Analysis requires a Rational ClearQuest client installation on the local computer. This installation includes the CQPerl executable, and you must configure the location of the executable in the AppScan Source for Analysis Rational ClearQuest preferences.
  - Integrating Rational Team Concert™ and AppScan® Source for Analysis
    Rational Team Concert™ integration with AppScan® Source for Analysis does not require that an additional Rational Team Concert client be installed on your computer.
  - Integrating Microsoft™ Team Foundation Server and AppScan® Source for Analysis
    The Team Foundation Server integration with AppScan® Source for Analysis requires a Microsoft™ Visual Studio Team Explorer client installation on the local computer.
  - Working with submitted defects
    When you submit more than a few findings as separate defects, the process runs in the background while you continue the triage process. After the defect submission, a defect ID received from the defect system is attached to the relevant findings and remains with that finding. To work with a defect that has been submitted to your defect tracking system, follow the steps in this topic.
  - Submitting bundles to defect tracking and by email
    The findings in bundles can be submitted to your corporate defect tracking system - or sent by email. Once you place findings in a bundle, you can submit these findings as bugs for developer remediation.
  - Tracking defects through email (sending findings by email)
- Findings reports and audit reports
  Security analysts and risk managers can access reports of select findings or a series of audit reports that measure compliance with software security best practices and regulatory requirements. This section explains how to create reports of aggregate finding data.
- Creating custom reports
  In the Report Editor, you create report templates used to generate custom reports.

Tracking findings submitted to Quality Center

Findings submitted to Quality Center are tagged with submission information:

Quality Center Defect ID
Submission date
Quality Center user name

Submission information appears in the Defect ID, Defect Date, and Defect User columns in a findings table in any findings view. However, the default Findings Table does not contain these columns. You must configure the table to include these columns by clicking the Select and Order Columns toolbar button and customizing the table. See Customizing the findings table for details about adding columns to the findings views.

Defect information persists from scan to scan, allowing you to track the status of an AppScan® Source finding during triage and remediation.