Line 509: | Line 509: | ||
<h2 class="section-heading">Introduction</h2> | <h2 class="section-heading">Introduction</h2> | ||
<h11 class="section-subheading text-muted"> | <h11 class="section-subheading text-muted"> | ||
− | + | Storing information isn’t as simple as finding a place to put it until you need it. The growth of digital information storage and transfer has also come with an increased demand for security and encryption. When we set out to design our modular DNA data storage system, we immediately thought of the question; is it possible to encrypt our DNA? | |
− | + | ||
<br> | <br> | ||
Line 516: | Line 515: | ||
<br> | <br> | ||
<br> | <br> | ||
− | + | </h11> | |
− | + | ||
</div> | </div> | ||
<br> | <br> | ||
Line 532: | Line 530: | ||
<section id="about"> | <section id="about"> | ||
+ | <div class="container"> | ||
+ | <div class="row"> | ||
+ | <div class="col-lg-12 text-center"> | ||
+ | <h2 class="section-heading">Why encrypt?</h2> | ||
+ | <h11 class="section-subheading text-muted"> | ||
+ | Imagine you have just used our software to encode your data into BabbleBlocks…. | ||
+ | |||
+ | <br> | ||
+ | <br> | ||
+ | <br> | ||
+ | <br> | ||
+ | <p>Scenario #1: When you decode your DNA, you are hacked and the data is stolen…</p> | ||
+ | <p>After retrieving your DNA sequencing results, you will input this back into our software for decoding. As your computer will most likely be connected to the internet, it is entirely possible for someone to steal your data during decode. </p> | ||
+ | <p>Scenario #2: You have sequenced your DNA. Before you manage to decode the sequence, someone else gets a hold of it…</p> | ||
+ | <p>Similar to the situation above, it is possible that if your sequencing results are being sent to you online they could be intercepted or the file on your computer may be hacked. Our encryption system ensures that only those with the correct key will be able to decode the DNA sequence to the original data. </p> | ||
+ | <p>Scenario #3: You want to send confidential data to someone, how can you prevent the message from being intercepted?</p> | ||
+ | <p>In the spirit of iGEM, our software and procedures will be open source. This means that if you were to send a DNA message to a friend, it would be possible to intercept the message and decode it using our systems.</p> | ||
+ | <p> A conversation with FBI Special Agent Edward You pointed out to us the importance of security in modern information transfer; in order for our method to be utilised by both private individuals and large scale companies, we need to incorporate a method of encryption that restricts decoding. Even archival data that is stored for long periods of time should have some level of encryption.</p> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | </h11> | ||
+ | </div> | ||
+ | <div align="center"> | ||
+ | <a href="#accordion"> | ||
+ | <span class="arrowtext">Scroll down to read more</span> | ||
+ | <img src="https://static.igem.org/mediawiki/2014/3/3e/Aalto_Helsinki_Nuoli.png" class="arrow"> | ||
+ | </a> | ||
+ | </div> | ||
+ | <br> | ||
+ | <br> | ||
+ | </div> | ||
+ | <section id="about"> | ||
<div class="container"> | <div class="container"> | ||
<div class="row"> | <div class="row"> | ||
Line 556: | Line 588: | ||
<br> | <br> | ||
</div> | </div> | ||
− | |||
</body> | </body> |
Revision as of 13:49, 15 October 2016
Team:Edinburgh/Part Collection
Introduction
Why encrypt?
Scenario #1: When you decode your DNA, you are hacked and the data is stolen…
After retrieving your DNA sequencing results, you will input this back into our software for decoding. As your computer will most likely be connected to the internet, it is entirely possible for someone to steal your data during decode.
Scenario #2: You have sequenced your DNA. Before you manage to decode the sequence, someone else gets a hold of it…
Similar to the situation above, it is possible that if your sequencing results are being sent to you online they could be intercepted or the file on your computer may be hacked. Our encryption system ensures that only those with the correct key will be able to decode the DNA sequence to the original data.
Scenario #3: You want to send confidential data to someone, how can you prevent the message from being intercepted?
In the spirit of iGEM, our software and procedures will be open source. This means that if you were to send a DNA message to a friend, it would be possible to intercept the message and decode it using our systems.
A conversation with FBI Special Agent Edward You pointed out to us the importance of security in modern information transfer; in order for our method to be utilised by both private individuals and large scale companies, we need to incorporate a method of encryption that restricts decoding. Even archival data that is stored for long periods of time should have some level of encryption.
Introduction
Another threat can be discovered at the stage when the user wants to decode the DNA sequence into text. Because at this stage your DNA is into a computer which is linked to a network, the risk is quite high of being stolen. We indeed see that the system requests some security measures in order to keep data safe. In conclusion, the ‘threat’ is someone stealing the information when the DNA is sent to a different person or the archive data. In this way, the value of the data might be of high importance, so we need to find a way of protecting it, because our stored data needs to be secure.