Re: [sacm] Hackathon Goals and Stretch Goals

Adam Montville <adam.w.montville@gmail.com> Tue, 09 May 2017 19:29 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 D24E61289B5 for <sacm@ietfa.amsl.com>; Tue, 9 May 2017 12:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level:
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 yRcylzPxRky9 for <sacm@ietfa.amsl.com>; Tue, 9 May 2017 12:29:42 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 C95271200B9 for <sacm@ietf.org>; Tue, 9 May 2017 12:29:42 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id p24so307531ioi.0 for <sacm@ietf.org>; Tue, 09 May 2017 12:29:42 -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=1k7fWjvRi31ldpSFomWnr8/FT/PaMU5+xkH+cYQtDRo=; b=eCJEqTOBY1/Hkd2eiQ0EBjESXt9ZZoeM55eBVCB/UI9i1x/JUKDMihCAQqPcukIg6V U5jB9aBLNMYPy87ld5qQgvGtMEHiz5liUNELL1m6sQJ9r4gSguLQrHBVL0ZDhrPbI3RD HKW31hg2SHBButu3P0utHFUqIKrFfOOWltEWhTfdVyDE8+hx3u/frWDoa4ztOKkygk2Z uU11Dn55Zvzb3sEr5doYTLEOYlSK8SbJoDGGeFdp5YoKzFdq3qUE/p+X1xkduTlE232f q1x8vkHK+eYv19FnIItxzh1ZGjZdTIMgLl2YKkeS1EDfaDDrzDHRu6QubmZtQx10WMRZ I0XQ==
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=1k7fWjvRi31ldpSFomWnr8/FT/PaMU5+xkH+cYQtDRo=; b=evwP8HzNWlgJxmOPFYlgVn0ckjx8ozNJEUNbxagOeeZJwzfrmYwewtoZDnWwJWtbfp U5RNMqvIXRWZSGMpO4CfUEwcQ4U02Jr2QtsGt/9G6Q2OBZ0s41K93CEdukNZuEx9/LFb qIJQ3g/3tID3vhVJNCI+AgCfeixmtIe6W0YkHnaThz0956LtRPt/3SO7BnUYVQOio+Vz gcEwoXAuACqX5FQ8GC7ypiPeOdyiNcDdqCPhKVGXRMO7Zh7kGEDWiZXZWr/sx/tanEHj UEIaCSVwjmBVcQXQEyhMfBkOyap3zE2XSncs9iwMJbaodCzXtyByGczz8A8lN1bA0owY CSSg==
X-Gm-Message-State: AODbwcBwteivgFmxA873PeeqKWTly9qzYFqjAofODFiIR9uuv+zREsh+ UTmv7dNyss9l1dUadfqtd6VN+zYbW/Bs
X-Received: by 10.107.23.129 with SMTP id 123mr22243iox.184.1494358182030; Tue, 09 May 2017 12:29:42 -0700 (PDT)
MIME-Version: 1.0
References: <CACknUNUhqqdumk1wombsAha0TQS4O4dNpajUs2Ak4jWDWZHXaA@mail.gmail.com>
In-Reply-To: <CACknUNUhqqdumk1wombsAha0TQS4O4dNpajUs2Ak4jWDWZHXaA@mail.gmail.com>
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 09 May 2017 19:29:31 +0000
Message-ID: <CACknUNUQ_sgw46GsU8LoOq1puEyo8DUnJ4599h0GE=+Nc2Hxow@mail.gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05bcc69b7655054f1c6020"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/LskQ7tj9Wvy1-0DSlEN_VakYj64>
Subject: Re: [sacm] Hackathon Goals and Stretch Goals
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, 09 May 2017 19:29:45 -0000

All:

This week Dave and I have had an opportunity to discuss these a bit
further. We've come up with the following set of goals and outcomes:

GOAL: Running code demonstrating the communication needs between identified
components as they pertain to the on-request collection case through the
scenario, where that case is described at
https://trac.ietf.org/trac/sacm/wiki/SacmVulnerabilityAssessmentScenario.
OUTCOME: We will have specific understanding of components' boundaries and
the necessary information flows (including information being communicated)
between them.

GOAL: Leverage existing collected data in a data repository. OUTCOME:
Demonstrate that previously collected data can be reused to support
vulnerability assessment

GOAL: Running code to extend that base case to include a mechanism capable
of monitoring a given set of endpoint attributes for change. OUTCOME: We
will have specific understanding of additional architectural considerations
for handling monitoring vs. on-request collection, as well as any
additional information flows required.

Does anyone care to bash these goal-ouctome pairs in the context of our
hackathon plans?  If so, please do so over the next day or two, otherwise
these will become the stated goals for our hackathon.

Kind regards,

Adam

On Tue, May 2, 2017 at 4:40 PM Adam Montville <adam.w.montville@gmail.com>
wrote:

> All:
>
> Last week Dave sent a list of milestones to the list. The first of which
> was for the WG to define some goals for the IETF 99 hackathon. I can see at
> least one primary goal with at least one stretch goal. The primary goal is
> to have running code demonstrating the basic/ideal case through our
> vulnerability scenario, where a new vulnerability is discovered and we need
> to reach out all the way to the endpoint to determine whether it is in fact
> vulnerable. A stretch goal might be to have running code demonstrating a
> "monitor for this vulnerability from now on" capability (I'm sure I'm not
> stating that as well as I could).
>
> Does anyone have additional goals? Or, are there better ways to state
> these particular goals (there probably are)?
>
> Kind regards,
>
> Adam
>