How to download flaws into a xls/csv file
Open the desired application on the Veracode platform, navigate to the relevant scan and click on View Report.
Click on Download on top right hand side and select Detailed XML Export (XML) and download the report.
Save the .zip file locally.
Steps:
Extract the .xml file from the .Zip file you have downloaded.
Create a new blank Excel spreadsheet, place the cursor in cell A1 and drag & drop the .xml file into the spreadsheet table. You should be prompted with a dialog as shown below:
Select the option to Use the XML Source task pane which will give you a pop-up panel on the extreme right of your Excel table with a list of all XML elements in the file.
Refer to the import Source panel shown below:
Collapse all top-level elements (using the + and - buttons) and then expand the element labelled 'ns1:severity' and expand to find the element labelled 'ns1:staticflaws' as shown. Click the name of this element to select it (it gets a solid colour background) making sure nothing else is selected in the entire tree. This is vital - if anything else is selected then hold the Ctrl key and click the unwanted item to de-select it. Once you have the selection as shown drag the element label 'ns1:staticflaws' onto the spreadsheet table into cell A1 and hit the Refresh button in the ribbon.That should give you an Excel version of the flaws.
Click on the "import" button from the developer tab.
Troubleshooting tips & warnings:
Excel should have Developer tab enabled to import XML.
To display the DEVELOPER tab, click on the File menu and then select Options from the drop down menu. When the Excel Options window appears, click on the Customize Ribbon option on the left. Click on the Developer checkbox under the list of Main Tabs on the right. Then click on the OK button.
Topics (2)
Related Articles
What's a consultation call and how to schedule one? 19.15KNumber of Views Is there a way to schedule a dynamic scan of an application to run on a regular basis? For example if we wanted to automat… 1KNumber of Views Why is no source code info displayed for certain scans under Triage Flaw? 943Number of Views How to fix CWE 829 – Add CSP header correctly ? 812Number of Views The Pipeine Scan --include parameter and the scanned file size 682Number of Views
This topic isn't available in this community.
Related Topics
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the Community.
.png)