{"id":158,"date":"2008-02-17T23:52:55","date_gmt":"2008-02-18T07:52:55","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/02\/17\/security-review-blogging-at-the-olympic-games\/"},"modified":"2008-02-18T22:20:30","modified_gmt":"2008-02-19T06:20:30","slug":"security-review-blogging-at-the-olympic-games","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/17\/security-review-blogging-at-the-olympic-games\/","title":{"rendered":"Security Review: Blogging at the Olympic Games"},"content":{"rendered":"<p>Summary:<br \/>\nThe International Olympic Committee will be granting Olympic athletes the right to blog at this year\u2019s summer games in China, and there will be a few interesting restrictions placed on what they can say.  In addition to the standard laws all bloggers have to conform to (copyright, etc) the athletes are prohibited from posting photographs of events, and from writing about other athletes, as well as from writing about anything that \u201cmay compromise the security, staging and organization of the games\u201d.  I\u2019m going to examine the motives of the committee in putting these restrictions in place as they may pertain to security, ignoring issues like intellectual property for now.<\/p>\n<p><!--more--><\/p>\n<p>Assets:<\/p>\n<ul>\n<li>The layout of the facilities.  This includes the location of rooms, training facilities and other parts of the buildings used by the athletes.<\/li>\n<li> The architecture of the buildings involved and any weak spots or entrances to the facilities that may not be well secured.<\/li>\n<li>The privacy of the room assignments of athletes.<\/li>\n<\/ul>\n<p>Adversaries:<\/p>\n<ul>\n<li>People targeting specific athletes or groups of athletes to cause harm.  The Olympic games have been a popular target in the past, most notably in the 1972 \u201cMunich Massacre.\u201d<\/li>\n<li>People looking to leverage internal information to alter the outcome of specific events.<\/li>\n<li>Those looking to invade the general privacy of athletes by compromising the security of the facilities.<\/li>\n<\/ul>\n<p>Weaknessess:<\/p>\n<ul>\n<li>The public nature of the Internet makes it very easy for prying eyes to find and utilize and vulnerable information posted about Olympic events.<\/li>\n<li>The games are by their nature a very public affair, which makes security from a top to bottom perspective rather difficult.<\/li>\n<li>The increased incentive to cause havoc at the Olympics due to the hugely international nature of the events, as well as the guaranteed publicity and notoriety.  Large congregations of specific groups of people make it more likely that hate groups will attack.<\/li>\n<\/ul>\n<p>Defenses:<\/p>\n<ul>\n<li>The committee has already done a significant amount to try to curb the potential damage they feel may be incurred from Olympic athletes blogging too openly.  These include the prohibition of photographs, blogging about events.<\/li>\n<li>If during the course of the games the committee finds any content that it feels could harm the security of the games, it should coordinate well with the ground security to ensure that they are able to be dynamic and responsive.<\/li>\n<li>The games committee has to balance freedom of expression with the necessary restrictions they put in place.<\/li>\n<\/ul>\n<p>Conclusion:<\/p>\n<p>The balance between allowing full freedom of expression and taking a pragmatic approach to security is a difficult one to find in this day and age.  Though it\u2019s nice that athletes will have personal blogs, it is unfortunate that restrictions need to be put in place at all.  The security that will be ensured by censoring the athletes is very much \u201csecurity by obscurity\u201d, but it may be an effective practice in circumstances like those at the Olympic games, where the security needs are very instance-specific and temporary in their nature.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Summary: The International Olympic Committee will be granting Olympic athletes the right to blog at this year\u2019s summer games in China, and there will be a few interesting restrictions placed on what they can say. In addition to the standard &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/02\/17\/security-review-blogging-at-the-olympic-games\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":41,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-158","post","type-post","status-publish","format-standard","hentry","category-security-reviews"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/41"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=158"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/158\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=158"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=158"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}