<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Github on TACE Data</title><link>https://tacedata.ca/tags/github/</link><description>Recent content in Github on TACE Data</description><generator>Hugo</generator><language>en-CA</language><copyright>2026 TACE Data Management Inc.</copyright><lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://tacedata.ca/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>i learned this lesson, with smaller stakes</title><link>https://tacedata.ca/posts/sec-cisa/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/sec-cisa/</guid><description>A CISA contractor exposed credentials, config files, and access tokens in a public GitHub repository. I had a smaller incident with a similar pattern — and a very different blast radius — in April.</description></item></channel></rss>