<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Zero Trust on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/zero-trust/</link><description>Recent content in Zero Trust on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 May 2023 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/zero-trust/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Computing (6): Cloud Security and Privacy Protection</title><link>https://www.chenk.top/en/cloud-computing/security-privacy/</link><pubDate>Sun, 07 May 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/cloud-computing/security-privacy/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/cloud-computing/security-privacy/illustration_1.png" alt="Cloud Computing (6): Cloud Security and Privacy Protection — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;p>In 2019 Capital One lost a hundred million customer records. The exploit chain was small: a misconfigured WAF allowed server-side request forgery against the EC2 metadata endpoint, that endpoint handed back IAM credentials, and the IAM role those credentials belonged to had wildcard &lt;code>s3:*&lt;/code> on every bucket in the account. One misconfiguration, one over-broad role, one rule the security team had not written. The bill, before legal: more than 80 million dollars.&lt;/p></description></item></channel></rss>