<?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/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-3904462731148724809</id><updated>2026-01-23T00:25:51.072-08:00</updated><category term="Security"/><category term="Compliance"/><category term="CISO"/><category term="GRC"/><category term="Risk"/><category term="APT"/><category term="ATM"/><category term="Barnaby Jack"/><category term="Cyber criminal"/><category term="EXIF"/><category term="Hacking"/><category term="IT-GRC"/><category term="ITGRC"/><category term="Integration"/><category term="Jackpotting"/><category term="Location tag"/><category term="Lockheed"/><category term="RIP"/><category term="RSA breach"/><category term="Risk Management"/><category term="Sony"/><category term="Threat"/><category term="Trend"/><category term="Vulnerability"/><category term="breach"/><category term="checkin"/><category term="geolocation tagging"/><category term="iPhone"/><category term="iphone geo location tagging"/><category term="metadata"/><category term="photo tags"/><category term="place"/><category term="privacy"/><category term="tag"/><title type='text'>Security</title><subtitle type='html'>&lt;b&gt;&quot;Those who can see the Invisible can do the Impossible&quot;&lt;/b&gt;</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>8</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-8238512729734834615</id><published>2013-08-15T18:11:00.003-07:00</published><updated>2013-08-15T18:16:24.121-07:00</updated><title type='text'>Will we ever learn? Big Data: Same security issues different technology</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
One thing stuck with me over the years that my history professor told me. &quot;Only thing from History we have learned is that we have never learned anything from History&quot;&lt;br /&gt;
&lt;br /&gt;
Think about that for a moment and now let me provide you the context. Remember 1980&#39;s when Internet was hot new thing and people were just so excited about the new frontier. We never thought about security. Fast forward in 1990&#39;s we got this amazing application servers which serves up content to the user. We never thought about security when we developed those.&lt;br /&gt;
Then we did the same thing with new protocols and services we developed on top of the existing infrastructure. Then to secure Network, Operating System, Applications and databases we started bolting on the security such as Firewall, IPS (Host and network), Web application firewalls, Database monitoring and virtual patching and so on that resulted in &quot;Good Enough&quot; Security.&lt;br /&gt;
&lt;br /&gt;
I am sure right now you are frowning at the use of word &quot;Good Enough&quot; security, because definition of that is very subjective and depends on the person to person and title to title.&lt;br /&gt;
&lt;br /&gt;
Everytime we come up with new shiny toy we look at the business benefits of the toy, forget about the security and then all hell break lose when that toy is ubiquitous.&lt;br /&gt;
&lt;br /&gt;
Big Data is going through the same cycle. Everyone wants to implement Hadoop and do something with it. They want to bring in every single click , every single network flow and every single repository to uncover the hidden information in the data.&lt;br /&gt;
&lt;br /&gt;
Very seldom companies are thinking about security of this huge data set which contains personally identifiable information (PII), Credit card information. Just because it is in HDFS doesn&#39;t make it secure. What about encrypting that information? How many of you are actually doing it? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You might think that SQL-injection type of attacks are only for the databases. With Big Data comes MDX injection. Concept remains the same, name changes ! You should definitely read the paper on MDX injection that was presented at BlackHat 2013. Paper can be found &lt;a href=&quot;https://media.blackhat.com/us-13/US-13-Chastuhin-With-BIGDATA-comes-BIG-responsibility-WP.pdf&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
In summary, if you are pen tester, don&#39;t get blinded by shiny big data platforms. If you are an auditor your audit checklist still remains the same, if you are a developer your considerations are still the same about bound checking, input sanitation, and other secure application development practices.&lt;br /&gt;
&lt;br /&gt;
This is our chance to learn something from history and instead of waiting for someone to bolt security on top of the platform we incorporate security within the platform. &lt;br /&gt;
If you want to take away one thing from this post then here it is...&lt;br /&gt;
1. BIG DATA platform is still growing and we can embed security in the platform.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/8238512729734834615/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/8238512729734834615?isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/8238512729734834615'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/8238512729734834615'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2013/08/will-we-ever-learn-big-data-same.html' title='Will we ever learn? Big Data: Same security issues different technology'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-7759470240056381906</id><published>2013-07-26T12:51:00.000-07:00</published><updated>2013-07-27T00:02:51.206-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="ATM"/><category scheme="http://www.blogger.com/atom/ns#" term="Barnaby Jack"/><category scheme="http://www.blogger.com/atom/ns#" term="Jackpotting"/><category scheme="http://www.blogger.com/atom/ns#" term="RIP"/><title type='text'>RIP Barnaby Jack )-:</title><content type='html'>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
It is sad that I am writing this post after a long time on such a bad day. I recently learned from&amp;nbsp; twitter that Barnaby Jack passed away. I am hoping its a prank ,&amp;nbsp; I am hoping its not true, I am hoping he would show up in his presentation at Blackhat.&lt;br /&gt;
&lt;br /&gt;
Barnaby requires no introduction, he hacked away Insulin pumps, ATMs, Pacemakers and all sorts of embedded devices. &lt;br /&gt;
&lt;br /&gt;
My eyes are wet while writing this post. I vividly remember while he was a part of Trace team at McAfee. Inspite of his deep insights and knowledge in hardware hacking and hacking in general , he was extremely humble. I remember when asked about hacking the hardware, he said &quot;Just get the soldering iron and Nitric acid mate&quot;&lt;br /&gt;
&lt;br /&gt;
I had privilege of discussing couple things and partying with him at Blackhat. It was an honor to know him and no words can do justice to his contribution to the security community.&lt;br /&gt;
&lt;br /&gt;
I would like to link his famous Jackpotting presentation at Defcon18. My deepest condolences to his family and friends. It is a huge loss and only time can make things little easier. RIP Barnaby. You will be missed. I can&#39;t believe that you are gone. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&amp;nbsp;&lt;iframe allowfullscreen=&#39;allowfullscreen&#39; webkitallowfullscreen=&#39;webkitallowfullscreen&#39; mozallowfullscreen=&#39;mozallowfullscreen&#39; width=&#39;320&#39; height=&#39;266&#39; src=&#39;https://www.youtube.com/embed/YsXLwdw76-Y?feature=player_embedded&#39; frameborder=&#39;0&#39;&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/7759470240056381906/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/7759470240056381906?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/7759470240056381906'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/7759470240056381906'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2013/07/rip-barnaby-jack.html' title='RIP Barnaby Jack )-:'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-6044248208631423892</id><published>2011-06-26T17:00:00.000-07:00</published><updated>2011-06-26T17:25:16.940-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="checkin"/><category scheme="http://www.blogger.com/atom/ns#" term="EXIF"/><category scheme="http://www.blogger.com/atom/ns#" term="geolocation tagging"/><category scheme="http://www.blogger.com/atom/ns#" term="iPhone"/><category scheme="http://www.blogger.com/atom/ns#" term="iphone geo location tagging"/><category scheme="http://www.blogger.com/atom/ns#" term="Location tag"/><category scheme="http://www.blogger.com/atom/ns#" term="metadata"/><category scheme="http://www.blogger.com/atom/ns#" term="photo tags"/><category scheme="http://www.blogger.com/atom/ns#" term="place"/><category scheme="http://www.blogger.com/atom/ns#" term="privacy"/><category scheme="http://www.blogger.com/atom/ns#" term="tag"/><title type='text'>geo location tagging and IPhone :</title><content type='html'>I am sure lot of articles were written on geo location tagging of the iPhone pictures and with different opinions. For some it was convenience and for others it was privacy issue. &lt;br /&gt;
&lt;br /&gt;
I believe in having a choice. As long as users have ability to turn on or off the given feature, it shouldn&#39;t matter. However Apple crossed the line when they stored this data on the phone without user&#39;s consent or knowledge. In this blog I am primarily going to talk about extracting metadata information , (including geo location tag ) from any pictures. &lt;br /&gt;
&lt;br /&gt;
Metadata is data about a data, and in our case its data about the picture or photo itself. When was picture taken ? From Which camera it was taken? Where it was taken ? &lt;br /&gt;
&lt;br /&gt;
Why it is important to know about this ? Well to start with , we dont need to upload the pictures on facebook and twitter mindlessly because it contains lot more information about you and your device than you think.&lt;br /&gt;
&lt;br /&gt;
Another reason is that, same technique can be used to exchange information secretly !  Thats cool isn&#39;t it ? I can edit the metadata and send the picture to you while for others its just a picture, the receiver will exactly know what was communicated through metadata. To make things even more hard to crack we can use encrypted message in Metadata. Though this project will be for later date, I am going to focus on retrieving information from the pictures.&lt;br /&gt;
&lt;br /&gt;
Today we are going to select any random picture and will determine its location and device identity. You ready? &lt;br /&gt;
&lt;b&gt;Pre-requisite:&lt;/b&gt;&lt;br /&gt;
If you want to have some fun, download &lt;a href=&quot;http://homepage.mac.com/aozer/EV/&quot;&gt;EXIF Viewer&lt;/a&gt;&amp;nbsp; and keep &lt;a href=&quot;http://www.worldatlas.com/aatlas/latitude_and_longitude_finder.htm&quot;&gt;world Atlas&lt;/a&gt; open in the other window.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Experiment:&lt;/b&gt;&lt;br /&gt;
To start with, take a picture from your own cell phone or select any picture from your library (preferably picture taken from your Cell phone). I have downloaded the picture as below.&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhg1tIHxZr4AQp0cZvYOSgGTc5yPsRxUxAt2n9w8ezp-O_sf9EVPQvHIfLIkx06s3d1MggQuvRXlAMLgQBdX2jt6o1Vm7qE4eQ-NINPPcvOhEItSn58eQhLfua8yq_AmDJKhCw5qzYFKgbS/s1600/photo+%25282%2529.JPG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;320&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhg1tIHxZr4AQp0cZvYOSgGTc5yPsRxUxAt2n9w8ezp-O_sf9EVPQvHIfLIkx06s3d1MggQuvRXlAMLgQBdX2jt6o1Vm7qE4eQ-NINPPcvOhEItSn58eQhLfua8yq_AmDJKhCw5qzYFKgbS/s320/photo+%25282%2529.JPG&quot; width=&quot;240&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
Now drag the picture on to your EXIF viewer and you will see information as below. Most importantly you will see device information in this case iPhone 3GS and the geo location tags where the picture was taken !&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgTfwQenlKcskktPgItspv5E181qVG9GB4Sy4mvJBhEAJ8Iy_aLrtnvO34kls6xyywjdLxNVy-lJpfG6V2Vfft7-bCJ1WTYuadi7eOmFEi4DbRKSK4TTtjuQx2lTRHaqg8wPvOnkS_F_btI/s1600/Photo_Device_geo_location.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;320&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgTfwQenlKcskktPgItspv5E181qVG9GB4Sy4mvJBhEAJ8Iy_aLrtnvO34kls6xyywjdLxNVy-lJpfG6V2Vfft7-bCJ1WTYuadi7eOmFEi4DbRKSK4TTtjuQx2lTRHaqg8wPvOnkS_F_btI/s320/Photo_Device_geo_location.jpg&quot; width=&quot;250&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1ktpZdw7sPqRLCrM15M1FB2vWJbc_JYVfWwLgEeDFRoqaeJcynHzI8W9WZxF7m_PZao5wjQJ6j7Yy6gmifU6kqvN94a-LexjbRfpvzndgjCHOWMUdbFcf1WW2stKxdSU5N_-vsdMMnCTC/s1600/Device_2_jpeg.png&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;43&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj1ktpZdw7sPqRLCrM15M1FB2vWJbc_JYVfWwLgEeDFRoqaeJcynHzI8W9WZxF7m_PZao5wjQJ6j7Yy6gmifU6kqvN94a-LexjbRfpvzndgjCHOWMUdbFcf1WW2stKxdSU5N_-vsdMMnCTC/s400/Device_2_jpeg.png&quot; width=&quot;400&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAjbq5OOeN1RwB2M-g0j03BNwR8X3grv6R4KbyvANlsWlzkX9qPlrB7eXk2YNajGbkztucrsNvYDhMVHYgTxeq9COzMbr0voxbayKKOHl12z4VLXO1BEijVLmp7DnBy-cTmyYcvtIDhFvj/s1600/Geolocation.jpeg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;34&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiAjbq5OOeN1RwB2M-g0j03BNwR8X3grv6R4KbyvANlsWlzkX9qPlrB7eXk2YNajGbkztucrsNvYDhMVHYgTxeq9COzMbr0voxbayKKOHl12z4VLXO1BEijVLmp7DnBy-cTmyYcvtIDhFvj/s400/Geolocation.jpeg&quot; width=&quot;400&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
&lt;br /&gt;
Now here comes the best part , take the coordinates in Latitude and Longitude and stick it in to World atlas. In our case it is , &amp;nbsp;Latitude N 37 34.67 and Longitude W 122 2.35&lt;br /&gt;
&lt;br /&gt;
You should see something as below. Clearly you know the location that the picture was taken in Fremont California!&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9qrPsrpXwt_s_XPbd7PZ0NGTgerR-5C0aWdRRoZTGqXfg0RI6N1hXQK6JEe7e696kJoce12SUuATmVNWqwnzlLbjYeThmda4qD150FSGYKYe3odlo7OuDUoOEAx-Ky-5Z1PVIhfILRft7/s1600/Worldatlas.jpeg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;160&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9qrPsrpXwt_s_XPbd7PZ0NGTgerR-5C0aWdRRoZTGqXfg0RI6N1hXQK6JEe7e696kJoce12SUuATmVNWqwnzlLbjYeThmda4qD150FSGYKYe3odlo7OuDUoOEAx-Ky-5Z1PVIhfILRft7/s400/Worldatlas.jpeg&quot; width=&quot;400&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
Isn&#39;t it cool ? &amp;nbsp;I am sure there are ways and means to strip the metadata from the pictures. I would let you research on it &amp;nbsp;and if you think some of the metadata strippers are worth sharing then please provide the link in the comment section.</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/6044248208631423892/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/6044248208631423892?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/6044248208631423892'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/6044248208631423892'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2011/06/geo-location-tagging-and-iphone.html' title='geo location tagging and IPhone :'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhg1tIHxZr4AQp0cZvYOSgGTc5yPsRxUxAt2n9w8ezp-O_sf9EVPQvHIfLIkx06s3d1MggQuvRXlAMLgQBdX2jt6o1Vm7qE4eQ-NINPPcvOhEItSn58eQhLfua8yq_AmDJKhCw5qzYFKgbS/s72-c/photo+%25282%2529.JPG" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-1766937556692097738</id><published>2011-06-13T13:10:00.000-07:00</published><updated>2011-06-13T13:10:50.198-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="APT"/><category scheme="http://www.blogger.com/atom/ns#" term="breach"/><category scheme="http://www.blogger.com/atom/ns#" term="Cyber criminal"/><category scheme="http://www.blogger.com/atom/ns#" term="Lockheed"/><category scheme="http://www.blogger.com/atom/ns#" term="RSA breach"/><category scheme="http://www.blogger.com/atom/ns#" term="Security"/><category scheme="http://www.blogger.com/atom/ns#" term="Sony"/><category scheme="http://www.blogger.com/atom/ns#" term="Threat"/><title type='text'>Design Inner security layers assuming outer security layers are already breached</title><content type='html'>Lockheed Martin, EMC, Sony: Design Inner Security Layer assuming Outer Layer is already breached.&lt;br /&gt;
Recent breach at Lockheed Martin, confirmed that the attacks we saw with Aurora and Stuxnet are just the beginning of the new era of the targeted attack. Now cybercriminals are executing perfect plan to get closer to the target without raising any red flags.  In case of Aurora attack, more than 30 US companies were breached. Apparently Google lost its intellectual property (IP) in this attack. Attack was identified by McAfee. We were very sure that this is not the end but the beginning of the new era and paradigm shift is required as soon as possible. &lt;br /&gt;
Sure enough, there were series of attacks, such as Night Dragon, attack on EMC which put SecureID tokens at risk, Sony, and recently Lockheed Martin. &lt;br /&gt;
Lockheed Martin is very important for USA as a defense contractor. Some of the most critical information such as the arsenal used in Afghanistan war and future military technology information are residing in Lockheed Martin network. I don’t want to speculate how the attackers were able to break in. There are multiple theories, such as Spear-Phishing, and some of the blogs and reports are correlating Lockheed Martin attack with EMC breach and attackers came in via VPN. Lockheed Martin has officially neither confirm nor denied this. So we have to wait for this information to unfold. &lt;br /&gt;
&lt;br /&gt;
However one thing is for sure, that we need paradigm shift. At McAfee we see 55,000 new malware every day. There are 2,000,000 (2 Million) malicious website detected every month. These numbers are just unmanageable by patches or blacklisting technology alone. But before we talk about solution let’s look at the anatomy of an attack. Any attack involves following three stages.  &lt;br /&gt;
1. Exploit the service or application. &lt;br /&gt;
2. Drop and execute the payload either in the memory or on the disk and &lt;br /&gt;
3. Finally get p0wned!! &lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiziEYlQUZBWY0fLbHwQOsS2WvnDyZW0cCJdkifQ-XfB3OGf7mjeNKQIpfSYQuy0XR3vg5bXzSy9jw7PP6rReDhVACiIj7tNSorlYVQRpEQFAO2_tKVJVfG1R0BSoAscJskDaDse2Lw-trg/s1600/Flow.PNG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left:1em; margin-right:1em&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;304&quot; width=&quot;400&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiziEYlQUZBWY0fLbHwQOsS2WvnDyZW0cCJdkifQ-XfB3OGf7mjeNKQIpfSYQuy0XR3vg5bXzSy9jw7PP6rReDhVACiIj7tNSorlYVQRpEQFAO2_tKVJVfG1R0BSoAscJskDaDse2Lw-trg/s400/Flow.PNG&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
 You should be able to dissect any attacks in to these three stages. Aurora, Night Dragon, Stuxnet, and possibly other future attacks.  Let me briefly explain the protection. For blacklisting solution, we need to have a signature to stop the vulnerability or the behavior based detection to identify something is wrong but behavior based detection is not 100% and signature for zero day vulnerabilities are not available. So Attackers will be able to successfully be able to go to step 2 after exploiting the “zero” day vulnerability. Don’t forget, Stuxnet used four “Zero Day” Vulnerabilities. So it is not a story from Mission impossible or Sword Fish movie. This is real. Once the vulnerability is exploited it’s time to execute payload and connect to command and control center to download some more malicious code such as keyloggers and sniffers.  &lt;br /&gt;
But with paradigm shift to application white-listing solution, you can protect against such attacks at all stages. Memory protection will prevent attacker from exploiting the vulnerability and in case attacker was successful in exploiting the vulnerability, the payload will not be able to execute from the disk or from the memory because payload is not part of the white list.  &lt;br /&gt;
It’s time to change the paradigm, and we need combination of white-list and blacklisting solution. &lt;br /&gt;
Look out for the solution which can cater to your server and desktop environment and supports *nix and windows operating system. &lt;br /&gt;
For Lockheed Martin , there is a possibility that it is linked to RSA token breach or maybe not, but we have to design our defenses in layers in such a way that while designing internal layer we are assuming that outer defense layer is already breached.  Application white-listing is definitely going to play huge role in security architecture in the years to come!  So next time when you are designing the security architecture with VPN, Firewall and two factor authentication and Antivirus , ask yourself a simple question, if there is a zero day vulnerability, will that be prevented with any of these technology?</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/1766937556692097738/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/1766937556692097738?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1766937556692097738'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1766937556692097738'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2011/06/design-inner-security-layers-assuming.html' title='Design Inner security layers assuming outer security layers are already breached'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiziEYlQUZBWY0fLbHwQOsS2WvnDyZW0cCJdkifQ-XfB3OGf7mjeNKQIpfSYQuy0XR3vg5bXzSy9jw7PP6rReDhVACiIj7tNSorlYVQRpEQFAO2_tKVJVfG1R0BSoAscJskDaDse2Lw-trg/s72-c/Flow.PNG" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-2011029366991913153</id><published>2010-06-06T15:26:00.001-07:00</published><updated>2010-06-06T15:26:25.677-07:00</updated><title type='text'>CISO, it is easier to justify security expenses than you think !</title><content type='html'>Almost every single IT-Security Managers or CISO faces three core questions when they present their case for budget.&lt;br /&gt;
1. We invested in product A last year, how are we doing with that product?&lt;br /&gt;
2. How to justify the cost of new products that are required to mitigate the new threat ? &lt;br /&gt;
3. Do I really need new product or existing product can be tweaked to mitigate new threats?&lt;br /&gt;
&lt;br /&gt;
These are very crucial&amp;nbsp; questions in getting new budget. Demonstrating the value of existing security solution and conclusively proving that CISO is&amp;nbsp; efficiently securing the organization with limited budget.&lt;br /&gt;
&lt;br /&gt;
To show value of the existing solution you have to show the report on the total threats per quarter being protected by the particular product and solution.&lt;br /&gt;
&lt;br /&gt;
To mitigate new threats , you must know&lt;br /&gt;
1. New threats which is &lt;b&gt;applicable to your&lt;/b&gt; environment. &lt;br /&gt;
2. Once new threats are identified you quickly need assessment of which assets are impacted&lt;br /&gt;
3. Finally answer to question 2 will answer which products are required, Do you need to tweak existing products or buy new product? &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Automation&lt;/b&gt; is of prime importance. No manual processes, every Monday morning you should have simple charts displaying which unprotected&amp;nbsp; new threats you should be worried about.&lt;br /&gt;
&lt;br /&gt;
For example: Company A has Antivirus and they have identified 400 new threats this quarter which are currently unprotected by AV and 50% of assets are at risk. CISO can clearly quantify the total number of threats new Network IPS product or Application whitelisting product will be able to protect the organization and reduce their risk profile.&lt;br /&gt;
&lt;br /&gt;
This is very important, quantifiable matrix to justify product procurement or tweaking of existing product&amp;nbsp; or patch deployment. &lt;br /&gt;
&lt;br /&gt;
Obviously the next question in your mind is, how to automate this ? I don&#39;t have budget nor resources to create such solution.&amp;nbsp; In that case I would recommend McAfee Risk Advisor. This product will not help you if you are not McAfee shop. However it is very easy to implement if you are existing McAfee customers with ePO and any one of the McAfee endpoint solution.&lt;br /&gt;
&lt;br /&gt;
As we know numbers never lie ! and as business demands more and more justification for the product procurement, it will be very important for CISO to create automated way to justify the expense on security. Something I would call P&amp;amp;L of Security.</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/2011029366991913153/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/2011029366991913153?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/2011029366991913153'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/2011029366991913153'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2010/06/ciso-it-is-easier-to-justify-security.html' title='CISO, it is easier to justify security expenses than you think !'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-8838270465702310456</id><published>2009-11-03T01:10:00.000-08:00</published><updated>2009-11-03T02:15:38.026-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="CISO"/><category scheme="http://www.blogger.com/atom/ns#" term="Compliance"/><category scheme="http://www.blogger.com/atom/ns#" term="Integration"/><category scheme="http://www.blogger.com/atom/ns#" term="Risk"/><category scheme="http://www.blogger.com/atom/ns#" term="Security"/><category scheme="http://www.blogger.com/atom/ns#" term="Trend"/><category scheme="http://www.blogger.com/atom/ns#" term="Vulnerability"/><title type='text'>Security Trend and Integration</title><content type='html'>&lt;span style=&quot;font-family: arial; font-size: 130%;&quot;&gt;In last 15 years, security has changed drastically. Initially security was focused on Operating System and its patches.  Windows NT Operating System + IIS 4.0 webserver spelled disaster in default configuration. By default everything will work and for security you need to run the hardening script. Advent of Internet brought altogether different perspective and outlook to the word stealing !&lt;br /&gt;
With this technology someone  in Russia can hack in to the servers in US via some zombies sitting in Germany. To prevent the attack from Internet , Firewall was developed. Best practice for firewall was to allow required protocols and services and deny everything else. Deny ANY ANY was catch all rule for every firewall.&lt;br /&gt;
As time went by hackers became more sophisticated and there came the whole new level of attacks with Firewalk and specially via TCP and IP fragmentation which could bypass the firewall. Also for the allowed services there was no security , some one can easily exploit bug in IIS, if Port 80 was allowed.&lt;br /&gt;
If you have Unicode vulnerability on IIS, then sure enough, Firewall  (Stateful or packet filter) will allow directory traversal and if IIS root is in the same logical drive as the system root , one can get the shell of remote machine.&lt;br /&gt;
Hence the advent of IDS and IPS technology to thwart these attacks on the allowed services and protocols.&lt;br /&gt;
Soon Hacker realized that Firewall and IPS both has some inherent vulnerability in its protocol stack specially with IP Fragmentation(Overlapping fragments) which can bypass the IPS and Firewalls. Many tricks were identified , and papers were written on IPS evasion techniques one of the paper was eluding IDS by Thomas H. Ptacek   and  Timothy N. Newshamand . Based on this paper Dug Song wrote Fragroute.&lt;br /&gt;
Soon Whitehat realized that IPS is not Nirvana and we required something more than IPS and Firewall.&lt;br /&gt;
Some key security players came with concept of security closer to host to avoid the typical issues with Network based security devices. Hence the Start of AV+ Hostbased IDS/IPS+Firewall.&lt;br /&gt;
If you look at the product set all the security products, except for firewall, came with the approach of identifying all the bad things which is infinite in number, on the other hand firewall denied all the bad things except for few allowed trusted sources and protocols.&lt;br /&gt;
Network based or Host based, except for firewall technology, all the other technology was based on Signature or behavior or some hybrid approach (combination of both) to identify malicious intent.&lt;br /&gt;
While Whitehats were busy securing OS and networks with these technologies, suddenly Web 2.0 and new application based attacks were identified like XSS, SQL injection and Cross-site request forgery on the application server side.&lt;br /&gt;
Clients became more and more powerful , technologies like AJAX, Java Script, Activex on the client side created whole new category of vulnerabilities which is client side vulnerabilities and were hard to detect with the scanners.&lt;br /&gt;
To reduce such attacks Application Firewall, IPS with appropriate application vulnerabilities signatures and protocol decode capabilities were introduced to the market.&lt;br /&gt;
For client side vulnerabilities scanner started adding the checks to identify key vulnerabilities in MS Office, Web browser and other client side and P2P applications.&lt;br /&gt;
Soon everyone realized that this is not enough, and came Application Whitelisting technology, which is based on the concept same as of the firewall, to allow known application to execute and disable execution of any other applications/code.&lt;br /&gt;
As I said before, conceptually we are back to square one ! Same concept as of the firewall where everything started , Allow required service and Deny everything else, this time its on the host for applications !&lt;br /&gt;
We took complete 360 degree turn and we are back to the same point.&lt;br /&gt;
As you can see the clear trend of Network to Host.&lt;br /&gt;
Firewall--&amp;gt;IDS--&amp;gt;IPS--&amp;gt;Application Proxy.&lt;br /&gt;
On Host, AV--&amp;gt;Firewall --&amp;gt;IDS/IPS--&amp;gt;Application Whitelisting&lt;br /&gt;
&lt;br /&gt;
Soon another paradigm was introduced by DLP players, of Data centric Security and new gadgets were introduced for IT, to prevent unauthorized malicious or unintentional data leakage.&lt;br /&gt;
&lt;br /&gt;
However question is if you have all these technology to secure your data, how do you integrate and identify trend in order to pro-actively identify the threats?&lt;br /&gt;
&lt;br /&gt;
Integration between these technologies is must! All the security products in the organization should create this huge ecosystem ,  with ability to share information and alerts and learn from the information and alerts. This is organization wide Integration which is must in todays challenging and evolving technology space.&lt;br /&gt;
&lt;br /&gt;
While Organization wide integration is great, I am envisaging the Inter Organization Information Sharing, Like blackhat contribute and support each other in the community, whitehat should have some way of sharing their data between organization which allows them to better prepare for the threats.&lt;br /&gt;
Having said that we are not too far away from it, I believe cloud computing will allow us to do just that !&lt;br /&gt;
Only time will tell....&lt;/span&gt;</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/8838270465702310456/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/8838270465702310456?isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/8838270465702310456'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/8838270465702310456'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2009/11/security-trend-and-integration.html' title='Security Trend and Integration'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-1380118863989884480</id><published>2009-02-21T18:38:00.000-08:00</published><updated>2009-02-21T19:34:36.055-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="CISO"/><category scheme="http://www.blogger.com/atom/ns#" term="Compliance"/><category scheme="http://www.blogger.com/atom/ns#" term="GRC"/><category scheme="http://www.blogger.com/atom/ns#" term="ITGRC"/><category scheme="http://www.blogger.com/atom/ns#" term="Risk"/><category scheme="http://www.blogger.com/atom/ns#" term="Risk Management"/><category scheme="http://www.blogger.com/atom/ns#" term="Security"/><title type='text'>Proactive and Reactive approach to Risk</title><content type='html'>&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4Z7M3fA1Gr2Q974Og3M1Ai539_ihNZH8sp9CzFxqcucPZtS6OXF4nPspyDpULdevxQsactj1dgAAk5MlA_px1NJMqLQts5MEWy85BwvVvM7Abmli6iO6ytdFF5AsJ_mSE3dsX9jm9w-hi/s1600-h/risk3.JPG&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;&lt;img id=&quot;BLOGGER_PHOTO_ID_5305449769349616338&quot; style=&quot;DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 400px; CURSOR: hand; HEIGHT: 320px; TEXT-ALIGN: center&quot; alt=&quot;&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4Z7M3fA1Gr2Q974Og3M1Ai539_ihNZH8sp9CzFxqcucPZtS6OXF4nPspyDpULdevxQsactj1dgAAk5MlA_px1NJMqLQts5MEWy85BwvVvM7Abmli6iO6ytdFF5AsJ_mSE3dsX9jm9w-hi/s400/risk3.JPG&quot; border=&quot;0&quot; /&gt;&lt;/span&gt;&lt;/a&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;&lt;br /&gt;&lt;/span&gt;&lt;div&gt;&lt;div align=&quot;center&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;Proactive and reactive approach to Risk ….&lt;/span&gt; &lt;/span&gt;&lt;/strong&gt;&lt;/div&gt;&lt;strong&gt;&lt;div align=&quot;justify&quot;&gt;&lt;br /&gt;&lt;/strong&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;Everybody is joining the bandwagon of ITGRC or GRC, if you are database Security Company or networking Product Company, all of them have their messaging around compliance. Compliance is small piece of the big picture, in my opinion big picture is RISK which drives G and C.&lt;br /&gt;Risk is what we want to manage and will decide our survival. I may be all compliant, and still have lot of Risk unaddressed or at unacceptable level.&lt;br /&gt;Risk is relatively new concept to IT and CISO/CIO has started understanding this concept but still we are light years behind financial risk managers who has very good understanding of risk and its different models (don’t look at financial stocks right now to prove me wrong ;) !!! )&lt;br /&gt;I am sure you get the point, when financial industry has been using risk since last 100 odd years versus IT has started using risk in last 5 years or may be decade before.&lt;br /&gt;Just like controls risk identification can be proactive or reactive in nature. This is not a debate about which one is better, we need both. By very nature of risk assessment, it is future prediction based on certain parameters which is nothing but “Perceived Risk”. Other is your reactive approach to risk which is backed by hard to refute numbers, for example Anti Virus incidents in last 1 year or emergency change management which can be directly correlated to Network Downtime. Based on these numbers you can associate new risk or change the existing risk and controls mitigating the risk. This is very powerful autonomous system. Perceive Risk is nothing but what you are afraid of and reactive approach will be what you should afraid of !!! This self correcting system will improve over time and will self adjust it self, its not perfect but its very powerful and effective. There is always systemic risk ! Anyone in wall street today knows about this risk , there is always a risk of system failure and no one is saved from that, since you are part of the system unless you change or create your own system, then you have some control over system risk. Like any thing in life this system is also not flawless and has its own risk, but this approach is defnintely better than just risk identification and assessment in board room for few hours.&lt;br /&gt;&lt;br /&gt;Question is how to get the reactive risk numbers? Its simple, most of the organization has Security and networking product implemented. Only required thing is product to collect the numbers from these silo solution and provide the trending. Based on trends and threshold one can definitely identify what you should be worried about, again in financial world these people have been doing this for years with VIX index, S&amp;amp;p 500 , Unemployment numbers and so on, some of them are leading indicators of things to come or some of them are lagging indicators .&lt;br /&gt;&lt;br /&gt;Apply same concept to IT and you will get similar indices for your environment, which is true only for your environment and business, since business objective for every company is different their risk appetite will obviously be different.&lt;br /&gt;&lt;br /&gt;Risk is such a fascinating topic, which involves, imaginations, math( discrete probability in math class remember ? ), Business and strategy !! Haven’t seen any topic covering so much of depth and breath.&lt;br /&gt;Proactive and reactive is just the nomenclature assuming you are identifying risk after something has happened versus you identifying the risk before something !&lt;br /&gt;However continuing from my first blog, business has all the rights to take their chances and accept the risk in order to achieve their business goals as long as Risk is acceptable. Million dollar question is who will decide what is acceptable? And what is acceptable risk ? May be good topic for my next blog….till then ….Keep watching DOW ;) Risk may reduce and then its time to buy :) &lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/1380118863989884480/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/1380118863989884480?isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1380118863989884480'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1380118863989884480'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2009/02/proactive-and-reactive-approach-to-risk.html' title='Proactive and Reactive approach to Risk'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4Z7M3fA1Gr2Q974Og3M1Ai539_ihNZH8sp9CzFxqcucPZtS6OXF4nPspyDpULdevxQsactj1dgAAk5MlA_px1NJMqLQts5MEWy85BwvVvM7Abmli6iO6ytdFF5AsJ_mSE3dsX9jm9w-hi/s72-c/risk3.JPG" height="72" width="72"/><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-3904462731148724809.post-1984117107295602797</id><published>2007-08-22T22:31:00.001-07:00</published><updated>2007-08-23T23:43:35.000-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Compliance"/><category scheme="http://www.blogger.com/atom/ns#" term="GRC"/><category scheme="http://www.blogger.com/atom/ns#" term="Hacking"/><category scheme="http://www.blogger.com/atom/ns#" term="IT-GRC"/><category scheme="http://www.blogger.com/atom/ns#" term="Security"/><title type='text'>Is fully Compliant  = Good Security ?</title><content type='html'>&lt;div style=&quot;text-align: justify;&quot;&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;B&lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;uzz&lt;/span&gt; word IT-GRC , who doesn&#39;t  know about it !! 17 billion dollar market as per Gartner report.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;You must be wondering what is this GRC acronym stands for ? why people are talking about it ?&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;I would like to take this opportunity and dwell a bit in to IT-GRC and express my thoughts on this market. Let me answer the question what GRC is , G stands for Governance, R stands for Risk and C stands for Compliance, as easy as it sounds...well not really !:).&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;Why people are talking about GRC ? Simple because Government and Compliance industry combination have created havoc for institution specially for  finance and medical insurance companies in US.  Regulations like SOX, HIPAA, GLBA, FFIEC BASELII ,PCI and what not !!! Every country has its own standards, Europe will have its own version of SOX and HIPAA .  To comply to this regulation smart marketing people came up with Frameworks, Initially BS-7799 now ISO -27001, COBIT and now I am hearing ITIL , all claiming to be master framework which can manage other frameworks regulation and standards. Each framework has its certification from which they create revenue.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;All the regulation and standards has one thing in common , Due care/Due diligence, Which means there is sufficient effort to prevent something catastrophic from happening and if fatal event happenes then organization is ready for the same. Also it takes in to account that Risk to the business is known and either it is accepted or mitigated or transferred.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;However , these giant frameworks and strict regulations are good to have but as they say &quot;Everything in Excess is Poison&quot;.  Too many regulations and too many framework will create chaos for the management and last but not least too many threats and vulnerability and hence too many RISK. Hence there is a need for GRC which can manage these many compliance to regulations.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;If we see current scenario, compliance is merely a tick mark against the requirement. Do You have IDS? Yes ...complied ! woohoo ... Well if Auditor is good he might get in to the details of log management , sometimes they do but at the end of the day BufferOverflow in .dll sounds like latin to Auditor. He will see a process, is this bufferoverflow mitigated?, and my worry is most of compliance auditors doesn&#39;t have the expertise to question the mitigation efficacy !&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;Million dollar question if I am completely compliant to say PCI regulation does it mean that I am secure ?  More often than not , answer is no. original scope of regulation is to strengthen security but the results are totally opposite !!  In the burden of so many regulations, security takes the backseat ! Multiple issues, Internal security guys are loaded with too many regulations, External auditor can not be expert in all the areas, and if you go to Defcon you will realize that no matter what you do , you are always hackable ! so why create strict regulation to compliance , its better to provide some leeway to the companies in midst of so many regulations.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;We have seen so many hacking incidence in the past , TJ MAX, and similar and   Monster being the recent.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;We will continue to be like Ostrich and will be happy looking at all the compliance reports and sending them to management to make them happy but at the end of the day it takes single Security breach to break that myth.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style=&quot;font-size:130%;&quot;&gt;&lt;span style=&quot;font-family:arial;&quot;&gt;Finally you are as good as your people. You make sure that people has required ethical and technical skills and you should be good ! No compliance standard or regulation can beat the security that you get from your loyal employees !&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://hack0r.blogspot.com/feeds/1984117107295602797/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/3904462731148724809/1984117107295602797?isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1984117107295602797'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/3904462731148724809/posts/default/1984117107295602797'/><link rel='alternate' type='text/html' href='http://hack0r.blogspot.com/2007/08/is-fully-compliat-good-security.html' title='Is fully Compliant  = Good Security ?'/><author><name>Vijay Upadhyaya</name><uri>http://www.blogger.com/profile/10061519503819130998</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry></feed>