Re: pci compliance

acks you can throw at a box thats fully closed up, and the aim is not to get it but rather to chew up all the ram and cpu and kill the box off. I suggest you read the PCI compliance document for the relevant level and make sure you test the system to comply with the documented requirements. _

RE: pci compliance

On Behalf Of Ross Cameron > On Mon, Jul 28, 2008 at 7:51 PM, kalin m <[EMAIL PROTECTED]> wrote: >> >> i'm about to submit a freebsd system to be scanned for pci compliance... >> >> is there any particular gotchas with bsd systems that can be detected at

Re: pci compliance

full of a penetration can you have if (almost) all incoming ports are blocked? thanks Ross Cameron wrote: On Mon, Jul 28, 2008 at 7:51 PM, kalin m <[EMAIL PROTECTED]> wrote: hi all... i'm about to submit a freebsd system to be scanned for pci compliance... is there a

Re: pci compliance

On Mon, Jul 28, 2008 at 7:51 PM, kalin m <[EMAIL PROTECTED]> wrote: > hi all... > > i'm about to submit a freebsd system to be scanned for pci compliance... > > is there any particular gotchas with bsd systems that can be detected at > the time of pci complianc

pci compliance

hi all... i'm about to submit a freebsd system to be scanned for pci compliance... is there any particular gotchas with bsd systems that can be detected at the time of pci compliance scanning? i know they use something like nmap if not nmap itself and i did myself on that machine and d