<?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>Documentation on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</title><link>https://blog.lameiro0x.com/tags/documentation/</link><description>Recent content in Documentation on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lameiro0x.com/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>Documentation &amp; Reporting</title><link>https://blog.lameiro0x.com/notes/post-exploitation/documentation-and-reporting/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/post-exploitation/documentation-and-reporting/</guid><description>&lt;h1 id="why-good-reporting-matters"&gt;Why Good Reporting Matters&lt;/h1&gt;
&lt;p&gt;Penetration testing is not only about finding weaknesses. It is also about producing a clear record of what was tested, what was observed, what was exploited, and what the client should do next. A report is a time-bound snapshot of the target environment, so it should state when the work happened, who performed it, what source systems were used during testing, and any special conditions such as VPN access or internal jump hosts.&lt;/p&gt;</description></item></channel></rss>