<?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>Appsec on TACE Data</title><link>https://tacedata.ca/tags/appsec/</link><description>Recent content in Appsec on TACE Data</description><generator>Hugo</generator><language>en-CA</language><copyright>2026 TACE Data Management Inc.</copyright><lastBuildDate>Sat, 20 Jun 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://tacedata.ca/tags/appsec/index.xml" rel="self" type="application/rss+xml"/><item><title>training tracker: stage 2 — the security audit nobody asks for</title><link>https://tacedata.ca/posts/train-stage-2-post/</link><pubDate>Sat, 20 Jun 2026 10:00:00 +0000</pubDate><guid>https://tacedata.ca/posts/train-stage-2-post/</guid><description>second post in the training tracker series: before adding a single new feature, the working single-user app gets a proper security review. What an audit of a small web app actually looks at, and why shipping something is the start of the job, not the end of it.</description></item></channel></rss>