Attach findings to a penetration testing assessment request

task australia Updated Sep 10, 2026 1 min read pentest-attach-findings-pentest-request.md
Raw file servicenow.com

Attach application vulnerable item findings to an existing penetration test request using the manual ingestion process.

Before you begin

Penetration test assessment request records must be in the Testing in Progress state.

Role required: ethical_hacker

About this task

You can attach findings to penetration test requests that are already in progress. The manual ingestion process uses a spreadsheet template to import multiple findings at once.

Procedure

  1. Navigate to All > Manual Ingestion > AVIT Pentest Import.

  2. On the Upload Application Pentest Findings page, select the link to download the template in your preferred format.

    Templates are available in spreadsheet or CSV format.

  3. Complete the required fields on the Instruction tab of the template.

    Note: The Pentest request number field is required to add findings to an existing penetration test request automatically.

    • For the Finding field, enter the row number from the Upload Findings tab.
    • For the Attachment field, paste or insert one image in the cell. Use additional rows for multiple images.
  4. Navigate to All > Manual Ingestion > AVIT Pentest Import.

  5. On the Upload Application Pentest Findings page, select Import File and locate your completed template file.

  6. Select Submit.

    The template file enters the manual ingestion Integration push queue. The Integration Push Queue record is displayed.

  7. Navigate to Penetration Test Workspace > Penetration test requests and open the penetration test request record.

    The findings from the template file appear on the Penetration test findings tab. Any image attachments are displayed on the finding records.

If your findings were not attached as expected, check the Integration Push Queue record for errors.

To view error details, select the error log link on the Integration Push Queue record.

Error message Cause Solution
Partial Success One or more penetration test request numbers are missing or invalid Correct the invalid request numbers in the template and upload the file again. Findings with valid request numbers are attached. The upload does not create duplicates for findings that have been successfully attached in previous uploads.
Failed The penetration test request is not in the Testing in Progress state Change the request state to Testing in Progress and upload the template again.
Failed No penetration test request numbers are provided The system automatically creates penetration test request records for the findings, grouped by application.
Search documentation
Search document titles and file paths on the australia branch