<?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>The Control Policy Group &#187; software security</title>
	<atom:link href="http://www.controlpolicy.com/category/software-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.controlpolicy.com</link>
	<description>Data security the way you run your business</description>
	<lastBuildDate>Mon, 06 Jun 2011 12:35:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>The biggest bugs hide in the cracks left by your system integrator</title>
		<link>http://www.controlpolicy.com/2008/06/the-biggest-bugs-are-hiding-in-the-cracks/</link>
		<comments>http://www.controlpolicy.com/2008/06/the-biggest-bugs-are-hiding-in-the-cracks/#comments</comments>
		<pubDate>Sun, 22 Jun 2008 18:04:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[software security]]></category>
		<category><![CDATA[CIO]]></category>
		<category><![CDATA[CTO]]></category>
		<category><![CDATA[CVSS]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[systems integration]]></category>

		<guid isPermaLink="false">http://www.controlpolicy.com/?p=14</guid>
		<description><![CDATA[The biggest bugs are hiding in the system integration interfaces your integration team glued on the day before delivery. They go home, you get fired. Perhaps you have been in this situation before: You&#8217;re a CIO/VP IT/IT manager and you&#8217;re preparing to implement a packaged business application &#8211; for example a new CRM system. Something [...]]]></description>
			<content:encoded><![CDATA[<p>The biggest bugs are hiding in the system integration interfaces your integration team glued on the day before delivery. They go home, you get fired.</p>
<p><span id="more-14"></span></p>
<p>Perhaps you have been in this situation before:</p>
<p>You&#8217;re a CIO/VP IT/IT manager and you&#8217;re preparing to implement a packaged business application &#8211; for  example a new CRM system. Something in the back of your mind says that the vendor&#8217;s development organization is probably not a lot different than yours (although you hope they&#8217;ve thought through the security issues first). What should you do?</p>
<ul>
<li>First inspect and penetration-test the system using black-box testing.</li>
<li> Then, using white-box testing &#8211;  assess infrastructure components, database interfaces and Web applications for vulnerabilities using our Legacy Risk Analysis Loop technique.</li>
<li>We will help you identify fault-prone modules in your particular operation and evaluate those modules with the most impact on system reliability and downtime.</li>
<li> We can go in and perform an onsite audit of the vendor secure software development practices during your RFP/RFI/pre-purchase stages.</li>
</ul>
<p>This process helps give your organization a much better picture of software defects  before you send the vendor the purchase order. Our Web collaboration tool supports continuous risk analysis and management with two main applications: a knowledge base and issue tracker:</p>
<p>The database of standard CVSS scores for components and CLASP problem types classifications is always available for the entire organization. Users can add new entities and modify scores as the business environment changes. By using an  issue tracker you can see a:</p>
<ul>
<li> A consistent thread of requests, changes and open action items during the risk analysis process and in particular in the Validate findings step</li>
<li> An Updated implementation status of countermeasures.</li>
<li>Real-time status tracking where unlike email, issues cannot get lost or be ignored!</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.controlpolicy.com/2008/06/the-biggest-bugs-are-hiding-in-the-cracks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Eliminating software vulnerabilities at the source</title>
		<link>http://www.controlpolicy.com/2008/04/buggy-software-is-insecure-software/</link>
		<comments>http://www.controlpolicy.com/2008/04/buggy-software-is-insecure-software/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 17:51:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[software security]]></category>

		<guid isPermaLink="false">http://www.controlpolicy.com/?p=13</guid>
		<description><![CDATA[Tight development schedules often create serious software vulnerabilities. The CEO committed to shipping June 1, the VP engineering is under the gun, the programmers know they are cutting corners, your resellers are getting ready to jump ship to your latest competitor. Is it worth it, knowing that the cost of fixing a bug in production [...]]]></description>
			<content:encoded><![CDATA[<p>Tight development schedules often create serious software vulnerabilities.</p>
<p>The CEO committed to shipping June 1, the VP engineering is under the gun, the programmers know they are cutting corners, your resellers are getting ready to jump ship to your latest competitor. Is it worth it, knowing that the cost of fixing a bug in production software is 100X the cost of fixing it during the implementation process?</p>
<p>How can you eliminate vulnerabilities in your software at the source?</p>
<p><span id="more-13"></span></p>
<p>We can help you:</p>
<p>* Eliminate those minor security releases that put a huge dent in your ship schedule and damage hard-earned customer equity.<br />
* Proactively control vulnerabilities and create a disclosure process with your customers that makes security an asset not a liability.<br />
* We can help you to improve your work practices in the software development life cycle by training and helping you build a team that can sustain quality.<br />
o Learn how to reduce avoidable rework<br />
o Learn how to reliably identify fault-prone modules in a company&#8217;s particular operation<br />
o Learn how to identify modules with the most impact on system reliability and downtime<br />
o Learn how to develop sustaining metrics for defect reduction<br />
o Train your application programmers in best security practices and help them see themselves as part of an integrated company-wide commitment to quality software.<br />
o Help your organization choose and implement disciplined practices such as Watts Humphrey&#8217;s PSP (Personal Software Process) and TSP (Team Software Process) that can have high ROI in defect reduction in new software development.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.controlpolicy.com/2008/04/buggy-software-is-insecure-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

