Prerequisites

Before submitting a new issue, please ensure you have completed the following (replace the space in the box with an "x" to denote that it has been completed)

• I have ensured that I am running the latest release
• The issue is repeatable
• The issue has not already been reported

Category

Please select a category for the item being created

• Bug
• Enhancement
• Assistance Request

Description

Please provide a brief synopsis of the feature request or issue; if the item being created is due to a bug, please complete the "Expected Outcome", "Actual Outcome", and "Reproduction Steps" sections as well, otherwise, check the boxes to show that it doesn't apply

Synopsis

When parsing *.fpr files generated via Fortify v16.11, the "Not a Finding" analysis result (formerly titled "Not an Issue") is not handled in such a way as to mark it complete in the POA&M / RAR reports

Expected Outcome

• N/A (Non-Bug Issue)

"Not a Finding" issues should be marked as completed in all reports

Actual Outcome

• N/A (Non-Bug Issue)

Issues with the title analysis result are still marked as being ongoing

Reproduction Steps

• N/A (Non-Bug Issue)

Parse a *.fpr file generated via Fortify v16.11

Attachments

Please provide any relevant attachments, as you see fit (e.g. screenshots); if supplying vulnerability data (e.g. CKL/Nessus files or reports), please ensure that they are sanitized of IP addresses and host names and email them to alex.kuchta@navy.mil - DO NOT POST VULNERABILITY FILES HERE

• Vulnerator Log (Required for bugs) - this can be found at C:\Users\%UserName%\AppData\Roaming\Vulnerator\V6Log.txt, where %UserName% is the user profile used to run the application
• Screenshots (Optional)
• Vulnerability Files (SANITIZED AND EMAILED)