Why the Calendar Decides Whether the Test Counts

GDF maps your contractual and regulatory requirements to a defined testing scope, evidence plan and reporting schedule.

The reason readiness matters more than the test itself is that the evidence an auditor accepts has a shape. It begins with a scope statement that explains why the systems tested are the systems the framework cares about, continues through signed rules of engagement and a documented methodology, presents findings with severity and reproduction detail, records remediation and closes with a retest showing each finding's status. A test that starts with the scope defined produces a report that explains its own coverage. A test scheduled with time for remediation and retest closes with a retest record for each finding. Both come from readiness, and the items below are what to assemble before the tester's first day.

The Order of Readiness, From Boundary to Retest

We work with your security, compliance and legal teams to agree on the priorities and deliverables.

With the boundary drawn, the rules of engagement follow: the systems in and out of scope, the test windows, whether production or an identical staging environment is tested, the credentials and roles the tester will use, the techniques permitted and the escalation contacts who can be reached during testing. Then the supporting records are gathered. The last twelve months of findings and threats, which PCI expects the methodology to consider. The vulnerability scan history, internal and external, with rescans after changes. The segmentation controls as configured. Finally, before the test begins, remediation owners and change windows are named for each system in scope, because a finding fixed within the window can be retested within it. Our penetration testing and vulnerability assessment services are delivered as separate records because auditors treat them as separate controls.

Who Owns the Scope, the Rules and the Fixes

The compliance officer owns the deadlines and the framework matrix. The CISO or security lead owns the scope and signs the rules of engagement, and where litigation or enforcement exposure exists, the engagement can run under legal direction from the start. Network engineering owns the diagrams and the segmentation configuration and stays available during internal testing. Application owners own the credentials, the test accounts and the staging decision for each application. IT operations owns the remediation calendar and the change windows. The tester owns the methodology, the evidence and the retest record, and works within the scope the organization sets.

Give the people who will try to help a defined role in the plan. A system administrator with a patch to apply during the test routes it through the escalation contact, so the report and the retest baseline describe the same environment. A network engineer who sees the tester approaching a segment leaves the firewall rules as they stand, so the finding reflects the environment the assessor will review. A developer who sees the alerts start checks the rules of engagement before touching a test account, because the test is authorized. The rules of engagement name a single escalation path for exactly these moments, and every change made during the window is recorded so the report and the environment tell one story.

What Auditors Look For in a Completed Test

The first thing an auditor checks is that the test is a test. A vulnerability scan compares observed services against a database of known weaknesses and is valuable as a recurring control, and the penetration test builds on it by checking whether a weakness is exploitable, whether two medium findings chain into a domain compromise and whether the regulated systems are reachable from where an attacker would stand. The second is coverage: production, or a staging environment identical to it, and the internal segment as well as the external perimeter, so the report covers what the requirement covers. The third is the retest. An auditor reads a finding as closed once the tester has confirmed the fix.

The quieter items are documentary. A methodology written down and adopted by the organization as its own lets the entity show it defined and followed one. A scope statement that explains how each listed host relates to the framework's boundary answers the coverage question before it is asked. A segmentation test dated after the most recent network change is what the requirement calls for. And an attestation letter carries the weight of the engagement record behind it. The audit and legal preparation library on this site sets out the records each framework's reviewer expects, so the engagement file can be assembled alongside the test.

How GDF Supports Compliance Officers, Internal Auditors and Security Teams

Global Digital Forensics has delivered security testing and forensic examinations since 1992 from sixteen US offices. Our penetration testing engagements begin with scoping against the framework boundaries, a rules of engagement document the organization signs and a methodology the organization can adopt as its own. Testing proceeds from outside and inside, with every finding confirmed by exploitation where it is safe to do so and evidence captured at each step. After remediation we retest each exploitable finding and record the result. The deliverable is organized the way an assessor reads it: methodology, scope with the boundaries tested, dates, findings with evidence, remediation, retest results and a framework matrix that maps each finding and control to the Part 500 section, PCI requirement, SP 800-171 practice or trust services criterion it bears on.

Internal auditors use the matrix to populate their workpapers. The CISO uses the technical appendix to drive remediation. The executive narrative serves leadership and the legal team, and where exposure exists the engagement runs under legal direction so the findings reach the people who need them in the form they need. Our clients include Fortune 1000 companies and AmLaw 100 firms, and our examiners have testified in federal and state courts when a security posture became a litigated question. The initial consultation is free. If the filing date is closer than the time you need for testing, remediation and retest, call (800) 868-8189 and we will build the calendar backward from the deadline with you on the first call.

The Checklist at a Glance

The readiness items to assemble before a penetration test, who owns each one, where it lives and how quickly it goes stale.
ItemWho actsWhere it livesHow fast it expires
Framework deadlinesCompliance officerPart 500 April 15 filing, PCI assessment date, SOC 2 period endFixed by the regulator or assessor
Scope and boundary diagramSecurity lead with network engineeringNetwork and data flow diagrams, CDE definitionStale after any significant change
Rules of engagementCISO signs with legal review, tester countersignsSigned engagement fileRenewed for each test window
Prior twelve months of findings and threatsSecurity operationsTicketing system and the last reportPCI expects the prior twelve months reviewed
Vulnerability scan cadenceSecurity operations with the scan vendorASV portal and internal scannerPCI quarterly, with rescans after changes
Segmentation controlsNetwork engineeringFirewall and access control configurationsPCI annual, every six months for service providers
Remediation owners and change windowsIT operationsChange management calendarRetest starts once the fixes land
Retest record and attestationTester, then compliance files itFinal report, framework matrix, attestation letterPoint in time, stale after the next change

Download the Checklist and Workbook

The ZIP file has four parts: a printable HTML copy of this checklist, a readiness workbook CSV, an obligation register CSV and a README file. Download the Penetration Test Readiness Checklist and Registers (ZIP). The workbook runs nine rows from the requirement and its edition through scope, rules of engagement, scanning, penetration and segmentation testing, remediation and verification, incident and filing clocks, and reporting. The obligation register lists eleven candidate duties, among them PCI DSS scanning and penetration testing, with eighteen columns for the instrument and edition, the exact clause, the cadence or trigger, the due date and how it was calculated, the decision owner, the date the source was verified and the applicability decision. Download it directly, or introduce yourself to GDF first; the choice is yours. If the assessment date is already set and the scope is not, the download can wait. Call (800) 868-8189 and a senior tester will work through the boundary and the calendar with you. The initial consultation is free.