{"id":65,"date":"2008-09-05T15:55:22","date_gmt":"2008-09-05T15:55:22","guid":{"rendered":"http:\/\/securitynirvanablog.wordpress.com\/?p=65"},"modified":"2008-09-05T15:55:22","modified_gmt":"2008-09-05T15:55:22","slug":"googleandthefivestagesofgrief","status":"publish","type":"post","link":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/2008\/09\/googleandthefivestagesofgrief\/","title":{"rendered":"Google and the Five Stages of Grief"},"content":{"rendered":"<p>This week Google has announced the Chrome browser. I tried it. It is ok for now \u2013 not great \u2013 but ok. It\u2019s fast and clean but missing some key features and many sites still don\u2019t work with it. I think the importance of this Chrome browser is what it tells us about Google\u2019s plans for the future \u2013 applications will come from the Web and run inside a browser. This is not a new concept \u2013 many of the applications that we use today are web-based.\u00a0 Think about Gmail, Salesforce.com, web-based office suites, YouTube, etc. Chrome just makes it clearer \u2013 forget about desktop applications, they are something of the past.<\/p>\n<p>There is a slightly more subtle implication, but to me a far more important one. Google and the likes of Google are establishing a direct relationship with the enterprise end user, bypassing the traditional IT-department controls over which applications are used and who can use them. The IT department only needs to provide the pipes. Google will take care of the rest. And speaking of pipes \u2013 that DS3 link you have isn\u2019t big enough. It needs to be upgraded - quickly! Google needs you to have more bandwidth. With everything coming in on ports 80 and 443 to the browser, QoS doesn\u2019t work. So, more bandwidth please.<\/p>\n<p>The migration of applications from the enterprise data center to Google and Salesforce.com, accompanied by the corresponding shift of information from the data center to the Internet is slowly changing the IT department\u2019s role. It also changes the security risks that need to be resolved. When users have the ability to choose the applications they use, when data resides outside the corporate network, and when everyone can use any application and access data wherever they are in the world \u2013 we are dealing with a completely different beast than we are used to!<\/p>\n<p>So, what can the IT department do about it? First they need to go through the five stages of grief \u2013<\/p>\n<p>1) Denial (our users are using these applications? Nah!);<br \/>\n2) Anger (our users are using these applications? WTF!);<br \/>\n3) Bargaining (hey, if you stop using these applications we will upgrade your computer);<br \/>\n4) Depression (I can\u2019t believe our users are using these applicationsL);<br \/>\n5) Acceptance (fine, are users really using these applications \u2013 let\u2019s deal with it).<\/p>\n<p>At that point, just deal with it. Put controls in place to allow you to determine who can use which application and put security measures in place to protect the use of these applications. How to do it? Sorry. I cannot promote my company\u2019s products in my blog so I cannot answer this question\u2026<\/p>\n<p>Nir.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This week Google has announced the Chrome browser. I tried it. It is ok for now \u2013 not great \u2013 but ok. It\u2019s fast and clean but missing some key features and &hellip;<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5],"tags":[12],"coauthors":[],"class_list":["post-65","post","type-post","status-publish","format-standard","hentry","category-firewall","tag-data-center"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/65","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/comments?post=65"}],"version-history":[{"count":0,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/posts\/65\/revisions"}],"wp:attachment":[{"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/media?parent=65"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/categories?post=65"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/tags?post=65"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/origin-researchcenter.paloaltonetworks.com\/blog\/wp-json\/wp\/v2\/coauthors?post=65"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}