<?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[GitGuardian - Medium]]></title>
        <description><![CDATA[Learn more about code security, secrets detection, application security and DevSecOps through in-depth articles, tutorials and chronicles. - Medium]]></description>
        <link>https://medium.com/gitguardian?source=rss----56ba4920c382---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>GitGuardian - Medium</title>
            <link>https://medium.com/gitguardian?source=rss----56ba4920c382---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:18:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/gitguardian" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Evaluating The GitGuardian Secrets Detection Platform: A Self-Guided Roadmap]]></title>
            <link>https://medium.com/gitguardian/evaluating-the-gitguardian-secrets-detection-platform-a-self-guided-roadmap-805f27167c03?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/805f27167c03</guid>
            <category><![CDATA[remediation]]></category>
            <category><![CDATA[evaluation]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[secrets-detection]]></category>
            <category><![CDATA[secrets]]></category>
            <dc:creator><![CDATA[Dwayne Mcdaniel]]></dc:creator>
            <pubDate>Tue, 27 Feb 2024 14:35:23 GMT</pubDate>
            <atom:updated>2024-02-27T14:35:13.010Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQyARZDw0Pg1A0HX-LyQvA.png" /></figure><p>Let’s face it: acquiring enterprise security software can feel daunting. There are so many competing security priorities in the enterprise, making it hard to know which ones to address and in what order. Once you are ready to evaluate solutions, it can be confusing to know where to start. This includes secrets security, both on the storage and management side and the detection and leak remediation side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qHDPQHHB0BSsyQB7" /></figure><p>For those who might be tackling secrets security now or in the near future, we want to shine a light on the path we have seen many customers take, moving from free, personal use of the <a href="https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com">GitGuardian Secrets Detection Platform</a> all the way through to successful enterprise adoption. While every organization is different, and your circumstances might be unique to you, we are happy to share what we have learned from our customers over the years.</p><h3>Free for individuals</h3><p>At GitGuardian, we want every developer to keep their secrets secret and stop credentials from leaking into their shared code. This is why we make GitGuardian Secrets Detection and <a href="https://www.gitguardian.com/ggshield?ref=blog.gitguardian.com">ggshield, our CLI</a>, absolutely free for individual developers. Many developers use GitGuardian when they are ready to release code into the wild, especially as open source projects, to make sure they are not opening any access to unintended users.</p><p>With just a few commands, any developer working on their personal projects or on open source contributions can add a <a href="https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?ref=blog.gitguardian.com">handy pre-commit or pre-push git hook</a> to their repositories to automatically prevent the over 400 types of secrets from making it into their git history.</p><h3>Free for small teams</h3><p>If your team has 25 developers or fewer, you also qualify to use our free tier of the <a href="https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com">GitGuardian Secrets Detection</a> platform. We do not restrict the power of our scanning tools for free customers, providing the same level of enterprise protection for all projects, large and small. What you see is what you get with GitGuardian.</p><p>While some teams discover the GitGuardian platform early in their journey, many enterprises are beyond this phase of growth when they decide to tackle secrets sprawl; we are here to help in the process.</p><h3>A free trial for your larger team’s projects</h3><p>When adopting or evaluating any enterprise solution, it is a good idea to start small and view the process as a journey, not a rushed <a href="https://www.merriam-webster.com/wordplay/moonshot-words-were-watching?ref=blog.gitguardian.com">moonshot style mission</a>. Yes, you should act with urgency to attain better security, but starting with small, manageable efforts is preferable to the extremes of doing nothing or abandoning other ongoing security efforts to focus on what might be a whale of a task.</p><p>Many teams start evaluating the <a href="https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com">GitGuardian Secrets Detection</a> platform by focusing on a single project or repository they deeply understand. When you first add a new repo to your defined perimeter, <strong>the platform will perform a historical scan</strong>. This deep scan will look through every branch and every commit in your project’s git history, uncovering any and all hardcoded secrets lurking below the surface. This is especially useful for inherited legacy code and decades-old <a href="http://www.laputan.org/mud/mud.html?ref=blog.gitguardian.com#Abstract">big balls of mud</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5Poiqz68od3SBYrJ" /></figure><p>Many teams use these historical findings as a baseline, showing if plaintext secrets in the code are a recurring, ongoing issue.</p><h3>Testing for new secrets over time</h3><p>Once a repository has been added to your GitGuardian perimeter, the platform will scan for any newly added secrets. Many teams will set a period of days or weeks to monitor for new issues and to test sample secrets that represent the real credentials that they worry will slip into the wrong hands. This is when teams also test our ability to <a href="https://docs.gitguardian.com/platform/monitor-perimeter/messaging-integrations/slack?ref=blog.gitguardian.com">scan Slack channels</a> for secrets.</p><h3>Alerting that works for you</h3><p>It is during these times that many teams will also test the alert integrations. While all alerts will, by default, trigger a warning email, most teams want to make sure any alerts also get added to the right channel on platforms like Slack or Discord or get those alerts automatically sent to services like PagerDuty or Splunk. You can also create <a href="https://docs.gitguardian.com/platform/monitor-perimeter/notifiers-integrations/custom-webhook?ref=blog.gitguardian.com">custom webhooks</a> that fire off the alert anywhere you need, into any custom SEIM or orchestration tooling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PirPJUWbfkzBadSv" /></figure><p>For anyone evaluating an enterprise scanning platform, the question should not only be, “Can it find issues?” but instead, “Can it help us find and solve our issues?” With GitGuardian, the answer is a resounding “Yes!”</p><p>Remediation of secrets is a challenge for a number of reasons. The interconnectedness of modern DevOps means one can not simply rip out or revoke a secret once published without fear of a cascading failure event. We must gather all the needed data about the <a href="https://blog.gitguardian.com/presence-and-validity-checks-product-update/">secret’s validity, presence throughout the codebase</a>, if it has been <a href="https://blog.gitguardian.com/unveiling-public-leak-checks-for-hardcoded-secrets-in-the-gitguardian-platform/">exposed publicly yet</a>, and other vital details.</p><p>Gathering facts is a start, but you also need to get feedback directly from the team member who added the secret into the code, the developer. Each incident managed through the GitGuardan dashboard has the option to easily <a href="https://blog.gitguardian.com/coordinating-and-prioritizing-remediation-with-gitguardian/">share the details with selected team members and gather feedback</a> directly through the platform. Even if the developer is external to your company, the share option can accommodate this communication through the use of a temporarily public URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d_y_pdeGDF9_OQS_" /></figure><h3>Working with larger enterprises</h3><p>Even though GitGuardian makes it easy to perform a self-evaluation and even use the product for free in some situations, we know that most enterprises will require a more formal approach. We have worked with a lot of organizations to perform a <a href="https://blog.gitguardian.com/evaluating-secrets-detection-platforms-is-messy/">Proof of Concept, POC, exercise and we are happy to share what that process looks like</a>.</p><h3>Finding your own path</h3><p><a href="https://www.gitguardian.com/state-of-secrets-sprawl-report-2023?ref=blog.gitguardian.com">Secrets sprawl is a growing problem</a> affecting every company that writes or leverages code. It is something enterprises need to address sooner than later. Advanced <a href="https://blog.gitguardian.com/a-maturity-model-for-secrets-management/">secrets management maturity</a> is needed by companies handling sensitive, mission-critical data, requiring addressing the problem of secrets storage and proper use with dedicated secrets managers like <a href="https://blog.gitguardian.com/talking-about-data-security-an-introduction-to-aws-kms-and-hashicorp-vault/">Vault by Hashicorp</a> or , as well as detecting and remediating secret leaks at scale.</p><p>It might be tempting to think, ‘I can just write some regular expression’ to address the issue. We have heard from many customers that when it comes down to “<a href="https://blog.gitguardian.com/secrets-detection-build-vs-buy/">build versus buy</a>” for secrets sprawl, the overhead and magnitude of what is needed often becomes overwhelming rather quickly. But you don’t have to just take our word for it. Check out the many, many <a href="https://www.gitguardian.com/customer-stories?ref=blog.gitguardian.com">reviews and testimonials about GitGuardian from our users</a>.</p><p>No matter where you are on your security journey, GitGuardian is here to help you get a handle on secrets sprawl. While we encourage you to do your own investigation of our platform, we are also ready to help you navigate this subject. <a href="https://www.gitguardian.com/book-a-demo?ref=blog.gitguardian.com">Reach out today and schedule a demo</a> and start down the path towards peace of mind when it comes to knowing where your secrets are.</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/evaluating-the-gitguardian-secrets-detection-platform-a-roadmap/"><em>https://blog.gitguardian.com</em></a><em> on February 20, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805f27167c03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/evaluating-the-gitguardian-secrets-detection-platform-a-self-guided-roadmap-805f27167c03">Evaluating The GitGuardian Secrets Detection Platform: A Self-Guided Roadmap</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pulumi VS Terraform: The Definitive Guide to Choosing Your IaC Tool]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/gitguardian/pulumi-vs-terraform-the-definitive-guide-to-choosing-your-iac-tool-6be9081aa6e7?source=rss----56ba4920c382---4"><img src="https://cdn-images-1.medium.com/max/2360/0*0DdTLVeKaD4qE6JX.png" width="2360"></a></p><p class="medium-feed-snippet">The definitive showdown between Pulumi and Terraform. Tips and FAQ included. Choose the right tool for the job.</p><p class="medium-feed-link"><a href="https://medium.com/gitguardian/pulumi-vs-terraform-the-definitive-guide-to-choosing-your-iac-tool-6be9081aa6e7?source=rss----56ba4920c382---4">Continue reading on GitGuardian »</a></p></div>]]></description>
            <link>https://medium.com/gitguardian/pulumi-vs-terraform-the-definitive-guide-to-choosing-your-iac-tool-6be9081aa6e7?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/6be9081aa6e7</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[pulumi]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Tiexin Guo]]></dc:creator>
            <pubDate>Tue, 27 Feb 2024 11:57:20 GMT</pubDate>
            <atom:updated>2024-02-27T11:57:20.231Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ChiBrrCon IV: Understanding risks and the role of the CISO]]></title>
            <link>https://medium.com/gitguardian/chibrrcon-iv-understanding-risks-and-the-role-of-the-ciso-156c92053d6c?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/156c92053d6c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[access-management]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[chicago]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Dwayne Mcdaniel]]></dc:creator>
            <pubDate>Fri, 16 Feb 2024 16:03:24 GMT</pubDate>
            <atom:updated>2024-02-16T16:03:16.176Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pyE2YSS212PC0mwt.png" /></figure><p>There are a lot of fun facts to know about Chicago. You might have heard about the <a href="https://en.wikipedia.org/wiki/Chicago-style_hot_dog?ref=blog.gitguardian.com">multi-topping hot dogs</a>, the skyscrapers, or the fact the city <a href="https://www.enjoyillinois.com/travel-illinois/the-history-of-chicago-river-dyeing/?ref=blog.gitguardian.com#:~:text=the%20river%20dyeing.-,If%20you%20visit%20Chicago%20during%20St.,right%20into%20the%20Chicago%20River.">dyes the river green every year</a>. I also learned recently that Chicago is home to a university with an astounding <a href="https://www.iit.edu/news/illinois-tech-ranked-nations-top-100-universities-and-29-best-value-us-news-world-report?ref=blog.gitguardian.com#:~:text=with%20more%20than%2090%20percent%20of%20its%202022%20graduates">90+% job placement rate</a>, Illinois Institute of Technology. We learned this from the president of the university, Dr. Raj Echambadi, as we gathered in one of their auditoriums to kick off <a href="https://chibrrcon.com/?ref=blog.gitguardian.com">ChiBrrCon IV</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*v1d6t2OuyzTYGWsQ" /><figcaption>Raj Echambadi, President of Illinois Institute of Technology, kicks off the 2024 ChiBrrCon</figcaption></figure><p>With over 600 registrants, this was the largest audience in the event’s history. With 27 sessions to choose from, a digital escape room experience, villages, and workshops, there was content for everyone throughout this one-day event. The weather was unseasonably warm here in 2024, making it an extremely great day to get together for conversations, a lot of learning, and some fun. Here are just a few highlights from this year’s event.</p><h3>Understanding risk is key to managing security</h3><p>“Did you know that space shuttle design is based around the size of a horse’s rear end?” That is how <a href="https://www.linkedin.com/in/irawinkler/?ref=blog.gitguardian.com">Ira Winkler, Field CISO, CYE Security</a>, began his keynote: “Your Cybersecurity Program is a Horse’s Behind.” What followed was a great talk on assumptions and managing risk.</p><p>The connection between horses and shuttles is due to the width of railroad tracks. While we use trains to move NASA equipment, those tracks still use this same width between rails today as when horses were still the primary mode of travel. He said we often do the same thing with our security budgets: we let the past model dictate how we forecast security needs. We need, instead, to challenge those assumptions and base our plans on the reality that we face today.</p><p>At the heart of his talk, Ira brought up measuring and communicating risk. We need to be able to translate the threats and vulnerabilities in terms of how much they could cost the company, along with estimates of what it would cost to fix the issues. He reminded us that there is no such thing as “zero risk” and that operating a business brings varying risks. Other teams care deeply about different types of risk than you might. Ira really set the tone for the whole day and event with his keynote, as there was a lot of conversation in the hallways about this very subject.</p><p>There is an accompanying article about this session recently published in <a href="https://www.darkreading.com/ics-ot-security/your-cybersecurity-budget-is-horses-rear-end?ref=blog.gitguardian.com">Dark Reading</a> if you want to read more on this topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5MSrgZp4wgCrsAVM.png" /><figcaption>Without being able to get the required budget, cybersecurity programs can’t be responsive to evolving threats. @irawinkler #ChiBrrCon</figcaption></figure><h3>Cybersecurity champions can help us all stay safe</h3><p>Continuing with the theme of risk, <a href="https://www.linkedin.com/in/kylejoerger/?ref=blog.gitguardian.com">Kyle Joerger, Technology Controls &amp; Compliance Manager at CME Group</a>, presented “Fostering Risk Culture with a Cybersecurity Champions Network,” laying out the fact that security culture is really risk culture. Risk culture is all the attitudes and behaviors related to awareness and management of risks. If only the ‘security’ team cares about the topic, then it is going to be very hard to manage risk across the organization at scale. This is where Champions come in.</p><p>Cybersecurity Champions are employees who are naturally curious and interested in security and are willing to step up and speak out to help keep everyone safe. While they won’t carry a security title, they will be the ‘go to’ security expert in their department, asking the right questions and sharing what they have learned about threat awareness and process adjustments the security team has researched.</p><p>This is a two-way conversation. Champions also act as a conduit for channeling feedback to the security team. As Kyle phrased it: “Having a champions network gets you a front-row seat to what others care about.” With this insight, security teams can shape training and provide better tools in many cases.</p><p>If you want to start a Cybersecurity Champions program in your organization, check out the <a href="https://owasp.org/www-project-security-champions-guidebook/?ref=blog.gitguardian.com">OWASP Security Champions Guide</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ozbFGwS_4k0YGB7I" /><figcaption>“Fostering Risk Culture with a Cybersecurity Champions Network” by Kyle Joerger</figcaption></figure><h3>Rethinking default access</h3><p>In a world where humans are, and are forecasted to remain, the weakest link in our security systems, we need a better way to manage access beyond passwords or even existing IAM roles. This was the basic premise of the session from <a href="https://www.linkedin.com/in/swwapnilp/?ref=blog.gitguardian.com">Swapnil Pawar from Apex Fintech Solutions</a>: “Secure Your Infrastructure with Cloud-Native PAM.”</p><p>PAM stands for Privileged Access Management, though you may see the A stand for ‘Account’ in some conversations. PAM is a security framework built on the notion that identities need to be secured, not just managed, to protect your most valuable assets. PAMs work from a principle of delivering just-in-time access only when needed and only after verification. It is a way to embrace Zero-Trust architectures to deal with poor offboarding hygiene or situations where an attacker generates new users.</p><p>Swapnil also introduced the audience to the concept of <a href="https://www.cyberark.com/what-is/zero-standing-privileges/?ref=blog.gitguardian.com">Zero Standing Privileges, ZSP</a>, which goes hand in hand with adopting PAM. Essentially, ZSP means that applications do not grant any permissions by default, and no long-term access is ever allowed. It is similar to how a good web application firewall will start with no ports open, meaning more configuration time but a safer overall stance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*TrBy-I7mcM5BEHGF" /><figcaption>“Secure Your Infrastructure with Cloud-Native PAM” from Swapnil Pawar from Apex Fintech Solutions</figcaption></figure><h3>Hearing from the CISO’s manager</h3><p>Every ChiBrrCon has closed with a CISO panel, with Chief Information Security Officers sharing their stories from their time inside some complex organizations. This year was a bit different. The “Next Gen CISO Panel” didn’t feature people with CISO titles, but instead, they invited the folks to whom CISOs report, essentially their bosses. The panel consisted of:</p><p>Each panelist made a similar comment that it is not that relevant who a CISO reports to. It is far more critical that they are able to talk in terms of risks and budgets. While security should be their primary area of expertise, they must balance those conversations with the other competing realities and risks of the business.</p><p>Abbey made a point that in an ever-changing threat landscape, it is important to be able to build relationships across teams. She suggested that people who want to get better at soft social skills and confidently present their findings should invest in <a href="https://www.secondcityworks.com/?ref=blog.gitguardian.com">improv training</a>. While it might seem odd to inject an art known for comedy into a business conversation, she said it has helped the team at StoneX immensely in their communication and team building.</p><p>On a more somber note, Sunil reminded us that the CISO role will likely become a lot more visible as we see more congressional hearings and public scrutiny, as we have with SolarWinds. Anyone who wants to go down this career path needs to be prepared for that eventuality.</p><p>Bringing the conversation back to risk, each panel member made a point about striking a balance between being too transparent and just generating noise and not being transparent enough, making it impossible to build trust. The higher you go in an organization, the more critical it is to concisely and effectively communicate your recommendations and findings while accepting that every organization operates with some level of risk at any time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1WALWo-CwTOiG0Ji" /><figcaption>Next Gen CISO Panel at ChiBrrCon</figcaption></figure><h3>Managing risk means having good data</h3><p>Your author was fortunate enough to present the session: “Stand Up Straight — Security Posture And You.” This talk is all about understanding how the various tools of Application Security Posture Management, ASPM, and Cloud Security Posture Management, CSPM, for example, have evolved and what underlying problems they are trying to solve. I believe it all comes down to helping you answer the question of “W<a href="https://blog.gitguardian.com/good-application-security-posture-requires-good-data/">hat do I work on next?</a>” based on available data about your risks and required efforts to remediate any known issues.</p><p>Throughout the event, risk was front and center of nearly every conversation. No matter what area of security you are focused on, from the CISO all the way to the Cybersecurity Champion, it all comes down to managing risks. How clearly we communicate about these risks and how we balance the competing priorities to remedy them is a challenge we all deal with. It is great to be part of a community where this is very well understood.</p><p>I hope to see you at ChiBrrCon next year, or perhaps sooner, and closer to you. Check out our <a href="https://www.gitguardian.com/events?ref=blog.gitguardian.com">Event page to see where the GitGuardian team</a> will be speaking and make plans to come to say hello.</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/chibrrcon-iv-2024/"><em>https://blog.gitguardian.com</em></a><em> on February 8, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=156c92053d6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/chibrrcon-iv-understanding-risks-and-the-role-of-the-ciso-156c92053d6c">ChiBrrCon IV: Understanding risks and the role of the CISO</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluating Secrets Detection Platforms Is Complex: GitGuardian is here to help you navigate the…]]></title>
            <link>https://medium.com/gitguardian/evaluating-secrets-detection-platforms-is-complex-gitguardian-is-here-to-help-you-navigate-the-6b11d1c5a229?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/6b11d1c5a229</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[secrets]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[buyers-journey]]></category>
            <dc:creator><![CDATA[Dwayne Mcdaniel]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 20:29:50 GMT</pubDate>
            <atom:updated>2024-02-07T20:29:43.110Z</atom:updated>
            <content:encoded><![CDATA[<h3>Evaluating Secrets Detection Platforms Is Complex: GitGuardian is here to help you navigate the process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BC8JPDuRFJk2vFjWFcsTrw.png" /></figure><p>Everyone loves buying new tools (or not). It feels good to be able to use a new platform or technology to address an issue in the organization. But almost everyone hates the chaotic buying process that comes with many enterprise purchasing decisions. It does not help that the sales experience varies wildly between projects and vendors.</p><p>While it might be your first time through the process of evaluating tools to solve the issue of secret sprawl, especially leaks into public GitHub repositories, GitGuardian has helped hundreds of enterprises find the right solution in far less time than they first imagined. We understand the common hurdles anyone adopting a new solution faces, including how to communicate the value and urgency of solving the issue as you build a case for any new tech. We are happy to help you navigate these waters as well.</p><p>It all comes down to defining success, showing results, and getting the right buy-in for moving ahead.</p><h3>Evaluating via a POC</h3><p>Most enterprises require a formal evaluation process where a Proof of Concept, POC, must be performed when making a purchasing decision. Historically, this has meant bringing various vendors on-site, a lengthy installation process in a specially provisioned environment, and hours of training before the actual evaluation can start.</p><p>These kinds of engagements have left a lot of folks, understandably, hesitant to engage with vendors early in their evaluations. Often, teams start creating pages of requirements and questionnaires, which they hope will be helpful later on in the procurement process. Unfortunately, this approach leads to even longer evaluations because when they see a solution in action, finally grasping the problem holistically, there are always new questions they could have never anticipated.</p><p>While it is always a good idea to do a thorough investigation of any tech you will be relying on, especially for security, we think there is a better approach that can get you to a decision much faster and with far happier stakeholders.</p><h3>Defining success with the right players</h3><p>We see the buying process as a journey. All great journeys start with knowing where you are going and knowing who will be in the traveling party. After all, <a href="https://en.wikipedia.org/wiki/The_Hobbit?ref=blog.gitguardian.com">Gandalf didn’t just push Bilbo</a> out the door without a plan; he gathered the full party together and showed them the map before they ever stepped out of the Shire.</p><p>Instead of spending days in isolation, guessing at how to talk about the issue of secret sprawl, you can spend that same time gathering the right players together to get on the same page about the scale and scope of the issue. We are happy to help with this discussion using the and we have assembled, trusted, and relied on by the <a href="https://devops.com/gitguardian-adds-tool-for-discovering-secrets-in-public-repositories/?ref=blog.gitguardian.com">AppSec community</a> for years now.</p><p>We can help you understand the risks you realistically face and potential missteps in previous attempts to address the symptoms. In just a few short hours, sometimes all on the same day, we can help you build an evaluation guide and success criteria to evaluate solutions to secrets sprawl. The goal is always to help you understand your current risk and how you can best lower it.</p><p>Next is the part that many people who have had a bad POC experience dread: the actual installation and testing.</p><h3>Results in hours, not weeks</h3><p>So many teams have struggled with the POC process, in our opinion, due to enterprise solutions historically requiring a lot of setup and team buy-in before you can even begin to see any results. If a solution takes weeks to become operational in your environment and requires dedicated time from, let’s be honest, an overworked team, then that POC is going to stretch out for longer than you anticipated, even when you take into account <a href="https://en.wikipedia.org/wiki/Hofstadter%27s_law?ref=blog.gitguardian.com">Hofstadter’s law</a>.</p><p>With the GitGuardian Platform, <strong>most organizations can expect to see initial results in minutes,</strong> not days. Defining your perimeter is extremely quick and straightforward. If you are trying to get a handle on secrets leaked to public repositories, then the actual integration and testing require almost no work from your end, take just a few minutes to perform, and you will only need to spend your time verifying the results. If you are evaluating GitGuardian Secrets Detection for your internal repos, a full historical scan of a large and real repository might take a few more minutes to surface any issues over a new, small example repo, but the results will be fully actionable. We find out customers are often surprised by how <strong>low touch and unobtrusive</strong> fully integrating GitGuardian can be.</p><p>Once you have your results in hand, faster than you might have spent just coming up with questions; otherwise, it is time to take those findings to the rest of the organization and continue to the procurement step.</p><h3>Justifying the decision to buy</h3><p>At the end of many traditional POCs, you will have a spreadsheet full of results and more questions than you started with. Even if you do have everything you need at this point, the next hurdle is getting the internal buy-in to go from identifying to adopting the solution to your secrets sprawl problem.</p><p>When evaluating <a href="https://www.gitguardian.com/monitor-public-github-for-secrets?ref=blog.gitguardian.com">GitGuardian Public Monitoring</a>, we give you actionable insight into your state of public secrets sprawl. The <a href="https://www.gitguardian.com/complimentary-audit-secrets-leaks-public-github?ref=blog.gitguardian.com">report</a> includes a high-level overview of the developers defining your perimeter, the commits scanned, the actual secrets that have been leaked over time, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*7ZEzHxb4V1GRZs5d" /></figure><p>We will also give you an analysis of the secrets we found, including showing you how many we found to be valid, a breakdown of severity levels, the number of sensitive files found, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*ZesdWBO2CNZ48lKk" /></figure><p>While we are just showing the highest level of the summary report here, our team is happy to dig into the findings in detail, answering any and all questions along the way. Importantly, we can help you put these findings in perspective for the next important step, communicating the risks of not fixing these issues.</p><p><a href="https://www.gitguardian.com/complimentary-audit-secrets-leaks-public-github">Get a Complimentary Audit</a></p><h4>Communicating Risk</h4><p>Every department and every team leader cares about the same thing: risk. Managing risk and making sure any efforts lower risk in some way. However, every team and leader likely defines risk differently. For your legal team, legal risk and compliance risks are likely top of mind for any endeavor. For the Board of Directors, it is all about managing the investors’ risk and keeping business risks at a manageable level while still taking enough risks in the marketplace. To get anything done in the enterprise world, you need to find a way to communicate and align with the risks of all sorts of stakeholders.</p><p>We have worked with companies of all sizes and complexity and understand deeply how secrets sprawl poses risks at every level. We can help you answer any questions and show the clear return on investment that solving this problem will bring and in terms they will comprehend. We are happy to assist in the educational process with lunch and learns, executive briefings, and customized learning engagements, no matter how large or complex your organization is.</p><p>If you are not quite ready to engage in a conversation about the issue, then we invite you to use our basic Value Calculator to get a sense of the scope of the issue.</p><figure><a href="https://www.gitguardian.com/value-calculator?ref=blog.gitguardian.com"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*of7CmFiaBkPKxgtG.png" /></a></figure><p><a href="https://www.gitguardian.com/value-calculator?ref=blog.gitguardian.com">The Value Calculator</a> is a rough estimate tool. We would be happy to meet with you to get you a personalized and much more detailed calculation.</p><h3>Helping you fix today’s problems today</h3><p>Buying security tooling carries an urgency that does not come with many traditional IT decisions. Spending an extra few weeks when testing a new rack of servers does not normally carry a risk of compromising your customer data and valuable cloud resources while you wait. Getting the right solution to solve your issues at scale shouldn’t wait weeks or months to evaluate and even longer to implement.</p><p>Secrets sprawl is something that should be addressed sooner than later. Let GitGuardian help you get on the road to solving it today. <a href="https://www.gitguardian.com/book-a-demo?ref=blog.gitguardian.com">Reach out</a> and let’s solve this issue together.</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/evaluating-secrets-detection-platforms-is-messy/"><em>https://blog.gitguardian.com</em></a><em> on January 30, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b11d1c5a229" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/evaluating-secrets-detection-platforms-is-complex-gitguardian-is-here-to-help-you-navigate-the-6b11d1c5a229">Evaluating Secrets Detection Platforms Is Complex: GitGuardian is here to help you navigate the…</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI and Cybersecurity in 2024 — What’s Changing and Why It Matters]]></title>
            <link>https://medium.com/gitguardian/ai-and-cybersecurity-in-2024-whats-changing-and-why-it-matters-755eb4c97226?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/755eb4c97226</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[predictions]]></category>
            <category><![CDATA[2024]]></category>
            <dc:creator><![CDATA[Thomas Segura]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 10:21:38 GMT</pubDate>
            <atom:updated>2024-01-29T10:21:38.356Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI and Cybersecurity in 2024 — What’s Changing and Why It Matters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K2aBGYp558tqApVd.png" /></figure><p>As 2024 unfolds, the cybersecurity landscape is witnessing a notable transformation, primarily driven by the increasing integration of Artificial Intelligence (AI). Here’s a deeper dive into what these changes entail and their significance in the cyber world.</p><p>One of the most significant changes we’re seeing is in the <a href="https://www.sec.gov/corpfin/secg-cybersecurity?ref=blog.gitguardian.com">regulatory framework governing cybersecurity</a>. Public companies are now required to report cybersecurity incidents within just four business days, marking a significant shift in corporate governance and cybersecurity management. This new mandate is reshaping how businesses approach cybersecurity, with a strong emphasis on compliance and proactive management of cybersecurity risks.</p><p>In parallel, the EU has taken a pioneering step by passing <a href="https://www.technologyreview.com/2023/12/11/1084942/five-things-you-need-to-know-about-the-eus-new-ai-act?ref=blog.gitguardian.com">the first regulation specifically targeting AI technology</a>. Although it might seem early, the groundwork for this law began back in 2021, and it has since been refined for the realities of a post-ChatGPT world. The AI Act establishes the EU as a leader in coordinating compliance, implementation, and enforcement of AI regulations.</p><p>The act sets mandatory regulations for AI, focusing particularly on foundation models. These are the most powerful systems, like GPT-4, Claude, or Gemini, developed using extensive datasets that may include billions of items, some of which could be subject to copyright. Given their potential impact, these models will face heightened scrutiny, particularly in terms of security.</p><p>Echoing the influence of the General Data Protection Regulation (GDPR), the AI Act is poised to become a global benchmark for AI regulation. The EU’s proactive stance in this area demonstrates its ambition to be the world’s leading tech regulator, potentially influencing global standards in AI governance.</p><h4>AI’s Dual Role in Cybersecurity</h4><p>The role of AI in cybersecurity is a complex one. On one hand, AI technologies offer enhanced protection for systems and data. They allow for more sophisticated and efficient security measures. On the other hand, they introduce new kinds of <a href="https://blog.gitguardian.com/yes-github-copilot-can-leak-secrets/">risks</a> and <a href="https://blog.gitguardian.com/chatgpt-security-concern/">vulnerabilities</a>. This duality is at the heart of strategic planning for CISOs and CSOs, who now have to consider both the advantages and the potential threats posed by AI. Balancing these aspects is crucial for developing effective cybersecurity strategies.</p><h4>The Evolution and Scrutiny of AI Developer Tools</h4><p>AI-based tools like Copilot and CodeWhisperer are revolutionizing the way developers work, significantly boosting productivity. However, these tools often bypass traditional security practices, potentially leading to new vulnerabilities. In response to this, we expect to see the emergence of oversight tools specifically aimed at scrutinizing and enhancing the security and quality of AI-generated code. This development is crucial in maintaining the balance between efficiency and security in software development.</p><h4>The Rising Importance of Generative AI in Cybersecurity Products</h4><p>Generative AI is quickly becoming an integral part of cybersecurity solutions. Its transition from an optional feature to a core component in both B2B and B2C cybersecurity products reflects the growing reliance on AI for advanced threat detection and response mechanisms. This trend will probably only get stronger next year, as we are yet to see LLM-first products claim superior workflows compared to traditional products.</p><h4>The Evolving Responsibilities of CISOs</h4><p>The responsibilities of Chief Information Security Officers (CISOs) are changing quickly due to an increasing attack surface and the need for ongoing security vigilance. With new regulations aiming to accurately reflect the cost of cyber risks in market dynamics, CISOs are under greater pressure to be proactive in risk identification and mitigation. This heightened focus is also a response to the board’s growing demand for a transparent and accurate understanding of the organization’s actual security stance. The ongoing SEC vs SolarWinds case, dubbed as <a href="https://danielmiessler.com/p/sec-vs-solarwinds-cybersecuritys-enron-moment?ref=blog.gitguardian.com">the ‘Enron moment’ of cybersecurity</a>, should definitely make a turning point.</p><h4>AI, Open-Source, and Compliance</h4><p>The integration of AI in cybersecurity brings to the fore the challenge of managing open-source software in compliance with new regulations. This challenge is reminiscent of the complexities faced in the implementation of the <a href="https://blog.gitguardian.com/are-the-fears-about-the-eu-cyber-resilience-act-justified/">EU’s Cyber Resilience Act</a>. As regulations become more stringent, the task of ensuring that AI and open-source software meet these new standards becomes increasingly significant and complex.</p><h4>In Conclusion: Striking a Balance in 2024</h4><p>In summary, 2024 is a pivotal year in the field of cybersecurity, with AI playing a central role. The key to success in this evolving landscape lies in finding a balance — leveraging AI for innovation and enhanced security, while also navigating the challenges of new regulations and the inherent risks of AI technologies. It’s a delicate balancing act, but one that is crucial for building a secure and resilient digital future.</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/ai-and-cybersecurity-in-2024-whats-changing-and-why-it-matters/"><em>https://blog.gitguardian.com</em></a><em> on December 20, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=755eb4c97226" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/ai-and-cybersecurity-in-2024-whats-changing-and-why-it-matters-755eb4c97226">AI and Cybersecurity in 2024 — What’s Changing and Why It Matters</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The New Frontier in Cybersecurity: Embracing Security as Code]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/gitguardian/the-new-frontier-in-cybersecurity-embracing-security-as-code-b8092fffd7bf?source=rss----56ba4920c382---4"><img src="https://cdn-images-1.medium.com/max/1180/0*Ps1Al3xW7TcQjk8B.png" width="1180"></a></p><p class="medium-feed-snippet">Security as Code (SaC) is often used with DevSecOps, but what does it mean exactly? Learn best practices for a more secure dev process.</p><p class="medium-feed-link"><a href="https://medium.com/gitguardian/the-new-frontier-in-cybersecurity-embracing-security-as-code-b8092fffd7bf?source=rss----56ba4920c382---4">Continue reading on GitGuardian »</a></p></div>]]></description>
            <link>https://medium.com/gitguardian/the-new-frontier-in-cybersecurity-embracing-security-as-code-b8092fffd7bf?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/b8092fffd7bf</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[security-as-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Tiexin Guo]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 10:21:31 GMT</pubDate>
            <atom:updated>2024-01-29T10:21:31.092Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Secure Code Review Best Practices [cheat sheet included]]]></title>
            <link>https://medium.com/gitguardian/secure-code-review-best-practices-cheat-sheet-included-e74eba499e6a?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/e74eba499e6a</guid>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[secure-coding]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[pull-request]]></category>
            <dc:creator><![CDATA[C.J. May]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 10:21:22 GMT</pubDate>
            <atom:updated>2024-01-29T10:21:22.766Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reducing vulnerabilities in your software means manual and automated secure code reviews. Download our handy cheat sheet to keep your review practice on track.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fvoMZOfor7U3Q6l7.jpg" /></figure><p>Code review is an important part of the development process that can help to identify issues with the quality of the software. <em>Secure</em> code reviews are a specific type of code review that is specifically evaluating the security of the software’s source code. Activities that don’t include the source code (like DAST tools and pentests) are not considered “secure code review.”</p><p>Download our handy cheat sheet to keep your application security code review practice on track.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YLuFEFZcW6kQwcJE.png" /></figure><p><a href="https://www.gitguardian.com/files/secure-code-review-cheat-sheet?ref=medium.com">Download the PDF here!</a></p><p>Some of the steps in a secure code review can be assisted by automated tools, but many need a human for critical thinking and understanding of real-world processes. In this post, we will explore the different things you should do during a secure code review, point out which of those things can be automated, then summarize everything into a cheat sheet for you to reference when performing your own secure code reviews!</p><h3>Automated secure code review tools</h3><p>First, we’ll look at the parts of a secure code review that can be automated. Modern <a href="https://www.gitguardian.com/code-security?ref=blog.gitguardian.com">code security tools</a> allow you to quickly find the low-hanging fruit and focus on higher-level security issues. By utilizing automated tools, you can be sure that part of your process is consistent and quick.</p><h4>SAST tools</h4><p>Static Application Security Testing (SAST) tools analyze source code through various automated methodologies to find some classes of vulnerabilities. SAST tools are good at discovering whether your code is vulnerable to things like injection attacks, buffer overflows, and misconfigurations. Another advantage of SAST tools is that they can often run right in your IDE, giving you instant feedback as you write the code. Some SAST tools can also scan configuration files for your infrastructure-as-code, which is a big topic by itself.</p><p>Some examples of popular SAST tools include:</p><ul><li>SonarQube</li><li>Veracode</li><li>Snyk Code</li><li>Synopsys</li></ul><h4>Secret scanning</h4><p>We are passionate about <a href="https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com">detecting secrets</a> in code, which is another part of secure code review that can be automated. GitGuardian’s platform provides real-time detection of secrets when they are exposed in your code, and because of that, we are the number one security app on the GitHub marketplace!</p><p>Like other SAST tools, secret scanning software can also be integrated into earlier parts of the development process to catch secrets before they even enter the git history. GitGuardian provides an open-source tool called ggshield that you can configure to run as a pre-commit hook. More details on how to set that up can be found here.</p><h4>SCA</h4><p>A really tricky part of secure code review that automated tools make easy is Software Composition Analysis (SCA). SCA tools look at the third-party components you are using in your code and let you know if any of them have a known vulnerability. If you had to track every version of every dependency in your code, it would take a lot of time. Not to mention having to review everything periodically as new vulnerabilities come out all the time. SCA tools make this type of secure code review a snap and let you focus on other things.</p><p>Some popular SCA tools include:</p><ul><li>GitHub Dependabot</li><li>Snyk Open Source</li><li>Synopsys Black Duck</li></ul><h3>Manual secure code review</h3><p>Now that we’ve gone through some tools that can quickly enhance your secure code review, we will cover security issues that are harder to look for programmatically. In order to review for these security issues, you’ll need the eyes of a developer who understands the intricacies of each issue.</p><h4>Maintainability and complexity</h4><p>This is one of the parts of secure code review that overlaps with regular code review. When code is overly complex and difficult to maintain long-term, it can create all sorts of problems. When your code is hard to understand, you are more likely to let bugs and potential vulnerabilities slip through into production. To make matters worse, when bugs or vulnerabilities do slip through, it can take longer to remediate them. As a code reviewer, you should be looking out for complex code and make suggestions to simplify when you identify some.</p><h4>New dependencies</h4><p>We already covered how to watch for vulnerabilities in your existing dependencies, but it’s also a good idea to do some critical thinking when adding a new dependency to your code. If you are going to be depending on a package long-term, there are a few key areas you should consider:</p><ul><li>Popularity: the more popular a package is, the more likely it will be to have people investing in its upkeep.</li><li>Security: if the package has a history of vulnerabilities and poor coding practices, it might indicate that it isn’t safe to use in your software.</li><li>Maintenance: you should make sure that the package is actively maintained and has a good track record of fixing bugs.</li></ul><h4>Business logic flaws</h4><p>While SAST tools are good at detecting some types of vulnerabilities, like injection attacks, they aren’t very good at detecting business logic flaws. These kinds of vulnerabilities have less to do with the type of input and more to do with the meaning of the input. These types of vulnerabilities may appear to be functioning as intended but can be exploited by attackers to create unexpected behavior. Business logic flaws vary widely depending on the purpose of your software, which is why you need a human who understands the data and processes involved. You can read more about business logic flaws and look at examples here.</p><h4>Proper use of encryption</h4><p>Encryption is a vital part of applications, and it takes the knowledge of a human reviewer to evaluate the usage of encryption (or lack thereof). As a reviewer, you should give particular scrutiny to parts of your code that are saving data to a database or file or sending and receiving data over the network. Data flow diagrams can also be helpful when evaluating the usage of encryption.</p><h4>Error handling</h4><p>Error handling may not be the first thing that comes to mind when you think about application security, but it can be an issue at times. When software fails, it usually generates some sort of message for the user, but this message varies in detail from obscure to revealing. When an error message is too revealing, it may disclose detailed information about how your software works which can assist a malicious hacker in finding ways to exploit it. It’s generally best to keep user-facing error messages simple, and to keep more detailed information behind the scenes for developers’ eyes only. As a reviewer, you should make sure that your error messages aren’t too revealing, and that your applications handle errors in all the places that they should be.</p><h3>Conclusion</h3><p>We covered a lot of different things to look for when performing a secure code review. Reducing vulnerabilities in your software starts with the code, which means secure code reviews are a critical part of the software development process. While some of your time and effort can be reduced by using automated tools, you should still keep your cheat sheet handy and evaluate all of these areas when reviewing code.</p><p>To learn more about the shortcomings of manual code review alone, check out <a href="https://blog.gitguardian.com/code-security-manual-code-reviews-aint-enough/">our blog post on the topic</a>!</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/secure-code-review-cheat-sheet-included/"><em>https://blog.gitguardian.com</em></a><em> on July 26, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e74eba499e6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/secure-code-review-best-practices-cheat-sheet-included-e74eba499e6a">Secure Code Review Best Practices [cheat sheet included]</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Become Great at API Key Rotation: Best Practices and Tips]]></title>
            <link>https://medium.com/gitguardian/how-to-become-great-at-api-key-rotation-best-practices-and-tips-07f2c5d3eed3?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/07f2c5d3eed3</guid>
            <category><![CDATA[key-management]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[key-rotation]]></category>
            <category><![CDATA[api-key]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[C.J. May]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 10:20:56 GMT</pubDate>
            <atom:updated>2024-01-29T10:20:56.107Z</atom:updated>
            <content:encoded><![CDATA[<h4>Secret management can be a complex challenge, especially when you are trying to do it in a way that is right for security. Key rotation is a big piece of that puzzle. In this article, we will take you from zero to hero on key rotation.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n1RJ114FEhAowu0x.png" /></figure><h3>Key rotation 101</h3><h4>What is key rotation?</h4><p>Key rotation is the practice of changing access keys on a regular schedule to reduce the likelihood that a key can be abused if it gets compromised.</p><h4>Why rotate API keys?</h4><p>Over time, <a href="https://www.gitguardian.com/glossary/secret-sprawl-definition?ref=blog.gitguardian.com"><strong>secrets sprawl</strong></a>. They end up being exposed in places they shouldn’t be due to human mistakes and operational practices during a product’s lifecycle. Detecting when a secret is exposed is important, but rotating API keys on a regular basis is an essential layer of security to ensure that exposed secrets can’t be used for long and are less likely to work when they are discovered.</p><h4>What happens if you never rotate an API key?</h4><p>The longer a key is around, the more chances it has to get leaked or compromised. Not only that, but if an API key is never rotated it is guaranteed to work for any malicious party that finds it. Rotating your keys on a regular basis reduces the window of opportunity in which a key can be abused.</p><h3>Key rotation best practices</h3><h4>Document from the beginning!</h4><p>Having well-documented API keys will help you avoid a hard time when you need to rotate a key. The first thing you should do on this front is to <strong>record where your keys are being used</strong>. If a key is compromised, you’ll want to quickly identify the affected applications and data. Even if it’s not for a critical security issue, it will make the general process of rotating the key a lot smoother.</p><p>The next thing to do is <strong>record who/what has access to an API key</strong>. When a developer leaves the company, even if it was on good terms, they should no longer have access to internal systems. Keeping a detailed record of which keys an individual has access to will make it possible to quickly rotate all the relevant keys.</p><h4>How often should you rotate API keys?</h4><p>As a best practice,you should<strong> rotate API keys at least every 90 days</strong>. If you have a strong automated process for rotating keys, you could rotate much more often than that. We will get into automation later, though.</p><p><strong>Important events may require you to rotate keys</strong> as well. Example events could be a developer leaving the company or a secret being compromised or exposed in plain text. Having a well-established process for key rotation is especially important for time-sensitive events like these.</p><h4>How do you rotate a key without downtime?</h4><p>To rotate a key with zero downtime, you’ll need to <strong>create and deploy a new key before revoking the old one</strong>. If possible, monitor logs to ensure that the new key is being used after it has been deployed. Once the new key is being used by your application, you can revoke the old key.</p><h4>What if the service only allows one active key at a time?</h4><p>If the service you’re using only supports one active key at a time, you have a couple of options. The option you go with will depend on whether you can choose a custom secret to replace your old one:</p><ul><li>If you can manually set the new key, you can <strong>have your application use BOTH the new key and the old one that is being rotated</strong>. Just have your app try the new key first, and then fall back to the old one if it fails. Once you have manually rotated it to the new custom value, your app will automatically start using the new key.</li><li>If you cannot manually set the new key, your only option to avoid downtime is to <strong>create a new application or account with its own key on the service side</strong>. Keeping track of multiple client credentials for the same application isn’t clean nor desirable, so <strong>this should be a last resort</strong>.</li></ul><h4>How do you automate key rotation?</h4><p>Assuming you know how to rotate a secret manually, <strong>it can be automated if the service exposes key management through their API</strong>. To enable automated key rotation, the service’s API needs to let you:</p><p>The final implementation of your automation is going to depend on the service you are working with and how they do key management. If you know the process and have access to the proper APIs, you can do it! One last thing — don’t forget to <strong>validate active and inactive keys</strong> as part of your automation!</p><h3>Key rotation examples</h3><p>Now that we know what key rotation should look like, let’s look at a couple real examples.</p><h4>Rotating a GitHub App Token</h4><p>Let’s start with an easy one. Rotating a key is straightforward because GitHub allows apps to have more than one active key at the same time. You can find your registered apps under Settings &gt; Developer settings &gt; GitHub Apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fhCbGJpcvjJ5rXgu" /></figure><p>To rotate the key for an app, you need to click the “Edit” button and scroll all the way down until you see the “Private keys” section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/0*bhU_zpk_88jG0gt9" /></figure><p>As you can see, we are able to generate a new private key without revoking the old one. In fact, GitHub doesn’t even allow us to revoke the old key until there is a new one available!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/0*icASp5d-uOJvN-GR" /></figure><p>For scenarios like this, this is what our key rotation process looks like:</p><ol><li>Generate a new private key</li><li>Deploy the new private key to our application</li><li>Revoke the old private key</li></ol><p>When we generated the new private key for our app, we didn’t need to worry about our app getting locked out because our old key stayed active. Services that allow multiple active keys are the easiest to work with when rotating secrets.</p><h4>Rotating an Airbrake project key</h4><p>Not all key rotations will be that easy, unfortunately, so let’s also walk through a difficult key rotation: Airbrake project API keys. Airbrake is a service that allows you to monitor your app for errors and performance issues.</p><p>You can find your Airbrake project’s API key right in the settings page on the right-hand side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sFqmXn9udgoTW2kN" /></figure><p>As you can see from the screenshot, each Airbrake project only has one active key, and the “Regenerate API Key” button will instantly revoke the current key and replace it with a new one. If our goal is to rotate the key with no down time, this puts us between a rock and a hard place.</p><p>We can’t choose what the next API key will be, so we can’t preload the next key into our app alongside the old key (the trick that we covered earlier). Our only option to avoid downtime is to create another Airbrake project, and deploy that new project’s ID and key to our application. This gets really messy because the new project won’t have all of the settings we changed in the old one. We could actively maintain two identical projects and switch between the two each time we need to rotate the API key, but that isn’t a good solution either.</p><p>In situations like these, our only option may be to regenerate and deploy the new API key as quickly as possible and accept a lapse in coverage for Airbrake monitoring. If you are a developer who is implementing authentication for your service’s API, take this as an example of <em>what not to do</em> to your API consumers. <strong>Allow for multiple active keys in the applications you develop.</strong></p><h3>Conclusion</h3><p>We’ve covered a lot of ground in this article from the what’s, why’s, and how’s of key rotation to some real-world examples. To wrap it all up, I’ll capture all the advice above into a concise best practices list. If you want to be great at API key rotation, you need to:</p><ol><li>Record where your keys are being used</li><li>Record who/what has access to an API key</li><li>Rotate keys at least every 90 days</li><li>Rotate keys when developers leave</li><li>Rotate keys when they are leaked or compromised</li><li>Create and deploy a new key before revoking the old one</li><li>(Try the backup plans if the previous step isn’t straightforward)</li><li>Automate rotation if the service exposes key management through their API</li><li>Validate that keys are active/inactive as expected</li><li>Allow for multiple active keys in the applications you develop</li></ol><p>Hopefully at this point you feel like you have a concrete understanding of key rotation, and maybe you’re even starting to think about how to be better at this in your own software development lifecycle.</p><p>If you feel like you’re a long way from greatness in this area, just start with good documentation and take it one app at a time. You’ve got this!</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/api-key-rotation-best-practices/"><em>https://blog.gitguardian.com</em></a><em> on December 28, 2023.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07f2c5d3eed3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/how-to-become-great-at-api-key-rotation-best-practices-and-tips-07f2c5d3eed3">How to Become Great at API Key Rotation: Best Practices and Tips</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure Your Secrets with .env]]></title>
            <link>https://medium.com/gitguardian/secure-your-secrets-with-env-4e56abb66ce0?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/4e56abb66ce0</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[secrets]]></category>
            <dc:creator><![CDATA[Greg Bulmash]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 10:20:38 GMT</pubDate>
            <atom:updated>2024-01-29T10:20:38.480Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Secure Your Secrets with .env</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-U4we_Y0St8n_zMzEm6Yw.png" /></figure><p>Using environment variables to store secrets instead of writing them directly into your code is one of the quickest and easiest ways to add a layer of protection to your projects. There are many ways to use them, but a properly utilized .env file is one of the best, and I’ll explain why.</p><h3>They’re project scoped</h3><p>Environment variables are a part of every major operating system: Windows, MacOS, and all the flavors of *nix (Unix, BSD, Linux, etc.). They can be set at an operating system level, user level, session level… It gets complicated, and where/how you define them matters to the scope in which they can be accessed.</p><p>This variety of scopes also creates the distinct possibility of variable collisions. If you’re looking for an environment variable named `API_KEY`, that could be getting re-defined in each scope, and if you’re not steeped in that OS, it’s extra work to be sure you’re not clobbering something someone set at a different scope that some other app or service needs.</p><p>.env files are only consumed at runtime and only in the context of the app that’s consuming them. That prevents them from clobbering any other environment variables on the system that might be consumed outside your app.</p><h3>They can be “ignored”</h3><p>If you’re working on a JavaScript application in Node, you can’t ignore your index.js file in the version control system. It contains essential code. But you can <a href="https://youtu.be/3KrjEytC5qc">set your </a><a href="https://youtu.be/3KrjEytC5qc">.gitignore file</a> to have the Git system ignore your .env file. If you do that from the inception of your repository, you won’t commit secrets to the project’s Git history.</p><p>A better option is to include a .sample.env file that sets the variable names, but only includes dummy data or blanks. People cloning/forking and using the repository can get the secrets via another route, then cp .sample.env .env (in a terminal), and assign the real values to the proper variables in the ignored .env file.</p><h3>They’re relocatable</h3><p>While most systems will default to looking for the .env file in the root of the app’s primary directory, you can always have it a level or two higher. So, if for example, a server configuration error or code bug leaves it possible to view all the files at the root of your web app as a directory, the .env will not be there for easy pickings.</p><p>This is not an uncommon practice. SSH keys are stored by default at ~/.ssh (a “hidden” subdirectory of the home directory of the user) on Windows, Mac, and Linux. You do not need to move them into the root directory of a project that uses them.</p><h3>A quick .env demo in Node</h3><p>Let’s say your working directory for the app you’re building is ~/Documents/work/projects/games/tictactoe and tictactoe is the root directory for the app you’re building and your Git repository. You can put the .env in the next directory up, games. And while we generally call the file type .env, you can call it .toecreds if you want to make it a distinct file that other processes would never even think to touch. We’ll use that in the demo.</p><p>Here’s how you’d do that in Node.js.</p><ol><li>In your games/tictactoe directory, npm init (go with the defaults) and then npm install dotenv.</li><li>Create your .toecreds file in the games directory.</li><li>Fill the .toecreds file with information in the following format VARIABLE_NAME=VALUE (no spaces). You can also start a line with # for a comment.</li></ol><pre># Leaderboard SaaS<br>LEADERBOARD_ENDPOINT=https://example.com/leaderboard/v1<br>LEADERBOARD_KEY=jknfwgfprgmerg…</pre><p>4. At the top of your index.js (or whatever file is your launchpoint) in games/tictactoe, include the following lines:</p><pre>require(‘dotenv’).config({ path: ‘../.toecreds’ });<br>console.log(process.env.LEADERBOARD_ENDPOINT);</pre><p>Run your index.js and the endpoint URL will be output to the terminal. Meanwhile, the environment variables you set in it will not be available from the terminal and the file lives a level above your repository and can’t accidentally be swept up if you misconfigure .gitignore.</p><p>Try adding a long timeout to the script and then running node index.js &amp; to return control back to the terminal after invoking the script. While the script is running in that shell session, the environment variables available to the shell still do not contain the secrets. They are scoped to your running application.</p><p>You can have dev, test, and prod credential sets, having your CI/CD tooling pull the correct keys for the deployment target from a secrets manager and write the .toecreds (or .env) file to the same relative directory.</p><h3>And there you have it</h3><p>The use of a .env file helps you keep your app’s secrets from ever being committed to your version control and provides an additional layer of protection against your secrets being discovered by hackers or other prying eyes. It’s a great addition to your developer / dev-ops toolbox.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e56abb66ce0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/secure-your-secrets-with-env-4e56abb66ce0">Secure Your Secrets with .env</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding the Risks of Long-Lived Kubernetes Service Account Tokens]]></title>
            <link>https://medium.com/gitguardian/understanding-the-risks-of-long-lived-kubernetes-service-account-tokens-07f10e866ef2?source=rss----56ba4920c382---4</link>
            <guid isPermaLink="false">https://medium.com/p/07f10e866ef2</guid>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[security-token]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Thomas Segura]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 09:18:29 GMT</pubDate>
            <atom:updated>2024-01-29T09:18:29.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PR6oqxZmaPy14kxM.png" /></figure><p>The popularity of Kubernetes (K8s) as the defacto orchestration platform for the cloud is not showing any sign of pause. This graph, taken from the <a href="https://www.wiz.io/blog/key-takeaways-from-the-wiz-2023-kubernetes-security-report?ref=blog.gitguardian.com">2023 Kubernetes Security Report</a> by the security company Wiz, clearly illustrates the trend:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4kxKzq6zGsBGds076quHXg.png" /></figure><p>As adoption continues to soar, so do the security risks and, most importantly, the attacks threatening K8s clusters. One such threat comes in the form of long-lived service account tokens. In this blog, we are going to dive deep into what these tokens are, their uses, the risks they pose, and how they can be exploited. We will also advocate for the use of short-lived tokens for a better security posture.</p><h3>What Are Kubernetes Service Account Tokens?</h3><p>Service account tokens are <strong>bearer tokens</strong> (a type of token mostly used for authentication in web applications and APIs) used by service accounts to authenticate to the Kubernetes API. Service accounts provide an identity for processes (applications) that run in a Pod, enabling them to interact with the Kubernetes API securely.</p><p>Crucially, these tokens are <strong>long-lived</strong>: when a service account is created, Kubernetes automatically generates a token and stores it indefinitely as a Secret, which can be mounted into pods and used by applications to authenticate API requests.</p><p>As a reminder, the <strong>Kubelet</strong> on each node is responsible for mounting service account tokens into pods, so they can be used by applications within those pods to authenticate to the Kubernetes API when needed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VtVsPdm1bjI1PFfM40oIzA.png" /></figure><p>If you need a refresher on K8s components, look <a href="https://blog.gitguardian.com/hardening-your-k8-pt-1/#:~:text=right%20into%20it.-,1.%20Kubernetes%20Components,-First%2C%20let%27s%20do">here</a>.</p><h3>The Utility of Service Account Tokens</h3><p>Service account tokens are essential for enabling applications running on Kubernetes to interact with the Kubernetes API. They are used to deploy applications, manage workloads, and perform administrative tasks programmatically. For instance, a Continuous Integration/Continuous Deployment (CI/CD) tool like Jenkins would use a service account token to deploy new versions of an application or roll back a release.</p><h3>The Risks of Longevity</h3><p>While service account tokens are indispensable for automation within Kubernetes, their longevity can be a significant risk factor. Long-lived tokens, if compromised, give attackers ample time to explore and exploit a cluster. Once in the hands of an attacker, these tokens can be used to gain unauthorized access, elevate privileges, exfiltrate data, or even disrupt the entire cluster’s operations.</p><p>Here are a few leak scenarios that could lead to some serious damage:</p><p>- <strong>Misconfigured Access Rights</strong>: A pod or container may be misconfigured to have broader file system access than necessary. If a token is stored on a shared volume, other containers or malicious pods that have been compromised could potentially access it.</p><p>- <strong>Insecure Transmission</strong>: If the token is transmitted over the network without proper encryption (like sending it over HTTP instead of HTTPS), it could be intercepted by network sniffing tools.</p><p>- <strong>Code Repositories</strong>: Developers might inadvertently commit a token to a public or private source code repository. If the repository is public or becomes exposed, the token is readily available to anyone who accesses it.</p><p>- <strong>Logging and Monitoring Systems</strong>: Tokens might get logged by applications or monitoring systems and could be exposed if logs are not properly secured or if verbose logging is accidentally enabled.</p><p>- <strong>Insider Threat</strong>: A malicious insider with access to the Kubernetes environment could extract the token and use it or leak it intentionally.</p><p>- <strong>Application Vulnerabilities</strong>: If an application running within the cluster has vulnerabilities (e.g., a Remote Code Execution flaw), an attacker could exploit this to gain access to the pod and extract the token.</p><h3>How Could an Attacker Exploit Long-Lived Tokens?</h3><p>Attackers can collect long-lived tokens through network eavesdropping, exploiting vulnerable applications, or leveraging social engineering tactics. With these tokens, they can manipulate Kubernetes resources at their will. Here is a non-exhaustive list of potential abuses:</p><p>- Abuse the cluster’s (often barely limited) infra resources for <strong>cryptocurrency mining</strong> or as part of a botnet.</p><p>- With API access, attackers could <strong>deploy malicious containers</strong>, alter running workloads, exfiltrate sensitive data, or even take down the entire cluster.</p><p>- If the token has broad permissions, it can be used to modify roles and bindings to <strong>elevate privileges</strong> within the cluster.</p><p>- The attacker could create additional resources that provide them with persistent access ( <strong>backdoor</strong>) to the cluster, making it harder to remove their presence.</p><p>- Access to sensitive data stored in the cluster or accessible through it could lead to <strong>data theft or leakage</strong>.</p><h3>Why Aren’t Service Account Tokens Short-Lived by Default?</h3><p><a href="https://blog.gitguardian.com/a-maturity-model-for-secrets-management/">Short-lived tokens are a security best practice in general</a>, particularly for managing access to very sensitive resources like the Kubernetes API. They reduce the window of opportunity for attackers to exploit a token and facilitate better management of permissions as application access requirements change. Automating token rotation limits the impact of a potential compromise and aligns with the principle of least privilege-granting only the access necessary for a service to operate.</p><p>The problem is that implementing short-lived tokens comes with some overhead.</p><p>First, implementing short-lived tokens typically requires a <strong>more complex setup</strong>. You need an automated process to handle token renewal before it expires. This may involve additional scripts or Kubernetes operators that watch for token expiration and request new tokens as necessary.</p><p>This often means integrating a <strong>secret management system</strong> that can securely store and automatically rotate the tokens. This adds a new dependency for system configuration and maintenance.</p><p>Second, software teams running their CI/CD workers on top of the cluster will need adjustments to support dynamic retrieval and injection of these tokens into the deployment process. This could require changes in the pipeline configuration and additional error handling to manage potential token expiration during a pipeline run, which can be a true headache.</p><p><strong>And secrets management is just the tip of the iceberg.</strong> You will also need monitoring and alerts if you want to troubleshoot renewal failures. Fine-tuning token expiry time could break the deployment process, requiring immediate attention to prevent downtime or deployment failures.</p><p>Finally, there could also be performance considerations, as many more API calls are needed to retrieve new tokens and update the relevant Secrets.</p><p>By default, Kubernetes opts for a straightforward setup by issuing service account tokens without a built-in expiration. This approach simplifies initial configuration but lacks the security benefits of token rotation. It is the Kubernetes admin’s responsibility to configure more secure practices by implementing short-lived tokens and the necessary infrastructure for their rotation, thereby enhancing the cluster’s security posture.</p><h3>Mitigation Best Practices</h3><p>For many organizations, the additional overhead is justified by the security improvements. Tools like service mesh implementations (e.g., <a href="https://istio.io/latest/about/service-mesh/?ref=blog.gitguardian.com">Istio</a>), secret managers (e.g., <a href="https://docs.cyberark.com/conjur-enterprise/latest/en/Content/Integrations/k8s-ocp/k8s-architecture.htm?ref=blog.gitguardian.com">CyberArk Conjur</a>), or cloud provider services can manage the lifecycle of short-lived certificates and tokens, helping to reduce the overhead.</p><p>Additionally, recent versions of Kubernetes offer features like the <a href="https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-request-v1/?ref=blog.gitguardian.com">TokenRequest</a> API, which can automatically rotate tokens and project them into the running pods.</p><p>Even without any additional tool, you can mitigate the risks by limiting the Service Account auto-mount feature. To do so, you can opt out of the default API credential automounting with a single flag in the service account or pod configuration. Here are two examples:</p><ul><li>For a Service Account:</li></ul><pre>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br> name: build-robot<br>automountServiceAccountToken: false<br>…</pre><ul><li>And for a specific Pod:</li></ul><pre>apiVersion: v1<br>kind: Pod<br>metadata:<br> name: my-pod<br>spec:<br> serviceAccountName: build-robot<br> automountServiceAccountToken: false<br> …</pre><p>The bottom line is that <strong>if an application does not need to access the K8s API, it should not have a token mounted.</strong> This also limits the number of service account tokens an attacker can access if the attacker manages to compromise any of the Kubernetes hosts.</p><p>Okay, you might say, but how do we enforce this policy everywhere? Enter Kyverno, a policy engine designed for K8s.</p><h3>Enforcement with Kyverno</h3><p>Kyverno allows cluster administrators to manage, validate, mutate, and generate Kubernetes resources based on custom policies. To prevent the creation of long-lived service account tokens, one can define the following Kyverno policy:</p><pre>apiVersion: kyverno.io/v1<br>kind: ClusterPolicy<br>metadata:<br>  name: deny-secret-service-account-token<br>spec:<br>  validationFailureAction: Enforce<br>  background: false<br>  rules:<br>  - name: check-service-account-token<br>    match:<br>      any:<br>      - resources:<br>          kinds:<br>          - Secret<br>    validate:<br>      cel:<br>        expressions:<br>        - message: &quot;Long lived API tokens are not allowed&quot;<br>          expression: &gt;<br>            object.type != &quot;kubernetes.io/service-account-token&quot;<br></pre><p>This policy ensures that only Secrets that are not of type kubernetes.io/service-account-token can be created, effectively blocking the creation of long-lived service account tokens!</p><h3>Applying the Kyverno Policy</h3><p>To apply this policy, you need to have Kyverno installed on your Kubernetes cluster (<a href="https://kyverno.io/docs/installation/methods/?ref=blog.gitguardian.com">tutorial</a>). Once Kyverno is running, you can apply the policy by saving the above YAML to a file and using kubectl to apply it:</p><pre>kubectl apply -f deny-secret-service-account-token.yaml</pre><p>After applying this policy, any attempt to create a Secret that is a service account token of the prohibited type will be denied, enforcing a safer token lifecycle management practice.</p><h3>Wrap up</h3><p>In Kubernetes, managing the lifecycle and access of service account tokens is a critical aspect of cluster security. By preferring short-lived tokens over long-lived ones and enforcing policies with tools like Kyverno, organizations can significantly reduce the risk of token-based security incidents. Stay vigilant, automate security practices, and ensure your Kubernetes environment remains robust against threats.</p><p><em>Originally published at </em><a href="https://blog.gitguardian.com/understanding-the-risks-of-long-lived-kubernetes-service-account-tokens/"><em>https://blog.gitguardian.com</em></a><em> on January 11, 2024.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07f10e866ef2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gitguardian/understanding-the-risks-of-long-lived-kubernetes-service-account-tokens-07f10e866ef2">Understanding the Risks of Long-Lived Kubernetes Service Account Tokens</a> was originally published in <a href="https://medium.com/gitguardian">GitGuardian</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>