FDCC results

--===============0486670130==
Content-Type: multipart/alternative; boundary=000e0cd5d0227a873a046398e2af

--000e0cd5d0227a873a046398e2af
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I have run the Windows XP Desktop v.2 audit files on my workstations and
have found that many of them are failing because the configuration does not
exactly match the configuration in the Nessus audit compliance file.

Are the audit compliance files not scripted to be inclusive, meaning that a
configuration on the target host can be stricter than what FDCC requires,
with out it showing up as a failure in the compliance scan?

Richard

--000e0cd5d0227a873a046398e2af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<div>I have run the Windows XP Desktop v.2 audit files on my workstations and have found that many of them are failing because the configuration does not exactly match the configuration in the Nessus audit compliance file. </div>

<div>&nbsp;</div>
<div>Are the audit compliance files not scripted to be inclusive, meaning that a configuration on the target host can be stricter than what FDCC requires, with out it showing up as a failure in the compliance scan?</div>

<div>&nbsp;</div>
<div>Richard</div>

--000e0cd5d0227a873a046398e2af--

--===============0486670130==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
--===============0486670130==--