<?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: Selling information security to the business</title>
	<atom:link href="http://www.writingusecases.com/wordpress/index.php/archive/selling-information-security-to-the-business/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.writingusecases.com/wordpress/index.php/archive/selling-information-security-to-the-business/</link>
	<description>Tips for the Business System Analyst</description>
	<lastBuildDate>Mon, 07 Nov 2011 09:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: admin</title>
		<link>http://www.writingusecases.com/wordpress/index.php/archive/selling-information-security-to-the-business/comment-page-1/#comment-2199</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 29 Mar 2009 01:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.writingusecases.com/wordpress/?p=229#comment-2199</guid>
		<description>Steven - 

Thanks for this article!

It reminds me that when thinking of security requirements, we need to go beyond simple login, but think about the larger issues faced by the corporation. Any project can become a security risk if we do not consider corporate security goals.

Beyond that, to convince high level executives of the need for corporate security, we have to speak their language. This should always be a goal - to speak the language of the stakeholder with whom we are communicating.

We can think of implementing corporate security the same as any other project we undertake - with stakeholder needs, requirements for the project, and end users who will have to deal with whatever solution we create.</description>
		<content:encoded><![CDATA[<p>Steven &#8211; </p>
<p>Thanks for this article!</p>
<p>It reminds me that when thinking of security requirements, we need to go beyond simple login, but think about the larger issues faced by the corporation. Any project can become a security risk if we do not consider corporate security goals.</p>
<p>Beyond that, to convince high level executives of the need for corporate security, we have to speak their language. This should always be a goal &#8211; to speak the language of the stakeholder with whom we are communicating.</p>
<p>We can think of implementing corporate security the same as any other project we undertake &#8211; with stakeholder needs, requirements for the project, and end users who will have to deal with whatever solution we create.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

