Re: [Model-t] model-t@iab.org list description

Eric Rescorla <ekr@rtfm.com> Sat, 03 August 2019 14:26 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: model-t@ietfa.amsl.com
Delivered-To: model-t@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D99012008C for <model-t@ietfa.amsl.com>; Sat, 3 Aug 2019 07:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.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 hjgFjHb01xbk for <model-t@ietfa.amsl.com>; Sat, 3 Aug 2019 07:26:30 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 3BBEF120088 for <model-t@iab.org>; Sat, 3 Aug 2019 07:26:30 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id m8so41869918lji.7 for <model-t@iab.org>; Sat, 03 Aug 2019 07:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3G8a9DgpddPIy5PkUTQsBbwtCpDotVaHMg2GY/mICC0=; b=vslFPvEQu7J3OOIxGvhoDZEsXhS68+uYnLVj3hDB8dz3BnvAI7Yd0A/gIT4uRBv4Pb Av2dO7GLD1or+ore+DjXj95iYeUpmq2gLOVN+ACXZukpcdhYEdJEIgLJKoAFVpOb/Ezv 2PyQ1uRWFzHu9P3MnFTyxnqzpseeJQpNW3bq+D0/OfjCuq5ao3aTAxpuPkEClrNvb24g Jz9+feAUAftZylesrOJZPf5mlf0A4dL64Uqh1l5vS/iwbXsgjyCZKPNIlP7Cm8m3w+2E igP1CgE2Y4vorxKKJfXgYqL84a0kQCJ3R+jpjl5uzTZPkymS1SKk14JUC288r/DRBTuX 1kyg==
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:cc; bh=3G8a9DgpddPIy5PkUTQsBbwtCpDotVaHMg2GY/mICC0=; b=Sv/kr/bTTCpqd/YGpIGiAzQljTFK++rWpB0v7st3KT32ZLG7JEOTbsynZs4wFOgwt/ DiLF7ETyw83rzDd2fR8qb6W7CCXD4/Tm72YGCeQEtCaa5TvTGi0862kiNc72zXdU9Ehs xiSNaoCaGn1IIlp1oPCyJBkl9yFNZdbAWXmHr0M0PJBcZHBI1YTbwqtSQhkkpQQUxSmN IGPqkef6wc1zJ58PZH+hgEQ1vq16YgO3DnNxmy9Czo9ycCnCCdHgyxdE34EMDWt8Gw2n C78yAzBJxj2mrxjFBeZJ6s2+MvGF9B5vC0raHSr0PJ94+q61rMgJouDDUzIJWwrH1LIY w1oQ==
X-Gm-Message-State: APjAAAUSjBoGcKcEEBUTfmresnFty+W1w5jJLjuKGLxETKIc512ch4UH bH4fmTvyX1j/znSzWyZJtM0+TIUq9cq8wPp/0AA=
X-Google-Smtp-Source: APXvYqxKP92BnA+3yphsR7vJeU3rF9zJWcfrHbKhTXMluDFmK1PcpDs3u3rkLGYiRNekYa+VQG3NXd4XdY49pJasn2g=
X-Received: by 2002:a2e:9cd4:: with SMTP id g20mr49547533ljj.205.1564842388488; Sat, 03 Aug 2019 07:26:28 -0700 (PDT)
MIME-Version: 1.0
References: <c3a112ba-baab-1cb0-97ad-21ff9999a637@cs.tcd.ie> <29756028-95f1-e6e5-b3ea-562cbc635df0@sandelman.ca> <5ef15ad2-5b20-e871-0d01-17cf906051c1@cs.tcd.ie> <22633.1564768705@localhost> <e7c02d44-353f-406c-818e-06a2e49ee212@www.fastmail.com> <5879878A-7CEA-4030-BB72-108CC4122719@gmail.com>
In-Reply-To: <5879878A-7CEA-4030-BB72-108CC4122719@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 03 Aug 2019 07:25:52 -0700
Message-ID: <CABcZeBP6gTCBSheUWfx-c66+RLLZEjfJ29M9LmkrKv+h2s=pQw@mail.gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, model-t@iab.org
Content-Type: multipart/alternative; boundary="000000000000b2143f058f374214"
Archived-At: <https://mailarchive.ietf.org/arch/msg/model-t/t20tuGwCtOOao0Vm1wxGgJW-eYs>
Subject: Re: [Model-t] model-t@iab.org list description
X-BeenThere: model-t@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions of changes in Internet deployment patterns and their impact on the Internet threat model <model-t.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/model-t>, <mailto:model-t-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/model-t/>
List-Post: <mailto:model-t@iab.org>
List-Help: <mailto:model-t-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/model-t>, <mailto:model-t-request@iab.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2019 14:26:33 -0000

Bret,

I'm having a fair amount of trouble understanding what these attacks you
are referring to mean. Perhaps you could lay them out in more detail?

-Ekr


On Fri, Aug 2, 2019 at 9:24 PM Bret Jordan <jordan.ietf@gmail.com> wrote:

> To borrow your words…  “If we are going to take security seriously”…  we
> need to understand and document the full attack surface.  So let us start
> listing them out.  Here are four.
>
>
> Attack: Active remote attack
> Exposure: Full compromise of system and data
> Client Knowledge: Potential indicators may be visible
> Protection Possibilities: Deploy both client and network level protections
> Headwinds: Client based protections are usually inadequate
> Severity: High
> Kill-Chain Phase: Lateral Movement
>
> Attack: Active in-band attack
> Exposure; Full compromise of system and data
> Client Knowledge: Potential indicators may be visible
> Protection Possibilities: Deploy both client and network level
> protections, user awareness training, content and DNS filtering
> Headwinds: Client based protections are usually inadequate
> Severity: High
> Kill-Chain Phase: Delivery and Exploitation
>
> Attack: Passive monitoring of traffic
> Exposure: Information about where traffic is going and potentially details
> of the content being shared
> Client Knowledge: No, it is very hard to detect passive monitoring tools
> Protection Possibilities: Encrypt traffic
> Headwinds: Global adoption of better encryption
> Severity: Low
> Kill-Chain Phase: Reconnaissance
>
> Attack: Active in-band monitoring and tracking
> Exposure: Information about what the user is doing and where they are
> going
> Client Knowledge: Generally no
> Protection Possibilities: Client and network level protections
> Headwinds: Some clients are making it hard to deploy client side
> protections
> Severity: Low
> Kill-Chain Phase: Reconnaissance
>
>
>
> Thanks,
> Bret
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
> "Without cryptography vihv vivc ce xhrnrw, however, the only thing that
> can not be unscrambled is an egg."
>
> On Aug 2, 2019, at 9:18 PM, Martin Thomson <mt@lowentropy.net> wrote:
>
> On Sat, Aug 3, 2019, at 03:58, Michael Richardson wrote:
>
> What I'm trying to say is that there are some threats that we deal with
> on the Capital-Internet that are far more manageable in the small.
>
>
> Like a red rag to a bull...
>
> I don't think that this is a sustainable attitude.  If we are going to
> take security seriously, we have to consider every networked device to be
> exposed to a hostile environment.  Now that doesn't mean that you can't
> take steps to limit hostility in networks, and there might be sound reasons
> to believe that the degree to which you have to expend resources in defense
> of certain attacks is different as a result.  But the notion of a gooey
> middle remains a big part of the problem statement.
>
> This isn't really on-topic for this list as I understand it, and I wasn't
> planning to say much here until someone said this.  Sorry Michael :)
>
> --
> Model-t mailing list
> Model-t@iab.org
> https://www.iab.org/mailman/listinfo/model-t
>
>
> --
> Model-t mailing list
> Model-t@iab.org
> https://www.iab.org/mailman/listinfo/model-t
>