Knowledge base

PCI Findings

Last Updated: 2026-10-19

Purpose

This article describes how to work with PCI compliance findings in the Outpost24 Portal, including special notes and the dispute process.

Introduction

A PCI compliance scan evaluates every in-scope asset against PCI DSS requirements and records the results as findings. Each finding is either compliant or failing, and every failing finding must be dealt with before the scan cycle is completed: remediate the underlying issue and rescan, or - where the finding does not apply to the environment - dispute it. Disputes are reviewed by Outpost24, the certified Approved Scanning Vendor (ASV), through a threaded conversation attached to the finding. In addition, the scan attaches special notes to certain findings; these are standardized ASV notices that require a written response before the scope is compliant.

This article covers the customer side of the process. For the scan cycle itself - environments, scopes, asset review, and completion - see PCI Scanning.

Requirements

  • It is assumed that the reader has basic access to the OUTSCAN account to access the Portal.

  • The user must be assigned a role with the PCI resource set to View to see findings, or View and manage to edit special notes and raise disputes. For more information, see Role Management.

  • To see the informational tabs of a scope, the role must also have the Findings resource set to View or View and manage.

Accessing PCI Findings

PCI findings belong to a scope and are reached by opening that scope.

  1. Click PCI environments in the Main Menu.

  2. Click the environment that holds the scope.

  3. Click a scope with the status NON COMPLIANT, COMPLIANT, or COMPLETED.

The Findings view is displayed, listing the findings of that scope, with a breadcrumb showing the environment and the scope. Click the scope name in the breadcrumb to open the asset review. Once a scope has findings, a Findings crumb is also displayed on the asset review, so the two views are used side by side.

Opening a PCI finding notification displays the Findings view for that scope, with the finding selected in the list.

The top bar of the scope also shows the informational tabs Ports, Products, Services, and Certificates. See the Informational Tabs for a Scope section.

PCI findings view

Table Columns

Column

Description

Status

The finding status. See the Finding Statuses section.

Name

The name of the finding.

Severity

The severity with the CVSS score. PCI findings use the three severity levels of the PCI ASV Program Guide: High (CVSS 7.0 and above), Medium (4.0 to 6.9), and Low (below 4.0). The Severity filter offers the same three levels.

Asset

The asset the finding was detected on.

Special note

The ASV special note attached to the finding. Response needed is shown when a response is still required. A lock icon is shown when the response is marked secure. A dash is shown when the finding has no special note.

Updated

When the finding was last updated.

The table supports saved view templates; see View Templates.

A Response needed column is available in the column picker to filter findings that still need an answer.

Finding Statuses

Status values are displayed exactly as the system defines them.

Status

Meaning

NON COMPLIANT

The finding is failing. Remediate and rescan, or dispute it.

COMPLIANT

The finding passes and counts toward compliance.

DISPUTED

A dispute has been raised and awaits an ASV decision.

DISPUTE DETAILS NEEDED

The ASV requested more information. Provide the details and dispute again.

DISPUTE REJECTED

The ASV rejected the dispute. The finding remains failing; it is possible to remediate or to raise a new dispute with stronger evidence.

DISPUTE ACCEPTED

The ASV accepted the dispute. The finding counts as compliant for scope completion.

A scope reaches the COMPLIANT status only when every finding is COMPLIANT or DISPUTE ACCEPTED and every special note has been answered.

Finding Details

Clicking a finding opens the detail panel on the right side of the window. The panel has two tabs, Details and Comments, and the finding status and name in the header.

PCI finding detail

Details Tab

The Details tab contains the full finding information: overview, solution, and classifications. When the finding carries an ASV special note, a PCI special note card is displayed at the top; see the Special Notes section.

Comments Tab

The Comments tab holds the dispute conversation and any other comments on the finding. See the Disputes section. The tab shows a count of the messages.

Informational Tabs for a Scope

When a scope is open, the top bar shows a toggle with the tabs Findings, Ports, Products, Services, and Certificates. Findings lists the PCI findings of the scope. The other tabs list the informational records found on the assets of the scope:

  • Ports - open ports, with the service name, protocol, and banner.

  • Products - detected products and their versions.

  • Services - services detected on the assets.

  • Certificates - certificates, with the subject, the issuer, and the expiry date.

Scope toggle with the Findings, Ports, Products, Services, and Certificates tabs

Each tab follows the selected scope. The list contains only the records of that scope, and this filter cannot be removed. The breadcrumb shows the environment, the scope, and the open tab.

The tabs list the same records, with the same default columns and the statuses Present and False positive, as Findings > Informational. For a description of the columns, see Ports Tab, Products Tab, Services Tab, and Certificates Tab. To export the list, open the overflow menu (three dots) in the toolbar above the table and select Export as CSV or Export as JSON.

Informational records are not PCI findings. They have no severity, cannot be disputed, do not change the compliance status of the scope, and are not included in the PCI report.

In the scope, the tabs are read-only: editing tags, marking or unmarking a false positive, deleting, and bulk actions are not available. To manage a record, go to Findings > Informational, which lists the same records, including those found on PCI scopes. For more information, see Informational.

Click a row to open the detail panel on the right side of the window. The header shows the record name and its status. The panel has two tabs:

  • Details - the asset, the source, and whether the record was seen in the last scan, followed by a card for each matched port, product, service, or certificate. A certificate also shows its chain as Issuer certificate cards. The last cards list the ports, where applicable, and the dates, such as First seen, Last seen, and Age. Click the asset to open the asset list of the scope.

  • Comments - the comments on the record. Comments belong to the record, so they are also shown in Findings > Informational.

Click Close to close the panel.

Ports tab of a scope with the detail panel open

Special Notes

The compliance scan attaches special notes to findings that match specific conditions defined by the PCI ASV Program Guide, for example detected remote access software, load balancers, point-of-sale software, or directory browsing. A special note is a standardized ASV notice; the customer is required to respond to it, declaring how the noted item is implemented and secured in the environment.

To respond to a special note:

  1. Click the finding to open the detail panel. The PCI special note card is displayed on the Details tab.

  2. Enter the response in the Special note field, describing the implementation and any compensating controls.

  3. Toggle Secure to declare the response.

  4. Click the Save special note button.

The response is saved and shown with the finding.

PCI special note card

Every special note in the scope must have a saved response with the Secure toggle enabled before the scope reaches the COMPLIANT status. A note cannot be saved empty. The special note card is displayed only on findings the scan attached a note to.

Disputes

When a failing finding does not apply to the environment - for example a false positive, or a risk mitigated by compensating controls - raise a dispute. Disputes are reviewed by the Outpost24 ASV team, and every step of the exchange is recorded in the finding's comment thread.

Raising a Dispute

A dispute can be raised on findings with the status NON COMPLIANT, DISPUTE REJECTED, or DISPUTE DETAILS NEEDED.

  1. Click the Create dispute button in the finding detail header. The button is available only on disputable findings.

    image-20260826-091320.png


Or:

  1. Right-click the finding in the table and select Create dispute from the context menu.

    Create dispute context menu


Then:

  1. Enter the Reasoning, explaining why the finding does not apply. This field is mandatory.

  2. Optionally, attach proof files such as configuration screenshots, scan evidence, or policy documents.

  3. Click the Create dispute button.

The finding status changes to DISPUTED and the reasoning is posted as the first message of the dispute thread.

Create dispute dialog with a selected prior dispute

Matching Prior Disputes

When a single finding is disputed, the Create dispute dialog shows a Matching prior disputes panel next to the New dispute form. The panel lists customer dispute messages from other findings that share the scope, the asset IP address, the check, or the environment with the current finding. Disputes that match on more of these are listed first, followed by the most recent. The dispute thread of the current finding and the responses of the ASV team are not listed. Only findings the user has access to are included.

Each card shows the start of the dispute text, a match label, and the number of attached proof files. When the asset matches, the card also shows the matching IP address. The match labels are:

  • Exact match - the same check on an asset with the same IP address.

  • Same asset - an asset with the same IP address, with a different check.

  • Similar finding - the same check, scope, or environment on a different asset.

To reuse a prior dispute:

  1. Click a card in the Matching prior disputes panel. The dispute text fills Reasoning, and the proof files of that dispute are listed under Proof with the label Previous.

  2. Edit the reasoning so that it fits the current finding.

  3. Review the previous proof files. Click a file name to download the file, or click the remove icon next to a file that does not apply.

  4. Optionally, upload additional proof files.

  5. Click the Create dispute button.

One card can be selected at a time. Clicking another card replaces the reasoning, including any edits, and the previous proof files with those of the new card. The previous proof files that are still listed when the dispute is created are copied to the new dispute.

The Matching prior disputes panel is shown only when a single finding is disputed. When several findings are disputed at once, enter the reasoning manually. When no prior disputes match, the panel displays No matching prior disputes.

Importing Prior Disputes from a Previous Scope

At the start of a new compliance cycle, disputes raised in the previous scope can be applied to the matching findings of the current scope in one step. When matching disputes exist, the findings of the scope show a Prior disputes available banner with the number of prior disputes found. The import is available on scopes that are not completed, to users with the PCI resource set to View and manage.

Prior disputes available banner and the Import prior disputes menu item

To import prior disputes:

  1. Open the findings of the current scope.

  2. Click Import prior disputes in the banner. Alternatively, open the overflow menu (three dots) in the toolbar above the table and select Import prior disputes.

  3. Select the disputes to import.

  4. Review the summary below the list, for example 3 disputes onto 2 findings.

  5. Click the Import (N) button, where N is the number of selected disputes.

Import prior disputes dialog

The list contains customer dispute messages from the previous scope of the same environment, which is the most recently created scope before the current one. A message is listed when its finding has the same check and the same asset IP address as a finding in the current scope with the status NON COMPLIANT. Each entry shows the check name, the dispute text, the IP address, and the number of attached proof files. Responses of the ASV team are not listed.

When several selected messages match the same current finding, they are combined into one dispute on that finding, oldest first. Their proof files are copied to the new dispute. Each finding that receives a dispute changes to DISPUTED and is reviewed by the ASV team. The message Prior disputes imported. confirms the import, and the findings are refreshed. Close the banner to hide it. Import prior disputes stays available in the overflow menu.

A dispute accepted in an earlier scope is not accepted automatically in the current scope. The ASV team reviews each imported dispute again.

The import is applied as a whole. If any selected dispute can no longer be imported, for example because the matching finding no longer has the status NON COMPLIANT, nothing is imported and the dialog stays open. Up to 200 disputes can be imported at once.

Only findings with the status NON COMPLIANT receive imported disputes. To reuse a prior dispute on a finding with the status DISPUTE REJECTED or DISPUTE DETAILS NEEDED, use the Matching prior disputes panel in the Create dispute dialog. When no prior disputes match, the import dialog displays No exact matches found.

Disputing Multiple Findings

To dispute several findings at once:

  1. Select the findings by checking the boxes on the left hand side.

  2. Click the Create dispute button in the toolbar that is displayed above the table.

  3. Enter the reasoning and optionally attach proof files.

  4. Click the Create dispute button.

One dispute per selected finding is submitted, all with the same reasoning and files. Findings that are not in a disputable status are rejected individually and reported.

The Dispute Thread

The Comments tab of the finding detail shows the dispute conversation first, then any other comments, in chronological order. Messages that raise a dispute carry a Dispute badge, and attachments are listed under the message that provided them; click an attachment to download it.

The ASV team responds with one of three decisions, each posted as a message in the thread:

Decision

Finding status

What to do

Accepted

DISPUTE ACCEPTED

Nothing. The finding counts as compliant for scope completion.

Details requested

DISPUTE DETAILS NEEDED

Read the request in the thread, then raise the dispute again with the requested information or attach the requested evidence.

Rejected

DISPUTE REJECTED

Remediate the finding and rescan, or raise a new dispute with stronger evidence.

Use the Reply field on a conversation to answer the ASV team without changing the finding status. Use the Add a comment field at the bottom of the tab to add a comment that is not a dispute.

Dispute thread

Each finding has one dispute thread. Later disputes and decisions on the same finding continue the same conversation. Disputes and their statuses are preserved when the scope is rescanned.

Once the scope is completed, its findings, special notes, and disputes are locked and no further dispute activity is possible.