<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IV Needle &#187; Forensics</title>
	<atom:link href="http://www.ivneedle.com/category/forensics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ivneedle.com</link>
	<description>Injecting Tech into the Vein</description>
	<lastBuildDate>Fri, 06 Aug 2010 15:38:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Send Data Over a Network Using netcat</title>
		<link>http://www.ivneedle.com/2010/01/send-data-over-a-network-using-netcat/</link>
		<comments>http://www.ivneedle.com/2010/01/send-data-over-a-network-using-netcat/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 19:17:22 +0000</pubDate>
		<dc:creator>Heavymeddler</dc:creator>
				<category><![CDATA[Forensics]]></category>
		<category><![CDATA[netcat]]></category>

		<guid isPermaLink="false">http://www.ivneedle.com/?p=204</guid>
		<description><![CDATA[Often you cannot direct copy files between machines. One way to pass data is using netcat. There are versions of netcat for both Windows and Linux. Here are the steps to setup a connection to transfer data over a network using netcat. Setup netcat to listen (the machine receiving the data)﻿ Command: nc -v -l [...]]]></description>
			<content:encoded><![CDATA[<p>Often you cannot direct copy files between machines. One way to pass data is using netcat. There are versions of netcat for both Windows and Linux. Here are the steps to setup a connection to transfer data over a network using netcat.</p>
<p><strong>Setup netcat to listen (the machine receiving the data)﻿</strong></p>
<ul>
<li>Command: nc -v -l -p 10000 &gt; command.txt</li>
<li>Notes: -p is the port that you are opening up to receive the data. You can name the text file anything you want (usually wise to name it something descriptive).</li>
</ul>
<p><strong>Run a command on the sending machine</strong></p>
<ul>
<li>Command: command | nc receiving_machine_ip_address 10000</li>
<li>When the transfer is complete, kill the command using Ctrl-c</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.ivneedle.com/2010/01/send-data-over-a-network-using-netcat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Analyzing Volatile Data</title>
		<link>http://www.ivneedle.com/2010/01/analyzing-volatile-data/</link>
		<comments>http://www.ivneedle.com/2010/01/analyzing-volatile-data/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 05:50:30 +0000</pubDate>
		<dc:creator>Heavymeddler</dc:creator>
				<category><![CDATA[Forensics]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[volatile]]></category>

		<guid isPermaLink="false">http://www.ivneedle.com/?p=193</guid>
		<description><![CDATA[What to check for when analyzing volatile data through a netcat connection: The System Date and Time Current Network Connects Open TCP or UDP Ports Which Executables Are Opening TCP or UDP Ports Cached NetBIOS Name Table Users Currently Logged On The Internal Routing Table Running Processes Running Services Scheduled Jobs Open Files Process Memory [...]]]></description>
			<content:encoded><![CDATA[<p>What to check for when analyzing volatile data through a netcat connection:</p>
<ul>
<li>The System Date and Time</li>
<li>Current Network Connects</li>
<li>Open TCP or UDP Ports</li>
<li>Which Executables Are Opening TCP or UDP Ports</li>
<li>Cached NetBIOS Name Table</li>
<li>Users Currently Logged On</li>
<li>The Internal Routing Table</li>
<li>Running Processes</li>
<li>Running Services</li>
<li>Scheduled Jobs</li>
<li>Open Files</li>
<li>Process Memory Dumps</li>
</ul>
<p><strong><span style="text-decoration: underline;">The System Date and Time</span></strong></p>
<p>Check this to keep the machine time in sync with logs and trusted NTP server.</p>
<p>Windows Commands:</p>
<ul>
<li>date</li>
<li>time</li>
</ul>
<p>Linux/Unix Command:</p>
<ul>
<li>date</li>
</ul>
<p><strong><span style="text-decoration: underline;">Current Network Configuration</span></strong></p>
<p>Check this to see if an attacker is currently connected or running a brute force attack against the internet. Note that port assignments can be checked at <a href="http://www.portsdb.org">www.portsdb.org</a>.</p>
<p>Windows/Linux/Unix Command:</p>
<ul>
<li>netstat -an (Note that the -an flag specifies to check all network connections)</li>
</ul>
<p><strong><span style="text-decoration: underline;">Open TCP or UDP Ports</span></strong></p>
<p>Check for rogue ports that were not opened by the system. A suspiciously open port can be the sign of a back door created by an attacker. Note that port assignments can be checked at <a href="http://www.portsdb.org">www.portsdb.org</a>.</p>
<p>Windows Command:</p>
<ul>
<li> netstat -an</li>
</ul>
<p>Linux/Unix Command;</p>
<ul>
<li>netstat -anp (the p shows the process number that opened the port)</li>
</ul>
<p><strong><span style="text-decoration: underline;">Executables Opening TCP or UDP Ports</span></strong></p>
<p>Using a tool called FPort distributed from <a href="http://www.foundstone.com" target="_blank">www.foundstone.com</a>, scan which executables are using ports. Compare the list to the list of questionable ports you gathered while running netcat. Research which process are system processes and which are suspicious.</p>
<p>Windows Command:</p>
<ul>
<li>FPort</li>
</ul>
<p>Linux/Unix Command:</p>
<ul>
<li>lsof (adding -n command lengthens the output)</li>
</ul>
<p><strong><span style="text-decoration: underline;">Cached NetBIOS Name Tables (Windows only)</span></strong></p>
<p>Checking the NetBIOS Name Table cache will show the NetBIOS name or IP address of recently connected machines.</p>
<p>Windows Command:</p>
<ul>
<li>nbtstat -c (the -c switch instructs nbtstat to dump the cache)</li>
</ul>
<p><strong><span style="text-decoration: underline;">Users Currently Logged On (Windows only)</span></strong></p>
<p>Using the PSLoggedOn tool in the PSTools suite distributed at <a href="http://www.sysinternals.com" target="_blank">www.sysinternals.com</a> you can see who is currently logged into your system. This would catch anybody that is connected remotely.</p>
<p>Windows Command:</p>
<ul>
<li>psloggedon</li>
</ul>
<p><span style="text-decoration: underline;"><strong>The Internal Routing Table</strong></span></p>
<p>Checking the Routing Table will identify instances where an attacker is routing his connection to avoid a firewall or gain access from a machine with greater access.</p>
<p>Windows/Linux/Unix Command:</p>
<ul>
<li>netstat -rn</li>
</ul>
<p><strong><span style="text-decoration: underline;">Running Processes</span></strong></p>
<p>Using the pslist tool to check which processes are running will show which processes have been run by an attacker. The elapsed time will help indicate which processes were launched by the system and which were launched by an attacker.</p>
<p>Windows Command:</p>
<ul>
<li>pslist</li>
</ul>
<p>Linux/Unix Command:</p>
<ul>
<li>ps -aux</li>
</ul>
<p><strong><span style="text-decoration: underline;">Running Services (Windows only)</span></strong></p>
<p>Using the PSService tool you can examine the services running on the target machine. Finding a rogue service can be valuable since attackers can run executables from them.</p>
<p>Windows Command:</p>
<ul>
<li>psservice</li>
</ul>
<p><strong><span style="text-decoration: underline;">Scheduled Jobs</span></strong></p>
<p>Attackers can schedule jobs to do things while they are not even there.</p>
<p>Windows Command:</p>
<ul>
<li>at</li>
</ul>
<p>Linux/Unix Command:</p>
<ul>
<li>cron</li>
</ul>
<p><strong><span style="text-decoration: underline;">Open Files</span></strong></p>
<p>The PSfile tool will check for any files opened remotely on the machine. This will help determine more information about the attack.</p>
<p>Windows Command:</p>
<ul>
<li>psfile</li>
</ul>
<p>Linux/Unix Command:</p>
<ul>
<li>lsof</li>
</ul>
<p><strong><span style="text-decoration: underline;">Process Memory Dumps (Windows only)</span></strong></p>
<p>Running process memory dumps and using tools to inspect the data will help gain additional information about the attacker and their intent. This is extensive and requires a large knowledge base to know what to look for.</p>
<p>Windows Command/Tool:</p>
<ul>
<li>userdump.exe (provided by Microsoft)</li>
</ul>
<p><strong><span style="text-decoration: underline;">Full System Memory Dumps (Windows only)</span></strong></p>
<p>Using the dd tool you can dump the entire memory of the target computer. It is wise to map a drive to a remote machine so that you do not overwrite valuable data.</p>
<p>Windows Command/Tools:</p>
<ul>
<li>dd</li>
</ul>
<p><strong><span style="text-decoration: underline;">Loaded Kernel Modules (Linux/Unix only)</span></strong></p>
<p>This command unloads the kernel modules so that you can inspect for items that are not system related.</p>
<p>Linux/Unix Command:</p>
<ul>
<li>lsmod</li>
</ul>
<p><strong><span style="text-decoration: underline;">Mounted File Systems (Linux/Unix only)</span></strong></p>
<p>These commands check for mounted file systems that are unexpected.</p>
<p>Linux/Unix Command:</p>
<ul>
<li>mount</li>
<li>df</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.ivneedle.com/2010/01/analyzing-volatile-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
