-------------------------------------------
From: Kyle Hourihan
Sent: Tuesday, November 04, 2008 4:52:57 PM
To: Tom Grabowski
Cc: [EMAIL PROTECTED]; Jonathan Hart ([EMAIL PROTECTED])
Subject: RE: Explanation of PCI 10.5.5 verificiation
Auto forwarded by a Rule

Anyone have anything for me?  I am sure someone has something on
this.....??!

 

 

From: Tom Grabowski 
Sent: Monday, November 03, 2008 11:46 AM
To: Kyle Hourihan
Subject: Re: Explanation of PCI 10.5.5 verificiation

 

Kyle,

Who is the customer?

Thanks,

Tom



   _____  

From: Kyle Hourihan <[EMAIL PROTECTED]>
Date: Mon, 3 Nov 2008 11:25:12 -0800
To: <[EMAIL PROTECTED]>, Chima Njaka <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Subject: Explanation of PCI 10.5.5 verificiation

>From the customer:
 
Kyle,
   Looking for a bit more detail about "how" a PCI auditor would
validate 10.5.5 compliance based on the use of Log Logic. The matrix
below doesn't really constitute compliance validation. Exactly what in
these reports and alerts (more likely the technology behind log
encryption, hashing and integrity checks) is used to demonstrate
compliance. Thanks.

 
Does anyone have the canned response to how we are able to make sure our
logs are not modified and how we lock down our logs with hashes?  And
can detect tampering?
 
I could write it myself, but I am sure someone else out there already
has a response.
 
Thanks in advance,
Kyle
 
 
Kyle X. Hourihan
SE, Business Development
LogLogic, Inc <http://www.loglogic.com/> .

[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
+1.408.215.5936



Reply via email to