[sacm] Component Communication Sequence (Was - Re: Components for Vulnerability Assessment)

Adam Montville <adam.w.montville@gmail.com> Tue, 02 May 2017 21:45 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 87F6E12960D for <sacm@ietfa.amsl.com>; Tue, 2 May 2017 14:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 nQ-1yqIMFp6f for <sacm@ietfa.amsl.com>; Tue, 2 May 2017 14:45:04 -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 526A8129C66 for <sacm@ietf.org>; Tue, 2 May 2017 14:42:35 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id o22so44434067iod.0 for <sacm@ietf.org>; Tue, 02 May 2017 14:42:35 -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=rE3mKl11dLA046ASivt8Mhgcjl/36pFRGphowFETQUI=; b=WKWQsp+hfAItY1KuZpJXFpgTHtZJ5xCryXlcCroo7taACiVcMinTjkSl+ccLthc1mV e6ZSsNUUMboCthxa65tdZ2ci35DeYKuwuRD9q+DP+1ffxudGnVV1ChbDgVilgagpy/q1 HKuLibcywA02vRPaR5sasgnPqiDirebb433cpg0y9jSzobD161Dskmt4SWqryUsqgD8p FdQSEQDWw9zpZ86htssPAfIcJV5LfPX15JvlYgxMfJclE5QsR+KWC0/QLmZujZCuIjlt zTu8p0eutoLAZLUqztm8T3nl0fh1KGe9d7KLfTsZK7o8KQgPu7NJycAZOk+yS6L9sdl7 eH2g==
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=rE3mKl11dLA046ASivt8Mhgcjl/36pFRGphowFETQUI=; b=AiH7fccznGxsKg6jdIVSkkTRRvBJqdTnfugpirGXvH0ks/LI0Zuv1IRlnu+W5p/RLM P0nN0EKOAVt7gZ2Nww4GFNpBPrJilsrXidHK1yf92U0kdFJ6Ugml7t8tgpj6ZcvnnYs3 Fe92nT808t2HIcIhdpbZCvY4wv1KQ5sBQw1Ju6A9A+keJ6wUPNu8Xks1sn+WeQ02Um9E T4UsBiGMciphiNnbhGGsaO9n+56U4r3Ti2fnRbLflI/2jhCMIK1SGq3y5VbcHn1Y4RcT JNCmlKWROJOYyP90ZL1R54Gfz7xhw+QOYZnVddMma3JEyoBbH73tNKIwTxWXxpQwb6u7 cj7g==
X-Gm-Message-State: AN3rC/4iHlaPjdFzR2noHD5/DDR/0XVB+/9VPIBF/sRSH3jkpWcw6jHd dn81AVQK+WLjTq+wPx4jPajyzxlEu47J
X-Received: by 10.107.23.129 with SMTP id 123mr30822661iox.184.1493761354232; Tue, 02 May 2017 14:42:34 -0700 (PDT)
MIME-Version: 1.0
References: <CACknUNUNhCCV8LRDpjEm1SvgwpLq+NEEDbc3LOPYzMyRbmfy9w@mail.gmail.com> <CACknUNXtxuHKcO35vzNR79m--UfNP4E5tRMSFr=WXJpbdQOCrw@mail.gmail.com>
In-Reply-To: <CACknUNXtxuHKcO35vzNR79m--UfNP4E5tRMSFr=WXJpbdQOCrw@mail.gmail.com>
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 02 May 2017 21:42:23 +0000
Message-ID: <CACknUNW9A0dttxjzAymS0CqN3eF7z63GyCecnn4y6QMUcpgt3g@mail.gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05bcc6e5ff47054e916a84"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/rOFE7NrrqP6B9kS69jGgp-PToBE>
Subject: [sacm] Component Communication Sequence (Was - Re: Components for Vulnerability Assessment)
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, 02 May 2017 21:45:06 -0000

Has anyone had time to take a look at the communication sequence here? I
know we've not yet completely settled on goals, but I feel like we should
still be able to have this discussion as well.

Thanks for your time.

Adam

On Fri, Apr 21, 2017 at 8:00 AM Adam Montville <adam.w.montville@gmail.com>
wrote:

> Hello Everyone,
>
> After some discussion on this topic, I feel like we've got no real
> objection to this proposed list of components. As such, this brings us back
> to the second version of the sequence diagram that some of us were working
> with not too long ago (see attached PDF vector diagram).
>
> Given that set of components, we can now start talking about the expected
> communications between them in an ideal case through the system. Remember
> that the VDI (vulnerability information) is assumed to have been
> transformed and placed into the VDD (vulnerability detection) Repository.
> I've numbered the flows in the attached sequence diagram to show the
> proposed order and so that we can talk about each flow by that number.
>
> Does this flow feel right to everyone on the list? What needs to be
> different? What alternate flows may exist for the basic case of checking
> inventory against a new vulnerability?
>
> Let's carry this discussion on for a week or so. (Do we need longer?)
>
> Kind regards,
>
> Adam
>
> On Tue, Apr 18, 2017 at 8:03 AM Adam Montville <adam.w.montville@gmail.com>
> wrote:
>
>> Hi All:
>>
>> We've got a list of components we think we care about for our
>> vulnerability assessment scenario (focusing on the narrowest "ideal case"
>> through the scenario for the time being.
>>
>> These are:
>>
>> * Vulnerability Detection Data Repository
>> * Vulnerability Assessor
>> * Endpoint Repository
>> * Collector
>> * Target Endpoint
>> * Assessment Results Repository
>>
>> For reference, see our wiki [1] and/or the slides from IETF 98 [2] and/or
>> the minutes from IETF 98 [3]
>>
>> Question to the WG: Is this an appropriate initial list of components?
>>
>> Please opine within the next few days (say by end of your day on
>> Thursday, wherever you may be), so that we can generate some momentum on
>> this effort.
>>
>> Kind regards,
>>
>> Adam
>>
>> [1]
>> https://trac.ietf.org/trac/sacm/wiki/SacmVulnerabilityAssessmentScenario
>> [2]
>> https://www.ietf.org/proceedings/98/slides/slides-98-sacm-vulnerability-scenario-discussion-00.pdf
>>
>> [3] https://www.ietf.org/proceedings/98/minutes/minutes-98-sacm-00.txt
>>
>>
>>