<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: EITDR &#8211; enterprise information technology data repository</title>
	<atom:link href="http://elamb.org/eitdr-enterprise-information-technology-data-repository/feed/" rel="self" type="application/rss+xml" />
	<link>http://elamb.org/eitdr-enterprise-information-technology-data-repository/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=eitdr-enterprise-information-technology-data-repository</link>
	<description>information system security, risk management, scam research</description>
	<lastBuildDate>Sun, 27 Nov 2011 07:30:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Enterprise Mission Assurance Support Service (eMASS) &#124; elamb</title>
		<link>http://elamb.org/eitdr-enterprise-information-technology-data-repository/comment-page-1/#comment-197682</link>
		<dc:creator>Enterprise Mission Assurance Support Service (eMASS) &#124; elamb</dc:creator>
		<pubDate>Wed, 31 Aug 2011 02:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://elamb.org/eitdr-enterprise-information-technology-data-repository/#comment-197682</guid>
		<description>[...] USAF Enterprise Information Technology Data Repository (EITDR) [...]</description>
		<content:encoded><![CDATA[<p>[...] USAF Enterprise Information Technology Data Repository (EITDR) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Littlejohn</title>
		<link>http://elamb.org/eitdr-enterprise-information-technology-data-repository/comment-page-1/#comment-180995</link>
		<dc:creator>Robert Littlejohn</dc:creator>
		<pubDate>Mon, 23 Mar 2009 12:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://elamb.org/eitdr-enterprise-information-technology-data-repository/#comment-180995</guid>
		<description>Although the article above is accurate in what it says, it inferes that the certification and accreditation process is based on EITDR. I currently work at the Agency and when I first arrived I was asked if I had ever done an EITDR C&amp;A. I responded that EITDR is a data repository not a certification and accreditation process. DOD has the DIACAP and federal systems are certified and accredited according to the NIST SP800 series guidance to be FISMA compliant. The Air Force uses IT Lean SISSU (security, interoperability, supportability, sustainability, and useability) as its &quot;branded&quot; process which incorporates acquisition and DIACAP. From a DITSCAP point of view there really isn&#039;t much of an SSAA or accreditation documentation anymore. Generally the package going forward to the DAA consists of the Information Systems Plan (ISP), DIACAP Scorecard, Plan of Action and Milestones (POA&amp;M), and the CA&#039;s recommendation letter.</description>
		<content:encoded><![CDATA[<p>Although the article above is accurate in what it says, it inferes that the certification and accreditation process is based on EITDR. I currently work at the Agency and when I first arrived I was asked if I had ever done an EITDR C&amp;A. I responded that EITDR is a data repository not a certification and accreditation process. DOD has the DIACAP and federal systems are certified and accredited according to the NIST SP800 series guidance to be FISMA compliant. The Air Force uses IT Lean SISSU (security, interoperability, supportability, sustainability, and useability) as its &#8220;branded&#8221; process which incorporates acquisition and DIACAP. From a DITSCAP point of view there really isn&#8217;t much of an SSAA or accreditation documentation anymore. Generally the package going forward to the DAA consists of the Information Systems Plan (ISP), DIACAP Scorecard, Plan of Action and Milestones (POA&amp;M), and the CA&#8217;s recommendation letter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

