IETF Logo Mail Archive

Re: [scap_interest] Operational Aspects

Adam Montville <amontville@tripwire.com> Tue, 14 February 2012 22:18 UTC

Return-Path: <amontville@tripwire.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 33A9821E800E for <scap_interest@ietfa.amsl.com>; Tue, 14 Feb 2012 14:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.27
X-Spam-Level:
X-Spam-Status: No, score=-4.27 tagged_above=-999 required=5 tests=[AWL=-0.671, 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 B2-SYPTScRgb for <scap_interest@ietfa.amsl.com>; Tue, 14 Feb 2012 14:18:19 -0800 (PST)
Received: from VA3EHSOBE009.bigfish.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id EB62721F84EC for <scap_interest@ietf.org>; Tue, 14 Feb 2012 14:18:18 -0800 (PST)
Received: from mail112-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.23; Tue, 14 Feb 2012 22:18:15 +0000
Received: from mail112-va3 (localhost [127.0.0.1]) by mail112-va3-R.bigfish.com (Postfix) with ESMTP id 411FE3A029E; Tue, 14 Feb 2012 22:18:18 +0000 (UTC)
X-SpamScore: -30
X-BigFish: VPS-30(zz9f17Rzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h946h)
X-Forefront-Antispam-Report: CIP:174.47.84.216; KIP:(null); UIP:(null); IPV:NLI; H:PDXHB01.tripwire.com; RD:174-47-84-216.static.twtelecom.net; EFVD:NLI
Received: from mail112-va3 (localhost.localdomain [127.0.0.1]) by mail112-va3 (MessageSwitch) id 1329257896744519_8972; Tue, 14 Feb 2012 22:18:16 +0000 (UTC)
Received: from VA3EHSMHS014.bigfish.com (unknown [10.7.14.245]) by mail112-va3.bigfish.com (Postfix) with ESMTP id A65BC4C0047; Tue, 14 Feb 2012 22:18:16 +0000 (UTC)
Received: from PDXHB01.tripwire.com (174.47.84.216) by VA3EHSMHS014.bigfish.com (10.7.99.24) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 14 Feb 2012 22:18:16 +0000
Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 14 Feb 2012 14:27:01 -0800
Received: from PDXMB02.tripwire.com ([fe80::f997:7b65:8e64:438e]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0355.002; Tue, 14 Feb 2012 14:18:15 -0800
From: Adam Montville <amontville@tripwire.com>
To: "Kent_Landfield@McAfee.com" <Kent_Landfield@McAfee.com>, "scap_interest@ietf.org" <scap_interest@ietf.org>
Thread-Topic: [scap_interest] Operational Aspects
Thread-Index: AQHM611pUdMxDo8SrEm/UADfFmLhZ5Y9b7oA//+GooA=
Date: Tue, 14 Feb 2012 22:18:14 +0000
Message-ID: <CB601365.9241%amontville@tripwire.com>
In-Reply-To: <CB602E89.2C54F%kent_landfield@mcafee.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [172.16.97.166]
x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5EA964CA7B04E7449DDC1D092F58DF53@tripwire.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: tripwire.com
Subject: Re: [scap_interest] Operational Aspects
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: Tue, 14 Feb 2012 22:18:20 -0000

Fair enough.  Just throwing things against the wall as they come to mind.

Adam

From: kent_landfield <kent_landfield@mcafee.com<mailto:kent_landfield@mcafee.com>>
Date: Tue, 14 Feb 2012 15:32:38 -0600
To: Adam Montville <amontville@tripwire.com<mailto:amontville@tripwire.com>>, <scap_interest@ietf.org<mailto:scap_interest@ietf.org>>
Subject: Re: [scap_interest] Operational Aspects

Adam,

We have more than enough on our plate with the specification / I-D work.  Let's see if we can deal with this in a more appropriate forum. I do not see this as that forum.  My 2cents…

Thanks.

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee | An Intel Company
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

From: Adam Montville <amontville@tripwire.com<mailto:amontville@tripwire.com>>
Date: Tue, 14 Feb 2012 15:12:51 -0600
To: "scap_interest@ietf.org<mailto:scap_interest@ietf.org>" <scap_interest@ietf.org<mailto:scap_interest@ietf.org>>
Subject: [scap_interest] Operational Aspects

While we're all bantering about on security automation, there's another side to the story.  Are there any operational concerns we might address within a WG should one be formed?  For example, we have, in the United States, NVD hosting a repository of information.  CCE identifiers are moderated and assigned by an operational process.  As new enumerations are published and new types of content are conceived, it's easy to imagine the need for some operational standardization.

Should we consider standardizing some of these processes, and if so would the WG we seek to establish be the appropriate place for that work?

Regards,

Adam W. Montville | Security and Compliance Architect

Direct: 503 276-7661
Mobile: 360 471-7815

TRIPWIRE | Take CONTROL
http://www.tripwire.com

_______________________________________________
scap_interest mailing list
scap_interest@ietf.org<mailto:scap_interest@ietf.org>
https://www.ietf.org/mailman/listinfo/scap_interest

v2.27.6 | Report a Bug | By Email | System Status