<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on fremverk</title><link>https://www.fremverk.com/en/categories/security/</link><description>Recent content in Security on fremverk</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>info@fremverk.com (fremverk)</managingEditor><webMaster>info@fremverk.com (fremverk)</webMaster><copyright>© 2026 fremverk</copyright><lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.fremverk.com/en/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Best practice keeps GitHub's most dangerous token alive</title><link>https://www.fremverk.com/en/blog/github-pat/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><author>info@fremverk.com (fremverk)</author><guid>https://www.fremverk.com/en/blog/github-pat/</guid><description>&lt;p&gt;Once again this October, a stolen or forgotten GitHub token has been enough to break into large companies. The obvious answer is to ban the riskiest type of token, but if you have set up GitHub by the book, you can&amp;rsquo;t, and then security rests on nobody out in the organization switching it back on.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://www.fremverk.com/en/blog/github-pat/og.png"/></item></channel></rss>