Re: [scap_interest] Security automation and MILE

<kathleen.moriarty@emc.com> Fri, 17 February 2012 17:58 UTC

Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: scap_interest@ietfa.amsl.com
Delivered-To: scap_interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4029321F8764; Fri, 17 Feb 2012 09:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.956
X-Spam-Level:
X-Spam-Status: No, score=-9.956 tagged_above=-999 required=5 tests=[AWL=0.643, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ht4gODQCzmDE; Fri, 17 Feb 2012 09:58:37 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 82DB421F8760; Fri, 17 Feb 2012 09:58:37 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1HHwY7F028258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2012 12:58:34 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 17 Feb 2012 12:58:23 -0500
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1HHwMtt026327; Fri, 17 Feb 2012 12:58:23 -0500
Received: from mx06a.corp.emc.com ([169.254.1.82]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Fri, 17 Feb 2012 12:58:22 -0500
From: <kathleen.moriarty@emc.com>
To: <lnunez@c3isecurity.com>, <nea@ietf.org>
Date: Fri, 17 Feb 2012 12:58:21 -0500
Thread-Topic: [scap_interest] Security automation and MILE
Thread-Index: AcztnVFw7tYitifbQcqLIdKlv4KOiAAAB7Rw
Message-ID: <AE31510960917D478171C79369B660FA0E308BD1F8@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E2F547B48@MX06A.corp.emc.com> <F80AF067-F96C-485E-AD78-C03F154DE457@c3isecurity.com>
In-Reply-To: <F80AF067-F96C-485E-AD78-C03F154DE457@c3isecurity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: scap_interest@ietf.org
Subject: Re: [scap_interest] Security automation and MILE
X-BeenThere: scap_interest@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion List for IETFers interested in the Security Content Automation Protocol \(SCAP\)." <scap_interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scap_interest>
List-Post: <mailto:scap_interest@ietf.org>
List-Help: <mailto:scap_interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scap_interest>, <mailto:scap_interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2012 17:58:38 -0000

Hi Luis,

We will have an update to the GRC-exchange document that generalizes RID to cover the exchange of other schemas posted soon.  This is part of the MILE charter.  It may hit some of the objectives for transport, although there could be others that are extensions from NEA that I am also interested to learn about.  We should try to fit the pieces together as we evolve specifications to standards for this ecosystem.

Thanks,
Kathleen

-----Original Message-----
From: Luis Nunez [mailto:lnunez@c3isecurity.com] 
Sent: Friday, February 17, 2012 12:55 PM
To: Moriarty, Kathleen; nea@ietf.org
Cc: scap_interest@ietf.org
Subject: Re: [scap_interest] Security automation and MILE

Along the lines of what Kathleen is doing.  I was wondering what are the Security Automation (SCAP) connections with NEA?

>From an endpoint assessment, SCAP is a natural fit.  Are there transport specifications that a SCAP client could leverage to converse beyond a NEA server? 

thanks.

-ln

On Feb 14, 2012, at 9:47 AM, <kathleen.moriarty@emc.com>; <kathleen.moriarty@emc.com>; wrote:

> Greetings,
> 
> In support of this effort, I plan to write and submit a draft very soon to show the relevance of this work to the IETF work in MILE.  The Structured Cybersecurity Information draft that extends IODEF is a very clear connection.  The GRC-Exchange work is another connection point.  Once I have it posted, I will share the link to this mailing list.
> 
> Best regards,
> Kathleen
> 
> _______________________________________________
> scap_interest mailing list
> scap_interest@ietf.org
> https://www.ietf.org/mailman/listinfo/scap_interest