{"id":23,"date":"2007-12-31T09:18:36","date_gmt":"2007-12-31T17:18:36","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=23"},"modified":"2007-12-31T09:48:35","modified_gmt":"2007-12-31T17:48:35","slug":"example-security-review-4","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2007\/12\/31\/example-security-review-4\/","title":{"rendered":"Example Security Review #3"},"content":{"rendered":"

Here’s another example CSE 490K Security Review<\/a>.<\/p>\n

<\/p>\n

Summary: <\/strong> Emotiv is primarily a video-game company that creates products that let people control games with their thoughts, both conscious and subconscious. Emotiv\u2019s \u201cProject Epoc\u201d product is a stylish looking cap that uses electroencephalography (EEG) to measure the electrical activity of the wearer\u2019s brain. It is able to sense the emotional state of a person as well as recognize a few simple intentions. It transmits the user\u2019s input to the receiver wirelessly.<\/p>\n

Assets and Security Goals:<\/strong><\/p>\n

    \n
  1. Protecting the privacy of the user\u2019s thoughts. People\u2019s private thoughts should not be available for others to see.<\/li>\n
  2. Protecting the integrity of the user\u2019s thoughts. People should not have thoughts that they didn\u2019t think attributed to them.<\/li>\n
  3. Protecting the health and safety of the user. The device should not harm the user physically or mentally.<\/li>\n<\/ol>\n

    Potential Adversaries and Threats:<\/strong><\/p>\n

      \n
    1. People want to know what other people are thinking. Employees want to steal ideas from coworkers, auctioneers want to know how much bidders are willing to pay, and desperate housewives want to know if their husbands know about their love affairs.<\/li>\n
    2. People want to trick other people. A malicious person could plant custom thoughts (like sell a certain stock) into a user by rewarding them in the game if they have that particular thought. This could be done by modifying the signals transmitted to the console, or by modifying the game program.<\/li>\n
    3. People want to physically harm other people. A malicious person could rig up the device to give an electric shock to heads of unsuspecting individuals.<\/li>\n<\/ol>\n

      Potential Weaknesses:<\/strong><\/p>\n

        \n
      1. Weak encryption of transmitted signal. If the transmitted signal is not strongly encrypted, the privacy of the user\u2019s thoughts could easily be compromised. This problem is exacerbated by the use of wireless communication, which makes capturing packets more undetectable.<\/li>\n
      2. Transmission of raw signals. If the device transmits the raw EEG signals to the console for processing, this provides much more information to hackers if they are able to compromise the system. A better solution is to first process the raw signals on the headset, and them transmit high level commands to the console. This would limit the amount of compromised information in the event of an attack.<\/li>\n
      3. Physical access to the user\u2019s brain. The device needs to have access to the user\u2019s brain in order to take EEG measurements. This is a problem because a malicious device could masquerade as the headset and also gain physical access to the user\u2019s brain.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

        Here’s another example CSE 490K Security Review.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5],"tags":[],"class_list":["post-23","post","type-post","status-publish","format-standard","hentry","category-announcements","category-security-reviews"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/23","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\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=23"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/23\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=23"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=23"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=23"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}