<?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>Sampson &#38; Associates</title>
	<atom:link href="http://www.sampson-associates.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sampson-associates.com</link>
	<description>Simplifying Computers</description>
	<lastBuildDate>Tue, 10 Apr 2012 15:42:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Sample Incident Response Plan</title>
		<link>http://www.sampson-associates.com/pci/procedures-and-documentation/sample-incident-response-plan/</link>
		<comments>http://www.sampson-associates.com/pci/procedures-and-documentation/sample-incident-response-plan/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 15:42:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Procedures and Documentation]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=338</guid>
		<description><![CDATA[1)      The person who discovers the incident will call the grounds dispatch office. List possible sources of those who may discover the incident. The known sources should be provided with a contact procedure and contact list. Sources requiring contact information may be: a)      Helpdesk b)      Intrusion detection monitoring personnel c)      A system administrator d)     A [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/procedures-and-documentation/sample-incident-response-plan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Retina</title>
		<link>http://www.sampson-associates.com/tools/scanning-tools/retina/</link>
		<comments>http://www.sampson-associates.com/tools/scanning-tools/retina/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 19:29:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Scanning Tools]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=332</guid>
		<description><![CDATA[http://www.eeye.com/Products/Retina/Community# Retina Network Community, a free vulnerability scanner for up to 128 IPs gives you powerful vulnerability assessment across your entire environment. With Retina Network Community you can: Reduce risk and improve security with complete vulnerability scanning across operating systems, applications, devices, and virtual environments. Comprehensive vulnerability database that includes zero-days and is continually updated [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/tools/scanning-tools/retina/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Lawsuit</title>
		<link>http://www.sampson-associates.com/pci/pci-lawsuit/</link>
		<comments>http://www.sampson-associates.com/pci/pci-lawsuit/#comments</comments>
		<pubDate>Thu, 12 Jan 2012 16:03:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=330</guid>
		<description><![CDATA[Wired has an article outlining a new lawsuit started by a merchant regarding fines levied by Visa and Mastercard after they have determined a breach of security in the merchants systems. The merchant states that they had no way of disputing the allegations that there was a breach of security allowing card numbers to be [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/pci-lawsuit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building a hardened LAMP web server.</title>
		<link>http://www.sampson-associates.com/troubleshooting/building-a-hardened-lamp-web-server/</link>
		<comments>http://www.sampson-associates.com/troubleshooting/building-a-hardened-lamp-web-server/#comments</comments>
		<pubDate>Sun, 08 Jan 2012 20:19:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Tips, Tricks, and Troubleshooting]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=281</guid>
		<description><![CDATA[Here we will cover some steps you can take to make sure that your LAMP (Linux, Apache, MySQL, PHP) server is secure. Ideally you would not normally run all 3 components on the same server, but in some cases it is overkill to separate them. For example this particular site is hosted on a virtual [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/troubleshooting/building-a-hardened-lamp-web-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ActiveMQ Starved DB Connections</title>
		<link>http://www.sampson-associates.com/troubleshooting/activemq-starved-db-connections/</link>
		<comments>http://www.sampson-associates.com/troubleshooting/activemq-starved-db-connections/#comments</comments>
		<pubDate>Thu, 05 Jan 2012 22:01:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Tips, Tricks, and Troubleshooting]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=308</guid>
		<description><![CDATA[This is indicated by the following error: 2011-12-18 01:25:29,132 [erSimpleAppMain] WARN JDBCPersistenceAdapter - Could not get JDBC connection: Network error IOException: Connection refused: connect java.sql.SQLException: Network error IOException: Connection refused: connect at net.sourceforge.jtds.jdbc.ConnectionJDBC2.(ConnectionJDBC2.java:410) at net.sourceforge.jtds.jdbc.ConnectionJDBC3.(ConnectionJDBC3.java:50) at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184) at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188) at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137) at org.apache.activemq.store.jdbc.TransactionContext.getConnection(TransactionContext.java:58) at org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter.doGetLastMessageStoreSequenceId(DefaultJDBCAdapter.java:159) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.getLastMessageBrokerSequenceId(JDBCPersistenceAdapter.java:230) at org.apache.activemq.broker.region.DestinationFactoryImpl.getLastMessageBrokerSequenceId(DestinationFactoryImpl.java:145) at org.apache.activemq.broker.region.RegionBroker.(RegionBroker.java:122) at org.apache.activemq.broker.jmx.ManagedRegionBroker.(ManagedRegionBroker.java:99) at org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:1830) [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/troubleshooting/activemq-starved-db-connections/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using NTLM authentication with Jira 4.4</title>
		<link>http://www.sampson-associates.com/troubleshooting/using-ntlm-authentication-with-jira-4-4/</link>
		<comments>http://www.sampson-associates.com/troubleshooting/using-ntlm-authentication-with-jira-4-4/#comments</comments>
		<pubDate>Thu, 05 Jan 2012 21:50:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Tips, Tricks, and Troubleshooting]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=305</guid>
		<description><![CDATA[This one took me a while to find so I am going to repost it here. Unfortunately with the newer version of Jira you can not leave the username/password blank on the db configuration screen. http://confluence.atlassian.com/pages/viewpage.action?pageId=262471708 &#160; Symptoms During startup JIRA throws a BlankStringArgumentException. The database connection doesn&#8217;t work. The following appears in the atlassian-jira.log: [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/troubleshooting/using-ntlm-authentication-with-jira-4-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network Diagram</title>
		<link>http://www.sampson-associates.com/pci/network-diagram/</link>
		<comments>http://www.sampson-associates.com/pci/network-diagram/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 17:38:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Procedures and Documentation]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=291</guid>
		<description><![CDATA[Here is a very simple network diagram showing the physical connections from the internet to the various network segments. You will notice that there are 3 distinct zones, each separated from the others with a firewall. This is required by PCI standards. Only the DMZ should have direct access to and from the internet the [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/network-diagram/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Security Tasks Calendar</title>
		<link>http://www.sampson-associates.com/pci/security-tasks-calendar/</link>
		<comments>http://www.sampson-associates.com/pci/security-tasks-calendar/#comments</comments>
		<pubDate>Mon, 02 Jan 2012 17:20:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Procedures and Documentation]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=286</guid>
		<description><![CDATA[The following tasks should be conducted on a periodic basis. Probably the best way to do this is to setup appointments in your calendar software. Each time a task is completed it should be documented with a ticket in your ticketing system (for example Mantis) and signed off by at least two different parties. &#160; [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/security-tasks-calendar/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI Section 1.3</title>
		<link>http://www.sampson-associates.com/pci/pci1/pci-section-1-3/</link>
		<comments>http://www.sampson-associates.com/pci/pci1/pci-section-1-3/#comments</comments>
		<pubDate>Tue, 15 Nov 2011 17:22:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[PCI Section 1]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=262</guid>
		<description><![CDATA[1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment. 1.3 Examine firewall and router configurations—including but not limited to the choke router at the Internet, the DMZ router and firewall, the DMZ cardholder segment, the perimeter router, and the internal cardholder network segment—to determine that there is [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/pci1/pci-section-1-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Section 1.2</title>
		<link>http://www.sampson-associates.com/pci/pci1/pci-section-1-2/</link>
		<comments>http://www.sampson-associates.com/pci/pci1/pci-section-1-2/#comments</comments>
		<pubDate>Mon, 14 Nov 2011 20:43:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[PCI Section 1]]></category>

		<guid isPermaLink="false">http://www.sampson-associates.com/?p=242</guid>
		<description><![CDATA[1.2 Build firewall and router configurations that restrict connections between untrusted networks and any system components in the cardholder data environment. Note: An ―untrusted network is any network that is external to the networks belonging to the entity under review, and/or which is out of the entity&#8217;s ability to control or manage. 1.2.1 Restrict inbound [...]]]></description>
		<wfw:commentRss>http://www.sampson-associates.com/pci/pci1/pci-section-1-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

