<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Developer hearted / Relational minded : Custom Security</title><link>http://blogs.msdn.com/jenss/archive/tags/Custom+Security/default.aspx</link><description>Tags: Custom Security</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Obfuscation is not a security feature – Spoofing the APP_NAME</title><link>http://blogs.msdn.com/jenss/archive/2008/05/06/obfuscation-is-not-a-security-feature-spoofing-the-app-name.aspx</link><pubDate>Tue, 06 May 2008 11:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8462463</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8462463.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8462463</wfw:commentRss><description>SQL Server 2005 introduced an interesting and long demanded feature, the LOGON triggers. First only defined via server event triggers, it has become more and more popular in same scenarios to prevent users with a certain machine environment accessing...(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/05/06/obfuscation-is-not-a-security-feature-spoofing-the-app-name.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8462463" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/Custom+Security/default.aspx">Custom Security</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server/default.aspx">SQL Server</category><category domain="http://blogs.msdn.com/jenss/archive/tags/T-SQL/default.aspx">T-SQL</category><category domain="http://blogs.msdn.com/jenss/archive/tags/.Net/default.aspx">.Net</category></item><item><title>Custom Security in SQL Server Analysis Services 2005/2008</title><link>http://blogs.msdn.com/jenss/archive/2008/03/05/custom-security-in-sql-server-analysis-services-2005-2008.aspx</link><pubDate>Wed, 05 Mar 2008 11:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8049150</guid><dc:creator>Jens K. Suessmeyer</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/jenss/comments/8049150.aspx</comments><wfw:commentRss>http://blogs.msdn.com/jenss/commentrss.aspx?PostID=8049150</wfw:commentRss><description>Sometime you might be stuck in a situation for Analysis Services where you have to pull of security information from an external system to get the information about dimension or cell security. Implementing that is not that hard as you might think of....(&lt;a href="http://blogs.msdn.com/jenss/archive/2008/03/05/custom-security-in-sql-server-analysis-services-2005-2008.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8049150" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2008/default.aspx">SQL Server 2008</category><category domain="http://blogs.msdn.com/jenss/archive/tags/Custom+Security/default.aspx">Custom Security</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+2005/default.aspx">SQL Server 2005</category><category domain="http://blogs.msdn.com/jenss/archive/tags/SQL+Server+Analysis+Services/default.aspx">SQL Server Analysis Services</category></item></channel></rss>