<?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>Tool | RobWillis.info</title>
	<atom:link href="/tag/tool/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>#yolosec</description>
	<lastBuildDate>Tue, 22 Apr 2025 09:00:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>New Tool! Invoke-RPCMap: PowerShell Script for Remote RPC Service Enumeration</title>
		<link>/2022/06/powershell-script-invoke-rpcmap/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 27 Jun 2022 02:13:00 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Pen Testing]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[RPC]]></category>
		<category><![CDATA[Scanner]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[Tool]]></category>
		<guid isPermaLink="false">/?p=5365</guid>

					<description><![CDATA[<p>Invoke-RPCMap Invoke-RPCMap can be used to enumerate local and remote RPC services/ports via the RPC Endpoint Mapper service. This information can useful during an investigation where a connection to a remote port is known, but the service is running under a generic process like svchost.exe. This script will do the following: Create a local log [&#8230;]</p>
The post <a href="/2022/06/powershell-script-invoke-rpcmap/">New Tool! Invoke-RPCMap: PowerShell Script for Remote RPC Service Enumeration</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>VMware vCenter CVE-2021-21972 Scanner</title>
		<link>/2021/02/vmware-vcenter-cve-2021-21972-scan-tool/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Sat, 27 Feb 2021 10:31:52 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Pen Testing]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[CVE-2021-21972]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[Tool]]></category>
		<category><![CDATA[vCenter]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[vulnerability]]></category>
		<guid isPermaLink="false">/?p=5318</guid>

					<description><![CDATA[<p>In this post, I am releasing a PowerShell POC script that will scan the specified target hosts and attempt to detect those that are vulnerable to VMware vCenter CVE-2021-21972. You can find the script, Invoke-CVE-2021-21972-Scan.ps1, on my github here: https://github.com/robwillisinfo/VMware_vCenter_CVE-2021-21972 The script executes in the following order: Create a log file, default log name is [&#8230;]</p>
The post <a href="/2021/02/vmware-vcenter-cve-2021-21972-scan-tool/">VMware vCenter CVE-2021-21972 Scanner</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Everything You Need To Know To Get Started Logging PowerShell</title>
		<link>/2019/10/everything-you-need-to-know-to-get-started-logging-powershell/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Mon, 07 Oct 2019 00:15:30 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Pen Testing]]></category>
		<category><![CDATA[PowerShell/Scripting]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[4103]]></category>
		<category><![CDATA[4104]]></category>
		<category><![CDATA[Downgrade Attacks]]></category>
		<category><![CDATA[ELK]]></category>
		<category><![CDATA[Get-PSEventLogSize]]></category>
		<category><![CDATA[GPO]]></category>
		<category><![CDATA[Group Policy]]></category>
		<category><![CDATA[Module]]></category>
		<category><![CDATA[Obfuscated]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[Restricted]]></category>
		<category><![CDATA[Script block]]></category>
		<category><![CDATA[SD]]></category>
		<category><![CDATA[Security Descriptor]]></category>
		<category><![CDATA[Tool]]></category>
		<category><![CDATA[Transcription]]></category>
		<guid isPermaLink="false">/?p=4432</guid>

					<description><![CDATA[<p>Intro Recently, I have been spending a lot of time researching and working with PowerShell logging. Since PowerShell is readily available (built-in to the OS) and has an assortment of functionality that can be used across the entire kill chain right out of the box, it is an ideal candidate for virtually any type of [&#8230;]</p>
The post <a href="/2019/10/everything-you-need-to-know-to-get-started-logging-powershell/">Everything You Need To Know To Get Started Logging PowerShell</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
	</channel>
</rss>
