Re: [scap_interest] Security automation and MILE

"Schmidt, Charles M." <cmschmidt@mitre.org> Fri, 17 February 2012 18:12 UTC

Return-Path: <cmschmidt@mitre.org>
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 8B78E21F8679; Fri, 17 Feb 2012 10:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Y1gn0xG7B5V5; Fri, 17 Feb 2012 10:12:57 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9593221F865E; Fri, 17 Feb 2012 10:12:57 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 04D8621B1326; Fri, 17 Feb 2012 13:12:57 -0500 (EST)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id BA3D321B161D; Fri, 17 Feb 2012 13:12:56 -0500 (EST)
Received: from IMCMBX04.MITRE.ORG ([169.254.4.153]) by IMCCAS02.MITRE.ORG ([129.83.29.79]) with mapi id 14.01.0339.001; Fri, 17 Feb 2012 13:12:56 -0500
From: "Schmidt, Charles M." <cmschmidt@mitre.org>
To: Luis Nunez <lnunez@c3isecurity.com>, "kathleen.moriarty@emc.com>" <kathleen.moriarty@emc.com>, "nea@ietf.org" <nea@ietf.org>
Thread-Topic: [scap_interest] Security automation and MILE
Thread-Index: AQHM7Z1MhsBinub86E+b26ttgPPGNJZBYusw
Date: Fri, 17 Feb 2012 18:12:55 +0000
Message-ID: <80B432C0A0D105468E74A98942733F77181DD5F0@IMCMBX04.MITRE.ORG>
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: yes
X-MS-TNEF-Correlator:
x-originating-ip: [129.83.31.51]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0065_01CCED6D.779C9370"
MIME-Version: 1.0
Cc: "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:12:58 -0000

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