×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Has anyone on the list received specific questions or had discussions
related to how the use of DDM from system to system affects the
determination of scope for the PCI DSS?
The primary goal of any organization subject to implementing and maintaining
the controls required by the PCI DSS is to simply limit the scope of
networks and systems that are part of the cardholder data environment (well,
it ain't always simple!). In a multi-partitioned IBM i environment, there
are some LPARs in-scope and many that are not, but the not-in-scope systems
do indeed interface with the in-scope systems via DDM. The easy answer is
exit programs with rules that control inbound access to the in-scope LPARs,
but I was wondering if anyone else has done something differently or
possibly even came up with a good answer as to why additional controls for
DDM are not needed (perhaps, due to some whiz-bang IBM i architecture 'this
or that' kind of thing, etc.)?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
