Security

From 2009.igem.org

Revision as of 10:25, 9 October 2009 by Pdmillett (Talk | contribs)

Resources

People

The BWC ISU is the closest thing to an international organisation to ensure biology is used solely for beneficial purposes. It is housed in the UN Office for Disarmament Affairs in Geneva and, as Deputy Head, Piers helps States Parties to the Biological Weapons Convention ban the hostile use of biology. As a microbiologist and chartered biologist, Piers supports the technical aspects of the ISU's work.



Reports

Synthetic Biology and Biosecurity Awareness in Europe by SynBioSafe, November 2007



Synthetic Biology: Social and Ethical Challanges by the Institute for Science and Society, May 2008



Synthetic Biology: Scope Applications and Implications by the UK Royal Academy of Engineering, May 2009




Other Resources

Why Secure Modern Biology?

This is a 30 minute video arguing why we need to secure synthetic biology. It was filmed at SB4.0 in Hong Kong in 2008. It includes a short quiz that demonstrates how hard it is to spot the use of biology for hostile purposes. It looks at some of the problems with trying to secure biology through top-down governmental approaches and the need to find a community-based response to this shared problem.

"Biology should be more fun. It should be about exploring the world around us. We should want to get out there and do things. We should be able to do things more easily. Securing biology should be something that helps us do that. It cannot be something that gets in the way."

Scientific research continues to bring us new and unexpected knowledge, technologies and approaches. Synthetic biology, being on the very cutting edge of what is possible, promises unprecedented opportunities for health, wealth and better living. But science and technology can be used for destructive purposes as well as for constructive ones. Refining our control of biology opens up chances to intentionally cause harm to humans, animals, plants and the environment that just did not exist before. That’s why it is important now, more than ever, for us to think about how others might use what we are doing in ways we would not be happy with.


Preventing Malign Use

Securing biology is not a simple task. It is not something those outside biology could, or should, do alone. Equally, this is not something that biologists can do by themselves (our focus, as the name implies is on the biology). This is a truly interdisciplinary problem - one that means we will need to work together, in new ways, with new partners, to find an approach that provides benefits for all. Given the interdisciplinary nature of synthetic biology, and the experience the community has in drawing in people from different backgrounds, we are well placed to position ourselves in the vanguard of those thinking about how science interacts with society and to help write the rules which will govern this ‘century of biology’.

As a participant in iGEM, there are three things you can do right now to help us secure our science:

  1. Include something in your project description and presentations that demonstrates that you have thought about how others could misuse your work
  2. Contribute to community discussions on what needs to go into a code against the use of our science for hostile purposes (see A Community Response)
  3. Look into what security provisions, such as laws and regulations, are already in place in your country (see Working within the Law)


Shaping the Future

Ensuring that biology is used safely, securely and constructively should be of concern to us all. This is a challenge we will have to face together. To do this we will need to figure out what we want biological engineering to look like, what we are prepared for others to do with it, and just how we want to tackle security issues. This page provides a space to focus on these issues and for you to help shape what should be done to stop those with a malign intent. There is a real opportunity here for iGEM and those participating in iGEM, not only to shape how they will deal with security issues but to drive their national and even international processes. You can make a real difference in securing biology – in your lab, in your country and across the world.


A Committment to Do No harm

There is a strong feeling amongst those involved with iGEM, as well as the broader synthetic biology community, that the work we do should be used only for the benefit of humankind. It should not be used to do harm or to make weapons. This understanding has prompted some to think about what the community can do to ensure that this never happens. One important step would be a code or personal declaration that everyone involved (from the organisers, through supervisors and advisors, to team members and even the mascots!) would commit themselves to. This helps to ensure that we think about security as something that does directly involve us, is part of our project and can be dealt with in a way that helps us to get on and have some fun engineering biology.


A Community Response

Areas a code might address:
  • An introduction about why there is a code
  • A reminder of the importance of personal responsibility and that as your career progresses so do your responsibilities
  • A commitment to get informed about principles and practices designed to prevent hostile use
  • A commitment to find out about and comply with regulatory frameworks, such as international, national and institutional laws and guidelines
  • An obligation to do no harm
  • A requirement to look at the reasonably foreseeable consequences of your activities
  • A commitment not to ignore possible breaches of the code by others
  • An obligation to act responsibly in case you stumble across something that does not easily sit with the aims of the code
  • Some link between the pursuit of science and the best interests of the society in which it is pursued
Any code that would commit community members to do no harm would be first and foremost the property of this community. There is a solid body of work dedicated to the sorts of things that might be included in such an effort (see the Resources section). But nothing should be taken for granted – the content of our code would be up to us to decide. Here are some of the areas that a code might cover. Are these accurate? Can you think of anything else that should be on this list? Is there too much and we should get rid of some (if so, what)? Is there any point to working on a code? Here is where you can get involved – we are hoping that you will have something to say. You can answer these questions or add anything else you want to say (you know the drill) in the comments section below.