Operations

PCI scan planning: scope, report, follow-up

A practical path for PCI DSS 11.3–oriented scanning: define authorized scope, run defensive checks, read the findings report, and schedule follow-up. Secure Assess delivers scan findings, a PDF with 11.3 mapping, and ASV-readiness PASS or FAIL — not certification or official ASV filing.

1. Scope what you own

Add targets you own or are authorized to assess. Verify ownership in the app, then create a scope that matches the cardholder environment you intend to check. Do not scan systems you are not authorized to assess.

2. Choose external and credentialed coverage

Run a defensive external scan of internet-facing hosts and services. When appropriate, supply credentials for a credentialed pass so the assessment can see patch and configuration detail from the authenticated side. Credentials are used to read, not to change.

3. Read the findings report

Secure Assess produces AI-triaged findings and a PDF that includes scope, scan findings, PCI DSS 11.3 mapping, advice, and ASV-readiness PASS or FAIL. That deliverable is for your review and remediation planning — we do not file it with a card brand.

4. Follow up on a schedule

Set a scan cadence so the same authorized scope runs again. Comparable reports make it easier to see what changed after you apply advice. Applying fixes remains your responsibility; the product reports and advises only.

Planning caveats

This is PCI DSS 11.3 VA / ASV-readiness — not a full 4.0 program.
ASV-readiness PASS/FAIL is not official ASV attestation or card-brand filing.
Not PCI 11.4 penetration testing.
Not CHD discovery or a complete cardholder-data inventory.

Canonical product page: PCI DSS 11.3 vulnerability assessment & ASV-readiness · VA workflow · pricing · open the app.

Plan the scan, then run it in the app

Authorize scope, start a defensive PCI-oriented assessment, and download the PDF with 11.3 mapping and ASV-readiness PASS or FAIL.

Start a scan PCI DSS 11.3