span8
span4
TheFME云安全白皮书provides an overview of how we secure our FME Cloud infrastructure. The questions that follow are popular questions that have come up in addition to what is defined in the whitepaper.
白皮书列出了云计算合规性是AWS提供,但安全有任何安全合规性,如果是的话,以什么样的标准?亚搏在线
Safe Software are not yet accredited. We are moving towards SOC accreditation, but we are not yet there as it is a comprehensive process.
Are your staff vetted, if so to what standard and how does this apply to just the small team performing updates.
我们不运行在我们的工作人员犯罪记录检查,但我们检查引用,并有一个全面的招聘流程。我们只有小团队谁可以实际访问FME云代码。这个团队必须遵守我们的内部安全指引,包括像使用的是两步验证访问任何我们使用的服务,加密机上有代码等不拷贝硬盘一个人被信任与接入基础设施。如果没有基础设施的关键组成部分,那么它被监视,当有人访问它每个人都惊动了。
Will customer data ever be viewed by your staff in Canada (if so it’s deemed to be data export by some clients residing in other countries), or do they just operate on the infrastructure/software?
没有也不会,不是没有客户的许可。我们必须通过WebUI和REST API不能访问FME Server实例,我们唯一潜在的访问是通过SSL,这是监测,如果我们打开端口,您将收到一封电子邮件。当工作支援问题,我们尽最大努力尊重您的隐私尽可能的,我们只获得解决问题所需的最小文件和设置。
当工作人员进入instances-你可以提供一些例子是什么日志由/电子邮件发送?
实例只能通过SSH我们的工作人员进行访问,我们绝不会做没有问。我们没有为你的FME Server登录密码。当您下载的密码的情况下尽快从我们的基础设施将它们删除。我们也监控实例上的系统日志,如果有人试图通过SSH(包括我们自己)访问实例,帐户所有者将收到一封电子邮件,警告他们,有人通过SSH访问它们的实例。您也将看到活动日志,该实例在仪表盘上的条目。电子邮件是这样的:
Hi xxxxx,
作为我们安全检查的一部分,我们想告诉你用户已登录到通过SSH您的实例*****。如果FME云支持团队并没有征求您的同意,或者如果您想了解更多详情,请联系我们的支持团队。
电话:+1 604-501-9985 x.278
EMAIL:support@fmecloud.com
注意实例的任何未经授权的访问也密切监视自己。
Sincerely,
在FME云团队
Do you have a copy of the typical SLA you provide and the Terms and conditions of the service.
我们不提供明确的SLA标准的FME云,你可以从所列的条款和条件见这里。合理的商业努力使line Services available that we talk about in the T&Cs—although not defined on our website—looks like this. During office hours (9am-5pm PST Monday-Friday excluding holidays), we will investigate issues within 2 hours. Outside of that window, we will do our best to investigate issues as they happen, but can’t guarantee response time. However we are open to creating tailored SLAs for individual clients based on your requirements.
还有与问候到实例连带责任的元素。我们看到的情况下运行到问题的主要原因是当它运行的磁盘空间了或者过载。我们现在有FME Cloud monitoring,使您在磁盘越过一定值或负载监控/ CPU超过限制和发送警报。这意味着你可以解决问题,他们把严重了。
SSL encryption – the white paper states this is 128 bit RC4, is this still correct?
The connection is encrypted and authenticated using AES_128_GCM and uses ECDHE_RSA as the key exchange mechanism. We have removed RC4 ciphers.
Is it possible to lockdown outgoing ports /IP’s on server instances?
目前,它是不可能的,这是我们可以添加,请在思想交流。传入端口可锁定。
Can you confirm that individual instances don’t have shared components (other than the AWS cloud infrastructure)
正确的,他们是专门的实例,也没有共享组件。进出实例的未来的唯一数据是通过我们用来做这样的事情进行操作系统补丁邮件队列。阅读更多这里。
在数据量扫荡加密的实例 - 如果这样到什么水平/协议?
所有EBS卷,我们发动针对该实例使用行业标准的AES-256算法进行加密,这是由AWS提供的默认加密。阅读更多这里。
Are the backup images encrypted – if so to what level?
Yes they are also encrypted using AES-256. We are essentially taking a copy of the EBS volume, since that is encrypted the backups and snapshots are too.
How are images, and/or backups destroyed?
当您在FME云终止实例,实例和EBS卷就被破坏了。相关的备份和快照将被销毁30天后触发终止命令后。我们等待30天,以便我们可以根据需要一段恢复的实例。30天之后,我们摧毁使用标准AWS命令备份和快照。请参见第28页AWS Security Best Practices白皮书和的24页安全进程的概述白皮书中,关于他们如何擦拭EBS卷和破坏硬件已达到其寿命结束后的细节。
如何安全应对安亚搏在线全威胁和什么是SLA化解?
我们不提供明确的SLA标准的FME云,你可以从所列的条款和条件见这里。We usually work to create tailored SLAs for individual clients based on their requirements. That said, we do have the capability to react immediately, it just isn’t always worth us doing so for every customer if they are running development and staging environments for example. If there is an intrusion or a vulnerability, we will know about it right away because of all the monitoring setup. We have key alerts go straight to all of our phones via a service called PagerDuty.
Can you provide examples of how you have dealt with critical security threats in the past.
已经有过在过去2年在全球范围发现了几个高调的安全漏洞:弹震,贵宾犬和心脏出血漏洞。我们并没有受到所有的人,但所有这些问题的过程是一样的。我们首先审核我们的整个基础设施,看看有什么会受到影响,并基于该评估安全风险是什么。我们经常在这一点上讨论我们的第三方安全专业的东西太多。在这我们容易,我们创建了一个补丁和滚动补丁之前弹震的情况下发送以下电子邮件受影响的客户:
嗨XXXXXX,
工程团队在FME云一直致力于评估9月25日披露的尾流对我们客户的影响CVE-2014-6271andCVE-2014-7169,俗称为弹震。问题在于bash的处理环境变量,并在理论上攻击者可以利用它来执行shell服务器上的命令,即运行程序。我们加入了互联网应对这一严重的漏洞几乎每一个服务提供商,并进行了全面的安全审查。
You are running an instance that has security updates deactivated (or you launched it before we provided the automated patching). We could not find any vulnerabilities in FME Server, but because of the severity of this bug (10/10 for severity) and as a preventive measure we will apply the security patch to your instance. We will therefore be logging onto your instance via SSH in the next few hours to apply the patch. We will not need to restart the instance but you will get an email saying someone has logged onto your instance.
作为最佳实践,我们已停用与停用安全更新的能力,以推出实例。这是直到我们100%确定该服务器,我们提供您在第一次发射是安全的。
If you have any questions or concerns, don't hesitate to联系我们。
Many Thanks,
FME云团队
We are aware that communication is critical when issues such as this arise and we aim to be as transparent as possible. After assessing our infrastructure for the heartbleed issue we posted on our blog:https://blog.safe.com/2014/04/fme-cloud-vulnerable-cve-2014-0160-aka-heartbleed/.
How do you monitor and manage the emergence of new security threats?
We runQualys’ network vulnerability每周通过调度表扫描针对FME云实例和FME云的Web应用程序的工具。Qualys公司不断的到最新的已知漏洞数据库的升级,所以通过扫描我们的基础设施,我们可以肯定的是,我们对即使是最近的问题的保护。如果我们是脆弱的,我们将收到电子邮件通知,然后立即努力解决这个问题。
In addition to these automated tools, we work with a third-party Certified Information Systems Security Professional (CISSP), to complete application and network security audits. This includes manual network vulnerability scanning and penetration testing against the FME Server instances and the FME Cloud web application where you manage all of your instances.
How do you do to communicate issues?
For general issues we will post updates onhttp://status.safe.com/and if there is a high profile security bug we will post findings on our blog if we are not affected. If we need to apply an urgent patch against either FME Server or the operating system, we will just apply the patch and notify the affected customers via email.
如何检查安全问题的服务器和云考虑您的产品开发周期的引入?
On FME Server and FME Cloud we use industry standard frameworks and tools to ensure that if there is an issue then it is easy to patch.
FME Server可以对每年发布周期。对于FME Server使用如PostgreSQL的,JVM和Tomcat的所有第三方组件;我们可以确保应用最新的安全补丁。我们还系统地监测在图书馆的漏洞,我们的船与FME引擎和我们使用.X版本纳入定期这些修补程序。一旦新的发行准备上去FME云,我们切换Qualys的网络漏洞扫描,使其指向构建FME服务器的检查,看看是否有任何已知漏洞。
FME Cloud works on a continuous deployment cycle. Firstly we have very strict rules about who can deploy and when you are allowed to deploy. We firstly have humans check for issues in the code reviews. When we push the code to our staging environment where two things happen, a service calledCode Climateruns which checks the actual code for common errors that people make that can lead to security exploits. We then have Qualys running against the application from the outside, performing vulnerability tests checking to see if there are any known exploits in our app. We then deploy the code to production.
如果您需要引入重大更改您休息的服务,例如,会发生什么。
我们整个FME云基础设施在很大程度上版本,从这些API通过对机器的图像,我们用它来提供FME Server中。这意味着为所有,但最很严重的错误,我们只会推变化到新版本。如果我们确实要推破变化,安全问题可能是我们需要做的唯一原因此,我们将事先传达给客户,通过电子邮件和其他渠道认为合适的。我们会给定义我们将在何时推出的变化,然后与客户合作,以确保他们知道他们如何更新他们的工作流程的时间窗口。亚搏在线
会发生什么,如果这个数据中心是往下走,我们将失去我们的服务,或者你会/ AWS自动移动到不同的数据中心?
目前,如果数据中心(所谓的可用性区域[AZ])是往下走,那么实例将无法访问在该期间。每个区域由多个AZS的。我们可以在一个区域跨越多个AZS添加支持容错部署,但它不是我们迄今要求,作为显着的成本和复杂性的增加。我们绝不会区之间移动数据。
Although instances may be unreachable for periods of time, if the data centre goes down we still won’t have loose your data. If the hardware on the instance fails, or the EBS volume becomes corrupt, we can rollback to a previous backup and restore the instance. This has not happened yet.
© 2019 Safe Software Inc |法律