<?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>hardening | RobWillis.info</title>
	<atom:link href="/tag/hardening/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>#yolosec</description>
	<lastBuildDate>Mon, 27 Jun 2022 04:55:35 +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>Hardening SSL &#038; TLS connections on Windows Server 2008 R2 &#038; 2012 R2</title>
		<link>/2015/10/hardening-ssl-tls-connections-on-windows-server-2008-r2-2012-r2/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Wed, 21 Oct 2015 10:02:34 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Cipher]]></category>
		<category><![CDATA[DHE]]></category>
		<category><![CDATA[Disable]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[MS SQL]]></category>
		<category><![CDATA[PCI compliance]]></category>
		<category><![CDATA[qualys]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[SSL V3]]></category>
		<category><![CDATA[Suite]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[TLS 1]]></category>
		<guid isPermaLink="false">/?p=2455</guid>

					<description><![CDATA[<p>Hardening your SSL/TLS connections is a pretty common thing to do on any Windows Server running IIS and web applications that utilize HTTPS, especially if they require some sort of compliance. It is generally a good idea to do this on all of your servers though, to ensure your secure connections really are secure. On [&#8230;]</p>
The post <a href="/2015/10/hardening-ssl-tls-connections-on-windows-server-2008-r2-2012-r2/">Hardening SSL & TLS connections on Windows Server 2008 R2 & 2012 R2</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>IIS 7/7.5 Hardening SSL TLS &#8211; Windows Server 2008 R2</title>
		<link>/2013/09/iis-77-5-hardening-ssl-tls-windows-server-2008-r2/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Sat, 21 Sep 2013 00:40:52 +0000</pubDate>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[beast]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[vulnerability]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">/?p=2098</guid>

					<description><![CDATA[<p>&#160;&#160;&#160;&#160;&#160;One of the first steps you should do when deploying a new public facing web server is hardening your server&#8217;s SSL/TLS connections. Disabling vulnerable protocols, ciphers, hashes and key exchange algorithms can help mitigate the now more common exploits like the BEAST attack. By default many weaker technologies are enabled, leaving IIS traffic vulnerable and [&#8230;]</p>
The post <a href="/2013/09/iis-77-5-hardening-ssl-tls-windows-server-2008-r2/">IIS 7/7.5 Hardening SSL TLS – Windows Server 2008 R2</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
	</channel>
</rss>
