<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Evidence on Hector Herrera</title><link>https://www.hectorherrera.pro/en/tags/evidence/</link><description>Recent content in Evidence on Hector Herrera</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 07 Aug 2026 16:35:00 -0500</lastBuildDate><atom:link href="https://www.hectorherrera.pro/en/tags/evidence/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing an operational model for cybersecurity incident management</title><link>https://www.hectorherrera.pro/en/work/designing-operational-model-cybersecurity-incident-management/</link><pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.hectorherrera.pro/en/work/designing-operational-model-cybersecurity-incident-management/</guid><description>Structuring an incident management operating model that connects governance, roles, playbooks, evidence, communications, exercises, metrics, and continuous improvement.</description></item><item><title>An incident response plan nobody can execute is not really a plan</title><link>https://www.hectorherrera.pro/en/ideas/an-incident-response-plan-nobody-can-execute-is-not-really-a-plan/</link><pubDate>Fri, 07 Aug 2026 16:35:00 -0500</pubDate><guid>https://www.hectorherrera.pro/en/ideas/an-incident-response-plan-nobody-can-execute-is-not-really-a-plan/</guid><description>A plan creates value when a team can activate it under pressure: people know who decides, what to record, what to preserve, how to escalate, and when to close.</description></item></channel></rss>