<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Incident Reporting - Tag - Dr. Ibrahim Waziri Jr.</title><link>http://iwazirijr.com/tags/incident-reporting/</link><description>Incident Reporting - Tag - Dr. Ibrahim Waziri Jr.</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 01 Oct 2026 12:00:00 +0100</lastBuildDate><atom:link href="http://iwazirijr.com/tags/incident-reporting/" rel="self" type="application/rss+xml"/><item><title>Why I Am Building Bitsfront</title><link>http://iwazirijr.com/2026-10-01-why-i-am-building-bitsfront/</link><pubDate>Thu, 01 Oct 2026 12:00:00 +0100</pubDate><author>Author</author><guid>http://iwazirijr.com/2026-10-01-why-i-am-building-bitsfront/</guid><description>Two clocks When a cyber incident hits a regulated institution, two clocks start at once. The security team starts reconstructing what happened. The legal and compliance team starts counting down to a regulator&amp;rsquo;s deadline. In most organizations those two clocks are not connected, and the space between them is where trust gets lost.
Over fifteen years in security, I have watched capable teams spend days rebuilding a timeline from logs and chat threads, while counsel works out which regulators need to hear about it, in what format, and by when.</description></item></channel></rss>