Re: [scap_interest] Security automation and MILE

Luis Nunez <lnunez@c3isecurity.com> Fri, 17 February 2012 18:38 UTC

Return-Path: <lnunez@c3isecurity.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 3EC4821E8071; Fri, 17 Feb 2012 10:38:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sdL8qGGGrC76; Fri, 17 Feb 2012 10:38:14 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 82DD221E8062; Fri, 17 Feb 2012 10:38:14 -0800 (PST)
Received: by ghbg16 with SMTP id g16so2251908ghb.31 for <multiple recipients>; Fri, 17 Feb 2012 10:38:14 -0800 (PST)
Received: by 10.236.185.42 with SMTP id t30mr2318979yhm.105.1329503894083; Fri, 17 Feb 2012 10:38:14 -0800 (PST)
Received: from [172.16.1.103] (cpe-066-057-025-190.nc.res.rr.com. [66.57.25.190]) by mx.google.com with ESMTPS id n10sm8220564ani.8.2012.02.17.10.38.12 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Feb 2012 10:38:13 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Luis Nunez <lnunez@c3isecurity.com>
In-Reply-To: <80B432C0A0D105468E74A98942733F77181DD5F0@IMCMBX04.MITRE.ORG>
Date: Fri, 17 Feb 2012 13:38:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B1CD04C-711D-44BD-BAE0-638792BFAA17@c3isecurity.com>
References: <AE31510960917D478171C79369B660FA0E2F547B48@MX06A.corp.emc.com> <F80AF067-F96C-485E-AD78-C03F154DE457@c3isecurity.com> <80B432C0A0D105468E74A98942733F77181DD5F0@IMCMBX04.MITRE.ORG>
To: "Schmidt, Charles M." <cmschmidt@mitre.org>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQlKKL8asvzZj4AwGlQH+u9TuoYeEr+5YVl9nvkq58uIkwEgDPfvbekKvo/8Myxn484h/c4x
Cc: "nea@ietf.org" <nea@ietf.org>, "scap_interest@ietf.org" <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 18:38:15 -0000

Charles,
thanks for info. and glad to see some key people working towards this.  We look forward to putting all this together.

-ln


On Feb 17, 2012, at 1:12 PM, Schmidt, Charles M. wrote:

> Hi Luis,
> 
> In fact, I am working on a TCG specification (along with Paul Sangster, Kent
> Landfield, and Steve Hanna) for exchange of SCAP information within TCG's
> Trusted Network Connect, which is NEA in the IETF. So yes - I completely
> agree that it is a natural fit and we are hoping to have a TCG spec
> outlining that fit by the end of the year. :)
> 
> Charles
> 
>> -----Original Message-----
>> From: scap_interest-bounces@ietf.org [mailto:scap_interest-
>> bounces@ietf.org] On Behalf Of Luis Nunez
>> Sent: Friday, February 17, 2012 11:55 AM
>> To: kathleen.moriarty@emc.com>;; 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
>> 
>> _______________________________________________
>> scap_interest mailing list
>> scap_interest@ietf.org
>> https://www.ietf.org/mailman/listinfo/scap_interest