October 29, 2026: scope language and worked-example counts#
The PCI scope guide and its downloadable register now keep CDE relationship separate from the assessment scope decision. Connected-to or security-impacting components are not an intermediate exemption from scope. The guide links the PCI SSC clarification and retains the responsible entity’s decision as the authority.
The inventory-audit example now reconciles 412 original records, 414 observed devices and eight object-level exceptions, with seven closed and one unresolved. Its active-record count and disposal history are stated separately.
The naming guide now distinguishes historical DNS preferred syntax from its later hostname update and the actual receiving application. Cable-layout estimates are identified as assumed arithmetic rather than measured readability. Fiber and busway examples no longer imply universal panel mappings, source independence or permission to relocate equipment. Intake and materials guidance now keeps validation, marking ownership and product-specific preparation decisions explicit.
These are editorial corrections to explanations and fictional examples, not results of physical equipment tests.
September 2026: cable examples and tool checks#
The cable-endpoint guide's label-dimension table and related figures were corrected to distinguish the dimensions used for wrap coverage and printed layout. The shared connectivity illustration now uses fixed A/B endpoint names. Those names remain the same at either end; local HERE/THERE references must reverse when read from the opposite end.
The label-size tool now distinguishes wrap-direction length from axial printable height and text orientation. Its output is a limited estimate to verify with a physical print, not confirmation that a product is suitable. The port-strip tool blocks export when the selected column numbering cannot represent the requested rows and port count.
Source-review records#
Visible source-review labels now come from recorded source dates. Where dates are missing, the site says that the review records are incomplete. A working publisher link does not establish that its technical content was reviewed, and a page update is not automatically a source review.
Report another issue#
Use the contact page to send a page URL, the issue and supporting evidence. This log summarizes material published corrections; minor spelling and formatting changes may appear only in the page's updated date.