[Smart] Six SMART drafts

Kirsty P <Kirsty.p@ncsc.gov.uk> Fri, 12 July 2019 15:07 UTC

Return-Path: <Kirsty.p@ncsc.gov.uk>
X-Original-To: smart@ietfa.amsl.com
Delivered-To: smart@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1409120405 for <smart@ietfa.amsl.com>; Fri, 12 Jul 2019 08:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ncsc.gov.uk
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 74NfjdfugbAo for <smart@ietfa.amsl.com>; Fri, 12 Jul 2019 08:07:03 -0700 (PDT)
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (mail-eopbgr110099.outbound.protection.outlook.com [40.107.11.99]) (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 0EDA9120256 for <smart@irtf.org>; Fri, 12 Jul 2019 08:07:02 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U0ealzcSbYkV2cC3lGESghw7lnzcfxGqdu4E8Ieri3ObW2kLGDhrHSTFek0GORxYelTT2MPGZBwuCSH+9y0VkUkQ8+78mXsyS83yqOrw5GC9xsGoyQDNyV9U7WOqBb3e2kB81lkm5oNY/bfGzQB5kzMdJe8uMTkitvb0h4NrsXmsGLWTTlt+KPS4c5gxokKRmzawiu8xXASIlgj0yAZYaAi5BW2O4WE/qmXozTHKIHyqLi3pxrvn/+op1/Pwpl1EPGdTqxMQSTWtnl94neinrHDUku4LI/AhayaJfWbXXlh3GXXt/MxCINJUlTFk1godAZLo1+lY39G5cTsMpqOFGg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ChkV3y2B6kmw3trGKqsMlu8usagiEMFk6YEDyL7Fd1Y=; b=h/0ZNntkrJ+4lLBUO7tFf++nA2tQUd34OiS3wad7A94sB+nWo4ts8r7AEBbL4BHzNmh8CIlSWReOlMAnGrlGotCVWF7j8GVRSkK0DPrHLwFQ77GIPVKwz1FInmhay11CFL+hLkm8bDa9DFb2wet/su2xWUdRev1swsNSU4m8ZRVYYBk7gH6y2attJ8qCxrDu1q8V6Ce59aDc0oGJI+KeAcuFnHY3AdbJslWupnbTMXyb1GLT73vusMpXNws1kQQzbmeFB2cGWGjAytXBJWlj5s76+29bEDTtQtLr1GJiu1TfvoIobT7TdImNvj9Fbsz4bdcS+ETSZzxRzcoDrZeW7g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=ncsc.gov.uk;dmarc=pass action=none header.from=ncsc.gov.uk;dkim=pass header.d=ncsc.gov.uk;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ncsc.gov.uk; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ChkV3y2B6kmw3trGKqsMlu8usagiEMFk6YEDyL7Fd1Y=; b=avyD02Qiw0WaIAF1vf3NvVcfC5SO3HzF5c0O7QP7kTxW5P4KIEItZgJ0OAqpxWB7zGFu2yh40o0kPjf6CUjzh83dbu8wxf4YSjkZCKKWkRhfKk3czTG1ENohIb+GEQZuHwR5L+tK7IFX8RdfHv9Srl7Noaeu9aXtpg83eYEx2iA=
Received: from CWLP123MB1716.GBRP123.PROD.OUTLOOK.COM (20.176.58.85) by CWLP123MB2132.GBRP123.PROD.OUTLOOK.COM (20.176.60.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.11; Fri, 12 Jul 2019 15:06:58 +0000
Received: from CWLP123MB1716.GBRP123.PROD.OUTLOOK.COM ([fe80::f5dc:8f89:9af3:7ef8]) by CWLP123MB1716.GBRP123.PROD.OUTLOOK.COM ([fe80::f5dc:8f89:9af3:7ef8%5]) with mapi id 15.20.2052.022; Fri, 12 Jul 2019 15:06:58 +0000
From: Kirsty P <Kirsty.p@ncsc.gov.uk>
To: "smart@irtf.org" <smart@irtf.org>
Thread-Topic: Six SMART drafts
Thread-Index: AQHVOMNzEUiDIlcmT0CejjWXLzsjfg==
Date: Fri, 12 Jul 2019 15:06:58 +0000
Message-ID: <CWLP123MB171659B3DE145F9F9C7DF64FD7F20@CWLP123MB1716.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Kirsty.p@ncsc.gov.uk;
x-originating-ip: [51.141.34.27]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7d7f4b07-5856-4e19-d04c-08d706da95c6
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CWLP123MB2132;
x-ms-traffictypediagnostic: CWLP123MB2132:
x-ms-exchange-purlcount: 9
x-microsoft-antispam-prvs: <CWLP123MB2132F7C972EBE965E5196FEBD7F20@CWLP123MB2132.GBRP123.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 00963989E5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(396003)(366004)(136003)(39850400004)(189003)(199004)(53754006)(13624006)(66574012)(71190400001)(14444005)(6506007)(2501003)(2906002)(55236004)(14454004)(1730700003)(256004)(8936002)(71200400001)(102836004)(186003)(81166006)(81156014)(3480700005)(6916009)(105004)(66066001)(6116002)(3846002)(7696005)(33656002)(99286004)(7116003)(316002)(26005)(606006)(476003)(236005)(6436002)(55016002)(74316002)(5640700003)(54896002)(86362001)(5660300002)(6306002)(9686003)(52536014)(478600001)(66946007)(486006)(25786009)(53936002)(66476007)(66556008)(2351001)(76116006)(64756008)(19627405001)(66446008)(68736007)(7736002)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:CWLP123MB2132; H:CWLP123MB1716.GBRP123.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ncsc.gov.uk does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ML40D47AhK5KVhIQ+N31QVgMmmpfIaq4x/scDTdS4LjFT4WiC+yxVSOzAFQAOuJSpuAtdu3JowryENxAOGlaG+spV9/tn5YhcxErPP9uvxKi9fxB/2Pw07CzbRqVAq5bzbXFQRXKcjszxUgdpSxytfX0UoPQsYplE/95RL6rvbuyRbcDKXQcUUPgeE0x0W4FszzbouGRQAEHtZgLdToQ8lq1vf917H0JVtBULwVuKhw6V+MBUdQta3ytbUI9L7UpxzNoD+NiH21P+2Ov7KgWWXLDxDS0rUSq+8ROjmTFGZhg6OrW38O7KYNsb7C59Jyz8GGglastdIMiJuqbw4OPKxKeFKjyFGELNiVP5pq59yMqb2ZJm50CU+8YRvnJaYD7/KKuGIL7eECxg830r46qgn9sqhduTFv3K523xkmJmGY=
Content-Type: multipart/alternative; boundary="_000_CWLP123MB171659B3DE145F9F9C7DF64FD7F20CWLP123MB1716GBRP_"
MIME-Version: 1.0
X-OriginatorOrg: ncsc.gov.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 7d7f4b07-5856-4e19-d04c-08d706da95c6
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jul 2019 15:06:58.1276 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 14aa5744-ece1-474e-a2d7-34f46dda64a1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: kirsty62596@ncsc.gov.uk
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CWLP123MB2132
Archived-At: <https://mailarchive.ietf.org/arch/msg/smart/sY9-UAF9FiYquiUTQH7SrabUSoE>
Subject: [Smart] Six SMART drafts
X-BeenThere: smart@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Stopping Malware And Researching Threats <smart.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/smart>, <mailto:smart-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smart/>
List-Post: <mailto:smart@irtf.org>
List-Help: <mailto:smart-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/smart>, <mailto:smart-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2019 15:07:09 -0000

Hi everyone,


SMART has five drafts on the IETF Datatracker <https://datatracker.ietf.org/doc/search?name=smart&sort=&rfcs=on&activedrafts=on&by=group&group=> - all of these (plus one extra!) are on our Github page<https://github.com/smart-rg/drafts> too.


Each draft falls in one of four categories:

  1.  Research on attacks or defences enabled or disabled by IETF protocols, and recommending protocol design fixes or considerations as a result – including privacy considerations
  2.  Papers on principles/key concepts in attack defence, to underpin attack defence research of protocols and evidence a threat landscape
  3.  Creating methodologies for researchers to consistently analyse protocols for attack defence, and use these to perform such analysis
  4.  Scoping out specific security research problems outside of the above three points. The sole aim of these scoping exercises is to create an Internet Draft and establish feasibility of creating a separate IRTF security research group on that specific security problem.


The drafts are below, with a short description and a link to find out more. If you're have comments, are supportive of the work or want to contribute to a draft, please post on the list or email the authors saying so.


Kirsty


======

draft-taddei-smart-cless-introduction

  *   Also known as CLESS: Capabilities and Limitations of Endpoint Security Solutions: draft-taddei-smart-cless-introduction<https://datatracker.ietf.org/doc/draft-taddei-smart-cless-introduction/>

CLESS<https://datatracker.ietf.org/doc/draft-taddei-smart-cless-introduction/> attempts to establish the capabilities and limitations of endpoint-only security solutions and explore potential alternative approaches.

draft-mcfadden-smart-endpoint-taxonomy-for-cless

  *   Endpoint Taxonomy for CLESS: draft-mcfadden-smart-endpoint-taxonomy-for-cless<https://datatracker.ietf.org/doc/draft-mcfadden-smart-endpoint-taxonomy-for-cless/>

CLESS<https://datatracker.ietf.org/doc/draft-taddei-smart-cless-introduction/> discusses endpoints in general terms. It has been suggested that there are classes of endpoints that have different characteristics. Those classes may have completely different threat landscapes and the endpoints may have completely different security capabilities. In support of the work on CLESS, this document provides a taxonomy of endpoints that is intended to provide a foundation for further work on CLESS and research on approaches to providing endpoint security alternatives in a diverse group of settings.

draft-sasse-smart-secui-questions

  *   Open Questions in Supporting Secure User Interactions: draft-sasse-smart-secui-questions<https://github.com/smart-rg/drafts/blob/master/draft-sasse-smart-secui-questions.txt>

Describes open questions in supporting usable security at the UI level. The questions are split into defining a set of manageable security tasks for countering the most common attacks, and the UI elements for signalling whether an intended action is secure.

draft-lazanski-smart-users-internet

  *   An Internet for Users Again: draft-lazanski-smart-users-internet<https://datatracker.ietf.org/doc/draft-lazanski-smart-users-internet/>

RFC 3552 introduces a threat model that does not include endpoint security. In the fifteen years since RFC 3552 security issues and cyber attacks have increased, especially on the endpoint. This document proposes a new approach to Internet cyber security protocol development that focuses on the user of the Internet, namely those who use the endpoint and are the most vulnerable to attacks.

draft-moriarty-caris2

  *   Coordinating Attack Response at Internet Scale 2<https://www.internetsociety.org/events/caris2> Report: draft-moriarty-caris2<https://datatracker.ietf.org/doc/draft-moriarty-caris2/>

Coordinating Attack Response at Internet Scale (CARIS) 2, sponsored by the Internet Society, took place 28 February and 1 March 2019 in Cambridge, Massachusetts, USA. Participants spanned regional, national, international, and enterprise CSIRTs, operators, service providers, network and security operators, transport operators and researchers, incident response researchers, vendors, and participants from standards communities.

This workshop continued the work started at the first CARIS workshop, with a focus for CARIS 2 on scaling incident prevention and detection as the Internet industry moves to stronger and a more ubiquitous deployment of session encryption.

draft-mcfadden-smart-rfc3552-research-methodology

  *   Methodology for Researching Security Considerations Sections: draft-mcfadden-smart-rfc3552-research-methodology<https://datatracker.ietf.org/doc/draft-mcfadden-smart-rfc3552-research-methodology/>

RFC3552 provides guidance to authors in crafting RFC text on Security Considerations. The RFC is more than fifteen years old. With the threat landscape and security ecosystem significantly changed since the RFC was published, RFC3552 is a candidate for update. This draft proposes that, prior to drafting an update to RFC3552, an examination of recent, published Security Considerations sections be carried out as a baseline for how to improve RFC3552. It suggests a methodology for examining Security Considerations sections in published RFCs and the extraction of both quantitative and qualitative information that could inform a revision of the older guidance.

This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries to ncscinfoleg@ncsc.gov.uk