<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CloudSecurity on Securosis</title><link>/tags/cloudsecurity/</link><description>Recent content in CloudSecurity on Securosis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Jan 2025 17:00:00 +0000</lastBuildDate><atom:link href="/tags/cloudsecurity/index.xml" rel="self" type="application/rss+xml"/><item><title>Defining Security Invariants</title><link>/research/howto/security-invariants/</link><pubDate>Thu, 09 Jan 2025 17:00:00 +0000</pubDate><guid>/research/howto/security-invariants/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Note:&lt;/strong&gt; This post has been revised to include the new capabilities released by AWS prior to re:Invent 2024.&lt;br&gt;
You can also check out the re:Invent presentation we did with Securosis: &amp;ldquo;Security invariants: From enterprise chaos to cloud order&amp;rdquo; &lt;a href="DEV401_Security-invariants-From-enterprise-chaos-to-cloud-order.pdf"&gt;slides&lt;/a&gt; - &lt;a href="https://www.youtube.com/watch?v=aljwG4N5a-0"&gt;video&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Deploying AWS Backup</title><link>/research/howto/awsbackup/</link><pubDate>Tue, 05 Sep 2023 09:23:37 -0400</pubDate><guid>/research/howto/awsbackup/</guid><description>&lt;p&gt;tl;dr - here is a &lt;a href="https://github.com/primeharbor/pht-awsbackup-management"&gt;link to the scripts&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="what-ransomware-in-aws-looks-like"&gt;What Ransomware in AWS looks like&lt;/h2&gt;
&lt;p&gt;In a typical ransomware attack, a threat actor will attempt to encrypt files on critical machines belonging to the victim. In exchange for a cryptocurrency payment, the threat actor will provide the decryption key and software to the victim, who then has to go through the arduous process of restoring their machines. The encrypted data is typically lost forever if the victim refuses to pay the ransom.&lt;/p&gt;</description></item><item><title>Leveraging AWS SSO (aka Identity Center) with Google Workspaces - version 2</title><link>/research/howto/aws-identity-center-google-v2/</link><pubDate>Sun, 25 Jun 2023 18:25:26 -0400</pubDate><guid>/research/howto/aws-identity-center-google-v2/</guid><description>&lt;blockquote&gt;
&lt;p&gt;This is a revised version of the original post &lt;a href="blog/aws-identity-center-google/"&gt;Leveraging AWS SSO (aka Identity Center) with Google Workspaces&lt;/a&gt; based on the new announcement &lt;a href="https://aws.amazon.com/about-aws/whats-new/2023/06/aws-iam-identity-center-automated-user-provisioning-google-workspace/"&gt;AWS IAM Identity Center now supports automated user provisioning from Google Workspace&lt;/a&gt; The original post is still valid, and in someways may be better, but this version has it&amp;rsquo;s own advantages.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Setting up &lt;a href="https://aws.amazon.com/iam/identity-center/"&gt;AWS IAM Identity Center (successor to AWS Single Sign-On)&lt;/a&gt;, hereafter called AWS SSO (because I have to pay AWS for egress on this site), is an excellent service to help you get rid of IAM users and enforce identity best practices around second-factor authentication, on and off-boarding employees, and assigning the right level of access depending on job function.&lt;/p&gt;
&lt;p&gt;Companies using Google Workspaces for email and collaboration can also leverage their Google accounts to access AWS via AWS SSO. The process isn&amp;rsquo;t clearly documented, and the provisioning support isn&amp;rsquo;t integrated, so here is a post to help you set it all up.&lt;/p&gt;</description></item><item><title>Leveraging AWS SSO (aka Identity Center) with Azure AD</title><link>/research/howto/aws-identity-center-azuread/</link><pubDate>Tue, 16 May 2023 20:33:45 -0400</pubDate><guid>/research/howto/aws-identity-center-azuread/</guid><description>&lt;p&gt;Setting up &lt;a href="https://aws.amazon.com/iam/identity-center/"&gt;AWS IAM Identity Center (successor to AWS Single Sign-On)&lt;/a&gt; henceforth called AWS SSO (because AWS charges for egress), is an excellent service to help you get rid of IAM users and enforce identity best practices around second-factor authentication, on and off-boarding employees, and assigning the right level of access depending on job function.&lt;/p&gt;</description></item></channel></rss>