| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 5 months |
| seen | Jan 24 at 15:58 | |
| stats | profile views | 0 |
|
Jan 11 |
awarded | Scholar |
|
Jan 11 |
accepted | Precedent for an in-house cardholder information server? |
|
Dec 17 |
comment |
Precedent for an in-house cardholder information server? Thanks for the answer. It's very enlightening. By "can't connect to anything in the CDE", I just meant that it can't fall under the definition of things "connected to the CDE" as mentioned very near the beginning of the section "Scope of Assessment for Compliance with PCI DSS Requirements". Also, we do have in mind to initiate connections from within the CDE and we definitely intend to run our design by our QSA. I do wish we could could find out how other people have done this before diving into it, though. Anyway, many thanks. :) |
|
Dec 14 |
awarded | Editor |
|
Dec 14 |
comment |
Precedent for an in-house cardholder information server? AJ Henderson. Thanks for your input. Unfortunately our payment gateway won't provide all of the functionality necessary to do something like that, and we probably won't be switching any time soon. Whatever we do, we'll pretty much have to do in-house. |
|
Dec 14 |
revised |
Precedent for an in-house cardholder information server? deleted 173 characters in body |
|
Dec 14 |
comment |
Precedent for an in-house cardholder information server? Hello, Polynomial. Thanks for your input. I'll edit my post. |
|
Dec 14 |
asked | Precedent for an in-house cardholder information server? |