IETF Logo Mail Archive

Re: [sacm] Identifying Vulnerability Assessment Code

Adam Montville <adam.w.montville@gmail.com> Tue, 16 May 2017 17:21 UTC

Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24CF712EC13 for <sacm@ietfa.amsl.com>; Tue, 16 May 2017 10:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bLGM3iIi6gQt for <sacm@ietfa.amsl.com>; Tue, 16 May 2017 10:21:41 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A2761294A4 for <sacm@ietf.org>; Tue, 16 May 2017 10:17:25 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id f102so97745026ioi.2 for <sacm@ietf.org>; Tue, 16 May 2017 10:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RlI6n8VaPPBJUqX8ZCfZswyD726baKoLTPlH1knM6Tk=; b=mjMsWxEqHE7G7vB2TOj/d125nj0d6y7ENx728O1VTrPStc0/VEH89dELcqzeM19gKe wNn0UhdDwcL2jEO6FXJwvjFbMD5AOCva76pRV7Nb8gUkd2SfGZq9vFsDDXlHaXre8b4L j6tFDktH+COxa4eHZsjL7OOqTuB+WeajxSc6L9zFpNtJrx4K+paQstRWxdmZoa4pWqXS Rso+BzEX3MZRzJDjPbZmqXTNPjB9jg4gpejLPjnGkkk7g9WT454FtRgtDpMeU5bBh+UG J/ysB1Z51DussfRFY40j0V9JClSGkE9WLrG4xE3zSWIv40n4SaC0N25v5S2cMyD2mQ50 q+BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RlI6n8VaPPBJUqX8ZCfZswyD726baKoLTPlH1knM6Tk=; b=jU7kuPgWWB8Nt1x4z2C97itK5Tz5BXWEe6iMp1FKnijyHxYWU95pMck2D5vuRv3mva 5hTT2fmr0s4YLyH+dKgmGyDojLZSAoyH8iWXQKIjakVBXuqX8lepXU8bslxlfNLedSGs JjOJy3/sRjz1vKqOlv4H1zAxmwUIUm+iCLrTcJ1fx27pxTMXXC6HgJgLJdXfTVUoD2xx de3A7PjJ9uthphZb5WgX1430Jyf+adEmWSV82MZZaY+fApkX34g8ZA8TmGBztGq09P/2 VbAY/vY4LxNOUXpfiF7P9ZUbI3C4Eyr/36cqHOz7bhKSQwurcVOewEE3wGBw0V+CzVV9 gJoA==
X-Gm-Message-State: AODbwcDcgSTJare6V2KNFspSw1Uh7VEkGbsaLEcCj2jbjRqLEpchf51q 3wtu1Eabn9RTSoDn9I+CE0iB65nQKw==
X-Received: by 10.107.23.66 with SMTP id 63mr7036700iox.184.1494955044713; Tue, 16 May 2017 10:17:24 -0700 (PDT)
MIME-Version: 1.0
References: <CACknUNWs8_4pBWPJHNyzVjb+aT3mb1=MqWEnyoWPiOzkz7jZEA@mail.gmail.com> <DM5PR09MB1307185DAA5B12D76926FD0CF0E60@DM5PR09MB1307.namprd09.prod.outlook.com>
In-Reply-To: <DM5PR09MB1307185DAA5B12D76926FD0CF0E60@DM5PR09MB1307.namprd09.prod.outlook.com>
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 16 May 2017 17:17:13 +0000
Message-ID: <CACknUNUV1bNkGN_OS3aY9U5t92YpCGcWTcwfsEAmME-__s4EEQ@mail.gmail.com>
To: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05c23e653bf7054fa75879"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/TZubOz3oXmnjcIY6ihVVsphaFc8>
Subject: Re: [sacm] Identifying Vulnerability Assessment Code
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2017 17:21:43 -0000

Great, thanks!

On Tue, May 16, 2017 at 11:50 AM Banghart, Stephen A. (Fed) <
stephen.banghart@nist.gov> wrote:

> Adam,
>
>
>
> I’m planning on bringing a ROLIE implementation with me to the Hackathon
> that could fill the Vulnerability Detection Data Repository component. The
> ROLIE implementation could also provide arbitrary data to any component
> along the pipeline in order to simulation data input/output. I intend to
> pre-load the ROLIE server implementation with sample NVD data and sample
> SWID tags so that we have something for the other components to work with
> if need be.
>
>
>
> Regards,
>
> Stephen Banghart
>
>
>
> *From:* sacm [mailto:sacm-bounces@ietf.org] *On Behalf Of *Adam Montville
> *Sent:* Tuesday, May 16, 2017 9:07 AM
> *To:* sacm@ietf.org
> *Subject:* [sacm] Identifying Vulnerability Assessment Code
>
>
>
> All:
>
>
>
> Last week a list of goals were sent to this list [1]. I did see some
> back-channel conversation, but nothing that made its way to the list. Then,
> those are our stated goals, and it is now time to start considering what
> code may already exist for our agreed upon components. Once again, these
> components are listed at [2] and repeated here:
>
>
>
> * Vulnerability Detection Data Repository
>
> * Vulnerability Assessor
>
> * Endpoint Repository
>
> * Collector
>
> * Target Endpoint
>
> * Assessment Results Repository
>
>
>
> We need to drive this to some conclusion relatively quickly. If you have
> or know of components filling these roles, please respond by the end of
> this week. Note that the target endpoint component will likely be
> determined based on which real-world vulnerability(ies) we choose to deal
> with as part of this exercise.
>
>
>
> Kind regards,
>
>
>
> Adam
>
>
>
>
>
> [1] https://mailarchive.ietf.org/arch/msg/sacm/LskQ7tj9Wvy1-0DSlEN_VakYj64
>
>
> [2] https://mailarchive.ietf.org/arch/msg/sacm/w_kL2vzDBPk0NN9N1WQcpb3Qwfw
>
>

v2.23.0 | Report a Bug | By Email