<?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 Cameron Tekiyeh on Medium]]></title>
        <description><![CDATA[Stories by Cameron Tekiyeh on Medium]]></description>
        <link>https://medium.com/@cameron.tekiyeh?source=rss-12132fd738d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d5TjaO_zkmsWsgVcL0JVAw.jpeg</url>
            <title>Stories by Cameron Tekiyeh on Medium</title>
            <link>https://medium.com/@cameron.tekiyeh?source=rss-12132fd738d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:40:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cameron.tekiyeh/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[Securing Workload Access: Snowflake’s Journey to Workload Identity and Access Management (Workload…]]></title>
            <link>https://medium.com/snowflake/securing-workload-access-snowflakes-journey-to-workload-identity-and-access-management-workload-7c10f3021986?source=rss-12132fd738d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c10f3021986</guid>
            <category><![CDATA[snowflake]]></category>
            <dc:creator><![CDATA[Cameron Tekiyeh]]></dc:creator>
            <pubDate>Fri, 12 Apr 2024 23:36:54 GMT</pubDate>
            <atom:updated>2024-04-12T23:36:54.518Z</atom:updated>
            <content:encoded><![CDATA[<h3>Securing Workload Access: Snowflake’s Journey to Workload Identity and Access Management (Workload IAM)</h3><p>Today I’m excited to share some of the things that Snowflake has been working on behind the scenes to make our ecosystem of applications more secure, and by extension making Snowflake an even <a href="https://community.snowflake.com/s/snowflake-security">more secure</a> place for your data and AI strategies.</p><p>We’re big believers in automation, and as a company we’ve <a href="https://www.tines.com/case-studies/snowflake">invested</a> in creating and implementing tools that allow us to simplify and streamline the work our teams need to do on a regular basis. Beyond simply eliminating repetitive tasks, investing in automation allows us to improve security by reducing blindspots, onboarding employees faster, and allowing less experienced team members to accomplish more.</p><p>Yet, as we built a more robust and capable ecosystem of tools to support our activities, it was essential that these tools could securely access Snowflake (and where necessary, each other) in a controlled, compliant, and automated manner. It’s here where our path to building a Workload Identity and Access Management (Workload IAM) strategy began, culminating with our partnership with <a href="https://aembit.io/">Aembit</a>.</p><h3>Access Management: Credentials, Secrets, and Identities</h3><p>Snowflake had developed a mature process for handling access between workloads. In fact, it looks much like what other organizations probably do. When developers need access to another service (whether it was to Snowflake, to another SaaS service, or even to an internal service), they filed a request with a IT CloudOps team who are responsible for creating a service account and an access credential, and securely delivering the access credential to the original, requesting party. That credential and the related service account could then be stored in Active Directory and synced to Okta, if necessary.</p><p>The original party was then responsible for inputting the credential into their application, and they were set. Yet each connection we set up created a significant, ongoing tax in terms of maintenance and security:</p><ul><li>Service accounts and Access Credentials needed to be stored and cataloged</li><li>Credentials needed to be regularly rotated, creating work for both SecOps and the application owner</li><li>Ongoing compliance and audits required us to regularly track down the owners of applications and assess whether the credential was still required.</li><li>Compliance required visibility and reporting into the whole process.</li></ul><p>In addition, we saw potential security risks that we could address:</p><ul><li>Many workloads depended on long-lived versus short-lived access credentials.</li><li>Once a credential was issued, it was possible that it could be used for multiple workloads, beyond what it was originally intended for.</li><li>We did not know anything about the posture of the workload: is it healthy enough to provide the access it is requesting?</li><li>Finally, multiple humans may touch these highly privileged credentials that are really meant to be used by workloads.</li></ul><p>While the original process had served us well, we knew, both from the development of our own software and the continuing expansion of the Snowflake ecosystem, that workload-to-workload access was only growing, and at the same time this was becoming a <a href="https://aembit.io/blog/real-life-examples-of-workload-identity-breaches-and-leaked-secrets-and-what-to-do-about-them-updated-regularly/">targeted attack surface</a> at other organizations. The combination of this emerging risk and the opportunity to automate a critical workflow elevated the priority of addressing workflow access management.</p><h3>Automating Secure Access with Aembit</h3><p>As we began crafting a solution to this problem, we considered User IAM as a model for how we’d like to operate: we wanted to have workload identities that could be verified upon access, with policies, and dynamically issued credentials delivered in real-time.</p><p>We looked at a number of available tools. For example, we considered our existing secrets managers and vaults, but we knew of existing challenges to credential issuance and credential usage processes. We also knew this tool would likely add a new burden to our developers and application owners. We also considered using the native IAM tools of our Cloud providers, but those tools were limited to their own environments, and we needed something that would give us a single, consistent way to automate access across all of our environments.</p><p>As a result of our research, we began working with <a href="https://aembit.io/">Aembit</a>. They provide a Workload IAM system that allows us to move from managing credentials to managing access. Aembit is designed to work as an independent workload identity broker that can validate the identity of a client workload (a SaaS Service, Container/VM, or even a script) using the identity natively provided by its operating environment, and then issue an access credential based on a policy we set.</p><p>Aembit integrates into the broad range of services we need to access by supporting a broad set of access credentials types and protocols. On the other side, they support our client workloads by supporting identity federation with cloud, on-premise, and SaaS services. Moreover, that integration can happen via API or by way of a clever auth proxy called Aembit Edge that transparently provides all the auth logic and credential management for the workload. More on that in a bit.</p><p>Not surprisingly, our initial use case with Aembit was to specifically secure access between a number of workloads and our own internal Snowflake instance.</p><p>Working with Aembit, we were proactively able to improve our environment in a number of ways:</p><ol><li><strong>Automate credentials issuance, just-in-time.</strong> Workload access requests are intercepted and evaluated by Aembit on an ongoing basis, injecting credentials when a policy is met. This means workloads no longer need to store long-lived credentials, and humans don’t need to touch them either. We’ve also eliminated the need for the manual credential rotation process in workloads and the potential of breaking critical application flows as a result.</li><li><strong>Go secretless.</strong> Since Snowflake (and a growing number of other services) support dynamic access credentials, Aembit can issue short lived credentials instead of long-lived keys. The Aembit Edge can inject these credentials into a request, even when the workload thinks it is using an API key. This gives us the flexibility to improve security without burdening developers, or without asking our vendors to change how their product works.</li><li><strong>Enable zero trust conditional access</strong>. Not only can we provide access based on an identity, we can assess related characteristics of the workload before providing access. For example, is the workload being actively managed by our Cloud Security tool? Is it performing its operation during the time of day we would expect? There are a range of conditions we can check based on the workload, its request, and the sensitivity of the service it requires.</li><li><strong>Provide a highly automated, compliant system of record.</strong> We see every access request, the policy it met, and what credential was issued. No more chasing down application owners, and no need to undergo complex reporting tasks for auditors.</li></ol><p>First and foremost, working with Aembit allows us to improve our security posture and introduce a new line of defense: Workload Identities create a new control plane with which we can secure access to our sensitive data and resources. This is essential today, and even more critical as our workload footprint grows.</p><p>Along with making us more secure, Aembit also helps automate existing processes. As we expand the scope of Aembit within Snowflake, we estimate that across credential issuance, credential management, compliance reviews, reporting, auditing, and overall process management, that Aembit can save us 5–10 hours a day.</p><h3>What’s Next: Empowering A Secure Snowflake Ecosystem</h3><p>We’re excited to have started this Workload IAM journey, and we have many plans on where it can help us. First, we’ll continue to expand the scope of our usage, covering areas such as our Software Supply Chain, building more sophisticated dynamic policies, and building a central “system of record” for our workload-to-workload access.</p><p>But we also think that Workload IAM is an important element of the Snowflake ecosystem. We are forging ahead on this path so that our customers can also securely automate their workload to workload access with confidence. Part of the value of us securing Snowflake internally in this manner is that it will be battle-tested for customers who would also like to secure their use of Snowflake access from workloads. We also believe that this can play an important role in<a href="https://www.snowflake.com/en/data-cloud/workloads/applications/native-apps/"> Snowflake Native Apps</a> as they become a part of your data &amp; AI fabric.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pyU5k_oqaw1Da8-3.png" /></figure><p>We look forward to continuing this work with Aembit and also using it to benefit you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c10f3021986" width="1" height="1" alt=""><hr><p><a href="https://medium.com/snowflake/securing-workload-access-snowflakes-journey-to-workload-identity-and-access-management-workload-7c10f3021986">Securing Workload Access: Snowflake’s Journey to Workload Identity and Access Management (Workload…</a> was originally published in <a href="https://medium.com/snowflake">Snowflake Builders Blog: Data Engineers, App Developers, AI, &amp; Data Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[USING SNOWALERT TO IMPROVE SECURITY TRAINING AND AWARENESS COMPLIANCE]]></title>
            <link>https://medium.com/snowflake/using-snowalert-to-improve-security-training-and-awareness-compliance-deeed6d0fdca?source=rss-12132fd738d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/deeed6d0fdca</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-training]]></category>
            <category><![CDATA[snowflake]]></category>
            <dc:creator><![CDATA[Cameron Tekiyeh]]></dc:creator>
            <pubDate>Tue, 09 Jul 2019 17:17:40 GMT</pubDate>
            <atom:updated>2019-07-11T23:22:17.275Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using SnowAlert to Improve Security Training and Awareness Compliance</h3><p><strong>Security Awareness Training ~</strong></p><p>According to Verizon’s <a href="https://enterprise.verizon.com/resources/reports/dbir/">2019 Data Breach Investigations Report</a>, 32% of successful data breaches involved a phishing attack. In recent years, Cyber Attacks have evolved to exploit any vulnerabilities of an organization and often times employees are used as the ‘front door’ for these attacks. Once inside, attackers can potentially perform damaging infiltration with ease. This is where employee security awareness training becomes so important.</p><p><strong>Struggling with Compliance ~</strong></p><p>While it may be easy to create / deploy these security awareness trainings every quarter, it has become extremely difficult for organizations to ensure that their employees are actually completing these trainings. Automated Learning Management System (LMS) Emails are often overlooked by employees due to notification fatigue of emails repeatedly being sent which results in filtered inboxes or ignored messages. This caused me to turn to instant messaging tool Slack to casually reach out to employees and remind them to complete their training. To my surprise, I noticed that I got a response from employees almost immediately and that their trainings were completed shortly after that. This method seemed to be very effective in reminding employees to complete their trainings; however, I would have to reach out to over 1000 employees manually over Slack in order to make any meaningful impact.</p><p><strong>Striving for Success by harnessing the power of Snowflake ~</strong></p><p>In order to reduce the manual efforts involved with reaching out to users individually (via email or Slack), but still maintain our personalized approach to following up employees, we decided to leverage our own products — Snowflake and SnowAlert (a security analytics framework that uses the Snowflake data warehouse for identifying security incidents across diverse data sources and time ranges)</p><p>As a first step, we set up connections to start ingesting the LMS and HR data into Snowflake. Having all of our data in one place, we were able to fully utilize its potential and create views that joined both of these data sets, giving us access to the complete suite of data needed. Now with the data loaded into Snowflake, we leveraged <a href="https://github.com/snowflakedb/SnowAlert">SnowAlert</a>, to configure a set of rules that defined the conditions under which a specified action could be taken. We immediately turned to instant messaging platform Slack to deliver personalized messages to users. This tool was well ingrained into our culture and was constantly in use by all employees — and we were able to integrate Slack into Snowalert using a series of handlers.</p><p>Moreover, we wanted to continue sending users individualized message that would spark interest and motivate them to complete trainings. Metrics, such as average completion rate of security training, can be automatically aggregated and calculated by Snowflake — updating in realtime. People are naturally competitive, if they feel like they are behind, they have more incentive to catch up. Including the user’s percent deviation from the average rate of completion for security trainings in the message we sent them, would motivate non-compliant users to complete their trainings by showing them how far behind they are. Conversely, showing a user how far above the average they are, would positively reinforce their behavior and encourage them to always finish their trainings on time in the future. See below for examples of the two different types of messages that were sent to real users:</p><p>Message sent to employees who are non-compliant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vjNgZLozioZ3u8L7" /></figure><p>Example of message sent to employees who are fully compliant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0fbTz94p-39JGRYM" /></figure><p><strong>Conclusion ~</strong></p><p>After sending out our first message using Key Pup (the name of the Slackbot that delivers our training compliance messages), we immediately observed a major spike of unique logins and completed courses. Using Snowflake and Sigma (cloud based BI tool) we were able to easily explore the ingested data and monitor the real time status of user behavior — allowing us to gain insights regarding the effectiveness of our SnowAlert Slackbot approach in comparison to our previous methods by measuring course competition progress. If for some reason we observe unfavorable results from our approach, we could reapply the logic from the created rules in SnowAlert to be applied to a different messaging platform — such as SMS, email or ticketing systems.</p><p>If you are interested in learning more, see the <a href="https://www.snowflake.com/use-cases/monitoring-security-analytics/">Snowflake Security Analytics web page</a> and read the <a href="https://resources.snowflake.com/security-analytics/snowflake-for-security-analytics?utm_cta=website-security-compliance-anti-fraud-module-Snowflake-for-Security-Compliance-Fraud&amp;_ga=2.40407202.1891056370.1560195627-865955404.1545091893">solutions guide</a>. To speak with Snowflake Sales to learn more, see a demo, or collaborate with us on SnowAlert, go to this <a href="https://www.snowflake.com/contact/">web page</a>.</p><p><strong>References</strong></p><p>“2019 Data Breach Investigations Report.” Verizon Enterprise,<br> <a href="http://enterprise.verizon.com/resources/reports/dbir">enterprise.verizon.com/resources/reports/dbir</a>/.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=deeed6d0fdca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/snowflake/using-snowalert-to-improve-security-training-and-awareness-compliance-deeed6d0fdca">USING SNOWALERT TO IMPROVE SECURITY TRAINING AND AWARENESS COMPLIANCE</a> was originally published in <a href="https://medium.com/snowflake">Snowflake Builders Blog: Data Engineers, App Developers, AI, &amp; Data Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>