Re: [Model-t] w3c also thinking about threat models

Christian Huitema <huitema@huitema.net> Mon, 23 September 2019 17:52 UTC

Return-Path: <huitema@huitema.net>
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 B7A681200FA for <model-t@ietfa.amsl.com>; Mon, 23 Sep 2019 10:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 drpUuJFmopSH for <model-t@ietfa.amsl.com>; Mon, 23 Sep 2019 10:52:49 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0DB120020 for <model-t@iab.org>; Mon, 23 Sep 2019 10:52:48 -0700 (PDT)
Received: from xse340.mail2web.com ([66.113.197.86] helo=xse.mail2web.com) by mx64.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iCSVy-0003mv-K4 for model-t@iab.org; Mon, 23 Sep 2019 19:52:47 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 46cWv00l1yzTPx for <model-t@iab.org>; Mon, 23 Sep 2019 10:45:32 -0700 (PDT)
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iCSOy-0002Rj-06 for model-t@iab.org; Mon, 23 Sep 2019 10:45:32 -0700
Received: (qmail 20109 invoked from network); 23 Sep 2019 17:45:31 -0000
Received: from unknown (HELO [192.168.200.64]) (Authenticated-user:_huitema@huitema.net@[72.235.197.82]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <stephen.farrell@cs.tcd.ie>; 23 Sep 2019 17:45:31 -0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <e22b6512-ec19-24dd-56fa-38ac87d1a321@cs.tcd.ie>
Date: Mon, 23 Sep 2019 07:45:29 -1000
Cc: Bret Jordan <jordan.ietf@gmail.com>, Dominique Lazanski <dml@lastpresslabel.com>, model-t@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D68AA072-F5A6-4535-8CB3-AE9ADD07476D@huitema.net>
References: <a327c668-6a17-bb9f-318e-e3cea6c6c1d0@cs.tcd.ie> <624F4CA6-8D84-4BD8-A74C-E5AE22709F72@lastpresslabel.com> <A30308F8-D2A5-45CF-88D9-D65240972D51@gmail.com> <27c70832-a631-4622-6119-3a47928c634e@cs.tcd.ie> <49EC2254-981B-4B79-9116-AC24385C2287@gmail.com> <e22b6512-ec19-24dd-56fa-38ac87d1a321@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Originating-IP: 66.113.197.86
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0dWQ8c9lblW44odAlK6ziUapSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDXz6Yli32IJdAuJ3ivsC2SsRX qYbtEQV1z/L435ZRxFSO8Gmm+6o5jvCT92SW7vPG+rYZvu7UEJiU3s27VgKHO7lwS3dBJTnTxDoD vBGGxpgwWbxrOZCJSMpTl/yE2fo2GM0/FQln02Joy/riMeAD7wZ6weYgSzquK2hxskqXvy8woCTx LKweTbuJ+19zsyHVGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbuhdxf5Dwg9wMBX5ckCo48ayVGvgdM/14NhEhsQ0jllqEE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ileQtX44ad09m ARiBoFHKYOu44D1K03PNuL1c0rhma4+r8BBPT0pWQl87aZpn74VFGfKI/Jra15E8WXq0E+iR3eov UwPy3x0FYtCNEb10sHyQCLHEvD1OqP6bgZ4L66GcgBg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0az+0HH5NxmOgWDjXNw8v7QzZxMPnetLBJMh51NiRRoHIBgS61TI/6r0udU0TXwnkTxmiK7 x42VjdzChZMe6O/DiWiiIzuXMTE3l4bIsk+O50s7uXOPuGEi6CQWCA3zlLq+08QV3No+S2msRDep v5w/kkG0v17AmegcpQ0tml/sN9lmMy/o83jVXTcfb9k0nLWblJy7uxV6dw8jzlsaNZe6hynMJcjx DydxsJEju76A7X1QIVydqXpZ6MHhiKws9Iiut28r9wo4SqUIg8Yh9hAM0n3LLzx/F2gT3wl8JQJv Bho=
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/model-t/k-a1PoieNVZiLM-qpppLLjEhb3U>
Subject: Re: [Model-t] w3c also thinking about threat models
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: Mon, 23 Sep 2019 17:52:51 -0000


> On Sep 23, 2019, at 5:32 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> Bret,
> 
>> On 23/09/2019 15:41, Bret Jordan wrote:
>> 
>> Given how nearly all attacks, campaigns, malware, and intrusion sets
>> use the web or software connecting to the web 
> 
> Malware (ab)using the web doesn't imply anything about
> what might be right or wrong with the current web security
> model though. Same as malware doing that doesn't imply
> anything about the security model for IP, which is also
> in use in almost all such cases.

Au contraire!

The past decades should have taught us that bug happens and are exploited. That's very relevant for the Internet threat model. If a server is exploited, will clients and further servers fall off like dominoes? What kind of defense in depth have we built in the architecture? How do we isolate nodes when they are faulty? What remediation strategies do we have available ?

You can apply this analysis to multiple subsystems. For example, if a name server is compromised, can the attackers gain access to the domains that it serves? Can they obtain certificates?

-- Christian Huitema