Re: [scap_interest] SCE XCCDF

As a standards content consumer, I would prefer we implement whatever needs to be improved within the OVAL language. As to what needs to be improved, we should probably compile a list and discuss it.

Aharon

DTCC Non-Confidential (White)
---------------------------------------------------
Michael "Aharon" Chernin
Security Automation Program Manager
Corporate Information Security -Depository Trust & Clearing Corporation
O: 813-470-2173

> -----Original Message-----
> From: scap_interest-bounces@ietf.org [mailto:scap_interest-
> bounces@ietf.org] On Behalf Of Chandrashekhar B
> Sent: Friday, February 24, 2012 12:14 PM
> To: David Solin; scap_interest-bounces@ietf.org; scap_interest@ietf.org
> Subject: Re: [scap_interest] SCE XCCDF
> 
> This is an alternative option to cases where OVAL cannot be used to as a
> checking language. But there will always be confusion when to use what as
> the capabilities of OVAL improve. There is certainly one use case, to develop
> remote checks to determine vulnerabilities, assuming OVAL is not meant for
> that. Any effort to standardize this interface is good.
> 
> Thanks,
> Chandra.
> Sent from BlackBerry(r) on Airtel
> 
> -----Original Message-----
> From: David Solin <david@joval.org>
> Sender: scap_interest-bounces@ietf.org
> Date: Fri, 24 Feb 2012 09:54:33
> To: <scap_interest@ietf.org>
> Subject: Re: [scap_interest] SCE XCCDF
> 
> _______________________________________________
> scap_interest mailing list
> scap_interest@ietf.org
> https://www.ietf.org/mailman/listinfo/scap_interest
> 
> _______________________________________________
> scap_interest mailing list
> scap_interest@ietf.org
> https://www.ietf.org/mailman/listinfo/scap_interest
<BR>_____________________________________________________________
<FONT size=2><BR>
DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email
in error, please notify us immediately and delete the email and any
attachments from your system. The recipient should check this email
and any attachments for the presence of viruses.  The company
accepts no liability for any damage caused by any virus transmitted
by this email.</FONT>