[Nsaas] Some thoughts about SAAS

Hosnieh Rafiee <hosnieh.rafiee@huawei.com> Thu, 28 August 2014 16:04 UTC

Return-Path: <hosnieh.rafiee@huawei.com>
X-Original-To: nsaas@ietfa.amsl.com
Delivered-To: nsaas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C276D1A8771 for <nsaas@ietfa.amsl.com>; Thu, 28 Aug 2014 09:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level:
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
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 lFLxv1JT6PBW for <nsaas@ietfa.amsl.com>; Thu, 28 Aug 2014 09:04:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7EDC1A8778 for <nsaas@ietf.org>; Thu, 28 Aug 2014 09:04:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLW57667; Thu, 28 Aug 2014 16:04:24 +0000 (GMT)
Received: from LHREML513-MBB.china.huawei.com ([fe80::b810:863:a57e:3ff]) by lhreml405-hub.china.huawei.com ([10.201.5.242]) with mapi id 14.03.0158.001; Thu, 28 Aug 2014 17:03:47 +0100
From: Hosnieh Rafiee <hosnieh.rafiee@huawei.com>
To: "nsaas@ietf.org" <nsaas@ietf.org>
Thread-Topic: Some thoughts about SAAS
Thread-Index: Ac/C2aY9o39tM7ggQpS6YIhOHJvDog==
Date: Thu, 28 Aug 2014 16:03:47 +0000
Message-ID: <814D0BFB77D95844A01CA29B44CBF8A7A29DBF@lhreml513-mbb.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.82.100]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nsaas/9eUqr3SXWuKb1Zk80cm_OJrLuDE
X-Mailman-Approved-At: Thu, 28 Aug 2014 09:06:06 -0700
Subject: [Nsaas] Some thoughts about SAAS
X-BeenThere: nsaas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "*NSaaS: Network Security as a Service mailing list*" <nsaas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nsaas>, <mailto:nsaas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsaas/>
List-Post: <mailto:nsaas@ietf.org>
List-Help: <mailto:nsaas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsaas>, <mailto:nsaas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 16:04:27 -0000

Hello,

Since security as a service (SAAS) is really a critical role for each customers in different countries and for governments as well, I am thinking about how would be possible to also protect customers from Surveillance agents and monitoring. 

Because if SAAS is offered by a country that its government is known to be a surveillance agent, Is there any particular requirement should be considered in standard architectures to avoid such role? 

If the target customer is a government/or any important company in a country, does it accept to use a SAAS that is located in another country? (fearing of spy)

How to avoid governments to force SAAS vendors/operators to access the detail information about security services so that they can monitor and access customer's data. Are these assumptions only operational issues or it might also impact the standards in this regard?

Thanks,
Best,
Hosnieh