<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abdul Zia on Medium]]></title>
        <description><![CDATA[Stories by Abdul Zia on Medium]]></description>
        <link>https://medium.com/@azia-gcp?source=rss-159587e1db98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Uhtui5jvKQNIHqaj</url>
            <title>Stories by Abdul Zia on Medium</title>
            <link>https://medium.com/@azia-gcp?source=rss-159587e1db98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:07:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azia-gcp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reducing Risk — The Google Cloud Super Admin]]></title>
            <link>https://medium.com/google-cloud/a-method-to-secure-the-super-admin-407e73330ed9?source=rss-159587e1db98------2</link>
            <guid isPermaLink="false">https://medium.com/p/407e73330ed9</guid>
            <category><![CDATA[security-principles]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[iam-roles]]></category>
            <dc:creator><![CDATA[Abdul Zia]]></dc:creator>
            <pubDate>Mon, 15 Jul 2024 14:40:36 GMT</pubDate>
            <atom:updated>2024-07-15T16:10:08.140Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reducing Risk of Unauthorized Access and Lost Access to the Google Cloud Super Admin Account</h4><p><em>Note: The thoughts, ideas, and methods expressed in this document are solely my own and do not reflect the views or opinions of Google Cloud.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6j_DVw5kWLi0GKVd9jTjEQ.png" /><figcaption>Image Generated by <a href="https://gemini.google.com/">Gemini</a></figcaption></figure><p>The Google Cloud super admin role, by default, has access to all resources and permissions within a Google Cloud project. However, for security and operational best practices, it’s strongly recommended to limit the actual usage of the super admin role as much as possible.</p><p>It is highly recommended to follow the <a href="https://cloud.google.com/resource-manager/docs/super-admin-best-practices">Super Admin best practices</a> to ensure security, and the ability to recover.</p><p>In highly sensitive environments, the principles of “separation of responsibilities” and “availability” should be applied to the super admin. This poses a couple of challenges:</p><ul><li>Theoretically, no one person should have access to a Super Admin account without oversight of a second person</li><li>More than one Super Admin is required to ensure if a Super Admin leaves the company or changes their role, that access to the Super Admin ability is not lost.</li></ul><p>One way to meet these requirements is to:</p><ul><li>Create 3 Super Administrator Accounts, with 2FA enabled</li><li>Assign 3 different Super Administrators persons for Password Access</li><li>Assign alternate Super Administrator persons the 2FA</li></ul><p>This table highlights the separation of responsibilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*CnFtBXaRgQZmlqv2TXBA0g.png" /></figure><p>To prevent unauthorized access, the protocol ensures that no single person can obtain elevated privileges without a second person’s involvement. Furthermore, if an individual departs, alternative administrators exist to access the Super Admin Capability, allowing the restoration of access for another individual to the orphaned Super Admin account, ensuring that there is always a designated individual in one of the roles.</p><p>The core principle is that the super admin role should be used in very rare circumstances. Instead, there should be a hierarchy of roles with progressively narrower access privileges and abilities that align with specific responsibilities. This approach ensures that each role has the necessary permissions to carry out its tasks effectively while minimizing the risk of unauthorized access and misuse of privileges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=407e73330ed9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/a-method-to-secure-the-super-admin-407e73330ed9">Reducing Risk — The Google Cloud Super Admin</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Tech Nibble: Securing the SSH Button with IAP]]></title>
            <link>https://medium.com/google-cloud/google-cloud-tech-nibble-securing-the-ssh-button-with-iap-c9a4ffb2a5f0?source=rss-159587e1db98------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9a4ffb2a5f0</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[iap]]></category>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[google-compute-engine]]></category>
            <category><![CDATA[iap-ssh]]></category>
            <dc:creator><![CDATA[Abdul Zia]]></dc:creator>
            <pubDate>Fri, 09 Dec 2022 16:14:17 GMT</pubDate>
            <atom:updated>2022-12-10T05:03:05.696Z</atom:updated>
            <content:encoded><![CDATA[<p><em>These Tech Nibbles are for learning and education purposes. I hope we all know better… but PLEASE don’t play around in a production environment </em>:)</p><p>This “Tech Nibble” <strong>quickly</strong> goes through the basic steps on securing the SSH button with <a href="https://cloud.google.com/iap">Identity Aware Proxy</a> rather than opening ssh on the firewall.</p><p>If you have created a Virtual Machine on GCE (<a href="https://cloud.google.com/compute">Google Compute Engine</a>) , undoubtedly you have seen the SSH button to connect to the machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KRFHT1claeihcZPxICEBZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*E78L3bL4LpiXSJC4gr6RDQ.png" /></figure><p>If you click this button and you have SSH (TCP:22) open to the VPC in your firewall, likely you are able to connect, however, if you haven’t opened TCP:22 you will see the below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*riI-mZRCrcneKn3lqYUw5g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*GPhzU8Bbwr6o86PaPNt9xw.png" /></figure><p>Instead of opening TCP:22 on the firewall, a more secure and manageable option is to use <a href="https://cloud.google.com/iap/docs/tcp-forwarding-overview">Identity Aware Proxy IAP TCP forwarding</a> to secure SSH access to the virtual machines. While this post specifically deals with SSH, this process also works for RDP. To secure SSH access ot the resource via IAP:</p><ol><li>Open the <a href="https://console.cloud.google.com/security/iap">IAP Configuration Page</a></li><li>Click the <a href="https://console.cloud.google.com/security/iap?tab=ssh-tcp-resources">SSH and TCP Resources</a> Tab</li><li>If you removed SSH access to the instance, you should see the error warning. Click it and you will see the message that you need to open all TCP from 35.235.240.0/20 to your resource.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ksMG7UXXcUCT1hR1N852qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nn6xv4NK-vfHF5HZaFxlBA.png" /></figure><ul><li>A best practice when setting firewall rules is to use tags. You can add a network tag to an <a href="https://cloud.google.com/vpc/docs/add-remove-network-tags#adding_new_tags_to_vm_instances">existing machine</a>, or <a href="https://cloud.google.com/vpc/docs/add-remove-network-tags#add_tags_to_new_vm">when the machine is created</a> under Advanced options → Networking.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*0ei578olwckxV-jrFEL5Ng.png" /></figure><p>4. Unless you have already set a network tag on your instance, go back to your instance in compute engine, and edit it to add an appropriate network tag.</p><p>5. Add a firewall rule to allow TCP:22 in the VPC firewall to you network tag from 35.235.240.0/20. It should be:</p><ul><li>Direction: Ingress</li><li>Source: 35.235.240.0/20</li><li>Priority above any blocking rules (recall that lower number is higher priority)</li><li>Destination: The network tag of the machine you want to enable SSH to</li><li>Protocol: TCP port 22 (Note that I am only opening 22 here, to be more restrictive, for other services, such as RDP, you will need to open the respective ports, such as TCP:3389 for RDP). There is little risk in opening all of TCP from 35.235.240.0/20 for IAP, however, many security administrators and policies like to be as restrictive as possible)</li><li>Action: Allow</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*Dym-Kes6v6Kcmn6QyzxRng.png" /></figure><p>6. Under <a href="https://console.cloud.google.com/iam-admin/iam">IAm and Admin → IAM</a>, add the following roles to the user or group that you want to give access to. This is the minimum required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*97H5h0X4MlhYtM5WMXUkiA.png" /></figure><p>Now, when you click the SSH button on the instance, if your user is authorized, you will be able to SSH from the web.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*yLaKWkJu9gA8i4X9ay-oNg.png" /></figure><p>Additional Resources:</p><p><a href="https://cloud.google.com/iap/docs/enabling-compute-howto">Enabling IAP for Compute Engine | Identity-Aware Proxy | Google Cloud</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9a4ffb2a5f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/google-cloud-tech-nibble-securing-the-ssh-button-with-iap-c9a4ffb2a5f0">Google Cloud Tech Nibble: Securing the SSH Button with IAP</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>