<?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 Arsh on Medium]]></title>
        <description><![CDATA[Stories by Arsh on Medium]]></description>
        <link>https://medium.com/@arsh987?source=rss-d2b43485a0c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6R0FRCoAWZLBfcwakV_2Ow.jpeg</url>
            <title>Stories by Arsh on Medium</title>
            <link>https://medium.com/@arsh987?source=rss-d2b43485a0c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:25:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arsh987/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[Chronicle SIEM]]></title>
            <link>https://medium.com/@arsh987/chronicle-siem-bc08e3155927?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc08e3155927</guid>
            <category><![CDATA[chronicle-siem]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Mon, 09 Oct 2023 17:01:56 GMT</pubDate>
            <atom:updated>2023-10-09T17:01:56.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lo8lOnQTomT3uCDasazZEQ.jpeg" /></figure><p>Chronicle SIEM is a cloud-native Security Information and Event Management (SIEM) solution that helps security teams detect, investigate, and respond to threats faster and more effectively. It offers several key features, including:</p><ul><li>Cloud-scale ingestion and analysis: Chronicle SIEM can ingest and analyze petabytes of security telemetry data from a wide range of sources, including on-premises, cloud, and hybrid environments.</li><li>Advanced detection capabilities: Chronicle SIEM includes a library of predefined detection rules based on the MITRE ATT&amp;CK framework and the ability to create custom rules using YARA-L.</li><li>Threat hunting: Chronicle SIEM provides security analysts with powerful tools to search and investigate threats across their data sets.</li></ul><p>Chronicle consists of the following key components:</p><ul><li>Data ingestion</li><li>Search</li><li>Dashboarding</li><li>Rules</li><li>Entity Graph</li><li>Parsing</li></ul><p>We will discuss these components one by one.</p><h3><strong>Data ingestion:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TYFFU8Q6ordzgvy1" /></figure><ul><li>Flow and Processing of Customer Security Data to Chronicle</li><li>Chronicle processes customer security data as follows:</li><li>An internal data forwarding service (such as Chronicle Forwarder) or a standard secure protocol (such as SFTP) sends raw security data directly to Chronicle. The security data is encrypted while in transit to Chronicle.</li><li>Chronicle retrieves security data stored in a cloud service (such as Amazon S3 or Google Cloud). The data is encrypted while in transit to Chronicle.</li><li>Chronicle logically segregates and stores your security data into your account in an encrypted form. Data is accessed by the customer only, plus a limited number of Google personnel as necessary to support, develop, and maintain the product.</li><li>Chronicle parses and validates the raw security data, making data easier to process and display.</li><li>Chronicle indexes the data to make it easier to search.</li><li>After it is validated and parsed, Chronicle checks the security data against third-party feeds (such as the DHS threat feed) and Chronicle’s internal threat analytics tools and systems.</li><li>Chronicle stores parsed and indexed data in an encrypted form within each account.</li><li>You log into your account to search and review your security data.</li><li>Chronicle searches for matches between your security data and the VirusTotal malware database. In a Chronicle event view, such as Asset view, click <a href="https://cloud.google.com/chronicle/docs/investigation/view-virustotal-information">VT Context</a> to display information from VirusTotal. Your security data is never shared with VirusTotal.</li></ul><h4><strong>Best Practices on Data ingestion</strong></h4><ul><li>Use<a href="https://cloud.google.com/chronicle/docs/ingestion/cloud/ingest-azure-activity-logs"> collection methods</a> and log formats recommended by Chronicle for common log sources (avoids parsing issues down the line)</li><li>NXlog is recommended for Windows log collection</li><li>Cribl works really well with Chronicle. There are some gotchas with forwarding of large logs.</li><li>SaaS sources that are not supported can be ingested using GCS/S3 or via<a href="https://cloud.google.com/chronicle/docs/ingestion/ingest-using-cloud-functions"> custom ingestion scripts</a> deployed as cloud functions</li><li>User and Asset Context data should ideally be ingested directly from the source as UDM entities (instead of some intermediate process or CSVs)</li><li>Some use cases like multi-column reference lists, IOC ingestion, nested/chained rules, advanced analytics and orchestration (rule output), etc are not well documented and may require some custom development</li></ul><h4><strong>Data Ingestion Examples:</strong></h4><ol><li><a href="https://cloud.google.com/chronicle/docs/install/forwarder-linux">Chronicle Forwarder for LINUX and Windows</a></li><li><a href="https://cloud.google.com/chronicle/docs/install/docker-forwarder-windows">Docker Forwarder windows</a></li><li>Setup <a href="https://cloud.google.com/chronicle/docs/administration/feed-management">Data feeds</a> ( for example if you need to ingest data from S3 or Cloud Storage, there are a number of endpoints available.</li><li><a href="https://cloud.google.com/chronicle/docs/ingestion/cloud/ingest-gcp-logs">Ingest Google Cloud Data to Chronicle</a></li></ol><h4><strong>Search:</strong></h4><p>The<a href="https://cloud.google.com/chronicle/docs/investigation/udm-search"> UDM search</a> function enables you to find Unified Data Model (UDM) events and alerts within your Chronicle instance. UDM search includes a variety of search options, enabling you to navigate through your UDM data. You can search both for individual UDM events and groups of UDM events tied to shared search terms.</p><p>Searching for data: To access Chronicle UDM Search, select UDM Search from the application menu on the Chronicle landing page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U2na1skwRrR6ZYGp" /></figure><h4><strong>Dashboarding</strong>:</h4><p>Monitor Data ingestion<a href="https://cloud.google.com/chronicle/docs/investigation/dashboards-user-guide"> Chronicle Dashboard</a>: Chronicle provides a set of default dashboards for analysis and reporting within the Chronicle user interface. Reporting is available by converting a dashboard to a shareable file (for example, PDF, Excel, CSV, etc.). These dashboards are built upon the capabilities of Looker:<a href="https://cloud.google.com/looker"> https://cloud.google.com/looker</a> and BigQuery:<a href="https://cloud.google.com/bigquery"> https://cloud.google.com/bigquery</a> (both Google Cloud products). Looker acts as a <a href="https://chronicle.security/blog/posts/introducing-brand-new-visualizations-in-chronicle/">visualization layer</a> while BigQuery acts as a data layer.</p><h4><strong>Rules:</strong></h4><p>The rules engine is a fundamental component of <a href="https://chronicle.security/">Chronicle</a>. Ingesting and searching data is important, but if you cannot generate detection events, analysts are left with petabytes of data to search through without a specific focus or prioritization.</p><p>The rules engine in Chronicle uses a language called <a href="https://cloud.google.com/chronicle/docs/detection/yara-l-2-0-overview">YARA-L</a> to build detections. For those not familiar with <a href="https://support.virustotal.com/hc/en-us/articles/115002178945-YARA">YARA</a>, it is the language that Google’s <a href="https://cloud.google.com/chronicle/docs/preview/vt-context">VirusTotal</a> team developed for use with malware samples</p><p>The three required sections of any YARA-L rule are the meta, events, and condition sections.</p><ul><li><strong>Meta</strong> contains the metadata associated with the rule itself.</li><li><strong>Events</strong> contain the UDM fields and their associated values that are being evaluated to determine if criteria exist for the rule to fire.</li><li><strong>Condition</strong> specifies the circumstances that would cause the rule to fire</li></ul><p>Detection rules samples.<a href="https://github.com/chronicle/detection-rules"> https://github.com/chronicle/detection-rules</a></p><p>If you are keen to learn more about YARA-L, Check out this <a href="https://go.chronicle.security/hubfs/YARA-L%20Overview%20White%20Paper.pdf?_gl=1*184o83t*_ga*MTA0MzQyNzY1My4xNjc4ODA2NDQw*_ga_C15JQND72P*MTY4NTYyOTQxOC4xMC4xLjE2ODU2Mjk2MjQuMC4wLjA.">whitepaper</a></p><h4><strong>Entity Graph</strong>(aka Rules Engine):</h4><p>Chronicle graph is a relational entity graph that can make use of joining UDM event data with <a href="https://cloud.google.com/chronicle/docs/event-processing/data-enrichment">context-enriched data</a> and supports relational models too — e.g., entity user X owns entity asset Y that has access to entity resource Z (a database, firewall, storage bucket, etc.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/0*0bJeL79xPerK-ndQ" /></figure><h4><a href="https://cloud.google.com/chronicle/docs/preview/parser-extensions/parsing-overview"><strong>Parsing:</strong></a></h4><p>In general, customers send data as original raw logs. Chronicle uniquely identifies the device that generated the logs using the LogType. The LogType identifies both. the vendor and device that generated the log, such as Cisco Firewall, Linux DHCP Server, or Bro DNS which parser converts the raw log to a structured Unified Data Model (UDM). There is a one-to-one relationship between a parser and a LogType. Each parser converts data received by a single LogType.</p><p>Chronicle provides a set of default parsers that read original raw logs and generate structured UDM records using data in the original raw log. Chronicle maintains these parsers.</p><p>Customers can also define custom data mapping instructions by creating a customer-specific parser. Contact your Chronicle representative for information about creating a customer-specific parser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zQ41o2wsYESfeSz2" /></figure><p>List of <a href="https://cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers">Supported Default Parsers</a></p><p>Next steps to learn:</p><ol><li>C<a href="https://chronicle.security/blog/?filters=new-to-chronicle-series,">heck out this blog series</a></li><li><a href="https://learn.chronicle.security/courses/take/chronicle-siem-fundamentals/texts/35475526-course-overview">https://learn.chronicle.security/courses/take/chronicle-siem-fundamentals/texts/35475526-course-overview</a><a href="https://secopscommunity.com/">https://secopscommunity.com/</a></li></ol><p><strong>Chronicle Essentials:</strong></p><ol><li><a href="https://chrome.google.com/webstore/detail/attck-powered-suit/gfhomppaadldngjnmbefmmiokgefjddd">Chrome extensions</a></li></ol><p>2.<a href="https://github.com/center-for-threat-informed-defense/attack-powered-suit"> ATT&amp;CK Powered Suit</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc08e3155927" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[APIGEE Migration Plan: Transitioning Self-Hosted APIs to APIGEE]]></title>
            <link>https://medium.com/@arsh987/apigee-migration-plan-transitioning-self-hosted-apis-to-apigee-2e3a000428a0?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e3a000428a0</guid>
            <category><![CDATA[apigee]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Mon, 22 May 2023 15:33:31 GMT</pubDate>
            <atom:updated>2023-05-22T15:33:31.607Z</atom:updated>
            <content:encoded><![CDATA[<p>In my initial investigation, I found a valuable <a href="https://www.googlecloudcommunity.com/gc/Cloud-Product-Articles/Migrating-to-Apigee-Reference/ta-p/76016">GCP reference document</a> offering comprehensive insights into the migration process. This document effectively covers various aspects such as functional and non-functional requirements, standard compliance, etc.</p><p><a href="https://github.com/apigee/devrel/tree/main/tools/apigee-sackmesser">Apigee Sackmesser </a>is a collection of tools that provide a unifying experience, and let you deploy API proxies, shared flows, and configuration to both stacks without writing any additional manifest files.</p><p>While there are multiple tools that exist for migrating APIs from different API management platforms to APIGEE, I have not come across a specific migration tool for transferring Self-hosted APIs from Compute Engine to APIGEE X. However, this article provides guidance on the necessary steps you can take to accomplish this migration successfully.</p><h3><strong>Here are a few suggestions:</strong></h3><ul><li>What are the current <strong>API authentication and authorization</strong> mechanisms in place on the existing platform? Let’s explore the potential for transitioning to a new model that enhances security, rather than simply considering a lift-and-shift approach. Whenever there is an opportunity, it’s important to prioritize improving security models. Here is a <a href="https://cloud.google.com/apigee/docs/api-platform/reference/policies/reference-overview-policy">Reference link</a> to the Apigee security policy.</li><li>Perform an assessment of your existing APIs, assign scores to each API, and focus on enhancing their security measures to mitigate any <strong>potential API threats</strong>. By implementing stronger <a href="https://cloud.google.com/apigee/docs/api-platform/security/api-security">security protocols</a>, you can safeguard your APIs from potential vulnerabilities.</li><li>Begin by establishing <strong>basic naming</strong> standards for APIs, policies, and other relevant components. Then, consider identifying key reusable components such as security measures, threat protection mechanisms, logging practices, and error-handling techniques. These components can be incorporated as part of <a href="https://cloud.google.com/apigee/docs/api-platform/fundamentals/shared-flows">shared flows</a>, enabling efficient and consistent implementation across multiple APIs.</li><li>After defining the <strong>essential shared flows, design an optimal template encompassing</strong> all the foundational components. This template should incorporate different policies available for a given proxy, allowing different developers to reuse and share it. Developers can efficiently leverage base components by establishing a comprehensive and reusable template while ensuring consistency across the API development process.</li><li>Implement a <a href="https://cloud.google.com/apigee/docs/api-platform/security/data-masking"><strong>masking</strong></a><strong> or encryption</strong> approach to safeguard sensitive data such as Personally Identifiable Information (PII) and Payment Card Industry (PCI) data.</li><li>Consider <a href="https://medium.com/google-cloud/continuous-integration-with-apigee-and-github-actions-bcba4178925c">CI/CD</a> approach to deploying APIs.</li><li>Explore <a href="https://cloud.google.com/apigee/docs/api-platform/analytics/analytics-services-overview">Analytics</a> will help to improve your APIs through <strong>analytics</strong>.</li><li>Conduct <strong>tuning</strong> exercises to <a href="https://cloud.google.com/apigee/docs/api-platform/analytics/endpoint-performance-dashboard">optimize performance</a> and enhance efficiency.</li></ul><p>Here are some additional helpful links:</p><ul><li><a href="https://cloud.google.com/apigee/docs/support">https://cloud.google.com/apigee/docs/support</a></li><li><a href="https://cloud.google.com/apigee/docs/api-platform/envoy-adapter/v1.4.x/troubleshooting">https://cloud.google.com/apigee/docs/api-platform/envoy-adapter/v1.4.x/troubleshooting</a></li><li><a href="https://github.com/orgs/apigeecs/repositories">https://github.com/orgs/apigeecs/repositories</a></li><li><a href="https://github.com/apigee/devrel">https://github.com/apigee/devrel</a></li><li><a href="https://github.com/telstra/habitat-commissioner">https://github.com/telstra/habitat-commissioner</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e3a000428a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR privacy policy for apps running on Google Cloud]]></title>
            <link>https://medium.com/@arsh987/gdpr-privacy-policy-for-apps-running-on-google-cloud-30cd5f2b9d72?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/30cd5f2b9d72</guid>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Tue, 14 Mar 2023 14:14:30 GMT</pubDate>
            <atom:updated>2023-03-14T14:18:20.902Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*8Niyjyc30q8mGjm7.jpg" /></figure><p>The General Data Protection Regulation (GDPR) is a data privacy law that applies to all businesses operating within the European Union (EU) or processing the personal data of EU citizens.</p><p>If your iOS app collects or processes the personal data of users who are located in the EU, you must comply with the GDPR.</p><blockquote><strong>Here are some key elements that should be included in a GDPR privacy policy for IOS apps:</strong></blockquote><ul><li><strong>You should clearly identify</strong> who is the data controller of the personal data collected by the app and provide their contact details.</li><li><strong>Types of personal data collected</strong>: You should list the types of personal data that your app collects from users. This could include names, email addresses, phone numbers, IP addresses, and other identifying information.</li><li><strong>Purpose and legal basis for processing</strong>: You should explain the purpose for which the personal data is collected and processed, as well as the legal basis for processing the data. For example, the legal basis might be user consent or legitimate interests.</li><li><strong>Recipients of personal data: </strong>You should identify any third parties with whom you share the personal data collected by the app.</li><li><strong>Data retention</strong>: You should explain how long you will retain the personal data collected by the app, and the criteria used to determine how long to retain it.</li><li><strong>User rights</strong>: You should inform users of their rights under the GDPR, such as the right to access their personal data, the right to have their personal data erased, and the right to object to the processing of their personal data.</li><li><strong>Security measures</strong>: You should describe the security measures you have in place to protect the personal data collected by the app.</li><li><strong>Cookies and other tracking technologies</strong>: If your app uses cookies or other tracking technologies, you should explain how they are used and obtain user consent for their use.</li><li><strong>International data transfers</strong>: If you transfer personal data to countries outside the EU, you should explain the safeguards you have in place to ensure that the personal data is protected.</li><li><strong>Changes to the privacy policy</strong>: You should inform users of any changes to the privacy policy and provide a date of the last update</li></ul><blockquote><strong>GDPR privacy policy for IOS apps running on Google Cloud</strong></blockquote><ul><li>Google Cloud is GDPR compliant provided you implement/deploy Google Cloud services correctly. However, your applications and their management of data are not GDPR compliant just because GCP is compliant.</li><li>You must <a href="https://gdpr-info.eu/">implement policies</a> and procedures to attain GDPR compliance and maintain compliance.</li><li><a href="https://appmaster.io/blog/gdpr-ccpa-cookie-law-for-mobile-app">Apps</a> must adhere to applicable laws and have a legitimate privacy policy to be accepted on Google Play and the Apple App Store.</li></ul><blockquote><strong>What are some steps you can take for my app to be GDPR compliant?</strong></blockquote><ul><li><a href="https://learn.microsoft.com/en-us/power-platform/admin/about-gdpr">Assess</a> whether the GDPR applies to your organization and what data under your control is subject to the GDPR.</li><li><a href="https://usercentrics.com/knowledge-hub/check-your-app-for-privacy-compliance/">Run a thorough assessment of the SDKs and third-party trackers running in your solution</a>.</li><li><a href="https://www.mobiloud.com/blog/gdpr-compliant-mobile-app">Show a consent screen on app launch asking users to opt-in to have their data collected or receive communications</a>.</li><li>Collect only necessary data.</li><li><a href="https://www.eiosys.com/how-to-make-app-gdpr-compliant/">Encrypt</a> user data. (to prevent misuse)</li><li>Use a two-factor authentication strategy.</li><li><a href="https://www.eiosys.com/how-to-make-app-gdpr-compliant/">Scrutinize how you handle user&#39;s data</a>.</li></ul><blockquote><strong>How to find out whether your app is GDPR compliant or not?</strong></blockquote><ul><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Find out</a> which law applies to your app.</li><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Perform an audit</a> to know all the mobile SDKs you use in your app and what data these SDKs collect and process.</li><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Inform users</a> of what personal data the SDKs are collecting.</li><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Collect valid</a> consent before collecting data (prior consent).</li><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Make it easy</a> for users to withdraw consent.</li><li><a href="https://cookieinformation.com/resources/blog/is-your-mobile-app-gdpr-compliant/">Store all</a> consents for documentation.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30cd5f2b9d72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Dataflow]]></title>
            <link>https://medium.com/@arsh987/google-cloud-dataflow-c7e218465cfb?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7e218465cfb</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[dataflow]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Thu, 09 Feb 2023 15:30:03 GMT</pubDate>
            <atom:updated>2023-02-09T15:30:03.722Z</atom:updated>
            <content:encoded><![CDATA[<p>Trimming down the cost of running Google Cloud Dataflow Classic</p><p><strong>1. Reducing the Disk size: </strong>By default, the disk size for the dataflow pipeline is set to 250GB for a batch pipeline and 400GB for a streaming pipeline. You can specify disk size as <strong>— diskSizeGb=30</strong></p><p><strong>2. Specifying a custom machine type: — workerMachineType=custom-8–7424 </strong>The value would correspond to 8 cores and 7424 MB of memory and you can tweak this according to your need.</p><p><strong>3. Disabling public IPs:— usePublicIps=false</strong></p><p><strong>4. Keeping your GCP services in the same region:</strong>To set the region while deploying your Dataflow pipeline, you can add the following execution parameter: <strong>— region=us-central</strong></p><p><strong>5. Horizontal scaling: </strong>If you are trying to figure out whether you want to enable auto-scaling or not or want to start without autoscaling: <strong>— autoscalingAlgorithm=NONE — numWorkers=3</strong></p><p><strong>Dataflow Prime:</strong></p><p><a href="https://cloud.google.com/blog/products/data-analytics/simplify-and-automate-data-processing-with-dataflow-prime">Dataflow Prime</a> helps you to customize your resources as needed for each stage of the pipeline, unlike dataflow classic.</p><p>To use Dataflow Prime, you can reuse your existing pipeline code and also enable the Dataflow Prime option either through Cloud Shell or programmatically.</p><p><strong>Dataflow Prime features:</strong></p><p>The following is the list of supported Dataflow Prime features for different kinds of pipelines:</p><ul><li><strong>Vertical Auto Scaling (memory).</strong> Supports streaming pipelines in Python and Java.</li><li><strong>Right Fitting (Dataflow Prime resource hints).</strong> Supports batch pipelines in Python and Java.</li><li><strong>Job Visualizer.</strong> Supports batch pipelines in Python and Java.</li><li><strong>Smart Recommendations.</strong> Supports both streaming and batch pipelines in Python and Java.</li><li><strong>Data Pipelines.</strong> Supports both streaming and batch pipelines in Python and Java.</li></ul><blockquote><strong><em>Below is the comparison between Dataflow Classic and Dataflow Prime</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/0*hA1Dv-7pPxUbB3KB" /></figure><p><strong>Use the following links to get more information on Dataflow which will help you Benchmark Dataflow jobs for cost, performance, and Capacity planning.</strong></p><p><a href="https://cloud.google.com/blog/products/data-analytics/simplify-and-automate-data-processing-with-dataflow-prime">https://cloud.google.com/blog/products/data-analytics/simplify-and-automate-data-processing-with-dataflow-prime</a></p><p><a href="https://cloud.google.com/dataflow/docs/guides/enable-dataflow-prime#enable-prime">https://cloud.google.com/dataflow/docs/guides/enable-dataflow-prime#enable-prime</a></p><p><a href="https://cloud.google.com/blog/products/data-analytics/benchmarking-dataflow-jobs?__s=tg5pjz1cgpjwz7jr39wl&amp;utm_source=drip&amp;utm_medium=email&amp;utm_campaign=GCP%2BNewsletter%2B%23313">https://cloud.google.com/blog/products/data-analytics/benchmarking-dataflow-jobs?__s=tg5pjz1cgpjwz7jr39wl&amp;utm_source=drip&amp;utm_medium=email&amp;utm_campaign=GCP%2BNewsletter%2B%23313</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7e218465cfb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GKE vs Autopilot vs Cloud Run]]></title>
            <link>https://medium.com/@arsh987/gke-vs-autopilot-vs-cloud-run-47b3afe4fa54?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/47b3afe4fa54</guid>
            <category><![CDATA[gke-autopilot]]></category>
            <category><![CDATA[gke]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[google-cloud-run]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Fri, 27 Jan 2023 18:54:52 GMT</pubDate>
            <atom:updated>2023-01-27T18:54:52.541Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/994/0*MlZWprxzmWNX9HtE.png" /></figure><p><a href="https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview"><strong>Autopilot</strong></a><strong>:</strong> the main difference between standard GKE and Autopilot is that it takes all cluster and node management. GKE Autopilot is an automated opinionated default, secure configuration of GKE. Nodes and node pools are completely managed by Google. Security updates and maintenance are automated. In terms of provisioning resources, all you have to do is set up your resource requests, limits, and auto-scaling rules, Autopilot will do the rest.</p><h4><strong>Billing.</strong></h4><p>You will only pay for the resources (CPU, RAM, and Storage), It’s not quite Serverless in the sense of zero-cost for zero load or seamless auto-scaling, if you have a pod running, you will be paying for its resources even if it is completely idle and unused. As with all managed services, it may seem more expensive per compute unit (CPU/memory) compared to GKE Standard.</p><h4><strong>Issues.</strong></h4><p>During my research I noticed that autoscaling is not exactly instant and is not really designed for rapid scale-up events, GKE Autopilot is <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#allowable_resource_ranges"><strong>somewhat restrictive</strong></a><strong> </strong>when it comes to CPU and memory requests: CPU requests are allowed in 250m increments (10m for DaemonSets), and there’s a 1.0–6.5 range allowed between CPU-to-memory GiB.</p><p>It takes several minutes to run the additional pods. By deploying too many Pods, we could easily run out of capacity, which triggers the cluster <strong>autoscaler</strong> to add many more nodes to the cluster, which in turn triggers a master resize event on GKE. The master resize happens on GKE because GKE the VMs that run the Kubernetes <strong>API server</strong> and <strong>etcd</strong> need to be resized to a higher machine type when the node count gets larger.</p><h4><strong>Additional useful information on Autopilot</strong></h4><blockquote><a href="https://wdenniss.com/tag/autopilot">https://wdenniss.com/tag/autopilot</a></blockquote><blockquote><a href="https://wdenniss.com/gke-autopilot-spare-capacity">https://wdenniss.com/gke-autopilot-spare-capacity</a></blockquote><blockquote><a href="https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#unsupported_cluster_features">https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#unsupported_cluster_features</a></blockquote><blockquote><a href="https://stackoverflow.com/search?q=gke+autopilot&amp;searchOn=3">https://stackoverflow.com/search?q=gke+autopilot&amp;searchOn=3</a></blockquote><h4><strong>How to reduce cost on Autopilot</strong></h4><blockquote><a href="https://medium.com/@krisztian.sala/reduce-costs-with-spot-pods-on-gke-autopilot-78ae87ffca1e">https://medium.com/@krisztian.sala/reduce-costs-with-spot-pods-on-gke-autopilot-78ae87ffca1e</a></blockquote><blockquote><a href="https://cloud.google.com/kubernetes-engine/pricing">https://cloud.google.com/kubernetes-engine/pricing</a></blockquote><h4><strong>Cloud Run vs GKE vs Autopilot</strong></h4><p>Cloud Run suits best for 1 process (a.k.a. container) per instance, so if you need to run a sidecar container better go with GKE Autopilot. In addition, Cloud Run doesn’t support messaging/eventing, so if your application needs to consume any Kafka topic or any kind of message-driven component, better go with GKE Autopilot. Now, about GKE Autopilot, if you need a scale-to-zero container you’d better go with a self-managed GKE cluster.</p><h4><strong>Decision Matrix.</strong></h4><p>The decision tree below may assist you in choosing between <strong>Cloud Run</strong> and <strong>GKE</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/0*a7fbYeRUODCC42Mf" /></figure><h4>Some other gotchas before starting to use GKE autopilot.</h4><p>1. Istio Service mesh is not supported by Autopilot <a href="https://github.com/istio/istio/issues/37150"><strong>here</strong></a> is the link for further info. It is by design. it is supported on the managed <a href="https://cloud.google.com/blog/products/containers-kubernetes/managed-anthos-service-mesh-on-gke-autopilot-clusters"><strong>Anthos service mesh</strong></a><strong>.</strong></p><p>2. At this moment it is not possible to convert standard clusters to Autopilot mode and converting Autopilot clusters to Standard mode is not supported.</p><p>3. Autopilot clusters enable workload identity by default. <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#authenticating_to"><strong>How to configure Autopilots to use workload identity</strong></a></p><p>4. Autopilot will just handle the nodes, but you would have to define how big the pods will be (via PodSpec) and when the pods will scale, it applies to horizontal and vertical pods auto-scaling, for HPA, and VPA to work you have to set resource limit and request.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47b3afe4fa54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How does BigTable work/Best practices:]]></title>
            <link>https://medium.com/@arsh987/how-does-bigtable-work-best-practices-c0744c303f30?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0744c303f30</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[big-table]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Wed, 18 Jan 2023 03:28:40 GMT</pubDate>
            <atom:updated>2023-01-18T03:28:40.441Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*IzfuytK8tQdpJSkI" /></figure><blockquote><strong>Cloud Bigtable can be described as three systems working together.</strong></blockquote><ul><li>A front-end server pool.</li><li>A set of compute nodes to handle connections (Cloud Bigtable Cluster).</li><li>A scalable backend of storage.</li></ul><p>All client requests go through the front-end server pool before they are sent to a Cloud Bigtable node. Each node in the cluster handles a subset of the recommendations for the entire system, and the frontends will handle balancing these connections depending on the type of action the contact is interested in, and what part of your data it wants to work on. To store the underlying data for each of your tables, Cloud Bigtable shards the data into multiple tablets where each tablet contains a contiguous range of rows within the table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/0*yT-IgEGjjK5AnURK" /></figure><p><strong>Expected performance:</strong></p><p>Cloud Bigtable delivers highly predictable performance, and according to the <a href="https://cloud.google.com/bigtable/docs/performance">official documentation</a>, you can expect to achieve the following performance for each node in your Cloud Bigtable cluster, depending on which type of storage your cluster uses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/0*VyOWOTKLTOStgn85" /></figure><p><strong>Bigtable’s performance could decrease due to several factors:</strong></p><ol><li>Reading many row keys or ranges in a single read request.</li><li>The Bigtable rows contain large amounts of data with many cells.</li><li>Improper design of table schema.</li><li>Network connection issues.</li><li>Using an out-of-date client library for the application.</li><li>Insufficient nodes in the cluster.</li></ol><p><strong>Bigtable capacity:</strong></p><p>Performance scales linearly as more clusters are added to a cluster. The capacity of Bigtable clusters should be determined according to the trade-off between throughput and latency and the trade-off between storage and performance. When the CPU load of a cluster is below 70%, Bigtable offers optimal latency. Planning at least twice the capacity for an application’s maximum queries per second is recommended. This allows a cluster to run at less than 50% of the CPU load, offering low latency to front-end services.</p><p>Bigtable optimizes the storage by distributing data across all the cluster nodes as the data volume increases. The storage usage per node is calculated by dividing the cluster’s storage utilization by the number of nodes in the cluster. Storage Utilisation for latency-sensitive applications is set to 60% or below. Workloads experience increased query processing latency even if the nodes meet overall CPU needs. More background work is required as the storage per node increases. This can result in low throughput and high latency.</p><p><strong>Replication</strong>:</p><p>Cloud Bigtable replicates data across multiple regions and zones to increase availability and durability. This ensures that serving applications are isolated from batch reads, and that data is stored globally. Replication increases read throughput but do not affect write throughput. Without replication, the write throughput for an instance doubles when the number of nodes in a cluster increases. However, with replication, each piece of data is written twice. First is when the write is received and then during replication to the other cluster.</p><p><strong>Monitoring Bigtable:</strong></p><p>Monitoring gives a detailed view of the usage of Bigtable. This can be done from the following places in the console.</p><ol><li>Bigtable cluster overview</li><li>Bigtable table overview</li><li>Key Visualizer</li><li>Bigtable monitoring</li><li>Bigtable instance overview</li><li>Google Cloud’s operations suite</li><li>Cloud Monitoring</li></ol><p>It can also be monitored using the Cloud Monitoring API. Users can monitor performance over time by breaking down metrics for various resources and using charts for a given period. Cloud Monitoring can import usage metrics from Bigtable. Usage metrics can be viewed in the Metrics Explorer on the Resources page under Monitoring.</p><p><strong>CPU Utilisation and Disk Usage:</strong></p><p>Nodes in a cluster perform various operations like reading, writing, and other administrative tasks, all of which require CPU resources. The metrics for CPU utilisations are:</p><ol><li>Average CPU Utilization of all the cluster nodes.</li><li>CPU Utilisation of the hottest node: The hottest node is the busiest node that changes states frequently.</li><li>CPU Utilisations by methods, table, and app profile.</li><li>Bigtable measures disk usage in binary units like Binary Gigabytes, also known as gibibytes (GiB). Storage metrics calculate data in the disk as of the last computation.</li></ol><p><strong>Key Visualiser:</strong></p><p>Monitoring the usage patterns of Bigtable can be done using Key Visualiser. It is a tool that helps users analyze and diagnose Bigtable. The visual reports generated by Key Visualiser give detailed insights into usage patterns that may be difficult to analyze otherwise. They can be used to improvise the existing schema designs and troubleshoot performance issues. Key Visualiser does not display all metrics responsible for the performance of Bigtable. Hence, additional troubleshooting along with Key Visualiser scans are needed to identify the causes of performance issues. Key Visualiser scans consist of a heatmap with aggregate values on each axis. Heatmaps show the patterns of a group of keys over time. The x-axis represents time, and the y-axis represents the row keys. Low metric values for a row key are said to be cold and are denoted in dark colors. High values appear as light colors. Such visual patterns make it easy to diagnose problems with just a glance.</p><p><a href="https://cloud.google.com/bigtable/img/keyvis-row-prefix-zoomed.png">Exploring Heatmaps</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PHUoGa657HWb06_9" /></figure><p>The given picture denotes a heat map in Key Visualiser. Issues identified by the Key Visualiser are displayed above the heatmap as diagnostic messages. The usage of a particular resource determines high and low values. If warning and performance metrics appear in bright colors, the Key Visualiser detects a potential problem. Colors in the heatmap can be adjusted using the +/- buttons on either side of the Adjust Brightness option. Increasing the brightness decreases the range of values represented by that color and vice versa. Users can use Rectangular Zoom to enlarge a particular area in the heatmap to get a closer and more detailed look. This helps notice issues for a specific period. Row keys represent a hierarchy of values, each having an identifier to capture usage and a timestamp. Users can drill down into the data of a heatmap using a common prefix shared by a group of row keys. Specific row-key hierarchies can be selected from the left side of the heatmap. The key prefix for all the row keys at that level is also displayed. Details about a metric are shown as a tooltip when the cursor moves over the heatmap. Tooltips can be pinned by clicking on the heatmap. The ops metric gives an overview of the usage pattern for a table. Users can switch metrics by choosing one from the Metric drop-down list above the heatmap.</p><p><strong>Heatmap Patterns:</strong></p><p>Five main heatmap patterns are frequently spotted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/0*b8jsov8CaeLvpIMO" /><figcaption>Heatmap patterns</figcaption></figure><ol><li>The pattern denotes sequential reads and writes. The diagonal line implies the access of contiguous key ranges in sequential order.</li><li>The pattern represents evenly distributed reads and writes. The fine-grained texture shows an effective usage pattern.</li><li>Alternating bands of dark and light colors show that the key ranges are accessed only at specific periods and not always.</li><li>An abrupt change from dark to light color denotes a sudden increase in adding or accessing rows in a specific period.</li><li>Horizontal lines of light and dark colors can represent hotkey ranges, usually while performing larger reads and writes.</li></ol><p><strong>Diagnostics:</strong></p><p>Diagnostic messages help identify issues in performance data while observing a <a href="https://cloud.google.com/bigtable/docs/keyvis-overview">Key Visualiser</a> scan. The messages can include a Warning symbol or Danger symbol to denote the problem-causing rows. Following are some of the diagnostic messages.</p><ol><li>High read pressure</li><li>High write pressure</li><li>Larger rows — It notifies that some rows in the table exceed 256MB of data.</li><li>No data scanned — This implies no performance data for the table.</li><li>Keyspace not to scale — If a table contains a small number of rows, the Key Visualizer cannot evenly distribute the row keys into buckets.</li></ol><p><strong>Plan your Bigtable capacity:</strong></p><ol><li><strong>High throughput and low latency:</strong> Bigtable offers optimal latency when the CPU load for a cluster is under 70%. For latency-sensitive applications, however, we recommend that you plan at least 2x capacity for your application’s max Bigtable queries per second (QPS). This capacity ensures that your Bigtable cluster runs at less than 50% CPU load, so it can offer low latency to front-end services. This capacity also provides a buffer for traffic spikes or key-access hotspots, which can cause imbalanced traffic among nodes in the cluster.</li><li><strong>Storage usage and performance:</strong> When storage utilization increases, workloads can experience an increase in query processing latency even if the cluster has enough nodes to meet overall CPU needs. This is because the higher the storage per node, the more background work such as indexing is required. The increase in background work to handle more storage can result in higher latency and lower throughput.</li><li><strong>For latency-sensitive applications:</strong> Google recommends that you keep storage utilization per node below 60%. If your dataset grows, add more nodes to maintain low latency. For further information on storage please check the <a href="https://cloud.google.com/bigtable/quotas#storage-per-node"><strong><em>official documentation.</em></strong></a></li><li><strong>Capacity planning:</strong> Always run your own typical workloads against a Bigtable cluster when doing capacity planning, so you can figure out the best resource allocation for your applications. You can follow the <a href="https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/tree/master/tutorials/bigtable_walkthrough"><strong><em>PerfKitBenchmarker tutorial for Bigtable</em></strong></a> to create tests for your own workloads.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0744c303f30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GCP Security Best Practices.]]></title>
            <link>https://medium.com/@arsh987/gcp-security-best-practices-7a1dae7c96fa?source=rss-d2b43485a0c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a1dae7c96fa</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[gcpsecurity]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Arsh]]></dc:creator>
            <pubDate>Thu, 05 Jan 2023 19:06:15 GMT</pubDate>
            <atom:updated>2023-01-09T15:57:23.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/689/0*9TRFp5jcGta5pKde.png" /></figure><p><strong>Security guardrails for End users.</strong></p><p><a href="https://cloud.google.com/resource-manager/docs/organization-policy/overview"><strong>Organization policy</strong></a> — Provides centralized and programmatic control over how the organization’s resources are deployed. For example, the organization policy constraint constraints/compute.requireShieldedVm, will prevent Engineers/users from deploying standard VMs. More info on <a href="https://cloud.google.com/compute/shielded-vm/docs/shielded-vm"><strong>Shielded VMs</strong></a>:</p><p><a href="https://cloud.google.com/vpc-service-controls"><strong>VPC Service Controls</strong></a><strong> </strong>— Prevents unauthorized data movement by isolating GCP resources and restricting data flows with fine-grained rules. VPC Service Controls enable context-based perimeter security to secure API-based services. Users working on a protected service within a VPC Service Control perimeter will be restricted to the rules defined by the administrator, helping to mitigate the risk of data exfiltration.</p><p><a href="https://cloud.google.com/iam"><strong>Cloud IAM</strong></a><a href="https://cloud.google.com/iam/docs/overview"> </a>— Enables granular access to ensure Developers only have access to specific Google Cloud resources, apply the principle of least privilege, preventing overly permissive roles.</p><p><a href="https://cloud.google.com/recommender/docs/recommenders?_ga=2.14625214.-800075116.1657130783"><strong>Recommender</strong></a> is a service that provides useful recommendations. It can be used to remove excessive permissions as well.</p><p><strong>Security guard rail at the organization level:</strong></p><p><a href="https://cloud.google.com/blog/products/identity-security/increasing-trust-in-google-cloud-visibility-control-and-automation"><strong>Visibility</strong></a><strong>: </strong>Cloud resources are often ephemeral and difficult to monitor. To ensure visibility, you can leverage first-party and third-party cloud security and monitoring services.</p><p><a href="https://cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy"><strong>Resource Hierarchy</strong></a><strong>: </strong>GCP lets you define your own resource hierarchy. For example, you can organize folders, projects, and teams under an organization, and assign permissions accordingly.</p><p><a href="https://cloud.google.com/logging/docs/central-log-storage"><strong>Centralized Logging and Monitoring</strong></a><strong>: </strong>You can implement logging and monitoring to ensure the health of your applications, pipelines, and various processes. Logging and monitoring systems collect and analyze the data needed to trace, profile, and debug. If you are running multiple environments, you should implement a centralized logging and monitoring solution that provides you with visibility of all assets.</p><p><a href="https://cloud.google.com/logging"><strong>Cloud Logging</strong></a><strong>: </strong>To collect logs that provide diagnostic information about the health of your assets you can use Cloud Logging, which is a native Google Cloud service. Cloud Logging integrates with the majority of Google Cloud services.</p><p><a href="https://cloud.google.com/monitoring"><strong>Cloud Monitoring</strong></a><strong>: </strong>To monitor your assets, you can use Cloud Monitoring. This is a native Google Cloud service that enables you to gain information about the overall performance and health of your infrastructure and applications. Cloud Monitoring can ingest metrics, metadata, and events. It then generates insights, which are visualized in customizable dashboards. You can also get alerts when certain events occur. Cloud Monitoring integrates with Cloud Logging, a wide range of Google Cloud services, and third parties.</p><p><strong>Misconfigurations:</strong></p><p>Many cloud data breaches occur due to misconfigurations. Here are some best practices you can implement to protect your cloud environment:</p><ul><li><strong>Continuously manage access controls</strong>: to ensure permissions are always relevant and assigned according to current roles. You can do this by monitoring IAM policies to ensure they are properly implemented.</li><li><strong>Enforce the principle of least privileges</strong>: you can do this by only giving users only the permissions they require for their jobs.</li><li><strong>Implement logging</strong>: to identify changes across your cloud environments and determine the extent of incidents.</li><li><strong>Automate as much as possible</strong>: to ensure you rapidly discover vulnerabilities, misconfigurations, and unauthorized activities.</li></ul><p><a href="https://cloud.google.com/policy-intelligence/docs/analyze-iam-policies#:~:text=roles%20or%20permissions-,You%20can%20use%20the%20Policy%20Analyzer%20to%20check%20which%20principals,does%20not%20specify%20a%20resource."><strong>Policy analyzer</strong></a> is a great tool to find out which users, service accounts, and groups have what access to which Google Cloud Services.</p><p><strong>Other Google Cloud Security Tools:</strong></p><p><a href="https://cloud.google.com/security-key-management"><strong>Google Cloud KMS</strong></a><strong>: </strong>Google Cloud Key Management Service (KMS) lets you manage cryptographic keys. You can use Google’s KMS to create, rotate and destroy several types of cryptographic keys, including AES256, RSA 3072, RSA 2048, RSA 4096, EC P384, and EC P256. You can either manually rotate keys or opt to automate the process.</p><p><a href="https://cloud.google.com/security-command-center/pricing"><strong>Google Cloud Security Command Center</strong></a><strong>: </strong>The Google Cloud Security Command Center can detect vulnerabilities in Google Kubernetes Engine (GKE), Google Compute Engine (GCE), and Google App Engine (GAE). Cloud Security Scanner lets you create, schedule, run and manage scans via the GCP console. Scanner can detect many vulnerabilities, such as Flash injection, cross-site scripting (XSS), and mixed content, as well as outdated or insecure JavaScript (JS) libraries.</p><p><a href="https://cloud.google.com/security/compliance"><strong>Google Cloud Compliance</strong></a><strong>: </strong>Google provides a wide range of resources and services you can use to maintain compliance in your global and regional resources. You can use Google Anthos to enforce compliance and security policies across your cloud environment.</p><p><strong>Security guard rails at code level:</strong></p><p><a href="https://owasp.org/www-project-top-ten/"><strong>OWASP Foundation</strong></a> offers many valuable resources, among them the OWASP Top 10, which features the most common security risks and is a good starting point.</p><p><strong>Access control:</strong> which includes authentication and authorization, is one of the basic building blocks of protecting your system.</p><p><strong>Enforcing strong encryption:</strong> is another important aspect of keeping your system secure. There are many readily available libraries to help you implement encryption, thus requiring minimal custom code to be written.</p><p><strong>Secrets management:</strong> is another important security measure. you should never hardcode or upload secrets such as passwords or access keys to code repositories.</p><p><strong>Automated scanning &amp; code reviews: </strong><a href="https://snyk.io/learn/cross-site-scripting/"><strong>Cross-site scripting (XSS)</strong></a><strong>, </strong><a href="https://snyk.io/learn/sql-injection/"><strong>SQL injection</strong></a>, and other types of attacks can exploit security vulnerabilities in your code. Both XSS and SQL injection attacks result from weakness in your code. A combination of regular <a href="https://www.g2.com/categories/secure-code-review"><strong>secure code reviews</strong></a> and <a href="https://www.comparitech.com/net-admin/best-static-code-analysis-tools/"><strong>automated tools</strong></a> that scan your code for these vulnerabilities can help prevent such attacks.</p><p>How to access apps, and VMs securely: <a href="https://cloud.google.com/beyondcorp-enterprise"><strong>BeyondCorp Enterprise</strong></a> is a zero-trust solution that enables secure access to applications.</p><p>If you are new to Google Cloud and looking to deploy infrastructure more securely and make it production-ready, a <a href="https://cloud.google.com/architecture/landing-zones"><strong>Secure landing zone</strong></a> is a great way to start.</p><p><strong>Other Useful GitHub repos:</strong></p><p><a href="https://github.com/terraform-google-modules/terraform-google-project-factory"><strong>https://github.com/terraform-google-modules/terraform-google-project-factory</strong></a></p><p><a href="https://github.com/orgs/GoogleCloudPlatform/repositories"><strong>https://github.com/orgs/GoogleCloudPlatform/repositories</strong></a></p><p><a href="https://github.com/GoogleCloudPlatform/terraformer"><strong>https://github.com/GoogleCloudPlatform/terraformer</strong></a></p><p><a href="https://github.com/GoogleCloudPlatform/security-response-automation"><strong>https://github.com/GoogleCloudPlatform/security-response-automation</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a1dae7c96fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>