<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-2397196717839865841.post7269170463308817627..comments</id><updated>2010-08-24T11:33:45.556+10:00</updated><category term='career advice'/><category term='australian information security market'/><category term='economics'/><category term='AISA'/><category term='FUD'/><category term='sacred cows'/><category term='webappsec'/><category term='vulnerability management'/><category term='IPS'/><category term='security patching'/><category term='futurism'/><category term='DoS'/><category term='causes'/><category term='privacy'/><category term='information security governance'/><title type='text'>Comments on Infamous Agenda: What should your security team look like?</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.infamousagenda.com/feeds/7269170463308817627/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2397196717839865841/7269170463308817627/comments/default'/><link rel='alternate' type='text/html' href='http://www.infamousagenda.com/2010/08/what-should-your-security-team-look.html'/><author><name>Matthew Hackling</name><uri>http://www.blogger.com/profile/12211732838162218259</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>1</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-2397196717839865841.post-6889534078715550194</id><published>2010-08-24T11:33:45.556+10:00</published><updated>2010-08-24T11:33:45.556+10:00</updated><title type='text'>I am a firm believer that if anything, the role of...</title><content type='html'>I am a firm believer that if anything, the role of the architect should be retained in house and the roles of penetration testers should be outsourced, if anything.&lt;br /&gt;&lt;br /&gt;Firstly - architects rely heavily on relationships with stakeholders and an understanding of the business environment, IT systems and applications as well as dependencies on legacy systems. This knowledge takes a very, very long time to acquire.&lt;br /&gt;&lt;br /&gt;Secondly - penetration testing is a constantly evolving field with a strong upkeep. These skills and the people it attracts need to be very well looked after and consistently trained. Most companies lack the training budget, patience or even just the time to provide this people the care they require.&lt;br /&gt;&lt;br /&gt;Thirdly - unless the pentest involves a whitebox methodology, then the pentester needs to be removed to maintain their independence in conducting a blackbox approach. If it is whitebox, then they can be supplied the data they needs regardless. Working inhouse removes that independence.&lt;br /&gt;&lt;br /&gt;Fourthly - depending on how busy your office environment is, your pentesters might not be left alone long enough to conduct a test. Have you ever tried doing a pentest with 5+ 1 hr meetings in a given day? Trust me, it isn&amp;#39;t possible.&lt;br /&gt;&lt;br /&gt;These were my experiences in my last role. I was bought onboard to do pentesting but overtime as the demands of the role increased, found my role changing to that of an architect and almost a technical PM managing pentesters. &lt;br /&gt;&lt;br /&gt;- J.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2397196717839865841/7269170463308817627/comments/default/6889534078715550194'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2397196717839865841/7269170463308817627/comments/default/6889534078715550194'/><link rel='alternate' type='text/html' href='http://www.infamousagenda.com/2010/08/what-should-your-security-team-look.html?showComment=1282613625556#c6889534078715550194' title=''/><author><name>Jarrod</name><uri>http://www.blogger.com/profile/09705073585945953338</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='01961497227698185767'/><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.infamousagenda.com/2010/08/what-should-your-security-team-look.html' ref='tag:blogger.com,1999:blog-2397196717839865841.post-7269170463308817627' source='http://www.blogger.com/feeds/2397196717839865841/posts/default/7269170463308817627' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1926495770'/></entry></feed>
