<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx</link><description>Back when the spam was spiraling out of control, I configured my blog to close comments after 90 days. I’ve removed the limitation now, for two reasons: the spam is under control, and I wanted to reply to a comment made to my post on IPsec/IPv6 direct</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3137137</link><pubDate>Thu, 16 Oct 2008 11:36:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3137137</guid><dc:creator>ColonelBlinky</dc:creator><description>&lt;p&gt;Totally agree on the last paragraph, add to it based on sound strategies, policies and procedures supported by the business (ie C-Level) we are no longer part of a Break/Fix department living in a place with no sign of daylight, but an intergral business unit.&lt;/p&gt;
&lt;p&gt;CB&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3137250</link><pubDate>Thu, 16 Oct 2008 16:22:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3137250</guid><dc:creator>Orin Thomas</dc:creator><description>&lt;p&gt;I was thinking about your comment about opionion revision in relation to philosophy of science. Scientific theories map against observations of a static reality - that is reality doesn't change even though the theories we use to describe it do. Information security is even more complex because the things that we are modelling in our head do not remain static - unlike the speed of light which is the same today as it was 100 years ago, the way that computers and networks interoperate does change over time. &amp;nbsp;The modelling in our heads needs constant revision because the thing that we are modelling does not remain static (and even if it did, history of science shows that things a lot of smart people once believed were fundamental truths turned out not to be so fundamentally true when someone else came along with a better explanation). Of course new evidence can suggest that one doesn't understand something as well as one thought one did, or it could mean that the thing that you did understand was actually flawed in some way. &lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3137399</link><pubDate>Thu, 16 Oct 2008 20:34:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3137399</guid><dc:creator>MikeS</dc:creator><description>&lt;p&gt;Steve: &amp;nbsp;I agree with you completely, but unfortunately I think there's one element you didn't include in your &amp;quot;thesis&amp;quot;: &amp;nbsp;the mixed-client corpnet and extranet.&lt;/p&gt;
&lt;p&gt;I understand that if all the correct (Microsoft) pieces are in place, then we can start to calm down the &amp;quot;enemy at the gates&amp;quot; approach to security. &amp;nbsp;However, even though we are thoroughly Microsoft on the inside of our company, many of the people who use our systems are NOT Microsofties, and aren't very tolerant of us telling them how they should/shouldn't configure their networks, PC's, firewalls, etc to use our connected services.&lt;/p&gt;
&lt;p&gt;Overall, I really, really like where Microsoft is going with their security technologies and emphasis, but I fear that in the near future the only people who will truly and completely benefit from this &amp;quot;new era&amp;quot; will be the folks with a self-contained corpnet that have gypsies who venture beyond the gates. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Those of us who have to deal with B2B service delivery to diverse customers will still see limited benefit from these new technologies. &amp;nbsp;The main reason? &amp;nbsp;As with any larger company, it's nearly impossible to push through such sweeping changes unless the ROI can be demonstrated. &amp;nbsp;And despite the obvious benefits to our OWN people, reconfiguring our network in such a manner would NOT generate a high-enough ROI for the beancounters to approve such a major change.&lt;/p&gt;
&lt;p&gt;So, I guess we're stuck with evolutionary (not revolutionary) baby steps in this direction. &amp;nbsp;I look forward to it, though, and to your future posts.&lt;/p&gt;
&lt;p&gt;Mike&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3138847</link><pubDate>Mon, 20 Oct 2008 04:50:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3138847</guid><dc:creator>Paul Y</dc:creator><description>&lt;p&gt;I gave up worrying about the device and netwrok several years ago. Today I have only worry about 2 things.&lt;/p&gt;
&lt;p&gt;1. Who are you, and what should you be allowed to access.&lt;/p&gt;
&lt;p&gt;2. How do I manage the bandwidth. &lt;/p&gt;
&lt;p&gt;Devices don't access data, the most they can damage is point 2. Bandwidth impacts are irritating, but not long term critical. Data loss is the problem, and it's device and network agnostic. &lt;/p&gt;
&lt;p&gt;Of course - there is the problem of sensitive data accessed on an untrusted device, and that device using those credentials or storing that data. I haven't seen ANY good answers for this space yet. &lt;/p&gt;
&lt;p&gt;Paul&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3140022</link><pubDate>Wed, 22 Oct 2008 00:11:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3140022</guid><dc:creator>Mikko</dc:creator><description>&lt;p&gt;Hi Steve&lt;/p&gt;
&lt;p&gt;I saw your demo at teched US and it was interesting and cool and as MikeS says it works if you have all the MS part in place... this should however not be the only way of access, you can have the opposite as well with terminal server technology where no data ever leaves the data center and no client ever has straight connection to the data center. So for your trusted MS clients you could use the &amp;quot;new&amp;quot; way and for the rest you could use the TS way or Citrix if you prefer that. one don't have to rule out the other, witch is a bit of the feeling you get when you are so exited about this &amp;quot;new&amp;quot; thing Steve :-)&lt;/p&gt;
&lt;p&gt;Regards.&lt;/p&gt;
&lt;p&gt;Mikko&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3140194</link><pubDate>Wed, 22 Oct 2008 07:58:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3140194</guid><dc:creator>Marta Guillen</dc:creator><description>&lt;p&gt;Mr. Steve,&lt;/p&gt;
&lt;p&gt;I have to appologize for using this way of communication with You, but after hours and hours of searching the Web for technical support in order to get help and solutions to my problem, I bumped into Your blog which I found very interesting.&lt;/p&gt;
&lt;p&gt;I am facing a security problem, where somebody has stolen passwords for old hotmail accounts of mine and is using them to harass me and harm me in many ways.&lt;/p&gt;
&lt;p&gt;I don't seem to be able to find answers anywhere and don't know how to stop it. Would You be so kind to help me with this problem if you could?&lt;/p&gt;
&lt;p&gt;Thank you very much, Best Regards.&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3140424</link><pubDate>Wed, 22 Oct 2008 20:08:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3140424</guid><dc:creator>Steve Riley</dc:creator><description>&lt;p&gt;MikeS-- true, direct connect works best when the clients are Windows. However, we can still support heterogeneous environments with third-party support for NAP and group policy provided by partner-created add-ons. And for those instances like you mentioned -- you simply can't make configuration decisions about computers you don't own -- there's always Terminal Server. In the next security newsletter, I'll have an article that covers this briefly.&lt;/p&gt;
&lt;p&gt;Mikko-- again, I'm not discounting Terminal Server; indeed, it's a critical part of the complete design. In the detailed documention I intend to start writing later, I will include that.&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3140425</link><pubDate>Wed, 22 Oct 2008 20:10:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3140425</guid><dc:creator>Steve Riley</dc:creator><description>&lt;p&gt;Marta-- I'm sorry but there's not a whole lot I can do to help you here. How do you know your passwords have been stolen? What evidence can you describe that supports this? What harassment are you receiving?&lt;/p&gt;
&lt;p&gt;Perhaps the best thing to do is simply close those accounts down. Log into them, change their passwords, log out, and never check them again. Eventually (I think after 90 days) they will deactive themselves.&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3149991</link><pubDate>Sun, 09 Nov 2008 16:42:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3149991</guid><dc:creator>gbromage</dc:creator><description>&lt;p&gt;Steve, I did enjoy your presentation at TechEd EMEA in Barcelona on this.&lt;/p&gt;
&lt;p&gt;I still have a concern over the portion of &amp;quot;Validate the health of machines initiating incoming connections and remediate if necessary &amp;quot;&lt;/p&gt;
&lt;p&gt;Validating the health would mean validating again known threats, surely? &amp;nbsp;It's the unknown ones that concern me more.&lt;/p&gt;
&lt;p&gt;I would think that there is a risk that people might make a basic assumption that a &amp;quot;trusted&amp;quot; client is automatically trust-worthy. &lt;/p&gt;
&lt;p&gt;A zero-day exploit would not be picked up by health certificate, and once the client is compromised that negates the BitLocker and client-side firewall mitigations.&lt;/p&gt;
&lt;p&gt;Further, if a client was root-kitted, it would not be detected by a server-side validation because how would the server tell, if the client (at the kernel level) is unaware that it has been compromised. &amp;nbsp;This could lead to an administrator assuming a trusted client is safe (for a given definition of &amp;quot;safe&amp;quot;) and exposing more information then they should.&lt;/p&gt;
&lt;p&gt;It might be better to still consider these clients as manageable, but inherently untrusted.&lt;/p&gt;
&lt;p&gt;I do realise that this is more of an implementation/assumption risk than an inherant design flaw, but it does still need to be considered.&lt;/p&gt;
&lt;p&gt;P.S. - there's comment spam above.....&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3155961</link><pubDate>Wed, 19 Nov 2008 00:16:50 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3155961</guid><dc:creator>Steve Riley</dc:creator><description>&lt;p&gt;gbromage-- No, the validation isn't against threats, but rather it's validating that the computer is configured the way you want before a connection is made. NAP gives you some of this, SCCM is more thorough (mostly through inventorying).&lt;/p&gt;
&lt;p&gt;No configuration can completely protect you against zero-day exploits and rootkits. Most of these have to run as local admin to spread beyond themselves; that's why it's important that people run as standard user and that UAC remain enabled.&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3157184</link><pubDate>Fri, 21 Nov 2008 00:38:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3157184</guid><dc:creator>Sanjay Tandon</dc:creator><description>&lt;p&gt;What the mind doesn't know, the eyes can't see. &lt;/p&gt;
&lt;p&gt;Corollary: If you don't know what attack surface you're exposed to, how can you adequately defend yourself?&lt;/p&gt;
&lt;p&gt;Further: If your people don't know what they're protecting your organization against, they can't adequately protect you. &lt;/p&gt;
&lt;p&gt;In other words: ...&lt;/p&gt;
&lt;p&gt;Know what I mean? :-)&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3157404</link><pubDate>Fri, 21 Nov 2008 10:16:28 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3157404</guid><dc:creator>.NET Library Developer</dc:creator><description>&lt;p&gt;You are doing a great job. Thank you. &lt;/p&gt;
&lt;p&gt;P.S. Are you checking your comments? There are several ads comments posted in last two days. &lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3162259</link><pubDate>Mon, 01 Dec 2008 09:10:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3162259</guid><dc:creator>Steve Riley</dc:creator><description>&lt;p&gt;Thanks much ... And yeah, I know, the blog spam is getting bad again. I can't believe that there's any kind of economic gain from it, I just don't get it.&lt;/p&gt;
</description></item><item><title>re: Comments, administrivia, and the future of the “infosec professional”</title><link>http://blogs.technet.com/steriley/archive/2008/10/15/comments-administrivia-and-the-future-of-the-infosec-professional.aspx#3162675</link><pubDate>Tue, 02 Dec 2008 05:44:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3162675</guid><dc:creator>bred</dc:creator><description>&lt;p&gt;it's nice site!!! &amp;lt;a href=&amp;quot; &lt;a rel="nofollow" target="_new" href="http://www.scam.com/member.php?u=103405"&gt;http://www.scam.com/member.php?u=103405&lt;/a&gt; &amp;quot;&amp;gt;adipex cheap&amp;lt;/a&amp;gt; &amp;nbsp;6317 &lt;/p&gt;
</description></item></channel></rss>