<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>forensics on Asa&#39;s Website</title><link>https://ahessmat.netlify.com/tags/forensics/</link><description>Recent content in forensics on Asa&#39;s Website</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 12 May 2021 01:31:39 +0000</lastBuildDate><atom:link href="https://ahessmat.netlify.com/tags/forensics/index.xml" rel="self" type="application/rss+xml"/><item><title>Book Review: Software Forensics</title><link>https://ahessmat.netlify.com/post/2021-05-book-review-software-forensics/</link><pubDate>Wed, 12 May 2021 01:31:39 +0000</pubDate><guid>https://ahessmat.netlify.com/post/2021-05-book-review-software-forensics/</guid><description>Preamble During a work trip to Washington I pulled the next read from a stack of books I checked out from my local library (I am so grateful that the libraries in my area have re-opened). Robert M. Slade&amp;rsquo;s Software Forensics: Collecting Evidence from the Scene of a Digital Crime is an easy read on a very complex topic.
Slade starts by distinguishing software forensics apart from digital forensics and network forensics; while predominantly affiliated with assessing malicious (or potentially malicious) software, it also has carved out space for identifying intellectual property theft.</description></item></channel></rss>