<?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 BRK0018 on Medium]]></title>
        <description><![CDATA[Stories by BRK0018 on Medium]]></description>
        <link>https://medium.com/@brk0018?source=rss-54dc4c95930f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YqaDmZjW3P3rmdaoKcfwVQ.png</url>
            <title>Stories by BRK0018 on Medium</title>
            <link>https://medium.com/@brk0018?source=rss-54dc4c95930f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:59:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brk0018/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[Implement Azure Bastion Host through Terraform]]></title>
            <link>https://brk0018.medium.com/implement-azure-bastion-host-through-terraform-9be3dba58d67?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/9be3dba58d67</guid>
            <category><![CDATA[azure-infrastructure]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[terraform-modules]]></category>
            <category><![CDATA[azure-architecture]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Fri, 17 Jun 2022 08:28:00 GMT</pubDate>
            <atom:updated>2022-06-17T08:50:25.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*Sji5YYiFRTYEdinMdGJuHQ.png" /></figure><p>Let’s implement ‘Azure Bastion’ through Terraform as part of our Terraform hands-on scenarios/series</p><p>Do you already know what is ‘Azure Bastion’ ? if not, please refer <a href="https://docs.microsoft.com/en-us/azure/bastion/bastion-overview">here </a>for details</p><p>Let’s first look at our Architecture diagram shown below to understand what all is needed for the successful implementation</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*IWB5WvqxbV24PSPtf_YAXQ.png" /></figure><p>In order to achieve the above, we need to first break down in to small steps— Let’s do that now as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R3n_zXUYB59Rm2N0YgHXHQ.png" /></figure><p><strong>Build the basic Terraform Folder Structure</strong></p><ul><li>Create a folder named Az_Bastion_Laband ensure to follow and implement ‘Pre-requisites’ , 2nd and 3rd sections of my <a href="https://brk0018.medium.com/deploy-linux-vm-with-terraform-on-azure-with-nsg-rule-and-boot-diagnostics-c868ca2bf8a7">previous blog</a> before proceeding to the next steps</li><li>Configure the backend.tf accordingly in that folder which is used to store the Terraform State remotely in the respective Azure Storage Account/Container</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*34ZjZI1aOwj-VU9GaZI7oQ.png" /><figcaption>backend.tf</figcaption></figure><ul><li>Create provider.tf in the same folder and have the below code which helps to configure infrastructure in Microsoft Azure platform. If you are wondering what are those under key_vault section, feel free to refer my <a href="https://brk0018.medium.com/use-keyvault-and-implement-vnet-peering-in-azure-with-terraform-939c099729c5">previous blog</a> which covers the explanation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*OBiGSDYreq8V4WGLVhbM3A.png" /><figcaption>provider.tf</figcaption></figure><ul><li>Create variables.auto.tfvars having the default declared values like below. We defined address spaces for VNet, Subnet and also for AzureFirewallSubnet as per the needs shown in the architecture above. firewall_allocation_method and firewall_sku will be consumed for building virtual_networks in the later section and definedscale_units as 2 for AzureBastionHost for later use as well</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*KboG6P6BqhPXdsI8e0rtaw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ByRwUlxC7nSuQVWruDsFw.png" /><figcaption>variables.auto.tfvars</figcaption></figure><ul><li>Create variables.tf like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/436/1*Pql2mHnTmp-rAtZjOCBqDw.png" /><figcaption>variables.tf</figcaption></figure><ol><li><strong>Create a Resource Group</strong></li></ol><ul><li>Files rg_main.tf, rg_variables.tf, rg_outputs.tf look like below. We’ve already covered the explanation of how to create Resource Groups using Terraform in our previous blogs. Hence, avoiding the duplication of explanation here but showing the code necessary for implementing this scenario [<em>Similarly, I’ll not repeat explaining the VNets, KV and all other modules which we’ve covered in our previous blog/s. Feel free to refer them if required </em><a href="https://brk0018.medium.com/use-keyvault-and-implement-vnet-peering-in-azure-with-terraform-939c099729c5"><em>here </em></a><em>and </em><a href="https://brk0018.medium.com/deploy-linux-vm-with-terraform-on-azure-with-nsg-rule-and-boot-diagnostics-c868ca2bf8a7"><em>here</em></a><em> as appropriate</em>]</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*xg9IVOYuULwQMp7U_CCRyw.png" /><figcaption>main.tf Snippet_1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*6lLCy3Q8Dj-ZLW69hMxTWg.png" /><figcaption>rg_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/1*4OiEZmbDnhB6qQhMF7w8Rw.png" /><figcaption>rg_main.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*Ipx0paqWhqDrXKGTZK4XyA.png" /><figcaption>rg_outputs.tf</figcaption></figure><p>2. <strong>Create a VNet and a Subnet in that Resource Group</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*z_mp1rTC6IAOtV747zCPxA.png" /><figcaption>vnet_main.tf</figcaption></figure><ul><li>Apart from the VNet and Subnet, we are creating a Network Interface for our LinuxVM so that Private IP can be assigned to it</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/465/1*UP2ROfKs3dPXgzauo5xpNw.png" /><figcaption>vnet_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*G2IvQLRZPazgtSzb6MWc5g.png" /><figcaption>vnet_outputs.tf</figcaption></figure><ul><li>Now, our main.tf looks like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*-mYLqQq_zWi6_pqIZHuC7g.png" /><figcaption>main.tf Snippet_2</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. Feel free to make use of<a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands in between</li><li>You should be able to see the VNet, and Subnet in the respective RG in the portal</li></ul><p>3. <strong>Create Azure Bastion Host and necessary components required</strong></p><ul><li>For a successful, Bastion Host deployment, we should create a subnet with name AzureBastionSubnet and assign a public ip to it as well. Let’s do it now</li><li>Create a folder az_bastion under modules and have the azb_main.tf, azb_variables.tf and azb_outputs.tf files as shown below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*CCcfkJVVZwhBraJ7I9EiCg.png" /><figcaption>azb_main.tf</figcaption></figure><ul><li>You can notice that with azb_main.tf, we are creating the AzureBastionSubnet subnet, azure publicIp and Azure Bastion Host which uses the subnet and the public-ip we created. You may notice some warning/error messages in your code as some variables like location, rg-test-name are not yet declared under az_bastion module. We’ll fix those issues in our next step with azb_variables.tf</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*pGdawmBAQ1PUtaII5_8VJA.png" /><figcaption>azb_variables.tf</figcaption></figure><ul><li>We need resources such as public-Ip and AzureFirewallSubnet-id for our other module consumption hence they are mentioned in azb_outpputs.tf as below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*defejr3rClP6tc1p7XK1gQ.png" /><figcaption>azb_outputs.tf</figcaption></figure><ul><li>Now, time to call this az_bastionmodule from main.tf</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NSO88VaCpYJE-1MvG685kw.png" /><figcaption>main.tf Snippet_3</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution.</li><li>You should be able to see the intended resources in the Azure Portal successfully</li></ul><p>4. <strong>Use </strong><a href="https://azure.microsoft.com/en-au/services/key-vault/#product-overview"><strong>Azure Key Vault</strong></a><strong> and create Secret for the LinuxVM</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dULfvsf9161gO9AULYbBhg.png" /><figcaption>kv_main.tf Snippet_1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*FBwmNPMsdbDqDrW03j7DXw.png" /><figcaption>kv_main.tf Snippet_2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*MMPF6CCTyKOJRs8obqx8vg.png" /><figcaption>kv_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*Kx1jcwMOtlFqoagdq2-8Ew.png" /><figcaption>kv_outputs.tf</figcaption></figure><ul><li>Let’s call the az_key_vault module from the main.tf</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*Fm-Fg9AAWNYvK2IVMgVfFQ.png" /><figcaption>main.tf Snippet_4</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution.</li><li>You should be able to see the intended resources including the KV in the Azure Portal successfully</li></ul><p>5. <strong>Create the LinuxVM</strong></p><ul><li>We’ll create the LinuxVM and assign the NIC we created before during virtual_networks module to this VM</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkNX5sr_u-MggGAVT98ypA.png" /><figcaption>vm_main.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/368/1*T1lkOgMn4ku2-nLNmFcJPA.png" /><figcaption>vm_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*ZkI_7AqYwKdm_79y_myRTA.png" /><figcaption>vm_outputs.tf</figcaption></figure><ul><li>Let’s call the vm module from the main.tf</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*TCCf2HJ4eLKVO4ZKfKDWdw.png" /><figcaption>main.tf Snippet_5</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution.</li><li>You should be able to see the intended resources including the VM in the Azure Portal successfully</li></ul><p>6. <strong>Define the NSG Rules for AzureBastionHost and also for LinuxVM</strong></p><ul><li>Before proceeding further, I strongly recommend you to read through this excellent <a href="https://docs.microsoft.com/en-us/azure/bastion/bastion-nsg">documentation </a>from Microsoft explaining the NSG needs for the Bastion</li><li>We should define NSG rules for both Ingress and Egress traffic from/to the Bastion and also Ingress traffic rules for the Linux VM</li><li>Recommended Ingress and Egress rules are like below for Bastion</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C4DsisWST6SvRAnloozBEw.png" /><figcaption>Ingress [INBOUND] for Bastion</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rxdhZQcEwVr-tMZdZ_NZeg.png" /><figcaption>Egress [OUTBOUND] for Bastion</figcaption></figure><ul><li>In order to implement the above NSG rules, let’s define traffic_rules module and implement the rules accordingly</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*t4d68mJYUrYep-kvOK4YnA.png" /><figcaption>rules_main.tf Snippet_1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/1*tpGXR7R03R-obHTGqzAcDQ.png" /><figcaption>rules_main.tf Snippet_2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*UcBU0RokpsM8JITF5cYWYA.png" /><figcaption>rules_main.tf Snippet_3</figcaption></figure><ul><li>Now, associate the NSG defined to the subnet AzureBastionSubnet like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*0y_ud7GRkckhlMsdBY7r5A.png" /><figcaption>rules_main.tf Snippet_4</figcaption></figure><ul><li>Define NSG rule for LinuxVM and associate it to the NIC [<em>You can also associate it with the subnet in which this VM is present like </em><em>vnet1-subnet1 in case if you want to try that option. I suggest you to understand what difference it makes associating it with the NIC vs Subnet</em>]</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*oGA_3jVWaPfKf0NZUfT97w.png" /><figcaption>rules_main.tf Snippet_5</figcaption></figure><p><em>[When the file contains many lines, it is not feasible to show in one shot and explain at the same time, hence I’ve divided them in to multiple snippets such as </em><em>rules_main.tf Snippet_*, where * represents numbering like 1,2,3 and so on.... I believe that allows you to follow the sequence of code accordingly. Same is true for files such as </em><em>main.tf. You can notice that as </em><em>main.tf Snippet_*]</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*cPaipK0uDSyty2wqhjY9CA.png" /><figcaption>rules_variables.tf</figcaption></figure><ul><li>We don’t really have anything from the traffic_rules module to output. Hence, rules_outputs.tf is blank and it just sits there idle for the terraform schema/structure purpose</li><li>Finally, your Terraform folder structure looks like below for your visibility [<em>Please ignore </em><em>images folderand </em><em>.md file </em>]</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/257/1*TNHqUzvDXb60wAr1P2xEcQ.png" /><figcaption>Az_Bastion_Lab folder structure</figcaption></figure><p>7. <strong>Deploy and Validate the Infrastructure</strong></p><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands and fix any errors by following the blog carefully</li><li>With this, the deployment of resources is complete can be observed in your Azure Portal</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy_khVoTcWY4xPLfu-tCJw.png" /><figcaption>All the Resources under the RG</figcaption></figure><ul><li>Connect to the LinuxVM using Bastion with username and the secret like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k7VR6F_uK9VmsC-zbrmzQA.png" /><figcaption>Connect to LinuxVM using Bastion</figcaption></figure><ul><li>After successful login, you can access the LinuxVM as shown below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*2idz3ADUolngZhv47hH3Xw.png" /><figcaption>LinuxVM after successful login</figcaption></figure><ul><li>That’s it and You are now done with this scenario :)</li><li>Full code can be accessed from here — <a href="https://github.com/ramakb/Az_Bastion_Lab">ramakb/Az_Bastion_Lab (github.com)</a></li></ul><p>Finally perform terraform destroy --auto-approve to destroy all the resources in the Azure Portal to free up consuming the $</p><p>Hope you find this information helpful.</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9be3dba58d67" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use KeyVault and Implement VNet Peering in Azure with Terraform]]></title>
            <link>https://brk0018.medium.com/use-keyvault-and-implement-vnet-peering-in-azure-with-terraform-939c099729c5?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/939c099729c5</guid>
            <category><![CDATA[azure-infrastructure]]></category>
            <category><![CDATA[terraforming]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[terraform-modules]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Mon, 13 Jun 2022 14:15:38 GMT</pubDate>
            <atom:updated>2022-06-13T21:53:55.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/890/1*Pgl1DEuygg5Y9dH9M3lnog.png" /></figure><p>In my <a href="https://brk0018.medium.com/deploy-linux-vm-with-terraform-on-azure-with-nsg-rule-and-boot-diagnostics-c868ca2bf8a7">previous </a>blog, we deployed a very simple scenario using Terraform.</p><p>In this blog, let’s get to a bit more next level where we implement <a href="https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview">VNet Peering</a> between the two virtual networks and we’ll also utilize <a href="https://docs.microsoft.com/en-us/azure/key-vault/general/overview">Azure Key Vault</a> to access our Virtual Machines through secrets rather than keeping the credentials in our code &amp; absorbing them through variable definitions which is NOT an ideal way of restricting the resource’s access</p><p><strong><em>How does our Architecture look like and What do we need to build</em></strong> ?</p><p>Below is the pictorial representation of our goal and let’s keep an eye as we progress with our implementation</p><p>A picture in mind always helps ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PX-s0AbaUhiBvA6_YWSvJg.jpeg" /><figcaption>VNet Peering and KeyVault</figcaption></figure><p>In order to achieve the above, we need to first break down things in to small pieces — Let’s do that and break in to as small steps as possible like below [<em>Remember that these/each step[s] can be further more granularized but for simplicity I’ve limited to ‘10’</em>]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5vXTfZbcdWTE5ojOVHRAnQ.png" /><figcaption>Steps to implement the Architecture shown above</figcaption></figure><p>Let’s begin the fun and make our hands a bit more dirty than before :)</p><p><strong>Build the basic Terraform Folder Structure</strong></p><ul><li>Create a folder named Vnet_Peering_Laband ensure to follow and implement ‘Pre-requisites’ , 2nd and 3rd sections of my <a href="https://brk0018.medium.com/deploy-linux-vm-with-terraform-on-azure-with-nsg-rule-and-boot-diagnostics-c868ca2bf8a7">previous blog</a> before proceeding to the next steps</li><li>Configure the backend.tf accordingly in that folder which is used to store the Terraform State remotely in the respective Azure Storage Account/Container</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*i9mZf98OOEQ2Rjg1c_zNjg.png" /><figcaption>backend.tf</figcaption></figure><ul><li>Create provider.tf in the same folder and have the below code which helps to configure infrastructure in Microsoft Azure platform. Please ignore the key_vault section for now and I’ll explain the use as we come to the section of ‘Key Vault’ Implementation further below of this blog</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*Nqa6DxAnN-ooTJ-fkk3_5A.png" /><figcaption>provider.tf</figcaption></figure><ul><li>Create variables.auto.tfvars having the default declared values like below. We defined address spaces for VNets and Subnets for both the Primary and Secondary Resource Group. firewall_allocation_method and firewall_sku will be consumed for building virtual_networks in the later sections</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qBnIyCDDTPgNCmhIcL3hTw.png" /><figcaption>variables.auto.tfvars</figcaption></figure><ul><li>Create variables.tf like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*DHdg7EQoN34GFFVj028oxA.png" /><figcaption>variables.tf</figcaption></figure><ol><li><strong>Create two Resource Groups</strong></li></ol><ul><li>Let’s create Primary and Secondary Resource Groups by defining them under the resource_groups module. Create a folder modules\resource_groups under Vnet_Peering_Lab and create files rg_main.tf, rg_variables.tf and rg_outputs.tf</li><li>Your folder structure should look similar to below. You can ignore other folders for now or feel free to create those folders and dummy files under those folders as shown below. Eventually, our entire Vnet_Peering_Lab will have all these files and you’ll be writing them as we go along :)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*Xx8-0UA80odN_pHeRpNbPQ.png" /><figcaption>VNet_Peering_Lab folder structure</figcaption></figure><ul><li>Creating the Primary and Secondary Resource Groups. Let’s call the resource_groups module from the main.tf from the root folder and pass the required variables in to that folder like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*F3QmypYa60z8QC13j-j3cw.png" /><figcaption>main.tf Snippet_1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/393/1*u60uQf6b6nD6qe-p1PphoA.png" /><figcaption>rg_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*CHwN5dahUqRckBz2DiuMcA.png" /><figcaption>rg_main.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*Zl939A5QlDyRS3lmTeGHjQ.png" /><figcaption>rg_outputs.tf</figcaption></figure><ul><li>Both the resource group names will be used in other modules, hence rg_outputs.tf has these definitions</li><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands as frequent as possible</li><li>You should be able to see the new [2] resource groups in your Azure Portal now</li></ul><p>2. <strong>Create a VNet and a Subnet in each Resource Group</strong></p><ul><li>If not created already, Create a folder modules\virtual_networks under Vnet_Peering_Lab and create files vnet_main.tf, vnet_variables.tf and vnet_outputs.tf</li><li>Let’s call the virtual_networks module from the main.tf from the root folder and pass the required variables in to that folder like below.</li><li>Take a look at the depends_on and how it is used in this section. Before we deploy the vnets and subnets in to the RGs, we must have RGs existing in the Portal and that condition fulfils the need below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*0dTS2wRC19MLXYLWXer_zA.png" /><figcaption>main.tf Snippet_2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*TAs12hxZABHs3_rN2ytwZw.png" /><figcaption>vnet_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*0dWDXC29JPKBc1v6MRXRYA.png" /><figcaption>vnet_main Snippet_1.tf</figcaption></figure><p>In the above, we are also creating a Public IP which will be associated with the LinuxVM [<em>we will deploy that in the later section</em>] for public access</p><ul><li>Create Network Interface [NIC] and associate the Public IP to it such that it can be attached to the LinuxVM once we deploy it</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*1pJ5t6UWIZiQ9nzmBHxY-g.png" /><figcaption>vnet_main Snippet_2.tf</figcaption></figure><ul><li>Create the VNet, Subnet for Secondary Resource Group and also NIC as well which will be attached to the WindowsVM [<em>we will deploy that in the later section</em>] for internal access</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*0BjGA2cazZ0-EGMaOmbEFg.png" /><figcaption>vnet_main Snippet_3.tf</figcaption></figure><ul><li>Now, it’s time to output the values as references from the virtual_networks module through vnet_outputs.tf like below. These values will be used in other applicable modules in our next sections</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*daeVg5TyBAjutduJrNUB_Q.png" /><figcaption>vnet_outputs.tf</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands as frequent as possible</li><li>You should be able to see the VNets and Subnets in respective RGs in the portal</li></ul><p>3. <strong>Implement VNet Peering between the two Virtual Networks</strong></p><ul><li>If not created already, Create a folder modules\virtual_network_peering under Vnet_Peering_Lab and create files peering_main.tf, peering_variables.tf and peering_outputs.tf</li><li>Let’s call the virtual_network_peeringmodule from the main.tf from the root folder and pass the required variables in to that folder like below</li><li>Again observe depends_on and how we are making use of it here</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v5jsolY3SI6IkUXAy6T1Xw.png" /><figcaption>main.tf Snippet_3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*cSgeRg0T2u2SU9THK_Bnuw.png" /><figcaption>peering_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*o4PaPwXuXan83kTb1mYjyg.png" /><figcaption>peering_main.tf</figcaption></figure><ul><li>We don’t really have anything from the virtual_network_peering module to output to consume in other modules. Hence, peering_outputs.tf is blank and it just sits there idle for the terraform schema/structure purpose</li><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands as frequent as possible</li><li>You should be able to see the successful peering connection between the two VNets in the Azure Portal like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQD_TuyZ0tfznbGuxQi15Q.png" /><figcaption>Peering Vnet1 to Vnet2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SHqm_esEj7DXDRB2XEwgYA.png" /><figcaption>Peering Vnet2 to Vnet1</figcaption></figure><p>4. <strong>Use </strong><a href="https://azure.microsoft.com/en-au/services/key-vault/#product-overview"><strong>Azure Key Vault</strong></a><strong> and create Secrets for the LinuxVM and the WindowsVM</strong></p><ul><li>If not created already, Create a folder modules\az_key_vault under Vnet_Peering_Lab and create files kv_main.tf, kv_variables.tf and kv_outputs.tf</li><li>Let’s call the az_key_vault module from the main.tf from the root folder and pass the required variables in to that folder like below.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZGrFbZyhSLn9wNLmvP6EBw.png" /><figcaption>main.tf Snippet_4</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*usAQkZRuRQp1bcJJrefeug.png" /><figcaption>kv_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1g4xdHPfZDXY439pdAC2g.png" /><figcaption>kv_main Snippet_1</figcaption></figure><ul><li>Under kv_main.tf, we create an Azure Key Vault with key, secret and storage permissions. As this is the development/test environment, we’ve given maximum permissions but in an ideal situation, these permissions will be limited to the <em>least possible</em> permissions to limit the lateral movement and unnecessary exposure</li><li>Continuing further, let’s create secrets which can be then used to feed as the admin_password to access both the VMs [LinuxVM and the WindowsVM]</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*PmBSi4wae-0z4aJOl5zERA.png" /><figcaption>kv_main Snippet_2</figcaption></figure><ul><li>Let’s output the secrets created and also the URI such that the secrets can be consumed under the vm module in up coming sections</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*v3N3Qa8Xy6XYRRAZyiL9mg.png" /><figcaption>kv_outputs.tf</figcaption></figure><p>Let’s understand a bit about key_vault section under providers.tf as we pointed in our earlier section of this blog</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*VyZRuP0FQ98uToFVbGLvZg.png" /><figcaption>provider.tf</figcaption></figure><ul><li>purge_soft_delete_on_destory = true → Enables the key vault to be deleted</li><li>recover_soft_deleted_key_results = false → Disables the use of soft deleted key vaults</li><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands as frequent as possible</li><li>You should be able to see the Azure Key Vault and the Secrets under it in the Azure Portal like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b-7RNPmZN8tQNrxdZ2-4GQ.png" /><figcaption>Azure Key Vault and Secrets in the Azure Portal</figcaption></figure><ul><li>As a sample, see detailed view for one of the secrets in the portal. Ideally, we should be setting up the Expiration date as we don’t want the secrets to be lying around for infinite time. But as this is the Dev/Test environment and we will terraform destroythe resources immediately after our successful deployment, this is ignored for now. Keep a note of this behaviour</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*-QRfAHTqYf0gMuoY9Cl3Jg.png" /></figure><p>5. <strong>Deploy LinuxVM </strong>[in Primary RG]<strong> and WindowsVM </strong>[in Secondary RG]</p><ul><li>If not created already, Create a folder modules\vm under Vnet_Peering_Lab and create files vm_main.tf, vm_variables.tf and vm_outputs.tf</li><li>Let’s call the vm module from the main.tf from the root folder and pass the required variables in to that folder like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EXOsJRSCdxXO3XteNwZLQ.png" /><figcaption>main.tf Snippet_5</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*-YYJSafi8JaFVg7bId0JKw.png" /><figcaption>vm_variables.tf</figcaption></figure><ul><li>It’s time to create our <strong>LinuxVM</strong> in the Primary RG. Observe how network_interface_ids we consumed here which were the outputs from the virtual_networks module. Similarly, observe the same for WindowsVM too</li><li>Commented the code for admin_ssh_key as we are using the Secret from the Azure Key Vault as the admin_password now</li><li>Also make a note of the comment under disable_password_authentication section and why we turned it as false now</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QhZ3u631DtY1dZzt5cNQsg.png" /><figcaption>vm_main.tf Snippet_1</figcaption></figure><ul><li>Let’s create our <strong>WindowsVM</strong> in the Secondary RG</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*UJbKeQrAi_U_H27ctEuoyA.png" /><figcaption>vm_main.tf Snippet_2</figcaption></figure><ul><li>In order to allow ICMP connection to our WindowsVM, we should be disabling the Windows Firewall on the VM. We use <a href="https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/virtual_machine_extension">VM Extension</a> to do so. Have a look at the code snippet below under vm_main.tf</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jXbM9YsHiRutAitTQXYWYg.png" /><figcaption>vm_main.tf Snippet_3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*BZVK7NjGjOzTPr3xLo-Mvg.png" /><figcaption>vm_outputs.tf</figcaption></figure><ul><li>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands as frequent as possible</li><li>You should be able to see the LinuxVM and the WindowsVM under the respective RGs in the Azure Portal now</li></ul><p>I think we’ve come good far in building the infrastructure we need through Terraform. Take couple of mins break and then deep delve in to the Azure Portal to see how your resources are showing up to understand the configurations between them and how they got tied through applicable parameters</p><p>It’s good time now for a break and relax before we implement the traffic rules</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*J-fNslr-84459O7ha6N7Zg.png" /><figcaption>Chai Time ;)</figcaption></figure><p>Let’s get back to the business</p><p>6.<strong> Define Traffic Rules for the LinuxVM and WindowsVM</strong></p><ul><li>Objective is to</li></ul><p>— Limit and allow the Internet Access to LinuxVM through SSH</p><p>— Limit and allow the ICMP access to WindowsVM from LinuxVM and RDP from Peered network only</p><ul><li>If not created already, Create a folder modules\traffic_rules under Vnet_Peering_Lab and create files rules_main.tf, rules_variables.tf and rules_outputs.tf</li><li>Let’s call the traffic_rules module from the main.tf from the root folder and pass the required variables in to that folder like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4s7AVIOpvaM6qPeTe3_9g.png" /><figcaption>main.tf Snippet_6</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*TiV-ccHsobOT9CulkF7VLg.png" /><figcaption>rules_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*U1xg5xPmzJ36dUHvfgampg.png" /><figcaption>rules_main.tf Snippet_1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iWFj3cmoGSEMrEh92reHtQ.png" /><figcaption>rules_main.tf Snippet_2</figcaption></figure><ul><li>We don’t really have anything from the traffic_rules module to output to consume in other modules. Hence, rules_outputs.tf is blank and it just sits there idle for the terraform schema/structure purpose</li></ul><p>Now perform terraform init, terraform plan and terraform apply --auto-approve one after the other successful command execution. I encourage you to also use <a href="https://www.terraform.io/cli/commands/validate">terraform validate</a> and <a href="https://www.terraform.io/cli/commands/fmt">terraform fmt</a> commands and fix any errors by following the blog carefully</p><p>With this, the deployment of resources is complete can be observed in your Azure Portal</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jj2ka6xlgycmNiW0AuVoIg.png" /><figcaption>Primary Resource Group</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpQf5lfiBSWVGp8DBzLVZw.png" /><figcaption>Secondary Resource Group</figcaption></figure><p>Let’s now test the access to our LinuxVM and WindowsVM and confirm the behaviour</p><p>— From the terminal from your local machine, perform ssh adminuser@LinuxVMPubIP [use the LinuxVM Public IP appearing in your Azure Portal in place of LinuxVMPubIP] and use the linuxVM-pswd from the portal as admin_password to login to the LinuxVM. You should be able to login successfully</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0D1UNVaq66CrfWTn2oLoFg.png" /><figcaption>SSH in to LinuxVM from the local machine</figcaption></figure><p>— Ping to WindowsVM from LinuxVM. Using the WindowsVM Private IP address [note down this IP address from your Azure Portal] and use ping WindowsVMPrivateIP to check whether it is working properly as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*eagF2C7eBA-yuZARIaKQFg.png" /></figure><p>— Try to RDP in to this WindowsVM frm your local machine using any of the RDP tools. You’ll be unsucessfull to do as the WindowsVM is expected to accept only the requests from the Peered Network resources</p><p>Finally perform terraform destroy --auto-approve to destroy all the resources in the Azure Portal to free up consuming the $</p><p>That’s it and You are now done with this scenario :)</p><p>Full code can be accessed from here — <a href="https://github.com/ramakb/VNet_Peering_Lab">https://github.com/ramakb/VNet_Peering_Lab</a></p><p>Hope you find this information helpful.</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=939c099729c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploy Linux VM with Terraform on Azure with NSG Rule and Boot Diagnostics]]></title>
            <link>https://brk0018.medium.com/deploy-linux-vm-with-terraform-on-azure-with-nsg-rule-and-boot-diagnostics-c868ca2bf8a7?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c868ca2bf8a7</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Sun, 05 Jun 2022 03:16:50 GMT</pubDate>
            <atom:updated>2022-06-05T03:20:49.226Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pPGmUYQx6yDyQD425Zp_Vw.jpeg" /></figure><p>As I started playing with Azure using Terraform, thought of sharing my hands-on learning through a blog about how to create and deploy a simple Linux VM using Terraform. Along with it, we’ll also control the traffic to that VM through a simple NSG Rule and associate it with the subnet in which we’ve this VM - that way we protect the VM rather than opening all the ports to the public access. We’ll also use storage account/container to store the boot diagnostics of the VM</p><p>To be frank, nothing fancy in this blog as the intention is to begin with some basic fundamentals</p><p>I’ll try to build more complex modules in the upcoming blogs to get in to more advanced levels. Fingers crossed!</p><p>Let’s begin our journey of “<strong>Basics with Terraform &amp; Azure</strong>”</p><ul><li><strong>Pre-requisites</strong></li></ul><ol><li>Azure subscription is required and The reader is expected to have an understanding about Azure Platform, Virtual Networks and Network Security Group fundamentals. General idea can be gathered from <a href="https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-overview">here</a></li><li>Terraform is installed on your local machine. Follow <a href="https://learn.hashicorp.com/tutorials/terraform/install-cli?in=terraform/azure-get-started">this </a>for guidelines</li><li>In the Azure Portal, Manually</li></ol><ul><li>Create a <a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal">Service Principal</a> and ensure to give contributor role through Access Control [IAM] to your subscription</li><li>Create a <a href="https://github.com/DFW1N/service-principle-guide-azure">Client Secret</a> and Ensure to copy and store the Secret Value</li><li>Use setx command to store the SubscriptionID, TenantID, ClientID values on to your system environment variables rather than passing or referring them in your variables.tf file.</li></ul><p>Example: setx SubscriptionID &quot;yoursubscriptionID&quot; Please <a href="https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc755104(v=ws.11)">refer </a>here for more information</p><p>2. <strong>In the Azure Portal, Manually</strong></p><ul><li>Create the Resource Group, Storage Account and a Container which will be primarily used for the backend TFState file</li></ul><p>3. <strong>On your local machine,</strong></p><ul><li>Use any of your favourite Code Editors like VSCode as an example</li><li>Create a folder with a name of your choice. In my example I’ve Exercise-3 as the folder name</li><li>Configure the backend.tf accordingly in the same folder which is used to store the Terraform State remotely in the respective Azure Storage Account/Container. Refer <a href="https://www.terraform.io/language/settings/backends">this </a>to understand more about Terraform Backend. Sample code is given below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*wGTef41IeNtqs7dWGKddwA.png" /><figcaption>backend.tf</figcaption></figure><ul><li>Create provider.tf in the same folder and have the below code which helps to configure infrastructure in Microsoft Azure platform using the Azure Resource Manager APIs — Please <a href="https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs">refer </a>here for more information</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*xN9waW71Zx8-f4nVI7dmhw.png" /><figcaption>provider.tf</figcaption></figure><ul><li>Create variables.auto.tfvars having the default declared values like below. The same can be defined in variables.tf as well but there are few advantages of having it in *.tfvars file. Please <a href="https://medium.com/@subrata.das/what-is-the-difference-between-variables-tf-and-terraform-tfvars-132f8d0d606a">refer </a>here for a simple clarification between variables.tf and *.tfvars</li><li>In the below, `-vnet-address-space` and `subnet-1-address-space` are used for the Virtual Network and the Subnet in which our Linux VM is going to be deployed</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*U8fDsrENVZ-CuI_Qravahg.png" /><figcaption>variables.auto.tfvars</figcaption></figure><ul><li>Create variables.tf like below. I’ve used random_ID variable. Intention is to attach this ID to the Resource Group name and the LinuxVM name which we are going to create soon in the next steps. Use of this random_ID is optional though</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/1*PwTw1N6-JRlwkyVbBwH8JA.png" /><figcaption>variables.tf</figcaption></figure><ul><li>Let’s first create the Resource Group and have below code in the main.tf Take a look at how I’m using the random_ID to attach it to the Resource Group name to bring the uniqueness to the naming convention</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*goUy6jiXyf6Mjibos8iCsQ.png" /><figcaption>main.tf snippet-1</figcaption></figure><p>After saving all these files, Open the terminal in the VSCode and perform below actions to initialize and execute your terraform project code</p><p><a href="https://www.terraform.io/cli/commands/init">terraform init</a> and observe the changes in the folder ‘Exercise-3’</p><p><a href="https://www.terraform.io/cli/commands/plan">terraform plan</a> and observe the console output and understand</p><p><a href="https://www.terraform.io/cli/commands/apply">terraform apply</a> --auto-approve</p><p>After this is successfully executed, open your Azure Portal and see the changes. You should be able to see the Resource Group listed in your Azure Portal</p><p>Please refer <a href="https://learn.hashicorp.com/tutorials/terraform/azure-build?in=terraform/azure-get-started">here </a>for more insights about what is the purpose of each of the above commands. In addition to the above commands, terraform fmt and terraform validate are pretty useful too. Explore about them and understand how they help</p><p>4. Now, it’s time to do little more like creating the Virtual Network, Subnet and actually deploying the Virtual Machine in to that Resource Group. I’m using the concept of terraform modules here. If you’ve never explored about this concept, I highly encourage to read this <a href="https://brendanthompson.com/posts/2020/terraform-to-module-or-not-to-module">blog</a></p><ul><li>Create a sub-folder structure like below under Exercise-3 where we would like to use separate modules for each of the sections like virtual_networks, vm, traffic_rules and storage_accounts</li><li>Under virtual_networks module, create the files as shown below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*-_pPWPtdnb9cg-MVxae2DA.png" /><figcaption>Exercise-3 folder view with modules in it</figcaption></figure><ul><li>In your main.tf, let’s reference this virtual_networks module and pass the required variables which can be used for creating the virtual network. I used time_sleep and also depends_on which are self-explanatory but feel free to explore how they will help in this scenario</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*7LnH1gRohOMKLmriKqG98w.png" /><figcaption>main.tf snippet-2</figcaption></figure><p>See below the different .tf files under virtual_networks module. vnet_outputs.tf outputs from this module will be consumed in other modules such as traffic_rules as per the needs in the following sections</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*UcU6xMQWTUO1E8_C4ovPng.png" /><figcaption>vnet_main.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*Oq619INm5H_YmmzwJJ4sVg.png" /><figcaption>vnet_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*i9DYY7L6QT80EkVNW5hsgw.png" /><figcaption>vnets_outputs.tf</figcaption></figure><ul><li>You might notice some warnings / errors at this stage as some references in vnet_main.tf are incomplete, we’ll sort them out soon in the following sections</li><li>As we’ve defined the VNet, let’s define the Linux VM vm module in main.tfand associate that with the VNet and the Subnet</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/1*Cm2DCETwSrYJtSFkV2XFEA.png" /><figcaption>main.tf snippet-3</figcaption></figure><p>Let’s create vm_main.tf, vm_variables.tf and vm_outputs.tf files under the vm module folder created earlier. The code snippets in those files looks like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*iN3yeqrFCXVQSBXUQ5Ey8w.png" /><figcaption>vm_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*mlxTlHsTV540VUaPI52-Sw.png" /><figcaption>vm_main.tf</figcaption></figure><ul><li>admin_ssh_key — in the above code snippet helps you to ssh in to the vm using your ssh keys. Please follow <a href="https://www.howtogeek.com/762863/how-to-generate-ssh-keys-in-windows-10-and-windows-11/">these </a>guidelines to generate the ssh keys and change the path in your code snippet as per the location of your ssh keys</li><li>vm_outputs.tf is currently blank as we don’t need to pass of the VM information to other modules in our scenario. Feel free to delete the vm_outputs.tf. But generally, I keep it as it is as it’s a good practice to follow the structure and this file can be used for any future modifications/enhancements to the scenario</li><li>You might notice still some warnings / errors at this stage as some references in vnet_main.tf and other .tf files incomplete, we’ll sort them out soon in the upcoming sections</li></ul><p>5. Let’s create some traffic_rules to only allow specific Inbound traffic to our vm</p><ul><li>Define the traffic_rules module in the main.tf like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*m_S6yLNkzquuBopcadUg-A.png" /><figcaption>main.tf snippet-4</figcaption></figure><ul><li>rules_main.tf and rules_variables.tf under traffic_rules folder</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*1RbpSGvzzTWj9xP4z1batQ.png" /><figcaption>rules_main.tf snippet-1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*XzwPsA3887CPWG0KEJLuoA.png" /><figcaption>rules_variables.tf</figcaption></figure><ul><li>similar to vm_outputs.tf, rules_outputs.tf are currently blank for the same reason as mentioned before</li><li>Till now, the folder structure looks like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/261/1*VKTbR5ZHV5XcgTPb28FkCA.png" /><figcaption>Exercise-3 folder &amp; file structure</figcaption></figure><p>6. Let’s capture the boot_diagnostics of the vm we wanted to deploy through this exercise. We’ll use storage_accounts module to fulfil these needs as shown below</p><ul><li>Define storage_accounts module in the main.tf like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21WtWdNaIVEobHAEUl6eZw.png" /><figcaption>main.tf snippet-5</figcaption></figure><ul><li>sa_main.tf, sa_outputs.tf and sa_variables.tf under storage_accounts folder look like below</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*g_patuBHMQ8ghb801k1Y3Q.png" /><figcaption>sa_variables.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*Duj19LJtygx1LrX-i1zTdg.png" /><figcaption>sa_main.tf</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*Gc6YMdoypV4v5y9u2docXg.png" /><figcaption>sa_outputs.tf</figcaption></figure><ul><li>Observe how output from sa_outputs.tf is referenced and consumed in vm_main.tf under boot_diagnostics</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*t_IW0X8VMf2D_ZvT95QmEg.png" /><figcaption>vm_maint.tf referencing the boot_diagnostics for uri</figcaption></figure><p>Now, Let’s run</p><p>terraform init, terraform plan and terraform apply --auto-approve. After successful deployment, You should be able to see all the resources in the Azure Portal successfully like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOj9wCKHOICZ5YndqGHA-w.png" /><figcaption>Azure Portal Resources deployed through Terraform</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yK0puthksZQR4wmQ7SQYqQ.png" /><figcaption>Linux VM with Public IP</figcaption></figure><p>Vnet Map looks like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/445/1*NwzNOVXajbKEtID-12Kksg.png" /><figcaption>tf-network topology before NSG rule</figcaption></figure><ul><li>Now observe, what we defined in vnet_main.tf and how they are shown in the above Vnet Map under your Azure Portal/yourVNet Overview/Topology section</li><li>Let’s ssh in to the VM using</li></ul><p>ssh adminuser@pubIPofyourVM once successfully logged in, use <a href="https://phoenixnap.com/kb/how-to-install-nginx-on-ubuntu-20-04">this</a> to install the nginx server on to that VM. Once you made the server up and running, open any browser and try to access it using <a href="http://pubipofyourvm/">http://pubIPofyourVM</a> and you should be seeing the nginx server welcome page like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l-lPorq-553obO_0KE-Tjg.png" /></figure><p>Notice that you are able to access your VM through port 80 as there are NO restrictions applied yet to your Inbound traffic to the Linux VM. Hence you are able to access it through browser without any traffic blocking</p><p>Also try to ping google.com from your VM ssh session. It should be successful to ping as well as Outbound traffic from your Linux VM is allowed too</p><p>Let’s associate the NSG rule we’ve created in the rules_main.tf code with the subnet now such that we only allow Inbound access through port 22. Now your rules_main.tf should be updated like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*8kR28nc-reScgn6qrNrr2g.png" /><figcaption>rules_main.tf snippet-2</figcaption></figure><p>After the save, perform terraform init, terraform plan and terraform apply --auto-approve to see the changes as intended on your resources</p><p>Now, if you access <a href="http://pubipofyourvm/">http://pubIPofyourVM</a>, shouldn’t be allowed as only Port 22 is acceptable. Hence, you should be still able to ssh in to that machine from your terminal and able to ping google.com as Outbound traffic from the VM rules are unchanged. And now observe the your Vnet Topology in the Azure Portal</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*ZhO4k63gbN6lvSrvkVB6GA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*Ng9AgrePCaQCg6k9eqI3aw.png" /><figcaption>tf-network topology after NSG rule applied</figcaption></figure><p>You can browse through the Storage Account/Container in the Azure Portal for the boot_diagnostics logs and confirm that they exist as per the expectations</p><p>With this, the deployment of the Linux VM with NSG rule and Boot Diagnostics is completely successfully</p><p>Finally perform terraform destroy --auto-approve to destroy all the resources in the Azure Portal to free up consuming the $</p><p>That’s it for now!</p><p>Hope this information finds useful.</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c868ca2bf8a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pathways to Best Cloud Security Posture Review in GCP]]></title>
            <link>https://brk0018.medium.com/pathways-to-best-cloud-security-posture-review-in-gcp-6b31b3cb9305?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b31b3cb9305</guid>
            <category><![CDATA[gcp-security-operations]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-security-architect]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 01:12:38 GMT</pubDate>
            <atom:updated>2022-02-25T01:12:38.276Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ydPr4xItOlqcm0NqjIFLQw.jpeg" /></figure><p>Generally we see many blogs focusing on the Cloud Security Best Practices mentioning from the Products/Services perspective which is good as it stands. But for a change, I wanted to take a different approach through this blog which focuses from the ‘GCP Project Execution teams or GCP Partners’ perspective to ensure they can perform the best cloud security posture review for their customers and/or their GCP tenancy</p><p>Intention behind this blog is to provide a guide to <em>GCP Consultants and Partners</em> help them to deliver The Best Cloud Security Posture Review offerings to their customers. As this is aiming at the GCP Consultants and Partners, the assumption is that they already have a very strong understanding of the GCP Products / Services including a thorough Security knowledge required to carry the assignment and /or assessment</p><p>What is<strong><em> Cloud Security Posture Review </em>[CSPR]</strong>?</p><p>It is an engagement phase aimed to identify the improvements in the existing Security designs and Operational processes by looking at the existing GCP tenancy of the customer</p><p>What is the <strong><em>Outcome of this phase</em></strong>?</p><p>A successful outcome results in addressing the Customer’s Security concerns and helps increase the confidence in them. And in turn, it also helps increasing the GCP adoption with confidence as a secure solution</p><p>The CSPR report document consists a detailed list of recommendations and the reasons behind them based on the assessments done through discussions/workshops among the applicable stakeholders.</p><p>Who is the <strong><em>Customer</em></strong> in this context?</p><ul><li>who have there applications/workloads running already in GCP under different environments like DEV, TEST, STAGE or PROD</li><li>who have an appetite to get their GCP environment reviewed to align with the Google Cloud recommended best practices</li><li>who have a security team but may or may not be aware of the GCP security configurations or setup like a google cloud’s SME and they want to get a better visibility of the things running within their GCP environment</li></ul><p>Before proceeding with the <strong>CSPR</strong>, the GCP Consultants or Partners required to gather background, additional [required] information/permissions and set the expectations correctly with the customer. I’m not covering the preparation checklist in this blog as it totally depends on the mutual agreement and alignment between the customer and the GCP Consultants/Partners and it can be as detailed as possible. The main objective of this blog is to cover the Key areas of focus for the CSPR and highlight the Top 3 to 5 elements under each of those areas</p><p>Let’s begin the journey by going through 7 key areas by asking the fundamental questions, understand the reasons behind those questions [why?] and come up with the best recommendation/s possible as a solution to each of them</p><p><strong>Cloud Resource Management</strong></p><p>It provides the ability to centrally manage all GCP Projects and further helps to group projects into Folders based on business units, developer environments, customer environments, or a combination of them. This hierarchical organisation enables the customers to easily manage common aspects of their resources such as Organisational Policies and IAM policies. Common questions to be asked under this area are listed below:</p><ul><li><em>How are the Projects and Folders organised in your organisation ?</em></li></ul><p>[Why ?] This helps create a clear and logical structure within their organisation such as departments, groups, teams, environments etc., and gives visibility following a defined hierarchy</p><p>[Recommendation/s] → Based on the business needs, define your organisation structure which can be then easily grouped by Cloud IAM permissions and Organisation policy inheritance. Customers can <a href="https://cloud.google.com/resource-manager">refer</a> here to get more insights and collaborate accordingly for a well structured resource hierarchy for their foot-print within the GCP environment</p><ul><li><em>Do you’ve right IAM permissions set at those levels / layers ?</em></li></ul><p>[Why ?] Following a Resource Hierarchy as recommended by Google Cloud, enables to simplify the application of IAM permissions. At the same time over complicating of Resource Hierarchy leads to a messy IAM permission process and makes it difficult to apply effectively and efficiently. Striking the right balance in the hierarchy is so critical else you might face difficulties in implementing principle of least-privilege access through the layers</p><p>[Recommendation/s] → Make use of folders to apply Cloud IAM permissions and organisation policies. Depending on the folder structure defined, more restrictive permissions and policies can be applied through IAM perms and Organisation policies. For e.g., production folder/s must have more stringent restrictions than the development or test folder/s.</p><p><em>Caution </em>— Avoid extensive use of folder level IAM permissions, but instead, apply permissions at a project or resource level.</p><ul><li><em>Do you’ve a standard / approval process defined for new project/s creation ?</em></li></ul><p>[Why ?] By default, Project Creator and Billing Account Creator is assigned to all the users in the domain at the Organisation level and if this gets compromised or if users could create projects that do not follow the defined organisation best practices, that leads to abandoned projects and creates unnecessary management overhead</p><p>[Recommendation/s] → Limit the Project creation under your organisation and implement required organisation policies to grant this only to applicable users. Another way to grant this through a service account such that it can be used through automation. Along with this close control, also define a Resource Isolation strategy which helps to have only a single application, service in a project for a specific environment to enforce full isolation</p><ul><li><em>Do you’ve a defined process &amp; review mechanism to implement new org polices ?</em></li></ul><p>[Why ?] If there is a process and / or review mechanism defined already, the implementation of org policies might lead to a significant impact to an existing application/s or service/s. So, a rigorous and well-defined review process should be established to reduce risk of operational impact and to clearly identify which org policies are meant to be implemented keeping in mind the business aspects</p><p>[Recommendation/s] → GCP comes with wide range of Org Policies ready to be implemented. To name a few are like ‘prevent External IP address’, ‘skip default network creation’, ‘use trusted images’, ‘resource location restriction’ and many more useful policies which contributes to a good security posture. Partners can <a href="https://cloud.google.com/resource-manager/docs/organization-policy/overview">refer</a> to educate the customers and collaborate effectively to strike the right balance</p><ul><li><em>How are Organisation Policies applied ? is it an automated process ?</em></li></ul><p>[Why ?] Configuring Org Policies via policy-as-code techniques using automation such as Terraform enables ease of use. Helps in reviewing each change request before the implementation, provides traceability and also change history</p><p>[Recommendation] → Use Terraform to manage org policies within the organisation and configure org policies as a code. More can be referenced <a href="https://github.com/terraform-google-modules/terraform-google-org-policy">here</a></p><p><strong>Identity, Authentication and Authorization</strong></p><p>Cloud Identity is used for managing users, groups, and domain-wide security settings. It is critical to centrally manage and secure user accounts, service accounts, and service account keys.</p><p>Key to this is to be able to manage IAM permissions at scale while granting the minimum set of permissions for the users to do their job through the least privilege principle possible</p><ul><li><em>Do you have a single source of truth established already and is it synchronised ?</em></li></ul><p>[Why ?] In order to handle the user lifecycle events such as on-boarding, off-boarding can be processed to the Cloud Identify platform. For a successful and risk free administration, synchronising from a single source of truth like HR system is the best approach. As part of this if they’ve any internal and external users, they can be synchronised from their corresponding single authoritative identity system/provider</p><p>[Recommendation/s] → Use a single authoritative identity store such as (Active Directory) and for external users (e.g. customers) into customer identity store and Leverage Google Cloud Directory Sync [GCDS] to sync users and groups from their directory service to Cloud Identity/GSuite. Ensure to synchronise users in real-time to Cloud Identity such that the status and profiles are matched between the Cloud Identity and the Central Identity service</p><ul><li><em>How do you disable the external or internal users and their access ? Is there any process defined ? What about Audit ?</em></li></ul><p>[Why ?] Terminated or Suspended users/employees should not be able to access GCP resources as soon as they are disabled from the HR system. Fool proof implementation of the audit and automation process will limit the damage and minimise the disruption to the users accessing cloud resources</p><p>[Recommendation/s] → Automate and regular audit the process of synchronising users, groups and organisational units from your Identify Store such as Active Directory to Cloud Identity. Leverage GCDS service to sync from your active directory in real-time. More can be referred <a href="https://cloud.google.com/community/tutorials/gcds-use-cases-common-and-complex">here</a></p><ul><li><em>How are the Administrative roles limited and monitored ?</em></li></ul><p>[Why ?] A Super Admin account is the highest privilege account in Cloud Identity and comes with super powers. These accounts should be limited in number and locked away to prevent unauthorised access and to reduce the risk of any compromise. Always have more than one Super Admin account as a backup in case a Super Admin account gets locked out. To reduce the potential for any compromise to this account, it should be *only* used infrequently. Remember to NOT assign this role to any accounts/email addresses that are used for your day-to-day communications</p><p>[Recommendation/s] → Do NOT configure more than 3 or 4 Super Admin accounts. Multiple accounts are needed for a backup strategy for scenarios like if one account gets locked out etc., Create dedicated accounts for Super Admin usage with an email address that is not specific to a particular user email address such as superadmin-users@examplecompany.com</p><ul><li><em>How are you handling Authentication and is it enforced ?</em></li></ul><p>[Why ?] To protect Super Admin accounts and avoid the situation of compromise of those accounts</p><p>[Recommendation/s] → Enforcing 2-factor authentication with Security Keys for all the Admins is a must. All Super Admin accounts must be set with recovery options enabled in case of any unexpected situations with strong authentication methods backing them up.</p><ul><li><em>How do you manage your service accounts, rotation policies and enforcement etc., ?</em></li></ul><p>[Why ?] Users who have Service Account User role on a service account/s can indirectly access all the resources that service account has access to. It is critical to audit the keys and ensure minimum amount of permissions are assigned to the service account/keys and keys are rotated frequently to reduce the attack surface in case if those keys get compromised</p><p>[Recommendation/s] → Disable default service accounts but create custom service accounts for each service with *only* the minimum permissions required for that service. Restrict users who can act as service accounts. Service accounts used by external systems use a static user managed key that do not expire and can be used from any location too. Doing the regular audit, giving them the least permissions possible and scheduled rotation is very critical to minimise the attack surface in case of any compromising situations. Define a consistent naming convention for service accounts that will help in auditing and identifying the purpose behind those service account’s usage easily. Ideally there should be ‘0’ service account users who can act as a service account</p><p><strong>Network Security</strong></p><p>GCP Virtual Private Cloud (VPC) provides networking functionality to VM instances, GKE containers, and Google-Managed Services that run on GCE VMs (such as Cloud Dataproc, App Engine Flex). A VPC provides global, scalable, flexible networking for cloud-based services and has several capabilities to secure and monitor the network</p><ul><li><em>Are default networks being used ?</em></li></ul><p>[Why ?] Default networks allocate a large ip range on creation and they do come with default firewall rules that open ports such as ssh, icmp etc., These IP ranges may be larger than required and increase the risk of IP conflict with on premises and/or other connected networks. Also, default open ports are a security risk if not properly addressed. Leaving these networks active opens them to the risk of users putting GCP resources on them and prone to compromise</p><p>[Recommendation/s] → Delete and stop using Default Networks. Instead, create a new custom network with regions and IP address ranges and custom firewall rules as per the needs. Implement Org Policy constraint constraints/compute.skipDefaultNetworkCreation. Use terraform for project creation and build default network deletion in to the terraform module. More can be referenced <a href="https://github.com/terraform-google-modules/terraform-google-project-factory">here</a>. Keep in mind that applying the constraint at the org level will only apply to future projects that are created in the organisation</p><ul><li><em>Are Shared VPCs being used ? and do you’ve dedicated projects as host projects ?</em></li></ul><p>[Why ?] Communicating between services over public internet increases potential attack surface as the traffic leaves the network. Shared VPC allows an organisation to connect resources from multiple projects to a common VPC network so that they can communicate with each other securely and efficiently using internal IPs from that network and it also helps centralise network administration and implement separation of duties.</p><p>[Recommendation/s] → Use Shared VPC to enable private IP communication between services and centralise network administration. Avoid using Shared VPC host projects for anything besides Shared VPC administration. Service project admins should have access to only specific subnets in within VPCs to ensure adequate isolation and separation of duties. More details can be referred <a href="https://cloud.google.com/vpc/docs/shared-vpc">here</a></p><ul><li><em>Is Private Google Access enabled for all subnets requiring access to Google APIs ? How do VMs access endpoints on the Internet ?</em></li></ul><p>[Why ?] By default, communication to Google APIs and Services is over public internet. With Private Google Access requests to stay within the Google Network thus enabling a public IP or NAT is not required for VMs to access GCP services</p><p>[Recommendation/s] → Enable private access on a subnet by subnet basis. Keep a note that, the firewall rules must allow egress to Google APIs and Services. Private Access is only applies to VM instances which are with Private IPs [NO external ip]. VMs can leverage Cloud NAT to go out to the internet to access the endpoints</p><ul><li><em>Is Internet egress DENIED by default ? and Are Load Balancers use strict SSL policies ?</em></li></ul><p>[Why ?] Creating a default deny firewall rule for all egress traffic mitigates data exfiltration risks. Ensure that the COMPATIBLE SSL load balancer policy is NOT used as it allows the broadest set of clients, including those which support out-of-data SSL features, to negotiate SSL with the load balancer</p><p>[Recommendation/s] → Create a firewall rule with the lowest priority that blocks all outbound/egress traffic for all protocols and ports in combination with default deny all ingress traffic. Ensure to create higher-priority firewall rules for specific traffic in order to open required ports and protocols. This way, we can prevent ports and protocols from being exposed unnecessarily. Use of RESTRICTED profile is recommended for sensitive and regulated workloads for load balancers. Ciphers enabled in the RESTRICTED profile are only supported by TLS 1.2. About SSL policies, more details can be referred <a href="https://cloud.google.com/load-balancing/docs/ssl-policies-concepts">here</a></p><ul><li><em>Are VPC flow logs enabled ? Are Firewall logging enabled for implicit DENY firewall ?</em></li></ul><p>[Why ?] It is critical to have the ability to conduct forensics if an incident were to occur for the networks with high sensitive data and that can be achieved by enabling the VPC Flow logs for every subnet in the VPC network. Similarly, Firewall rules logging helps providing network security by defining rules for traffic incoming and outgoing from the network. These logs are very critical to audit and to verify that existing firewall rules are working as intended :)</p><p>[Recommendation/s] → Enable VPC Flow logs for all the sensitive networks so that in case of an incident, network forensics can be conducted. The logs can be very large and have associated costs as well. Adjust the sampling rate and aggregation rate based on your requirements and you can turn them on a specific subnet as well which handle sensitive information. Similarly, ensure that Firewall Rule logging is enabled for all the firewall rules in place</p><ul><li><em>How do you protect your applications against DDoS and Application layer attacks ? Have you configured end-to-end TLS encryption for applications behind HTTP&lt;S&gt; load balancers using IAP ?</em></li></ul><p>[Why ?] In oder to protect your internet facing applications, filtering incoming traffic is critical through security policies. End-to-end encryption is essential to NOT to send the traffic over the wires in plain-test. This ensures transport security and protects your sensitive data</p><p>[Recommendation/s] → Global Load Balancers provide automatic defense against L3/L4 infrastructure DDoS attacks and Use of Google Cloud Armor security policies protects your load balanced services from application layer attacks such as OWASP Top10 vulnerabilities. Use Global HTTP&lt;S&gt; load balancer in combination with Cloud Armor Security Policies to front end your internet facing applications and services. Configure HTTPS load balancer, IAP, backend service and application to listen on SSL port only and allow only HTTPS traffic on VPC firewall.</p><p><strong>VM Security</strong></p><p>GCP provides a wide range of ways to configure your VM which includes options on how to best secure your instance (IAM access, firewall rules, service accounts, API scopes, SSH, base images, logging, etc). It is a huge responsibility to keep the VM operating system and applications up to date with the latest security patches from both Customer’s and also from being the GCP Parter’s perspective.</p><ul><li><em>Are you in need of a sole tenancy ?</em></li></ul><p>[Why ?] Sole-tenant nodes ensure that your instances do not share host hardware with instances from other projects and use of labels might help to separate your sensitive workloads from non-senstive workloads. As an example, some payment processing work loads might require physical isolation from other workloads or virtual machines in order to meet the compliance requirements</p><p>[Recommendation] → Use sole-tenant nodes to keep your instances physically separated from other instances. More details can be referred <a href="https://cloud.google.com/compute/docs/nodes/sole-tenant-nodes">here</a></p><ul><li><em>Create least privileged custom service accounts for VMs ?</em></li></ul><p>[Why ?] By default, compute engine default service account has Project Editor role which grants access to all the GCP resources within that project. If this service account is assigned to a Compute Engine instance, anyone with access to this instance will have access to all the resources in the project which is not recommended practice.</p><p>[Recommendation] → Do NOT use the Compute Default Service Account rather always a create a custom service account and provide minimum IAM permissions needed for the application on the VM instance to get the required job done</p><ul><li><em>Do you need SSH/RDP access to your VMs from Internet ?</em></li></ul><p>[Why ?] IAP’s TCP forwarding feature lets you control who can access administrative services like SSH and RDP from the public internet. This feature prevents from being openly exposed to the internet and instead, services must pass authentication and authorisation checks on IAP proxy before they get to the targeted resource</p><p>[Recommendation] → Configure IAP with context-aware access to restrict IP CIDR range, client devices and users/groups who are allowed to access. The users gain access *only* if they pass the authentication, authorisation, Ip / device check</p><ul><li><em>How do you ensure only trusted golden images are deployed ?</em></li></ul><p>[Why ?] Only images that have passed the security vulnerability tests and have been configured in an appropriate manner should be allowed to be used within the VPC and we know well enough already the reasons behind it ;)</p><p>[Recommendation] → Ensure an Organisation Policy is created to limit the allowed compute hardened images available for consumption</p><ul><li><em>Regularly patch the custom images and establish an image update process for custom images ?</em></li></ul><p>[Why ?] Having an automated plan for managing the images with the latest security patches and other security updates reduces the attack surface and helps to quickly remediate vulnerabilities in OS and installed software packages</p><p>[Recommendation/s] → Automate the creation and update of new images process. Further tag your images with the version, time, date to help with auditing and debugging purposes. Enforce lifecycle policies on custom images by marking images for deletion and obsolescence and use org policy to ensure that only trusted images are being used.</p><p><strong>Data Security</strong></p><p>GCP offers fully-managed, scalable database services to support your applications and store your data. With managed services there is a wide range of controls and configurations available to store your data securely. The use of these configurations and controls help define your security posture to the best possible.</p><ul><li><em>What tools are being used to scan, classify and report any sensitive data ?</em></li></ul><p>[Why ?] In case if you’ve sensitive data such as credit card numbers, names, social security numbers etc., this information needs to be redacted on a top priority else has the risk of being compromised</p><p>[Recommendation] → Consider implementing DLP [Data Loss Prevention] practice that helps discover and classify the sensitive data. Then redact for sensitive data elements which helps to preserve the utility of your data for joining or analytics while obfuscating the raw sensitive identifiers</p><ul><li><em>Are you protecting your Cloud SQL database instances from being open to the world ?</em></li></ul><p>[Why ?] Minimise the attack surface on database instances and only trusted/known and required IPs should be authorised to connect to it.</p><p>[Recommendation/s] → Configure CloudSQL with private ip only to minimise the attack surface. Configure the root user with a very strong password. Always setup Cloud SQL instances to accept only SSL/TLS connections ie., enforce SSL for all connections.</p><p><em>Note</em>: Connections to your instance through the Cloud SQL Proxy are encrypted whether you configure or enforce SSL/TLS or not. SSL/TLS configuration affects only connections made using IP addresses</p><ul><li><em>Are any datasets shared publicly or are there any datasets shared directly with external users ?</em></li></ul><p>[Why ?] To avoid data exposure, restrict public access especially on data sets that contain restricted or sensitive data</p><p>[Recommendation] → To avoid data exposure, restrict access to internal users on a need to know basis. This can be done in configuration step using IAM Policies and enforced using Organisation Policies</p><ul><li><em>Do you have Data Lifecycle policies configured for GCS buckets and did you define retention policies for compliance needs ?</em></li></ul><p>[Why ?] Ensure that the data older than necessary is no longer retained, reducing the opportunity for unintended data loss. Data in a bucket has a risk of inadvertently being overwritten and/or deleted without a policy in place. From compliance perspectives, this can be a potential issue</p><p>[Recommendation/s] → Data life cycle policy configurations to buckets help to apply a set of rules to current and future objects in that buckets. When a particular object meets the criteria of one of the rules, Cloud storage automatically performs a specified action on that object which overcomes the unintended loss or storage. On the other side from compliance requirements, Bucket locks can help protect the data is not overwritten or deleted</p><ul><li><em>Do you have publicly accessible buckets or objects ?</em></li></ul><p>[Why ?] To avoid unnecessary data exposure, restrict public access especially on buckets/objects that contain restricted or sensitive data</p><p>[Recommendation/s] → Update the IAM policies on the buckets, update the object level ACLs or disabling the use of object level ACLs with an organisation policy to remove the unnecessary public access. This can be further enforced using VPC Service Controls or Forseti validator</p><p><strong>K8S Security</strong></p><p>GKE offers a wide range of configuration options that allow organisations to apply security controls and policies that meet their requirements, and new and improved security features are added frequently. The overall security posture and strength of isolation for each workload, cluster, and surrounding environment depends largely on the combined set of security features, controls, and policies that are put in place.</p><ul><li><em>Are container images built from a minimal base ? and where do they come from ?</em></li></ul><p>[Why ?] Helps to have only core and necessary software available which in turn protects from future work and maintenance work from security perspective. Enforcing the latest approved base images during the image creation process ensures the latest security fixes and updates are incorporated as well which reduces the no. of vulnerabilities in the resulting image</p><p>[Recommendation/s] → Use the smallest possible base image to reduce the amount of OS packages and libraries installed. Build validation process in to your CICD pipeline to ensure only secure base images are used. More details can be referred <a href="https://cloud.google.com/architecture/best-practices-for-building-containers">here</a></p><ul><li><em>Are you storing secrets in your containers ? if so, think again!</em></li></ul><p>[Why ?] In case of any compromise, revocation and rotation of secrets would only involve changes to the security credentials themselves and would not require a rebuild and redeploy of every affected container image. This is possible only if you remove all environment-specific configurations and security credentials out of the container images</p><p>[Recommendation/s] → Secrets should be stored in a centralised secrets management system and workloads should only be combined with the necessary secrets at run-time per-environment basis. It is critical to perform a regular audit to your code repository to ensure that NO database credentials, API keys or other secrets are ‘based in’ to the code and image build process. Watch <a href="https://www.youtube.com/watch?v=wGz_cbtCiEA&amp;t=27s">this</a> to refresh your thoughts about container image best practices</p><ul><li><em>Do you’ve Container LifeCycle Management defined and followed ?</em></li></ul><p>[Why ?] It is critical to scan container images upfront and it is equally important to scan them over time to ensure their security posture is always the latest to meet the desired standards. Consider a scenario where A scan passed the vulnerability scan initially, but after discovery of a new vulnerability or CVE in the cyber world, it will no longer meet the necessary latest requirements</p><p>[Recommendation] → Ensure all images are scanned, updated, rebuilt on a recurring basis to obtain the required security fixes. Configure GCP Container Analysis or any 3rd party tool to scan the container images and notify teams when containers in use NO longer meet the desired security requirements. Please refer <a href="https://cloud.google.com/container-registry/docs/container-analysis">here</a> for more insights</p><ul><li><em>What about ‘Resource Isolation’ and ‘Resource Management’ under K8S ?</em></li></ul><p>[Why ?] Resource Isolation is very critical to avoid contention issues and also to reduce the likelihood of certain resource exhaustion failure scenarios. Resource Management is key as well to ensure all pods have requests and limits rightly configured to prevent over and / or under subscription of resources</p><p>[Recommendation/s] → Enable LimitRanges to set a base CPU and RAM requests/limits on pods for a better Resource Management across the workload/s and similarly place the critical micro-services on to a dedicated node pool and isolate them from custom micro-services on to another dedicated node pool. Use ‘taints’, ‘tolerations’ and ‘node affinity’ features to ensure that the scheduling and deployments happens as per the specifications and configurations</p><ul><li><em>How are you managing your ‘cluster admins’ and do you use ‘cluster network policies’ ?</em></li></ul><p>[Why ?] The no. of users who have the ability to control your GKE clusters should be restricted to the smallest possible admins and it should be a very well known and limited list of members/users. Defense-in-Depth can be achieved by enabling and properly defining the Network Policies to restrict pod-to-pod communication. For eg., if you’ve a compromised front-end service in your application, through network policy you can control the communication links back to the lower levels down the layers and successfully protect the bottom layers from the compromised front-end service/s. It fundamentally helps to reduce the attack surface in case of any compromise or malfunction in the system</p><p>[Recommendation/s] → Ideally a small no. of DevOps/SRE users and development team members should be part of the Cluster Admin responsibilities. Monitor closely the user base with those permissions through a regular audit and review mechanisms. Add applicable rules in Network Policies to restrict communication between workloads and help to avoid lateral movement within the cluster. More details can be referred <a href="https://cloud.google.com/kubernetes-engine/docs/tutorials/network-policy">here</a></p><p><strong>Security Operations</strong></p><p>Securely managing the automated operations lifecycle of GCP resources, protecting its logging and monitoring streams, ensuring all systems conform to a secure configuration baseline, and responding to security incidents are all important capabilities for security and operations teams to master. Insufficient focus in these areas can manifest in security misconfigurations, slow development cycles, and missed or delayed responses to security incidents.</p><ul><li><em>Do you’ve a centralized and aggregated logging in place ? Is there any 3rd party SIEM integration in place ?</em></li></ul><p>[Why ?] Configuring a Centralized system that aggregates the logging allows security teams to manage alerts and gives full context of incident/s.</p><p>[Recommendation] → Create a sink in a GCP organisation or folder and set that sink’s includeChildren parameter to True. This configuration inherits all the child projects under that organisation and folder which can simplify the process of exporting all logs for a given environment in to a 3rd party SIEM solution or an integration with Cloud Security Command Center</p><ul><li><em>Do you restrict access to Exported Logs ? Is versioning enabled on Log sink buckets ?</em></li></ul><p>[Why ?] Always limit the access to these exported logs to a no. of accounts with appropriate permissions in place to avoid any compromise and data exposure. To support the retrieval of objects that are deleted or overwritten, Object versioning feature is very important</p><p>[Recommendation/s] → Follow the principle of least privilege to provide access permissions to these logs. Grant minimum permissions required to get the job done and monitor who has what access and why and document as necessary. For all GCS buckets which are targets of log exports, enable Object Versioning or implement ‘bucket lock’ feature to prevent any malicious action</p><ul><li><em>How often do you conduct Risk assessments and Vulnerability Scanning ?</em></li></ul><p>[Recommendation] Frequent assessments and scanning of the infrastructure and other GCP services and your source code ensures to remediate vulnerabilities whenever they arise [‘why’ is very well known hence skipped]</p><ul><li><em>Do you’ve an Incident Response [IR] plan in place ?</em></li></ul><p>[Why ?] A well formed IR plan can reduce the impact of an incident, avoids the confusion but helps to remediate the issue in an organised way through systematic approach and /or actions</p><p>[Recommendation] Develop and maintain an appropriate IR Plan in accordance with the necessary compliance frameworks. The NIST 800–61 is commonly used baseline for building a response plan. Please refer <a href="https://csrc.nist.gov/publications/detail/sp/800-61/rev-2/final">here</a> for more details</p><p>That’s enough with questions and recommendations as an entry point to achieve the goal.</p><p>During this engagement process, GCP Partners can come up with a document covering all the applicable areas through ‘Technical Review and Improvements’ [sample is shown below] and present it to the stakeholders. Based on the mutual agreement and alignment, this engagement can get in to the implementation phase/s</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*ByBQxIj_Y-54x6PbdJTAqw.png" /><figcaption>Technical Review &amp; Implementations Document</figcaption></figure><p>A Good way of showing the improvements is by preparing the list of items/sections and comparing the “Before/Old Status” and “After/New Status” such that the value addition is very clear and precise to the stakeholders. Sample is shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*eQP4nWhnGu3nOh8YjKt4eA.png" /><figcaption>Technical Review &amp; Improvements Summary</figcaption></figure><p>This is it!</p><p>Hope you find this information useful.</p><p><strong><em>Thanks for taking time to read!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b31b3cb9305" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implement Cloud Armor Security Policy/s using Terraform]]></title>
            <link>https://brk0018.medium.com/implement-cloud-armor-security-policy-s-using-terraform-1794792e2842?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1794792e2842</guid>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-armor]]></category>
            <category><![CDATA[google-cloud-armor]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Wed, 19 Jan 2022 04:42:03 GMT</pubDate>
            <atom:updated>2022-01-19T04:42:03.688Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IXmTwP9vBB-Vh_1w0BpsvA.png" /></figure><p>Google Cloud Armor helps you protect your Google Cloud deployments from multiple types of threats including DDoS [Distributed Denial-of-Service] attacks and Application attacks such as XSS [Cross-Site Scripting] and SQLi [SQL Injection]</p><p>Google Cloud Armor provides some automatic protections but other protections must be configured manually by you to get the most out of it’s powerful usage</p><p><strong>Note</strong>: Google Cloud Armor provides protection only to the ‘<em>Applications which are behind an External Load Balancer</em>’ and some features are ‘<em>only available for an External HTTP&lt;S&gt; Load Balancer</em>’</p><p><strong>Protect your Google Cloud Deployments with Google Cloud Armor Security Policies</strong></p><p>GCP Cloud Armor Security Policies help protect your application by providing Layer 7 filtering and scanning incoming requests for common web application attacks. Each Security Policy is a combination of set of rules that filter the traffic based on conditions such as an incoming request’s IP Address, IP Range, Region Code or Request Headers</p><p>These security policies are available *only* for backend services which are behind an external HTTP&lt;S&gt; load balancer</p><p>In this blog, I’ll cover how to implement security policies through Terraform for ‘<em>Instance Groups </em>as the backend service’ and primary focus would be to help define WAF Rules and consume them through Security Policy</p><p>In order to configure Google Cloud Armor Security Policies, specific IAM permissions are required. Please <a href="https://cloud.google.com/armor/docs/configure-security-policies">refer</a> here</p><p>Let’s first define the instance_group using the terraform file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*a922ZZOnMDfuE8UpM7bqJQ.png" /><figcaption>instance_group.tf</figcaption></figure><p>Applicable variables are defined in variables.tf as below [You’ll notice some more definitions/declarations in the file which will be consumed in the later sections of the blog]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*3pulZP7Db-23PfOh6qqzyg.png" /><figcaption>variables.tf — snippet part: 1</figcaption></figure><p>Let’s define specific ‘variables’ for specific ‘rules’ which will be consumed with the Cloud Armor Security Policies.</p><p>First, the ‘Default ALLOW Rule’.</p><p>Depending on your business case needs, you can modify the below rule to either ‘<em>allow</em>’ or ‘<em>deny</em>’ with different set of priorities</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*Uwl0gAVkb5GVbOo4jB6rXg.png" /><figcaption>variables.tf — snippet part: 2</figcaption></figure><p>Rule evaluation order is defined by the ‘<em>rule priority</em>’ from the lowest number to the highest number. <em>The rule with the lowest numeric value assigned has the highest logical priority and is evaluated prior to values with lower logical priorities</em>. The priority for each rule must be set to a number from ‘0 to 2147483646 inclusive’. The priority value <em>2147483647</em> is reserved for the ‘<em>default rule</em>’ and it is used as shown in the above image</p><p>Please refer ‘<a href="https://cloud.google.com/armor/docs/security-policy-overview#default-rule">Rule evaluation order</a>’ documentation for more details which is very informative and useful</p><p>Each Google Cloud Armor security policy contains a ‘<em>default rule</em>’ that is matched if none of the highest priority rules are matched or if there are no other rules in the policy. The default rule is automatically assigned a priority 2147483647 and it is always present in the security policy</p><p>Let’s define the Security Policy in cloud_armor_sec_policy.tf as we already have the ‘<em>default rule</em>’ defined in the variables file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*Vbpp6sq23YjdTdcPEtTl1g.png" /><figcaption>cloud_armor_sec_policy.tf — Snipppet part: 1</figcaption></figure><p>Now, it’s time to consume the defined rule in the Security Policy with the https load balancer [https_loadbalancer.tf] like shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*GJQakrRVaWFNBdfFaBccJg.png" /><figcaption>https_loadbalancer.tf</figcaption></figure><p>If I expand the ‘groups’ section which is our Instance Group, it looks like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*q9LnxP30DM-LIG76il9eqw.png" /></figure><p>As this blog is focused more on to the Security Policies and WAF Rules., I’ll suggest you to refer ‘<a href="https://cloud.google.com/load-balancing/docs/https#health-checks">External HTTPS Load Balancer</a>’ ‘<a href="https://cloud.google.com/load-balancing/docs/health-checks">Health checks</a>’ and ‘<a href="https://cloud.google.com/compute/docs/instance-groups">Instance Groups</a>’ for more detailed information about them</p><p><strong>Pre-configured WAF Rules</strong></p><p>Google Cloud Armor comes with Preconfigured rules for XSS, SQLi, LFI, RFI and RCE which are based on the <a href="https://github.com/coreruleset/coreruleset//">OWASP Modsecurity</a> core rule set</p><p>Each preconfigured rule consists of multiple signatures. Incoming requests are evaluated against the preconfigured rules. A request matches a preconfigured rule if the request matches any of the signatures that are associated with the preconfigured rule. A match is made when the ‘<em>evaluatePreconfiguredExpr()’</em> command return the value ‘<em>true’</em></p><p>During your observation if you see that the preconfigured rule is matching more traffic than necessary or if that rule is blocking more traffic than the actual needs, you can fine tune that rule to reduce the noise by disabling the unnecessary signatures. Use the syntax like below to reduce the noise from ‘SIGNATURE1’ and ‘SIGNATURE2’ for a particular ‘RULE’ using the <a href="https://cloud.google.com/armor/docs/rules-language-reference">custom rules language</a></p><pre>evaluatePreconfiguredExpr(RULE, [&#39;SIGNATURE1&#39;, &#39;SIGNATURE2&#39;])</pre><p>Using the above format, the rule for SQLi sensitivity level 3 can be written like below where the below rule helps ignore the traffic by unblocking the traffic from signatures ‘owasp-crs-v030001-id942421-sqli’ and ‘owasp-crs-v030001-id942432-sqli’</p><pre>evaluatePreconfiguredExpr(&#39;sqli-stable&#39;, <br> [&#39;owasp-crs-v030001-id942421-sqli&#39;,<br> &#39;owasp-crs-v030001-id942432-sqli&#39;]<br>)</pre><p>Each preconfigured rule has a sensitivity level that corresponds to a <a href="https://coreruleset.org/faq/#paranoialevel">ModeSecurity paranoia level</a>. Lower the sensitivity level indicates a higher confidence signature, which is less likely to generate a false positive. A higher sensitivity level increases security but also increases the risk of generating a false positive</p><p>Sensitivity Level 1 is advised for beginners, installations covering many different sites and applications and Sensitivity Level 4 is aimed at experienced users protecting installations with high security requirements. Running at Level 4, will likely produce a very high number of FPs which have to be treated before the site can go to production</p><p>Now., Let’s define a WAF rule for SQLi with the sensitivity level 2 [To configure a rule at a particular sensitivity level, you need to disable the signatures at other greater sensitivity levels]. In this case, we should disable the signatures which are levels 3 and 4 and the WAF rule looks like below</p><pre>evaluatePreconfiguredExpr(&#39;sqli-stable&#39;, <br>[&#39;owasp-crs-v030001-id942251-sqli&#39;,<br> &#39;owasp-crs-v030001-id942420-sqli&#39;,<br> &#39;owasp-crs-v030001-id942431-sqli&#39;,<br> &#39;owasp-crs-v030001-id942460-sqli&#39;,<br> &#39;owasp-crs-v030001-id942421-sqli&#39;,<br> &#39;owasp-crs-v030001-id942432-sqli&#39;]<br>)</pre><p>Similarly, If we’ve to define a rule with the sensitivity level 1., we should disable all the signatures at level 2, 3 and 4 respectively for that particular WAF</p><p>Now, as we understand how the rules get defined and how you use signatures to either block or unblock your traffic needs — Let’s declare WAF rule for OWASP TOP 10 in variables.tf.</p><p>You can add or delete specific signatures for each of these vulnerabilities based on your needs and also you can remove certain rules if necessary. Fine-tuning can be as granular as you can think of as long as you are able to identify the specific traffic requirements and define the correct syntax for that WAF rule</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U3b4cVZFabm5ZzwdH_R50w.png" /><figcaption>variables.tf — snippet part: 3</figcaption></figure><p>Let’s consume the OWASP TOP 10 WAF rule through the Security Policy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*w36-kb3oq1VZt4IEQNI3LA.png" /><figcaption>cloud_armor_sec_policy.tf — Snipppet part: 2</figcaption></figure><p>Recently, Apache Log4j issue made a big news in the cyber security space and google cloud deployments are no exception to protection. So, you can declare a WAF rule for the Apache Log4J as well in the variables.tf like shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*VGjLhZMLW_P0ypXMlF-y2Q.png" /><figcaption>variables.tf — snippet part: 4</figcaption></figure><p>and consume it through the Security Policy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*yzrJJyjAvOrMUkOE-bCGTQ.png" /><figcaption>cloud_armor_sec_policy.tf — Snipppet part: 3</figcaption></figure><p>Wonderful blog from google cloud is <a href="https://cloud.google.com/blog/products/identity-security/recommendations-for-apache-log4j2-vulnerability?skip_cache=true">here</a> about the recommendations to deal with the Apache Log4j 2 vulnerability</p><p>Finally, the cloud_armor_sec_policy.tf file looks like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*RZFfZDZBdWUZokX7T3rGVw.png" /><figcaption>cloud_armor_sec_policy.tf</figcaption></figure><p>In case if you want to only allow users from a specific region [say ‘AU’] and disallow the access to your application/s from other regions [‘non-AU’], you can define a variable in the variables.tf like below as a sample and consume it similar to other examples shown above under the security policy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*CBZM97lWoTrKdCcmlUDbtA.png" /><figcaption>sample for region specific access</figcaption></figure><p>The variables defined for iap and security_response_headers in variables.tf are like below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*G9CrknfnGh22Q3oylCY8dw.png" /><figcaption>variables.tf — snippet part: 5</figcaption></figure><p>In case if you face any issues with Google Cloud Armor, there is an amazing detailed <a href="https://cloud.google.com/armor/docs/troubleshooting">troubleshooting guide</a> available to refer along with <a href="https://cloud.google.com/armor/docs/request-logging">request logging</a></p><p>That’s it for now.</p><p>Hope this information finds useful.</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1794792e2842" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GCP — Cloud Security Best Practices for Enterprises]]></title>
            <link>https://brk0018.medium.com/gcp-cloud-security-best-practices-for-enterprises-4553f4a546a6?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4553f4a546a6</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[gcpsecurity]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[cloud-security-architect]]></category>
            <category><![CDATA[cloud-security-solution]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 05:45:24 GMT</pubDate>
            <atom:updated>2022-01-06T05:45:24.887Z</atom:updated>
            <content:encoded><![CDATA[<h3>GCP — Cloud Security Best Practices for Enterprises</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9oRoLjbHTkSxcmnPFk816g.jpeg" /></figure><p>I started my journey in to the Cloud Security Engineering space, Been looking in to several enterprises and their existing GCP Infrastructure/s from Cloud Security Architecture perspective — noticed some of the fundamental issues &amp; gaps with their existing Cloud Architecture and Cloud Security Posture.</p><p>As I understood the gaps to some extent [still long way to go and experience many more business cases and scenarios though] - It has been going through my mind for couple of months now that ‘Why don’t I write and simplify it for easy and quick reference for everyone desired?’ to have a look and take this further to enhance their Cloud Security Posture from the very beginning of their Cloud Journey</p><p>and</p><p>The Time has come now to sit and start writing it down. Thanks to X’mas vacations/holidays which helps bit of free mind and enables the idea/s to flow easily. I prefer sitting at one-go and finish it in one-sitting from the very start to end irrespective of the time it takes to complete, that helps me to keep that continuous flow of thoughts in to my writing.</p><p>That’s me and Only Me!</p><p>The Perfect time to trigger my idea to blog here which aims to give initial *must* considerations for any GCP Cloud Project or Projects for your organisation</p><ol><li><strong>Channelize your Resources and Structure your Resource Hierarchy</strong></li></ol><p>Fundamental issue I’ve noticed is that everything is jam-packed in to one single folder and isolation is existing only between the projects but within the same folder which leads to a potential attack surface</p><p>To avoid this, Channelize your resources and following <em>‘resource hierarchy’</em> allows you to map your organisation’s (operational) structure to Google Cloud and thus allow you to manage them in an organised manner</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuHn4NgCd5VdeOWKafA8Mw.png" /></figure><p>The Org Node aka ‘Organisation’ helps to provide central visibility and control over all the resources under that Organisation node</p><p>Folders help to create isolation between different teams or departments under the organisation. Folders can be further split in to sub-folders based on your business needs and there is no restriction on folder levels.</p><p>The bottom layer is the ‘Project’ level. Projects help contain GCP resources which help constitute your application/s. Projects can contain resources spread across multiple regions and geographies. Best Practice is to have one project per application per environment. For eg., if you’ve 2 applications ‘A’ and ‘B’, with a development, staging and production environment, you would have 6 projects in total such as A-dev, A-stage, A-prod and B-dev, B-stage, B-prod. This segregation helps in isolating the environments from each other so that changes in one project/env do not accidentally impact other project/env and also helps provide better access control too</p><p>2. <strong>Implement IAM [Identity and Access Management] as the standard</strong></p><p>In a nut shell, most common issues found are like using ‘individual’ accounts instead of ‘groups’ to grant access to specific Google Cloud resources and fully ignoring the basic security principle of ‘least privilege’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*cs_kQ1cLMz4AsmPobBSmEQ.png" /></figure><p>To avoid this, follow the recommended IAM best practices such as:</p><ul><li>Always use fully managed google accounts which are tied to your corporate domain name through Cloud Identity. This forms a management layer through which enabling or disabling the access to your google cloud resources is easily possible</li><li>Synchronise your user directory to Cloud Identity which lets your users to access the google cloud resources with their existing credentials. This leads to have your identity platform as the ‘single source of truth’ whereas Cloud Identity helps you to control the ‘how’ access to your google cloud resources</li><li>Control access to resources using google groups instead of individual accounts and use Service Accounts where applicable. For all the server-to-server interactions, use service accounts. For example, avoid Automatic IAM permissions for default service accounts and Ability to create service accounts in a production environment</li><li>Define Organization Policy/Policies which helps to set restrictions on specific resources to determine how those can be configured and used. For example, you can define a constraint to restrict any VM to not to use default service account.</li></ul><p>3. <strong>Custom Network and Network Security —Think and Design Early</strong></p><p>To be frank, the issues I noticed under this section are like eye-openers as I couldn’t believe my eyes when I first looked at it.</p><p>You know what — People are using ‘Default’ Networks. Just not that but also ‘Default’ firewall rules which are unbelievably true from my perspective. You cannot start worse than this ;&gt;(</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evthMJFN4nDUuw5fQkEyNg.jpeg" /></figure><p>Let me simplify the bare minimum things to start considering from the beginning</p><ul><li>Avoid using ‘Default’ VPC Network especially in Google Cloud rather use ‘Custom’ VPC Network. There is a massive difference between other CSPs vs about GCP how the default VPC has been set up. Spend little time to understand that before you start. Google recommends enterprises to use custom mode VPC Networks for some valid reasons. <a href="https://cloud.google.com/architecture/best-practices-vpc-design#custom-mode">Refer</a> here for more information</li><li>Avoid using ‘Default’ firewall rules instead create your own ‘custom’ firewall rules which brings loads of control about how you can group and isolate related resources with combination of the network and firewall rules. These firewall rules allow you to specify the type of traffic like ports and protocols and the source or destination of the traffic. Default firewall rules open up ports for a wide range of IP addresses for some protocols which is a potential security risk and not a recommended best practice</li><li>Enable Firewall Rule Logging which helps to audit, verify and analyse the effectiveness of the firewall rules in action. It’s a recommended practice to enable these logs for audit and analysis purpose</li><li>Use VPC Flow Logs and create a process to enable flow logs when needed. Theses logs can be used for network monitoring, forensics, real-time security analysis and also helps in expense optimisation too</li><li>Avoid or Limit External Access to the internet to only those google cloud resources that need it. Resources within a VPC network can communicate among themselves anyhow through internal IP addresses and this can be further limited using Firewall rules if needed. Use google cloud services such as ‘Cloud NAT’ and ‘Private Google Access’ based on the use case to avoid simply opening up your resources to the internet. Common mistakes noted are like Every VM has an external IP address attached to it, GCS buckets are freely accessible apart from not using the earlier mentioned services</li><li>Centralise and Control the Network using Shared VPC or VPC Peering. VPC Network Peering helps to connect different VPC networks and to communicate internally without traversing through the internet whereas Shared VPC allows an organisation to connect resources from multiple projects to a common network to communicate securely and efficiently using the internal IP from that network. In case if you are trying to connect from on-premises to Google Cloud, use Cloud VPN or Interconnect services depending on the business use case</li></ul><p>4. <strong>Securing your Applications and Data</strong></p><p>Google Cloud has many wonderful Products and Services which helps your applications and data to be more secure and safe in addition to the scale you are looking for. Start using them to get the best benefit</p><p>Some of the major gaps I’ve noticed with my different enterprise GCP foundation assessments are like No VPC Service Controls in place, No usage of Secret Manager at all, Poor Cloud SQL Security Configuration, Cloud Functions running with abnormalities and Steps not taken for Application Scalability and Security</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*srn4Z8QX0-AziVUiiDktsQ.png" /></figure><p>Let me simplify ‘why’ you need to consider them from the get go:</p><ul><li>In case if you are using the services such as GCS and BigQuery, VPC Service Controls bring the ability to mitigate the risk of data exfiltration from these services. It is a recommended practice to configure VPC Service Controls to create perimeters that protect the resources and data on those services</li><li>Sensitive information such as passwords, API keys or certificates are stored in plain-text format instead of using the Secret Manager. To protect and limit access to the sensitive information, start using the Secret Manager. It also comes with versioning and rotation mechanisms for more secure and control management. The best use case scenarios such as DB Passwords, API Keys and Certificates must be used with Secret Manager without fail</li><li>In some cases, noticed Cloud Functions are running with deprecated run-time environments which poses a potential security risk due to existing vulnerabilities against it. In order to avoid, applicable Organisation Policies can be enabled and in addition to that implement a standard development practices and guidelines within your organisation. It is also recommended to implement a Monitoring and Review process of service usage and their versions at regular intervals</li><li>SQL Security focus is another area where I’ve noticed fundamental issues during my assessments. In order to attain better SQL Security, consider implementing Restrict Public IP access on the Cloud SQL instances by enabling an organization policy<em>. </em>For additional security, consider using Cloud SQL Proxy. Also, through organization policy unauthorized network access can be disallowed as well. Always, allow only secured connections to access your Cloud SQL instances either through TLS protocol or SSL encryption</li><li>To bring Application Security and Provide Scalability at the same time, use a combination of Global Load Balancer with Cloud Armor Security Policies for WAF Protection. You can also use Cloud CDN to accelerate your applications for the users and Identify Aware Proxy services to control access to your applications and thus implement Zero-Trust Access model. External Global Load Balancer enables to run and scale your applications behind a single external IP address whereas Cloud Armor helps to protect from multiple types of threats including DDoS attacks and application attacks like XSS and SQLi etc.,</li></ul><p>5. <strong>Logging, Monitoring and Operations</strong></p><p>Enterprises typically run multiple applications and processes and often across different platforms. Logging and Monitoring of these applications from Operations perspective is a key element which helps track the health of the applications. To help with these business needs, google cloud has Cloud Logging and Cloud Monitoring services to manage logging, monitoring, debugging, tracking, profiling and many more.</p><p>General tendency I’ve noticed during my assessments is that the business users are unaware these services and their benefits. In this blog, I’ll try to highlight ‘why’ it is beneficial to make use of these services to the best possible</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*anyAfBBZ1u83AThYrVe1hA.jpeg" /></figure><ul><li>Enable logging for any historical analysis and monitoring purposes which helps to track the health of the applications and GCP resources regularly. It is a good practice to set up a separate Monitoring Project for the Production folder and export the logging through applicable log sink/s. Do keep a note that logging retains app and audit logs for a limited period of time. In case if you want to retain logs for longer duration to meet compliance regulations, utilise other GCP services to fit your purpose</li><li>Setup required Alerts through notification channels to help act on the alerts as needed</li><li>The centralised logging location must be highly secured with access to only privileged members and a SIEM to monitor these logs regularly. Secure mechanisms help prevent log manipulation which could cover up malicious activity or attacks and SIEM could monitor and alert for</li><li>Use Security Command Center [SCC] and Security Scanner [SS] as both of these products enable to monitor and track the security vulnerabilities in the applications continuously through a single plain of glass to help mitigate and handle them aggressively. The SCC provides a centralised vulnerability and threat reporting service to help strengthen the security posture of the GCP infrastructure whereas SS identifies the security vulnerabilities in the applications</li><li>To increate agility and reduce time-to-market for applications and features, break silos between different teams such as development, operations, security and networking team and build the DevOps culture and use the Tools where necessary to achieve it collaboratively</li></ul><p>6. <strong>Billing and Management</strong></p><p>Even though this sounds very critical as it deals with $, it was surprising to see in some cases that this section has been handled in a least effective manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*o8QikiQaDQMcgT4VJqRWlg.png" /></figure><p>Fundamentally, enterprises should take steps to understand ‘how each of these google cloud resources are charged’, ‘how they can setup a billing management controls’ and then plan for their capacity requirements by implementing cost controls and build centre of excellence over time</p><p>Budget Alerts are very critical for control and monitoring of the $$$ spent and implement ‘Labelling’ where ever applicable for easy tracking and isolation in breaking down the costs. These alerts help in the case of any excessive spending due to any malicious activity or attacks such as DDoS etc.,</p><p>In order to build a centre of excellence, it is a good practice to nominate Google Cloud Experts and Champions in your team/organisation. A range of training and certification options are available to help nominated champions to grow in their area and build their expertise. Teams can stay up to date on the latest news, announcements and customer stories by following the Google Cloud Blog</p><p>That’s it for now.</p><p>As you know, the topic is very huge and we can go on and on and on as there are too many things to consider and highlight in each of the sections above ….</p><p>but with this blog, I wanted to touch upon bare minimum things to start eyeing from the day one and start building it more and more securely as you progress.</p><p>Hope this information finds useful.</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4553f4a546a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What it takes to be a ‘Certified’ GCP Professional Network Engineer ?]]></title>
            <link>https://brk0018.medium.com/what-it-takes-to-be-a-certified-gcp-professional-network-engineer-4c188ccc318d?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c188ccc318d</guid>
            <category><![CDATA[gcp-certification]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[google-network]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Tue, 24 Aug 2021 15:56:28 GMT</pubDate>
            <atom:updated>2021-08-25T04:14:16.899Z</atom:updated>
            <content:encoded><![CDATA[<h3>What it takes to be a ‘Certified’ GCP Professional Network Engineer ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V0gx7C9OGu4YabPACgNbOA.png" /></figure><p>You know what ? — I’m on cloud9s at the moment………………</p><p>Few hours back, I took this test online from home and glad to see the screen showing me ‘PASS’ :)</p><p>I’m still waiting for the official certification from Google Cloud as its still in the ‘Review Process’ at the moment as shown below. But I think it shouldn’t stop me from sharing about my journey towards this epic moment!</p><p>This is a very special moment for me because I didn’t plan to take this cert but eventually ended up preparing for it looking at the context and value addition it brings on to the table. And I can definitely say that it’s worth more than you can imagine. I’ll cover all those interesting facts below…Keep reading!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHlBrniv-6X9ESlaRAPsaw.png" /></figure><p>My thoughts and views are very fresh considering I dealt with it few hours back and my preparation. Hence, I think this is the best time to put all those in words through this blog which can help other aspiring engineers to follow</p><p><strong><em>Little background</em></strong></p><p>As mentioned before — this certification was never in my to-do list as I wanted to focus more specifically towards Cloud Security Specialisation. But while I was preparing for the GCP Professional Cloud Security Engineer certification, it hit my mind to focus on to the Network Specialisation as well. Because, Network and Security go very deep hand-in-hand — it’s impossible to think about the Security without being understanding the Networking concepts and how they join the dots together. They are very very very deeply interlinked — That’s the reason and that’s the only reason!</p><p>If you are really serious about the Cloud Security within the GCP space, I strongly recommend to take up the Security and Network Certifications [both] without fail. Definitely, you’ll feel the kick it takes to grab those under your belt :)</p><p>I think this holds very true for other CSPs as well but I don’t have much expertise to talk about AWS, Azure etc., and feel free to refer to the appropriate references as applicable</p><p><strong><em>What’s the Best Path ?</em></strong></p><p>According to me [<em>these views are my very own., follow with your own &amp; individual judgement</em>], If you are very much keen on to the GCP Cloud Security, I think FIRST — preparing for the Professional Cloud Architect [which gives a very broad and deeper understanding about most of the GCP Products and Services], SECOND — preparing for the Professional Cloud Security Engineer [which gives a very thorough and detailed security perspective for each of the GCP Products and Services] and THIRD — finally hooking up with Professional Network Engineer [which gives a very detailed perspective to all of the GCP Networking Products and Services] is the best way to soak information step-by-step.</p><p>The above path best suits for the fresh minds who are with less experience with the GCP Cloud Technologies but if you have been already playing with the Cloud Space for a good time, then I think above might not really fit for you. Instead, based on your focus area/s — you can straight away jump on to that particular professional specialised certification. Applicable Commercial experience definitely helps you smash it though!</p><p><strong><em>Is this Particular Certification Exam ‘Tough’ ?</em></strong></p><p>Yeah — without a doubt — 100%! This is my 4th Certification within the GCP space and I can definitely say that if you are not well prepared., this exam can peel your skin very easily and you’ll sense it for sure. I didn’t mean other Certification exams are easy but this one is sitting at the top in complexity comparing to my exposure to other exams I’ve taken till now.</p><p>If you are NOT from a networking background [like me], the learning path is going to be a bit lengthy for sure. You need to be hanging around there with little more patience to get through this complex concepts and knowledge — be aware of it!</p><p>If you are from a Networking background and hold a good hands-on networking industry experience, I think it brings loads of advantage while studying for this exam but if not, I strongly recommend to First study the Networking fundamentals before actually going through the topics of this certification. I’ll guide you through what you can read in my later sections of this blog…I got that covered..so, relax :)</p><p><strong><em>Let’s get to the Learning Path now</em></strong></p><p>If you are following this blog, I already mentioned about the ‘Best Path’ to follow. So., let’s go little deep how to tackle those required learning paths:</p><p>First and foremost, You need to be aware of the Networking Fundamentals. For this, I strongly recommend — <a href="https://www.professormesser.com/network-plus/n10-007/n10-007-training-course/">Professor Messer</a> free course especially targeted for Network+ audience. You don’t need to take up that certification but ensure to go through those videos and get a good head around those fundamental concepts and contexts. Other useful playlist is from <a href="https://www.youtube.com/watch?v=qiQR5rTSshw">FreeCodeCamp.org</a>. Do follow based on your choice and there are few more playlists available over youtube freely on the same topic and deep dive what works for you — Just search for ‘Network+’ and start to consume</p><p>Then, prepare for the Professional Security Engineer content. If you are really serious about taking up that certification, you can find my detailed blog with guidelines <a href="https://brk0018.medium.com/do-you-want-to-know-what-it-takes-to-be-a-certified-gcp-professional-security-engineer-d3f90009f565">here</a></p><p>IT’s now time to actually think about the Network Engineer Certification — First and foremost, read through the amazing documentation prepared by Google Cloud <a href="https://cloud.google.com/certification/cloud-network-engineer?hl=en">here </a>which covers important areas such as ‘Exam Overview’, ‘Exam Guide’ and many other useful sections. This has to be your go-to page to be best aligned with the latest and greatest information all the time for this certification. Do not miss to regularly visit that page.</p><p>Next, Coursera has put up a very decent preparation course for this specialisation and can be referred <a href="https://www.coursera.org/specializations/networking-google-cloud-platform">here</a>. I’m a great fan of Coursera for their awesome content and practical labs through Qwiklabs. Don’t miss it., you’ll be amazed by the Quality of Content for sure!</p><p><a href="https://acloudguru.com/">AcloudGuru</a> is the next choice I recommend. Follow through this <a href="https://learn.acloud.guru/course/gcp-certified-professional-cloud-network-engineer/dashboard">course</a> and ensure to complete Learning Path. It has loads of useful information through videos and practice tests. The course is very well structured and organised in perfect sections aligned to the ‘Exam Guide’ of the Google Cloud Platform which makes things easy for learners to co-relate the topics, the content and the context</p><p>You’ll notice that the Contents of GCP Professional Security Engineer Certification and the Contents of GCP Professional Network Engineer Certification are overlapping with each other to major extent. Hence, the best way to tackle these certs is to first take up the GCP ProSecEngr certification and then aim for the GCP ProNWEngr certification — that way you already have good ground covered to clear the exam with flying colours.</p><p>Apart from these, I suggest you to follow &amp; watch Google Cloud Platform on Youtube. Some of the recommended playlists are below for your reference. There are plenty other freely available videos about Networking from GCP as well to refer as time permits</p><ul><li><a href="https://www.youtube.com/watch?v=cNb7xKyya5c&amp;list=PLIivdWyY5sqJ0oXcnZYqOnuNRsLF9H48u">GCP Networking end-to-end</a></li><li><a href="https://www.youtube.com/watch?v=wmP6SQe5J7g">VPC Deep Dive and Best Practices</a></li><li><a href="https://www.youtube.com/watch?v=b3tBauMiXAs&amp;list=PLPS8Ty7UpM1XhJBLqHXBAL3sqhfsSU-gw">Learn GCP with Mahesh</a></li><li><a href="https://www.youtube.com/watch?v=PGl-P9E5Xdk&amp;list=PLQMsfKRZZviRZJ6epTvt1kOYGy9AYJBz7">Awesome GCP</a></li></ul><p><strong><em>Doing the Practice Tests</em></strong></p><p>Once you have covered the Coursera and AcloudGuru and other Youtube playlists, I think it’s a perfect time to start practising with the sample tests. The first one to hit is the ‘<a href="https://cloud.google.com/certification/sample-questions/cloud-network-engineer?hl=en">Sample Questions</a>’ from GCP under cloud.google.com</p><p>Then to follow with the AcloudGuru Practice Tests. Ensure to achieve 95+% in each of your attempt. And with every test, try to retrospect what questions are going wrong and why ? similarly, It’s a good practice to double ensure the questions you’ve answered correctly to why did you answer them and what was the reason behind it. The more and more practice tests you attempt, the more understanding and clear concepts settle in your brain.</p><p><em>Networking and Security Exam use-case scenarios can be end-less and you’ll sense it as you go deep dive in to those practice tests. So, more practice is better to get your head around the possible scenarios</em></p><p>Always - It’s the best practice to refer to the official <a href="https://cloud.google.com/">cloud.google.com</a> documentation all the time to justify your responses and re-validate those regularly.</p><p>Compared to the GCP ProfSecEngr certification, this certification has the lesser content but they are very deep and complex to understand and to conceptualise. This is the fundamental difference I’ve noticed while my preparation. Primarily, you’ll be tested deep dive in the below areas:</p><ul><li>Load Balancers</li><li>Networking and Network Security</li><li>Hybrid Networking</li><li>Networking Operations and Monitoring</li><li>Kubernetes and Kubernetes Security</li><li>IAM &amp; Resource Management</li><li>Cloud DNS</li><li>Cloud CDN</li></ul><p>Another area to learn is Kubernetes. In order to clear this exam, you must be aware of the Kubernetes fundamentals and Security perspectives of it. The more you know about Kubernetes, the better you’ll be. You’ll be definitely tested with at least 3–5 questions related to Kubernetes, it’s setup, it’s security and IP Ranges etc., In case if you take it easy — risk is yours!</p><p>Along with the above reading, I was also reading to <a href="https://www.linkedin.com/in/ammett/?originalSubdomain=tt">Ammett Williams</a> notes for a quick reference to go through before sitting for the actual exam. I definitely highly recommend it. In case if you are interested, please find the details <a href="https://www.startcloudnow.com/google%20cloud.html">here</a></p><p>Apart from studying and referring to the above, I absolutely followed the <a href="https://brk0018.medium.com/do-you-want-to-know-what-it-takes-to-be-a-certified-gcp-professional-security-engineer-d3f90009f565">same</a> strategy while attempting the exam as I followed for my GCP ProfSecEngr certification exam. It’s working for me and hope it helps you as well.</p><p>Along with those items, I would like to mention couple of more points specific to this certification exam to keep in mind:</p><ul><li><strong><em>Long and lengthy questions</em></strong> — For this certification, be prepared to face the lengthy questions [I faced almost 7–8 long / lengthy context for the questions]. What I recommend is to keep them ‘Flagged for review’ in case if you are unable to tackle them right away. Finish up other questions and come back to them later point to handle. Be mindful of your time-management. It is going to be critical for your success</li><li><strong><em>How much time to prepare </em></strong>— I think this totally depends on your background and experience. Don’t compare with anyone else and build a race unnecessarily, that’s not going help you in anyway. You are the best judge of your situation and plan accordingly</li><li><strong><em>Hit when you are ready from within </em></strong>— I think this is self-explanatory. Have patience and focus for the ultimate end result</li></ul><p><em>That’s all for now. Hope this blog finds you helpful!</em></p><p>While I’m waiting for my official certification, I wish you all the very best!</p><p><strong><em>Thanks for taking time to read!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c188ccc318d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you want to know ‘What it takes to be a Certified GCP Professional Security Engineer ?’]]></title>
            <link>https://brk0018.medium.com/do-you-want-to-know-what-it-takes-to-be-a-certified-gcp-professional-security-engineer-d3f90009f565?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3f90009f565</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[google-cloud-security]]></category>
            <category><![CDATA[cloud-security-services]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[google-cloud]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 06:24:47 GMT</pubDate>
            <atom:updated>2021-06-28T05:41:57.042Z</atom:updated>
            <content:encoded><![CDATA[<h3>What it takes to be a ‘Certified’ GCP Professional Security Engineer ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*LtNI1bz4qXlaHqH8E46H0Q.png" /></figure><p>Hmmmm….Another day and Another &lt;in fact very big&gt; excitement in my journey. This time I just don’t want to express my satisfaction &amp; feelings in words and stop there — Rather also would like to help many aspiring Cloud Engineers with my blog by providing the necessary things / references and give back to the community as much as possible.</p><p>Again, I’m Not the expert on this subject but being a learner and a newbie — I know how much this blog can add value to those who are in the same path or planning to be on the same path in the near future.</p><p>From my view, every information available over the internet in these lines will be useful as long as the user / reader takes out the right context for this Professional Certification. So, feel free to refer to as many other references available online in order to ensure you cover all the grounds possible to attain this Certification under your belt.</p><p><em>Absolutely nothing wrong about studying and preparing for more!</em> You are not going to loose any thing rather I guarantee that you’ll get &amp; gain more understanding and knowledge as you try more, which is a big plus if you are keen to land your feet in to this exciting and most happening domain — Cloud Security — <strong><em>I bet you, it’s worth :)</em></strong></p><p>I just wrote this exam couple of hours ego and the status looks like below. I’m still waiting for the official certification from Google Cloud as its still in the official ‘review process’ but I thought it shouldn’t stop me from sharing my own experiences and learnings I’ve used while preparing for this awesome certification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*-Blf5QcxU-lLO5G6X8ueGQ.png" /></figure><p>Let me take you through what I did and what I recommend. I also would like to share my personal strategy as a recommendation for you guys to follow if that works for you.</p><p>Every one is different and unique. And My views or strategy might not work for you —take it easy and I totally understand and happy to learn from your experiences too if makes sense to me!</p><p>In this blog, I’m not really focusing on what topics [I mean ‘exam guide’] Google Cloud will test your ability for this certification as that can be referred in the official documentation which can be found here — <a href="https://cloud.google.com/certification/cloud-security-engineer">https://cloud.google.com/certification/cloud-security-engineer</a> and do NOT want to duplicate the same. Rather referencing that official website is more logical and authentic at any given point of time. So, I suggest — Please always refer to the official <a href="https://cloud.google.com/">cloud.google.com</a> page for the latest information and changes</p><p>As you understand the Exam Guide and you know what is expected out of this preparation, the next best First Step is to go through and learn from <strong>Coursera</strong> — <a href="https://www.coursera.org/professional-certificates/google-cloud-security">Security in Google Cloud Platform Specialisation</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*g8PG8KGS3K5JoiKZUWHetQ.png" /></figure><p>As shown, it has got amazing 7 modules which will help you to walk through and learn most of the aspects for this specialisation</p><p>As a bonus, it also comes with some awesome Qwiklabs to make your hands dirty for the right balance between the concepts to the console</p><p><em>— Don’t miss it. I promise, you’ll nJoy the Quality of Content!</em></p><p>After playing around with Coursera, it’s time to jump on to <strong><em>Linux Academy</em></strong>, now it is <a href="https://acloudguru.com/"><strong>AcloudGuru</strong></a> though and register for ‘Google Cloud Certified Professional Cloud Security Engineer’ course</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*Aws3s66Jq5EgiiUZMexqCQ.png" /></figure><p>This course is full of content and context. You will be made to walk through each of the GCP Services and brings ‘Security’ in to the context for each of those as you go through the modules</p><p>I’m really impressed with the way this course is structured and organised in bits-and-pieces to sufficiently make you aware of the Security perspectives</p><p>As you are going through the above courses, you’ll be exposed to the official Google Cloud Platform documentation. I recommend to read as much as possible to ensure you get the correct understanding and attention to detail while noting down your points about the Services, Security and Best Practices.</p><p>Remember — at the end of the day, it boils down to the ‘Best Practices’ and ‘Google’s Recommended’ ways of doing in order to attain the Best Security posture for all the applicable Cloud Services. As long as you keep that perspective and ensure to follow them for the real use-case scenarios, I say you are on the right track.</p><p>Without Networking Security, achieving Security overall is a myth and this is true for anyone who is preparing for the Security certification. Please prepare to go through the ‘Professional Cloud Network Engineer’ course under ACloudGuru as it goes deep dive in to the Networking Services which truely is a must to understand concept to be a Security Engineer</p><p>Once you are done with Coursera and ACloudGuru and You think, you can test your brain — that’s when is the right for you to check your knowledge through a practice test. Refer to <a href="https://cloud.google.com/certification/sample-questions/cloud-security-engineer">GCP PSE Sample Test</a>. This is a free test and unlimited times with 23 questions set. It repeats the same questions though but a great way to practice and repeat for overall topics coverage.</p><p>What I recommend is — do NOT try to just select the right answer rather try the technique to eliminate every wrong answer and be very clear why those answers are wrong. If you follow this strategy, you will not just ensure you are correct but you’ll end up gain more understanding about other possible use-case scenarios for each of those topics. While you are checking to eliminate the wrong answers, you can try to come up with what services can be fitted to those scenarios as well if applicable</p><p>I recommend to practice more frequently and try to spend more time based on the gaps you identify for a thorough understanding. Definitely a great way to introspect your knowledge across the topics for sure.</p><p>For any services or scenarios, if you are unable to justify — the best way is to ‘re-read’ the question and ‘re-align’ the Best Practices and/or Google’s Recommended ways and you’ll be able to join the dots much clearly now with more confidence with the concept and the context as well</p><p>In alignment to the above mentioned <a href="https://cloud.google.com/certification/guides/cloud-security-engineer">official exam guide</a>, I suggest you to refer and get a good understanding for the below items. This not only helps you to give a great insight but gives you an awesome understanding about how Security works on GCP and how it has been implemented within and across the layers</p><ul><li><a href="https://cloud.google.com/security/overview/whitepaper">Google Cloud Security White-paper</a></li><li><a href="https://cloud.google.com/beyondcorp">BeyondCorp Research papers</a> — I highly recommend as these papers help you to keep your thought process from Security perspective. This is not just for the Certification exam perspective but it moulds you to be a ‘Security’ mind</li><li><a href="https://cloud.google.com/kms/docs">Cloud KMS</a> — Ensure to breathe this. Google will try every aspect to confuse you during the exam. And if you are unclear, it’s easy for you to get lost and loose your control. So, ensure you really understand CSEK, CMEK and DEK, KEK and how actually it boils down across the levels</li><li><a href="https://cloud.google.com/security/encryption/default-encryption">Encryption at Rest</a> and <a href="https://cloud.google.com/security/encryption-in-transit">Encryption in Transit</a> — No need to special mention about the importance of these topics. Please spend as much time as possible to understand thoroughly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*liuu2654GDn4juIcICZKuQ.png" /></figure><ul><li><a href="https://cloud.google.com/armor/docs">Cloud Armor</a> — The more you spend time on to this, the better. I suggest you cover every aspect about this service in the documentation.</li><li><a href="https://cloud.google.com/iap">Cloud IAP</a> — Ensure you understand why, where and when to use this. You’ll be thrown in to many use-case scenarios for sure in the exam.</li><li><a href="https://cloud.google.com/dlp">Cloud DLP</a> — Just imagine in how many ways it can help for a better Security. A sure topic which attracts at least multiple scenarios. So, be clear with it</li><li><a href="https://cloud.google.com/security-command-center">Security Command Center</a> and <a href="https://cloud.google.com/security-command-center/docs/concepts-web-security-scanner-overview">Web Security Scanner</a> — These topics in general are very straight forward unless otherwise you are in confusion. So, take time to qualify for the quality</li><li><a href="https://cloud.google.com/blog/products/identity-security/protecting-your-gcp-infrastructure-at-scale-with-forseti-config-validator">Forseti Security</a> — To be frank, I didn’t expect to face many scenarios on this topic but Google really tested all ways for use cases. I recommend, you to read through the official documentation thoroughly to be able to cover all the corner case situations. Mostly, they are straight forward and if you are good with the concepts — easy way to get more ‘pass %’ :)</li><li><a href="https://cloud.google.com/access-context-manager/docs">Access Context Manager</a> — If you know the ‘Why and When’, then you are definitely in a good position</li><li><a href="https://cloud.google.com/security/compliance">Compliance</a> — I just got one question but I think easiest topic to gain more ticks. So., I leave it to you to decide how much time you want to spend.</li><li><a href="https://cloud.google.com/products/networking">Networking Services</a> — This is one of the heaviest topic in ‘Security’ and we all know why. So, the more deeper understanding you’ve on to this topic — the better possibilities of clearing the exam with flying colours. Ensure to cover Cloud VPC, VPC Peering, Shared VPC, Cloud Interconnect [Dedicated &amp; Partner] and Firewalls another great topic. As you can imagine, hell lot of possible scenarios can be created — be prepared to face it with a smile :)</li><li><a href="https://cloud.google.com/load-balancing">Cloud Load Balancing</a> — Similar to the Networking Services, the more you prepare and deep understand, the more you can smile ;)</li><li>Identity Services — It’s a mix of <a href="https://cloud.google.com/resource-manager">Resource Manger</a>, <a href="https://cloud.google.com/iam">IAM</a> and <a href="https://cloud.google.com/identity">Cloud Identity</a>. Be prepared to face about <a href="https://cloud.google.com/community/tutorials/gcds-use-cases-common-and-complex">GCDS</a> and use cases too</li><li>Compute Services — Be thorough with <a href="https://cloud.google.com/products/compute">Compute Engine</a> and <a href="https://cloud.google.com/kubernetes-engine">GKE</a> best practices. Spend good time to understand about GCE Security and GKE Security concepts as well</li><li>Storage Services — Be prepared to understand <a href="https://cloud.google.com/storage">Cloud Storage</a> and Security best practices. Many use cases and scenarios possible to be explored like ACLs, Signed URLs, Bucket Lock and different data encryption techniques</li><li><a href="https://cloud.google.com/monitoring">Monitoring</a> — Be thorough with Logging, Monitoring and Alerting mechanisms and how logs can be integrated to the external providers</li><li><a href="https://cloud.google.com/dns">Cloud DNS</a> — be clear with Cloud DNS and DNSSEC</li><li><a href="https://cloud.google.com/security/encryption-in-transit/application-layer-transport-security">Application Layer Transport Security</a></li><li><a href="https://cloud.google.com/blog/products/containers-kubernetes/exploring-container-security-the-shared-responsibility-model-in-gke-container-security-shared-responsibility-model-gke">Shared Responsibility Model</a> — I say easy topic to get more smiles on the table provided you understand it. Definitely, have a read through and keep this in mind with use cases. Google can trick you easily if you missed the context about IaaS, PaaS or SaaS</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*xzlVBFvwRpgNnFoFwsbPqQ.png" /></figure><p>Apart from these, I’ve some awesome YouTube playlists too for you to digest. Listed very few here and there are loads of GCP Video content to soak. Just go for it based on your patience :)</p><ul><li><a href="https://www.youtube.com/watch?v=cNb7xKyya5c&amp;list=PLIivdWyY5sqJ0oXcnZYqOnuNRsLF9H48u">GCP Networking End-to-End</a></li><li><a href="https://www.youtube.com/watch?v=wmP6SQe5J7g">VPC Deep Dive and Best Practices</a></li><li><a href="https://www.youtube.com/watch?v=StJ1NOQjAjo">GCP Encryption of Data</a></li><li><a href="https://www.youtube.com/watch?v=X-rSMkKqyt4&amp;list=PLxQzKf1gjjCPqkPeX0pJqI9lp2Ifyy1oW&amp;index=13">GCP Kubernetes Security</a></li><li><a href="https://www.youtube.com/watch?v=TpJr8qKhbhY&amp;list=PLxQzKf1gjjCPqkPeX0pJqI9lp2Ifyy1oW&amp;index=10">GCE Security</a></li><li><a href="https://www.youtube.com/watch?v=ZQHoC0cR6Qw">Best Practices GCP Security</a></li></ul><p>As you get more stronger with your concepts and topics —Now, is the best time to go for the Practice Tests with ACloudGuru — Do these practice tests as many times as possible.</p><p>Again, I’m re-iterating here. Do NOT focus on the scope rather focus on understanding of each question and eliminating the wrong answer first. My suggestion, the more you are able to eliminate the wrong answers, the more possibilities of you knowing the concepts and techniques thoroughly. It doesn’t matter if you just score 30% or 40% at your first attempt — The Question to ask yourself is ‘Are you really damn good with those 30 or 40% concepts ?’. If not, you might end up missing and making them wrong in your next attempt</p><p>Now is the time to read, re-read, practice and re-practice.</p><p>If you ask me, I have done almost 8–10 times of these practice tests with ACloudGuru until I got like 98–100% of my every attempt and I think that’s when you know that you got the stuff about GCP Cloud Security &lt;to some extent OK :) — it’s a big ocean to be known ;)&gt;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*pO8EI8gL9tCjhRXui3M-Nw.png" /><figcaption>ACloudGuru GCP PSE Practice Test Scores</figcaption></figure><p>Once you able to achieve 90+% in every your attempt, definitely you’ll have your inner feeling telling you that it’s time to hit the real exam. Just Go for it!</p><p>Again, Please do NOT take me wrong here — Getting 90% or even 100% in practice tests with NOT only ACloudGuru or any other&lt;including Google Cloud’s practice test&gt; doesn’t guarantee that You’ll be passing the real test with flying colours in any way. In case someone claims that, please gently ignore with a smile and focus on your learning. What that “%” means is, You are able to identify the right choices given those situations in those practice tests — <em>that’s all — Nothing more, Nothing less!</em></p><p>The Real Official Google Cloud Certification Exam is totally different and it’s a different ball game altogether. Until you face the real exam and see ‘Pass’ from Google Cloud through official confirmation, you are NOT certified ;) — I’m not discouraging here but trying to be open and transparent. It’s better to know the truth than the false promises!</p><p>Some things I followed while attempting the exam:</p><ul><li><em>Do NOT waste time for the tricky questions as you face them — take it with a smile, mark it for a ‘review later’ and move on</em></li><li><em>The moment you are in dilemma with a question and for its correct answer, just mark it for a ‘review later’ and move on — Wasting crucial time is not worth</em></li><li><em>For the questions which you are very clear with your responses, Tick them with the right answers and move on — The more you get these ticks, more time you can save for your ‘review later’ questions</em></li><li><em>Once you reach to the end of the questions, take a deep breathe and attack your ‘review later’ questions.</em></li><li><em>I bet — You’ll be much more comfortable now to respond to those questions as your mind is already fine tuned in to those contexts. Some times while answering other questions, you’ll get a clear picture for some of your ‘review later’ questions…just use it and move on :). This is like a ‘Tube-light’ trick!</em></li><li><em>Utilise rest of the time to attack those unanswered questions. Do follow the earlier strategy mentioned like — If you are not able to figure out the correct answer, Do begin with eliminating the wrong answers. Damn sure, You’ll be able to dissect the correct answer now!</em></li><li><em>If you still have time, better to re-review and utilise the time to the fullest</em></li></ul><p><em>That’s all for now. Hope that simplifies the complexity!</em></p><p>As I’m waiting for my official certification, I wish you all the very best!</p><p>Hope this blog helps you and motivates you to go for the GCP Professional Cloud Security Engineer certification</p><p><strong><em>Thanks for taking time to read!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3f90009f565" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My very Own On-boarding experience with #Kasna / #MantelGroup]]></title>
            <link>https://brk0018.medium.com/my-very-own-on-boarding-experience-with-kasna-mantelgroup-86077060f8c3?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/86077060f8c3</guid>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Fri, 11 Jun 2021 11:51:44 GMT</pubDate>
            <atom:updated>2021-06-12T00:41:12.874Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hcOLKmbYx_lVSr3ldPA0yg.jpeg" /></figure><p>Wow…Wow…Wow and just Wow :) — Does it sound familiar ? I think NOT just ‘familiar’ but ‘exceptional feeling’ right ?</p><p>Yeah, I know — Sometimes, it’s hard to find words in the dictionary which can really ‘match’ to express our feelings and I’m in that situation now for a very good reason!</p><p>Yeah…You got it right — You guessed it. I’m on Cloud9s at the moment and I might take more time to come back on to the ground. Hopefully, this long weekend [due to Queen’s birthday] might help me to calm down and settle down mentally and physically as I spend more quality time with my family ;)</p><p>I thought of taking a complete break from the digital world [I mean staying away from the computer] but the excitement NOT letting me. So, I thought it’s a good time for me to capture my experience in writing as close to the reality as possible.</p><p>Hence, here I’m with another blog where I wanted to narrate my very first week journey #Kasna #TheMantelGroup where I’ll try to put my emotions translate in to words</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e88CiS86IX_JCGzPrtfIEA.png" /></figure><p>First and Foremost, I’m very happy to myself [there are ‘many well wishers and supporters’ who deserve more credits than me in this case but I’m happy to start with me as I triggered this thought process ;)] that I took this strange rather bold decision to break from my old-career path [very much comfort zone] to the very new [from my perspective] Cloud [Sec] Engineering Space. I know everyone says ‘Age is just a number’ but everyone knows as we grow, it’s not that easy to change the gears completely and dare to start from almost ‘0’. I’m not exceptional here and I know many have done this very well before me but everyone’s journey is different and everyone has their own story in life to narrate</p><p>As I/we age, I/we know ‘The transition is NOT that easy’ [Don’t take me wrong., the transition is NOT complete yet, as it’s just the beginning and I’m yet to prove myself in this fascinating &amp; fast growing Cloud [Sec] Engineering space] but to me landing in to the ‘Cloud Engineering role’ is like ‘half-job’ done and rest half is ‘To focus, learn, contribute, grow and REPEAT’ and this is where the importance of ‘association’ comes in to the picture and that’s where I’m really fascinated to express my experience as a kick-starting journey. On a personal side note, I’m trying to compete with my 13-year old son in leaning…he is eyeing in to Ethical Hacking now a days :) — <a href="https://nayanballa.me/">https://nayanballa.me/</a>— hope he continues his learning journey</p><p>I started my adventure with <a href="https://kasna.com.au/">Kasna</a> / <a href="https://medium.com/u/22d86eb73179">Mantel Group</a> on 7 June and I heard &amp; I know about them from the very social media that they are recently ranked as the Great Place to Work in Australia — <a href="https://mantelgroup.com.au/great-place-to-work/">https://mantelgroup.com.au/great-place-to-work/</a> which is one of the drive for my decision and along with this credibility, <a href="https://kasna.com.au/">Kasna</a> has been the Prime partner of Google Cloud in Australia is another Big &amp; Prime motivation for me to grab that opportunity with both open-hands ignoring the other offers/benefits at this moment</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dcK7aQPPDv77e1G84h3wgQ.jpeg" /></figure><p>I’ve been dreaming to join <a href="https://kasna.com.au/">Kasna</a> for a good time but I was not ready as I was learning and up-skilling myself in to the GCP space to be eligible to start applying for the roles / opportunities. Finally after a good journey of learning, I’m now here as a ‘<strong>Kasnian</strong>’ and it’s been a week! Compared to rest of the Amazing Kasnians, I’m a newbie in to this space and lot to learn from each of them every day going forward!</p><p>Somehow, from the day I received a call from <a href="https://medium.com/u/7258b821e347">Gökhan (Eli) Gündüz</a> about the opportunity and through the days I’d discussions with Jan V, Kai C followed by Simon P and Michael B for the final outcome — all just happened like a magic flow and within a very short span of time. From the very discussions I had with them, it is/was very clear to me as I started sensing the strong culture and people focused mindset and approach. Everyone of them made me very comfortable during the discussions and somehow I already felt like part of the team from the day-1 of the chats. All of these Five Maestros, made a huge impression already to be the prime drive for my decision. But you know, NO matter how much I made comfortable by them, I always had that extra curiosity to think how it will be in reality once I land.</p><p>But, after spending my very first week— I can firmly say that the teams and the people live by the [Five] principles they defined as part of the culture. Not even for a single moment I felt that we are going away from those from the ground-up or top-down. Is in’t that Just amazing ? Isn’t that Just Wow…Wow….and…Wow :) — Yeah, I know!</p><p>Unfortunately, I’d to do virtual on-boarding due to covid situation in Victoria but Eli G &amp; ‘P and C’ group again ensured all is settled very well ahead of my joining date in fact., I’d received all the items necessary to rock-and-roll almost a week ahead :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0UVE_Fw1rozhQhnKVOCyIg.jpeg" /></figure><p>As I’m in to the new radar, I was aiming to go to office at least for couple of days a week so that I can learn more from the team being in-person as it makes a bit easy for me to interact and get going smoothly. But, You know destiny always has different plans I guess [generally, nothing comes easily to me, I know everyone feels the same :)] — so, ended up being remote 100%. That’s where I was/am a bit stressed to see how I’ll be able to cope up and align to the team/s and members across the group</p><p>This is where It made a huge difference in a positive way from my views to the reality. I was thinking it’ll be really difficult for me but the team and the members made me very comfortable by checking with me on a regular basis and ensured that all-is-well and reachable to me at any point of time</p><p>During this time, I tried to interact and build my network within the team as much as possible [of course, I’m yet to interact with many more awesome and amazing colleagues → on going approach for the next couple of weeks :) and it’s a continuous movement from my end] and to my surprise, every interaction I’d and every discussion I’d gone through — it’s just mind blowing to see their helping hand and supportive nature. Everyone is very humble, respective and open-minded to help you in all possible means</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*LaZKZSBEzxOz2hDhsdU2mA.png" /></figure><p>From my experience, Everyone of them successfully demonstrated the culture to the fullest possible throughout their interactions. Everyone understands ‘The journey of transition’ and what it takes to land in to this fascinating engineering space from a different profile and each of them have demonstrated an amazing ‘<strong><em>In it together</em></strong>’ attitude throughout their communication and also ‘<strong><em>Love what you do &amp; be awesome at it</em></strong>’ approach very clearly and intensively — it appeared to me that the culture is/has been flowing throughout the team/s effortlessly. Kudos to the Senior Leadership team for leading from front in demonstrating the culture from the top-down and bottom-up!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*uOc8GyfG-WNaKERi_Yq-zg.png" /></figure><p>Fortunately, I’d an opportunity to meet &amp; interact with the Senior Leadership team [Simon P, Trogo B and Lincoln E] as well within my very first week and What to say — They made me feel comfortable and confident [It’s good that I already had an opportunity to meet &amp; discuss with one of them as part of the interviewing process]. This catchup, truly generated lot of positive vibes in me and gave me the trust and confidence to move forward in the positive direction! It was direct, friendly, simple but effective too — Personally, What I learnt from this interaction is to always keep an eye to ‘<strong><em>Make Good Choices</em></strong>’ and ‘<strong><em>Make Things Better</em></strong>’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*-nkI1F4rmjfFxotimMCYNg.png" /></figure><p>I proudly say that the 5th principle ‘<strong><em>Communicate Directly</em></strong>’ is one of the best demonstration I’ve seen across the group all the times without any hidden facts. All the necessary information is easily accessible and available to everyone and absolutely there is NO indirect communication. Everyone takes pride in communicating directly and openly as this is ‘<em>Central to everything we do</em>’ atmosphere. The team is very flat in structure and the hierarchy doesn’t come in to the picture as long as we are very much clear about the purpose and the objective and working for the betterments</p><p>I can go on-and-on but the bottom line is to say that I’m feeling happy and humble at the same time. And full credit goes to my fellow-Kasnians, Eli G and the P&amp;C team for their warm welcome</p><p>Long way to go from here and Lot to learn for me to soak from each one of you…Let me continue this amazing journey officially with Google Cloud Platform through #Kasna / #MantelGroup!</p><p><em>Thanks for taking time to read!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86077060f8c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Un-structured Data Security — GCP is ‘The Highest Rated’ Leader as of now]]></title>
            <link>https://brk0018.medium.com/un-structured-data-security-gcp-is-the-highest-rated-leader-as-of-now-16c12a4389cb?source=rss-54dc4c95930f------2</link>
            <guid isPermaLink="false">https://medium.com/p/16c12a4389cb</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[cloud-security-services]]></category>
            <category><![CDATA[google-cloud-service]]></category>
            <category><![CDATA[google-cloud-security]]></category>
            <category><![CDATA[data-security]]></category>
            <dc:creator><![CDATA[BRK0018]]></dc:creator>
            <pubDate>Mon, 31 May 2021 07:35:01 GMT</pubDate>
            <atom:updated>2021-05-31T07:35:01.318Z</atom:updated>
            <content:encoded><![CDATA[<h3>Un-structured Data Security — GCP is ‘The Highest Rated’ Leader as of now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*DaMYsyP1PvlOZIxgFWlyAA.jpeg" /></figure><p>As per ‘<strong>The Forrester Wave: Un-structured Data Security Platforms — Q2 2021</strong>&quot; research, <strong><em>Google Cloud is offering a First-class cloud data security platform </em></strong>that enables customers to balance security controls and business needs</p><p>The Reports notes that “<strong>T<em>oday, there is a steady march toward truly integrated single platform offering</em></strong>”</p><p>As I came across this report as part of my self exploration about the ‘Cloud Security’, this drew my attention. As this is not only interesting but a good brainer, I really wanted to understand the reasons behind that big and bold research statement — And as I started reading and making some of my own notes, thought it’s a good idea to capture it over a blog for a wider audience readability and sharing. Here I’m with another small contribution to the community from my end</p><p>For this research, ‘<strong>The Forrester Wave</strong>’ looked in to <em>26 different criteria&#39;s to evaluate the Unstructured Data Security of the different platform providers and identified 11 most significant ones</em> as — Broadcom, Digital Guardian, Forcepoint, Google, GTB Technologies, McAfee, Micro Focus, Microsoft, Proofpoint and Varonis — researched, analysed and scored them. The overall report shows how each provider measures up and helps security and risk professionals select the right one for their needs</p><p>Most of the organisations across the globe are expanding [or in the phase of expansion strategies] their use of the cloud services and as they are expanding, most of their sensitive data [unavoidably] moves to and lives in the cloud. These organisations use AI-driven business insights with the help of this data as it powers/helps the organisations to move ahead. Much of this sensitive data is in unstructured format and this is very challenging in most of the cases to manage and secure. We are already discussing too much about the unstructured data, Let’s understand it first:</p><p><strong>What is Un-structured Data ? </strong>— I tried to dissect to illustrate the difference between ‘The Structured Data’ and The ‘Un-structured Data’ in the below Fig-1. I believe this is simple and self-explanatory as well</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIe9E-fAbgxY-FaiIWWNQQ.png" /><figcaption>Fig-1: Structured vs Un-structured Data in a nut-shell</figcaption></figure><p><strong>A Data Security Platform — </strong>To deliver on to this strategy, Google Cloud is offering comprehensive data security features engineered in to the platform. Strong security defaults are complemented by tools and capabilities that enable customers to manage security for structured and un-structured data:</p><ul><li>Discovery and Governance tools which help customers manage and protect sensitive data flows across the organisation</li><li>Controls enable policies to be implemented and enforced, including customer-managed and external key management, data masking and tokenisation, and confidential computing for data in-use</li><li>Analytics enable customers to review data usage and identify potential malicious activity</li><li>Comprehensive audit logging</li><li>All of the services are fully managed solutions available for Console UI and full-featured APIs</li></ul><p><strong>Focus On Discovery, Classification and Obfuscation —</strong> One of the critical thing for protecting the unstructured data is to identify [discovery] of the sensitive data then to Classify it and Finally Obfuscate the same</p><ul><li>DLP platform enables the discovery and classification of the data in real-time, on-demand, continuously and also in event-driven workloads</li><li>Obfuscation can help protect the sensitive data like PII [Personal Identifiable Information] which is critical to many enterprise workflows. Cloud DLP helps to inspect and mast this data with techniques like redaction, bucketing, and tokenisation, which help to strike the balance between the risk and utility — this is especially crucial when dealing with the unstructured or free-text workloads. Google Cloud supports 150+ detectors to mask which can be deployed in data migrations and business workloads like real-time data collection and processing</li></ul><p><strong>Innovating For The Future — </strong>Google Cloud’s approach to innovation in data security is productisation of capabilities developed are successfully used for Google’s own use as well as customer control requirements. Some of the Uniqueness is highlighted below</p><ul><li><a href="https://cloud.google.com/security/encryption/default-encryption/">Encryption-at-rest </a>— Google was the very first cloud provider to make this as default and a Global Key Management services with customer control</li><li>Encryption protection for data-in-use — Huge research and investment focused on critical areas that further enhance the data security such as Confidential Computing. Many more such like VPC Service Controls [which provide perimeter controls to prevent data exfiltration]</li><li><a href="https://cloud.google.com/access-transparency">Access Transparency</a> — First of it’s kind cloud service which allows cloud users to audit provider [CSP’s] access to their [Cloud User’s] data just as they do on-premises</li><li>The <a href="https://cloud.google.com/beyondcorp">BeyondCorp</a> security model — A new approach to Enterprise Security to access control based on a user’s identity and context rather than a Perimeter based security — protected profile for ‘Zero Trust Access’</li></ul><p><em>After researching, analyzing, and scoring “the providers that matter most” Forrester Research named Google Cloud a Leader in The Forrester Wave™ Unstructured Data Security Platforms, Q2 2021 report, and rated </em><strong><em>Google Cloud highest overall</em></strong><em> in the current offering category among the providers evaluated.</em></p><p>The evaluation outcome looks like below as on Q2 2021</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*2DWHVOvqFZJ_nnWQTeOdNQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*ixb0bVzodBrC18TybrmnVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*lspVxBOuET8kyWAA-LoU8g.png" /></figure><p>In summary, this is what is captured about Google:</p><ul><li><em>Google offers breadth and depth with built-in data security in the cloud.</em></li><li><em>Google Cloud Platform, Google Workspace, and BeyondCorp Enterprise have underlying data security products and features for protecting customer data.</em></li><li><em>Google productises capabilities originally developed to secure its own business and brings a disciplined approach to product enhancements for enterprise requirements. It serves a wide range of enterprise and mid-market clients, with a focus on emphasising data protection needs by industry.</em></li><li><em>Google further enables a Zero Trust approach with third-party integrations through its BeyondCorp Alliance of partners in device management, endpoint security, and gateways.</em></li><li><em>It takes a broad view of DLP, which includes in-line redaction of sensitive elements in unstructured data and DLP APIs that extend support to additional data types like images or other media.</em></li><li><em>Customer references noted Google’s ease of use, despite the multiple user interfaces and consoles to navigate.</em></li><li><em>Customers identified its data security capabilities as feeling siloed and desired more integration across the Google ecosystem; they also wanted greater insights into where data security concerns exist and risk analysis capabilities.</em></li><li><em>Security buyers whose organisations use Google should strongly consider looking at the variety of built-in capabilities available to them</em></li></ul><p>References used:</p><p><a href="https://cloud.google.com/">Google Cloud Platform</a> — Documentation</p><p><a href="https://cloud.google.com/beyondcorp">BeyondCorp</a> — Documentation</p><p>Each topic in a nut-shell mentioned in this blog can be a big subject to explore and elaborate which is not the intention behind this blog. Hence, leaving the context limiting to the topic highlighted. If you are motivated to know more, feel free to refer to the links provided and drill to the deepest level possible.</p><p>That’s all for now —<strong><em> Stay safe and Thanks for taking time to read!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16c12a4389cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>