<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-30T19:14:00+00:00</dc:date>

	
	<item>
		<title> Security and Reliability: A Closer Look at Penetration Testing (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20130312_security_and_reliability_a_closer_look_at_penetration_testing</guid>
		<link>https://circleid.com/posts20130312_security_and_reliability_a_closer_look_at_penetration_testing</link>
		<description><![CDATA[As noted in my first article of this series (see part one, two and three), security and reliability encompass holistic network assessments, vulnerability assessments and penetration testing. This month I'd like to go deeper into penetration testing; however, first, let's go back for a quick refresh before getting started. <a href="https://circleid.com/posts20130312_security_and_reliability_a_closer_look_at_penetration_testing">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Security and Reliability: A Closer Look at Vulnerability Assessments (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20130306_security_and_reliability_closer_look_at_vulnerability_assessments</guid>
		<link>https://circleid.com/posts20130306_security_and_reliability_closer_look_at_vulnerability_assessments</link>
		<description><![CDATA[Building on my last article about Network Assessments, let's take a closer look at vulnerability assessments. (Because entire books have been written on conducting vulnerability assessments, this article is only a high level overview.) What is a vulnerability assessment? <a href="https://circleid.com/posts20130306_security_and_reliability_closer_look_at_vulnerability_assessments">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> Security and Reliability: A Deeper Dive into Network Assessments (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20130304_security_and_reliability_a_deeper_dive_into_network_assessments</guid>
		<link>https://circleid.com/posts20130304_security_and_reliability_a_deeper_dive_into_network_assessments</link>
		<description><![CDATA[As noted in the first part of this series, Security and Reliability encompasses holistic network assessments, vulnerability assessments, and penetration testing. In this post I'd like to go deeper into network assessments. I stated last time that the phrase "network assessment" is broad. <a href="https://circleid.com/posts20130304_security_and_reliability_a_deeper_dive_into_network_assessments">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> An Introduction to Security and Reliability - What Does It Really Mean? (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20130228_introduction_to_security_and_reliability_what_does_it_really_mean</guid>
		<link>https://circleid.com/posts20130228_introduction_to_security_and_reliability_what_does_it_really_mean</link>
		<description><![CDATA[I co-authored a book in 2005, titled "Extreme Exploits: Advanced Defenses Against Hardcore Hacks." My chapters focused on securing routing protocols such as BGP, and securing systems related to DMZs, firewalls, and network connectivity. As I look back over those chapters, I realize that the basic fundamentals of network security really haven't changed much even though technology has advanced at an incredible pace. "Defense in depth" was a hot catch phrase seven years ago, and it still applies today. <a href="https://circleid.com/posts20130228_introduction_to_security_and_reliability_what_does_it_really_mean">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	
	<item>
		<title> So You Think You're Safe from DNS Cache Poisoning? (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/postsso_you_think_youre_safe_from_dns_cache_poisoning</guid>
		<link>https://circleid.com/postsso_you_think_youre_safe_from_dns_cache_poisoning</link>
		<description><![CDATA[Everyone is probably well aware of the Kashpureff-style DNS cache- poisoning exploit (I'll call this "classic cache poisoning"). For reference, see the [url=http://www.cert.org/advisories/CA-1997-22.html]original US-CERT advisory[/url] prompted by this exploit. Vendors patched their code to appropriately scrub (validate) responses so that caches could not be poisoned. For the next 7-8 years, we didn't hear much about cache poisoning. However, there was still a vulnerability lurking in the code, directly related to cache poisoning. ...On April 7, 2005, the SANS ISC (not to be confused with Internet Systems Consortium) [url=http://isc.sans.org/diary.php?date=2005-04-07]posted an update[/url] detailing how Microsoft Windows DNS servers were still being poisoned, even though the "Secure cache against pollution" option was set. The SANS ISC found that Windows DNS servers using BIND4 and BIND8 servers as forwarders were being poisoned. But how could this be? <a href="https://circleid.com/postsso_you_think_youre_safe_from_dns_cache_poisoning">More...</a>]]></description>
		<dc:date>2026-04-30T12:14:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>