Data at rest (was Re: IETF Chair)
Robert Sparks <rjsparks@nostrum.com> Wed, 14 October 2020 14:29 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0491B3A0E03 for <ietf@ietfa.amsl.com>; Wed, 14 Oct 2020 07:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level:
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 2D8quk7dVQ-a for <ietf@ietfa.amsl.com>; Wed, 14 Oct 2020 07:29:12 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 2D81F3A0E59 for <ietf@ietf.org>; Wed, 14 Oct 2020 07:28:59 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 09EESu1J042232 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Wed, 14 Oct 2020 09:28:57 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1602685737; bh=6TMq8wqn44IR44KVsUhto6bkRQABIpQpF+c3/YVhaag=; h=Subject:To:References:From:Date:In-Reply-To; b=Bldv1aWZ8d+nN78eJeOax2MpotDf9VU56LaLKSLBj/iAcvRqlpEmVM1l6QDH6RP9p +AqPBAkgzyV0xfKwBu8dQWfkF6wbP4Z/27RAnsH21mh4K7UesvP/jsGMhD5NILdlHF 6CS41gPVARFDCKvGql/RvAeAZlKobMGha/EWvLrI=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
Subject: Data at rest (was Re: IETF Chair)
To: ietf@ietf.org
References: <2B51679C-2BED-4F7B-B146-FF1524B00AA5@akamai.com> <C775E80B-9A31-492E-BA6A-96F9FE831316@akamai.com> <128277543.164613.1602611739735@email.ionos.com> <CAMm+LwjCGVUuFXK+fAzpV176hseXB9iLzC-7OZQZf=ca9+3x0A@mail.gmail.com> <20201014141954.GB18373@mit.edu>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <5e05b064-1bfb-194f-81e6-2e4a02f9fb12@nostrum.com>
Date: Wed, 14 Oct 2020 09:28:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <20201014141954.GB18373@mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/baK9duzQTa0PYcO30px85gJu4aE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 14:29:14 -0000
(Trivial reply to groom the subject. If other forks of the thread continue, I hope the next poster there does the same). RjS On 10/14/20 9:19 AM, Theodore Y. Ts'o wrote: > On Tue, Oct 13, 2020 at 07:22:10PM -0400, Phillip Hallam-Baker wrote: >> The biggest security problem we face today is breach of data at rest, a >> confidentiality problem. But 90% of the efforts of the academy and 99% of >> those of commerce are focused on the Blockchain, an integrity technology. >> Meanwhile it has taken me most of the last five years working in various >> forums to persuade people to look at threshold decryption, a technology >> developed in the 1990s that is actually a confidentiality control capable >> of securing data at rest. > I'd agree, but at the same time, I'll note that securing data at rest > is generally not an issue which is solved via internet protocols and > interoperability guarantees, but rather is something that needs to be > designed in hardware (e.g., trusted key stores, firmware verification) > and in software (trusted boot, multiple layers of encryption in the > software stack, bring your own key for those customers who demand it) > and in operational practices (reduction of people with privileged > access, two person controls, auditing, etc.). > > An example of the sorts of things which are needed to secure data at > rest can be found here[1], from my employer, but all cloud providers > should have something similar (or they'd better, if they want to > retain customer trust). > > [1] https://cloud.google.com/security/overview/whitepaper > > If you look at this, you'll find that most of it is out of scope for > the IETF. > > - Ted >
- IETF Chair Salz, Rich
- Re: IETF Chair Brian E Carpenter
- Re: IETF Chair Sarah Banks
- Re: IETF Chair Carsten Bormann
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Kyle Rose
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Kyle Rose
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Carsten Bormann
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- Re: IETF Chair Timothy Mcsweeney
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Salz, Rich
- RE: IETF Chair Khaled Omar
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Mezgani Ali
- RE: IETF Chair Khaled Omar
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Theodore Y. Ts'o
- Re: IETF Chair Leif Johansson
- Data at rest (was Re: IETF Chair) Robert Sparks
- Connections, and timing (was: IETF chair) Keith Moore
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Barry Leiba
- Re: IETF Chair Phillip Hallam-Baker
- Re: blockchain, not IETF Chair John Levine
- Re: IETF Chair Michael Thomas
- Re: IETF Chair Phillip Hallam-Baker
- Re: IETF Chair Benjamin Kaduk
- Re: IETF Chair Stephen Farrell
- Blockchain is alchemy Phillip Hallam-Baker
- Re: Connections, and timing (was: IETF chair) Amelia Andersdotter
- Re: IETF Chair Ben Laurie
- Re: IETF Chair Larry Masinter
- Re: IETF Chair Timothy Mcsweeney
- Re: IETF Chair Timothy Mcsweeney
- Re: IETF Chair Timothy Mcsweeney