[Research] [Blog] [Politics] [My Book] [Music] [Contact Details]
Temporal Node Centrality in Complex Networks proposes new metrics for analysing highly dynamic systems. If there's an epidemic of flu, should you close down the schools or the subway? (blog)
2011 highlights included a major report on the Resilience of the Internet Interconnection Ecosystem which studies how an attacker might bring down the Internet; an updated survey paper on Economics and Internet Security which covers recent analytical, empirical and behavioral research; and Can We Fix the Security Economics of Federated Authentication? which explores how we can deal with a world in which your mobile phone contains your credit cards, your driving license and even your car key. What happens when it gets stolen or infected? (blog)
2010 highlights included a paper on why Chip and PIN is broken for which we got coverage on Newsnight and a best paper award (later, the banks tried to suppress this research). Other bank security work included a paper on Verified by VISA and another on the unwisdom of banks adopting proprietary standards. On the control systems front, we published papers on the technical security and security economics of smart meters, on their privacy, on their deployment and on key management for substations. I created a psychology and security web page and wrote a paper on putting context and emotion back in security decisions.
2009 highlights included Database State, an influential report we wrote about the failings of public-sector IT in Britain (a number of its recommendations have been adopted by the new government); The snooping dragon which explains how the Chinese spooks hacked the Dalai Lama in the run-up to the Peking Olympics; Eight Friends are Enough, which shows how little privacy you have on Facebook; and The Economics of Online Crime. There are also videos of talks I gave on dependability at the IET, Krakow and De Montfort, as well as a survey paper, the slides, and a podcast. Finally, I wrote an Unauthorised History of Cambridge University.
2008 highlights included a major study of Security Economics and European Policy for the European Commission; the second edition of my book "Security Engineering"; the discovery of serious vulnerabilities in Chip and PIN payment systems; an analysis of the failings of the Financial Ombudsman Service (see also a video from the World Economic Forum in November 2008); the FIPR submission to the Thomas-Walport Review; a piece on confidentiality in the British Journal of General Practice; three videos on privacy made by ARCH; and a video on surveillance. I started a Workshop on Security and Human Behaviour to bring together psychologists with economists and security engineers to work on deception and risk.
2007 highlights included technical papers on RFID and on New Strategies for Revocation in Ad-Hoc Networks (which explores when suicide attacks are effective); a Google tech talk on searching for covert communities online; a paper on fraud, risk and nonbank payment systems I wrote for the Fed; and a survey paper on Information Security Economics (of which a shortened version appeared in Science). I was a special adviser to House of Commons Health Committee for their Report on the Electronic Patient Record. Finally, following the HMRC data loss, I appeared in the debate on Newsnight.
2006 highlights included technical papers on topics from protecting power-line communications to the Man-in-the-Middle Defence, as well as a major report on the safety and privacy of children's databases for the UK Information Commissioner, which got a lot of publicity. I ended the year by debating health privacy on the Today programme with health minister Lord Warner, who resigned shortly aftewards.
2005 highlights included research papers on The topology of covert conflict, on combining cryptography with biometrics, on Sybil-resistant DHT routing, and on Robbing the bank with a theorem prover; and a big survey paper on cryptographic processors.
2004 highlights included papers on cipher composition, key establishment in ad-hoc networks and the economics of censorship resistance. I also lobbied for amendments to the EU IP Enforcement Directive and organised a workshop on copyright which led to a common position adopted by many European NGOs.
I am Professor of Security Engineering at the Computer Laboratory. My research students are Joe Bonneau, Wei-Ming Khoo, Rubin Xu and Dongting Yu. Richard Clayton, Steven Murdoch, Robert Watson and Sergei Skorobogatov are postdocs. Alumni include former postdocs Mike Bond, Vashek Matyas and Andrei Serjantov, while Jong-Hyeon Lee, Frank Stajano, Fabien Petitcolas, Harry Manifavas, Markus Kuhn, Ulrich Lang, Jeff Yan, Susan Pancho, Mike Bond, George Danezis, Sergei Skorobogatov, Hyun-Jin Choi, Richard Clayton, Jolyon Clulow, Hao Feng, Andy Ozment, Tyler Moore, Shishir Nagaraja, Robert Watson, Hyoungshick Kim and Shailendra Fuloria have earned PhDs.
My research topics include:
By default, when I post a paper here I license it under the relevant Creative Commons license, so you may redistribute it with attribution but not modify it. I may subsequently assign the residual copyright to an academic publisher.
As systems scale globally, incentives start to matter as much as technology. Systems break when the people who could fix them are not the people who suffer the costs of failure. So it's not enough for security engineers to understand cryptomathematics and the theory of operating systems; we have to understand game theory and microeconomics too. This has led to a rapidly growing interest in ‘security economics’, a discipline I helped to found. This discipline is starting to embrace dependability and software economics; at the other end, it's growing through bevaioural economics into the psychology of security. I maintain the Economics and Security Resource Page and a similar web page on Security Psychology. There is also a web page on the economics of privacy, maintained by Alessandro Acquisti. My research contributions include the following.
We've written a major report for ENISA on the Resilience of the Internet interconnection ecosystem which has been adopted as ENISA policy. Here is the full report (238 pages) and, for the busy, the 31-page executive summary. We believe this is the first time anyone has documented how the Internet actually works in practice, as opposed to in theory; we spent a lot of time speaking to network operators about how they negotiate peering and transit, what goes wrong, how they deal with failures and where the incentives for resilience are inadequate.
From time to time, Tyler Moore and I write a survey paper on security economics. Here is the latest (2011): Economics and Internet Security: a Survey of Recent Analytical, Empirical and Behavioral Research. Our previous survey paper, Information Security Economics – and Beyond, appeared in various versions from 2006 to 2009. There was a short survey in Science in late 2006; a version for economists at Softint in January 2007; a version for security engineers at Crypto in August 2007 (see slides); a book chapter for mathematicians; a video of a survey talk at De Montfort, and finally an archival journal version in Phil Trans Roy Soc A (Aug 2009). It's the Anthropology, Stupid! discusses how we might put context and emotion back into security decisions. The Economics of Online Crime appeared in the Journal of Economic Perspectives; it looks at the econometrics of fraud and phishing, and makes a number of suggestions for improving the responses of banks and law-enforcement agencies. The Impact of Incentives on Notice and Take-down examines how take-down speed varies with the incentive of the party requesting removal. Banks are quick to remove phishing websites that mention them by name, but they ignore mule recruitment websites because it's harder to tell which bank will be affected. We have two futher papers on security economics in banking. The first is on Verified by VISA – the mechanism that asks for your card password when you shop online. This is an example of how a poor design can win out if it has strong deployment incentives (see also blog post and slides). The second, On the Security of Internet Banking in South Korea, analyses the effects of Korea's decision to use national cryptography standards for Internet banking rather than just using the same protocols as the rest of the world. On the security economics of electricity metering appeared at WEIS 2010 and warns that the government's smart meter programme probably won't work. Other papers on security economics and control systems include Security Economics and Critical National Infrastructure (at WEIS 2009); Certification and Evaluation (at IEEE ETFA 2009); and The Protection of Substation Communications (SCADA Security Scientific Symposium, 2010). The Trust Economy of Brief Encounters argues that as transactions become more transient, we will have to authenticate more; it appeared at the protocols workshop in 2009. We did a major study of security economics in the Single Market for the European Network and Information Security Agency. We looked at the market failures underlying spam, phishing and other online problems, and made concrete policy proposals. A shorter version (62 pages) appeared at WEIS 2008 (slides) and an even shorter version (25 pages), at ISSE. Closing the Phishing Hole – Fraud, Risk and Nonbanks reports research on payment regulation commissioned by the US Federal Reserve. This paper identified speedy asset recovery as the best way to deter online fraud; fraud is made easy by systems like Western Union that make it hard to recover stolen funds. The topology of covert conflict asks how the police can best target an underground organisation given some knowledge of its patterns of communication, and how might they in turn might react to various law-enforcement strategies. We present a framework combining ideas from network analysis and evolutionary game theory to explore the interaction of attack and defence strategies in networks. Although we started out thinking about computer viruses, our work suggests explanations of a number of aspects of modern conflict generally. Why Information Security is Hard – An Economic Perspective was the paper that got information security people thinking about economics. It applies microeconomic analysis to explain many phenomena that security folks had found to be pervasive but perplexing. Why do mass-market software products such as Windows contain so many security bugs? Why are their security mechanisms so difficult to manage? Why are government evaluation schemes, such as the Orange Book and the Common Criteria, so bad? My `Trusted Computing' FAQ undermined the Trusted Computing Group's initiative to install DRM hardware in every computer, PDA and mobile phone. `TC' was designed to please Hollywood by making it hard to pirate music and videos – and to please the software industry by locking in customers more tightly. But it could have damaged privacy, censorship, and innovation. Cryptography and Competition Policy – Issues with `Trusted Computing' is an economic analysis I gave at WEIS2003 and also as an invited talk at PODC 2003. A shortened version of the paper appeared in a special issue of Upgrade (there's also a French translation). I spoke about TC at the "Trusted Computing Group" Symposium, which helped drive German government policy. The row about `Trusted Computing' was ignited by a paper on the security of free and open source software I gave at Softint 2002 in Toulouse; see coverage in the New York Times and The Register. In the first part of my Toulouse paper, I show that the usual argument about open source security – whether source access makes it easier for the defenders to find and fix bugs, or makes it easier for the attackers to find and exploit them – is misdirected. Under standard assumptions used by the reliability growth modelling community, the two will exactly cancel each other out. That means that whether open or closed systems are more secure in a given situation will depend on whether, and how, the application deviates from the standard assumptions. These ideas aare developed in a later paper, Open and Closed Systems are Equivalent (that is, in an ideal world) which appeared as a chapter in Perspectives on Free and Open Source Software. See press coverage in slashdot, news.com and The Register. On Dealing with Adversaries Fairly applies election theory (also known as social choice theory) to the problem of shared control in distributed systems. It shows how a number of reputation systems proposed for use in peer-to-peer applications might be improved. It appeared at WEIS 2004. The Economics of Censorship Resistance examines when it is better for defenders to aggregate or disperse. Should file-sharers build one huge system like gnutella and hope for safety in numbers, or would a loose federation of fan clubs for different bands work better? More generally, what are the tradeoffs between diversity and solidarity when conflict threatens? (This is a live topic in social policy - see David Goodhart's essay, a response in the Economist, and a post by Clay Shirkey.) This paper also appeared at WEIS 2004. Here are papers on The Initial Costs and Maintenance Costs of Protocols, which I gave at Security Protocols 2005, and How Much is Location Privacy Worth? which I gave at WEIS 05.There are two annual workshops I helped establish. On the psychology side, the Security and Human Behaviour workshop is great fun and hugely productive. See the papers, liveblog and audio for 2009; and the papers, liveblog and audio for the first meeting in 2008. On the economic side, the Workshop on Economics and Information Security is now into its tenth year and attracts over a hundred participants.
Since about 2000, there has been an explosion of interest in peer-to-peer networking &ndash the business of building useful systems out of large numbers of intermittently connected machines. One of the seminal papers was The Eternity Service, which I presented at Pragocrypt 96. I had been alarmed by the Scientologists' success at closing down the penet remailer in Finland, and have more than once been threatened by lawyers who did not want me to comment on the security of their clients' systems. Yet the modern era only started once the printing press enabled seditious thoughts to be spread too quickly and widely to ban. But when books no longer exist as tens of thousands of paper copies, but as a file on a single server, will government ministers and judges be able to unpublish them once more? (This has since happpened to newspaper archives in Britain.) So I invented the Eternity Service as a means of putting electronic documents beyond the censor's grasp. The Eternity Service inspired second-generation censorship-resistant systems such as Publius and Freenet; one descendant of these early systems is wikileaks. Our contribution to that is in helping to maintain Tor, the anonymity service used by wikileaks and by many others.
But history never repeats itself exactly, and the biggest deal turned out to be not sedition, or vulnerability disclosure, or even pornography, but copyright. Hollywood's action against Napster led to our ideas being adopted in peer-to-peer filesharing systems. Many of these developments were described here, and discussed at conferences like this one. See also Richard Stallman's classic, The Right to Read.
Many of the ideas in early peer-to-peer systems reemerged in the study of ad-hoc and sensor networks and are now spilling over into social networking systems. My contributions since the Eternity paper include the following.
Eight Friends are Enough: Social Graph Approximation via Public Listings shows how easy it is for an outsider to work out the structure of friendships on Facebook. (For more, see our blog on Facebook's technical privacy and its democracy theatre.) New Strategies for Revocation in Ad-Hoc Networks won the best paper award at ESAS07. In it we show how to use suicide bombing for revocation in networks. Suicide attacks are found widely in nature, from bees to helper T-cells; this model may help explain why (press coverage here and here). The idea was developed further in Fast exclusion of errant devices from vehicular networks at SECON 08. I worked on the security of Homeplug, an industry standard for broadband communication over the power mains. A paper on what we did and why appeared at SOUPS 2006. This is a good worked example of how to do key establishment in a real peer-to-peer system. The core problem is this: how can you be sure you're recruiting the right device to your network, rather than a similar one nearby? Sybil-resistant DHT routing appeared at ESORICS 2005 and showed how we can make peer-to-peer systems more robust against disrutpive attacks if we know which nodes introduced which other nodes. The convergence of computer science and social network theory is an interesting recent phenomenon, and not limited to search and recommender systems. Key Infection - Smart trust for Smart Dust appeared at ICNP 2004 and presents a radically new approach to key management in sensor and peer-to-peer networks. Peers establish keys opportunistically and use resilience mechanisms against later node compromise. This work challenges the assumption that authentication is largely about bootstrapping. The Economics of Censorship Resistance examines when it is better for defenders to aggregate or disperse. Should file-sharers build one huge system like gnutella and hope for safety in numbers, or would a loose federation of fan clubs for different bands work better? A New Family of Authentication Protocols presented our "Guy Fawkes Protocol", which lets users sign messages using only two computations of a hash function and one reference to a timestamping service. It led to many protocols for signing digital streams and also raised foundational questions about the nature of a digital signature. The Resurrecting Duckling: Security Issues for Ad-hoc Wireless Networks was very influential. It describes how to do key management between low-cost devices without either the costs or privacy problems of central servers. (There's also a journal version of the paper here.) The Cocaine Auction Protocol explored how transactions can be conducted between mutually mistrustful principals with no trusted arbitrator, while giving a high degree of privacy against traffic analysis. The Eternal Resource Locator: An Alternative Means of Establishing Trust on the World Wide Web investigated how to protect naming and indexing information and showed how to embed trust mechanisms in html documents. It was motivated by a medical school project to protect the electronic version of the British National Formulary: see Secure Books: Protecting the Distribution of Knowledge. Later work included some thinking on how to secure a digital repository; and Jikzi, an authentication framework for electronic publishing, on which there are both general and technical papers. (Jikzi also led to a startup.) The XenoService - A Distributed Defeat for Distributed Denial of Service described defeating DDoS attacks using a network of web hosts that can respond to an attack on a site by replicating it rapidly and widely. It used Xen, a hypervisor developed at Cambridge for distributed hosting, which led to another startup.
Who controls the off switch? describes the strategic vulnerability created by the UK plan to replace 47m gas and electricity meters with ‘smart meters’ that can be switched off remotely.
A recurrring theme is the vulnerabilities in the EMV payment system, known in the UK as Chip and PIN. We won an award for a paper describing a man-in-the-middle attack that allows a stolen card to be used with any pin. There was a TV piece on Newsnight; see also ZDnet, the Telegraph, the Mail, the Mirror, the Register, Bruce Schneier, the press release and our FAQ. Rather than fixing the problem, the UK banks sought to suppress our research; see comment in the Guardian, the Indy, the Mail, the Cambridge News, Slashdot, Ars Technica, Radio 4 and Radio 5). Other recent work on problems with bank systems includes a paper on Verified by VISA, the mechanism that asks for your card password when you shop online, and a tech report On the Security of Internet Banking in South Korea. Optimised to Fail: Card Readers for Online Banking documents the shortcomings of the CAP card readers used for online banking; see also our blog, press coverage and the later journal version. Thinking inside the box: system-level failures of tamper proofing documented serious vulnerabilities in Chip and PIN payment terminals and won the Best Practical Paper award at the 2008 Oakland conference. It was also featured on Newsnight; see the video and the viewers' comments. Here are some frequently asked questions, our press release, and coverage in the Register, the Newsnight blog and the Telegraph. My paper Failures on Fraud appeared in a central bankers' magazine and argued that all this is yet another symptom of the failure of bank regulation. The snooping dragon: social-malware surveillance of the Tibetan movement explains how the Chinese intelligence services compromised many of the computers at the Dalai Lama's private office, and what this means for information security (also slides). Why Cryptosystems Fail may have been cited more than anything else I've written. This version appeared at ACMCCS 93 and explains how ATM fraud was done in the early 1990s. Liability and Computer Security - Nine Principles took this work further, and examines the problems with relying on cryptographic evidence. The recent introduction of EMV ('chip and PIN') was supposed to fix the problem, but hasn't: Phish and Chips documents protocol weaknesses in EMV, and A Note on EMV Secure Messaging in the IBM 4758 CCA documents even more. The Man-in-the-Middle Defence shows how to turn protocol weaknesses to advantage. See my paper RFID and the Middleman for the likely next wave of frauds. On a New Way to Read Data from Memory describes techniques we developed that use lasers to read out memory contents directly from a chip, without using the read-out circuits provided by the vendor. The work builds on methods described in Optical Fault Induction Attacks, which showed how laser pulses could be used to induce faults in smartcards that would leak secret information. That paper appeared at CHES 2002; it made the front page of the New York Times and also got covered by slashdot. After we discovered the above attacks, we developed a CPU technology that uses redundant failure-evident logic to thwart attacks based on fault induction or power analysis. Our first paper on this technology won the best presentation award in April at Async 2002. Our journal paper, Balanced Self-Checking Asynchronous Logic for Smart Card Applications, has details and test results. Our classic paper on hardware security, Tamper Resistance – A Cautionary Note, describes how to penetrate the smartcards and secure microcontrollers of the mid-1990s. It kicked off the modern academic study of hardware security and won a Best Paper award. Our second paper on the subject was Low Cost Attacks on Tamper Resistant Devices, which describes a number of further tricks. See also the home page of our hardware security laboratory, and Markus Kuhn's page of links to hardware attack resources. On the Reliability of Electronic Payment Systems describes work I did to help develop prepayment utility metering, which made possible the electrification of millions of homes in Africa. It appeared in the May 1996 issue of the IEEE Transactions on Software Engineering. An ealier version, entitled Cryptographic Credit Control in Pre-Payment Metering Systems, appeared at Oakland 95. A later paper on this subject discussed how we could apply what we'd learned to support utility meter interworking in the UK after deregulation. On the Security of Digital Tachographs successfully predicted how the introduction of smartcard-based digital tachographs throughout Europe from 2005 would affect fraud and tampering. How to Cheat at the Lottery reports a novel and, I hope, entertaining experiment in software requirements engineering. The Grenade Timer describes a novel way to protect low-cost processors against denial-of-service attacks, by limiting the number of cycles an application can consume. The Millennium Bug – Reasons Not to Panic describes our experience in coping with the bug at Cambridge University and elsewhere. This paper correctly predicted that the bug wouldn't bite very hard. Journalists were not interested, despite a major press release by the University: I later discussed what we could learn from the incident in a radio interview with Stephen Fry. The Memorability and Security of Passwords -- Some Empirical Results tackles an old problem - how do you train users to choose passwords that are easy to remember but hard to guess? We did a randomized controlled trial with a few hundred first year science students which confirmed some folk beliefs, but debunked some others. This became one of the classic papers on security usability. Murphy's law, the fitness of evolving species, and the limits of software reliability applies the techniques of statistical thermodynamics to the failure modes of any complex system that evolves under testing. It provides a common mathematical model for the reliability growth of complex computer systems and for biological evolution. Its findings are in close agreement with empirical data, and it inspired later work in security economics. Security Policies play a central role in secure systems engineering. They provide a concise statement of the kind of protection a system is supposed to achieve. This article is a security policy tutorial. Combining cryptography with biometrics shows that in those applications where you can benefit from biometrics, you often don't need a large central database (as proposed for Britain's ID card). There are smarter and less privacy-invasive ways to arrange things.The papers on physical security by Roger Johnston's team are also definitely worth a look, and there's an old leaked copy of the NSA Security Manual that you can download (also as latex).
Key Management for Substations: Symmetric Keys, Public Keys or No Keys? debunks the proposal to mandate public-key crypto in electricity substations. In this particular application, the right solution is usually to have no crypto at all.
What Next after Anonymity? argues that it isn't enough to worry about the confidentiality of metadata (anonymity); we sometimes need to protect their integrity as well. API Level Attacks on Embedded Systems are a powerful way to attack cryptographic processors, and indeed any systems where more trusted processes talk to less trusted ones. The idea is that a "secure" device can often be defeated by sending it some sequence of transactions which its designer did not expect. We've defeated pretty well every security processor we've looked at, at least once. This line of research originated at Protocols 2000 with my paper The Correctness of Crypto Transaction Sets; more followed in the first edition of my book. Robbing the bank with a theorem prover, shows how to apply advanced tools to the problem, and ideas for future research can be found in Protocol Analysis, Composability and Computation. For a snapshot of how this interacts with physical security, see our survey of cryptographic processors, a shortened version of which appeared in the February 2006 Proceedings of the IEEE. An up-to-date survey of API attacks can be found in the second edition of my my book. Programming Satan's Computer is a phrase Roger Needham and I coined to express the difficulty of designing cryptographic protocols; it has recently been popularised by Bruce Schneier (see, for example, his foreword to my book). The problem of designing programs which run robustly on a network containing a malicious adversary is rather like trying to program a computer which gives subtly wrong answers at the worst possible moment. Robustness principles for public key protocols gives a number of attacks on protocols based on public key primitives. It also puts forward some principles which can help us to design robust protocols, and to find attacks on other people's designs. It appeared at Crypto 95. The Cocaine Auction Protocol explores how transactions can be conducted between mutually mistrustful principals with no trusted arbitrator, even in environments where anonymous communications make most of the principals untraceable. The Initial Costs and Maintenance Costs of Protocols appeared at the 2005 Protocols Workshop and shows how economics can enter into protocol design. NetCard - A Practical Electronic Cash Scheme presents research on micropayment protocols for use in electronic commerce. We invented tick payments simultaneously with Torben Pedersen and with Ron Rivest and Adi Shamir; we all presented our work at Protocols 96. The GCHQ Protocol and its Problems pointed out a number of flaws in a key management protocol promoted by GCHQ as a European alternative to Clipper, until we shot it down with this paper at Eurocrypt 97. Many of the criticisms we developed here also apply to the more recent, pairing-based cryptosystems. The Formal Verification of a Payment System describes the first use of formal methods to verify an actual payment protocol, which was (and still is) used in an electronic purse product (VISA's COPAC card). This is a teaching example I use to get the ideas of the BAN logic across to undergraduates. There is further detailed information in a technical report, which combines papers given at ESORICS 92 and Cardis 94. An Attack on Server Assisted Authentication Protocols appeared in Electronics Letters in 1992. It breaks a digital signature protocol. On Fortifying Key Negotiation Schemes with Poorly Chosen Passwords presents a simple way of achieving the same result as protocols such as EKE, namely preventing middleperson attacks on Diffie-Hellman key exchange between two people whose shared secret could be guessed by the enemy.Protocols have been the stuff of high drama. Citibank asked the High Court to gag the disclosure of certain crypto API vulnerabilities that affect a number of systems used in banking. I wrote to the judge opposing this; a gagging order was still imposed, although in slightly less severe terms than Citibank had requested. The trial was in camera, the banks' witnesses didn't have to answer questions about vulnerabilities, and new information revealed about these vulnerabilities in the course of the trial may not be disclosed in England or Wales. Information already in the public domain was unaffected. The vulnerabilities were discovered by Mike Bond and me while acting as the defence experts in a phantom withdrawal court case, and independently discovered by the other side's expert, Jolyon Clulow, who later joined us as a research student. They are of significant scientific interest, as well as being relevant to the rights of the growing number of people who suffer phantom withdrawals from their bank accounts worldwide. Undermining the fairness of trials and forbidding discussion of vulnerabilities isn't the way forward (press coverage by the Register and news.com).
Reports of an attack on the hash function SHA have made Tiger, which Eli Biham and I designed in 1995, a popular choice of cryptographic hash function. I also worked with Eli, and with Lars Knudsen, to develop Serpent – a candidate block cipher for the Advanced Encryption Standard. Serpent won through to the final of the competition and got the second largest number of votes. Another of my contributions was founding the series of workshops on Fast Software Encryption.
Other papers on cryptography and cryptanalysis include the following.
The NHS has a long history of privacy abuses. The previous prime minister's own medical records were compromised; the miscreant got off scot-free as it was not in the "public interest" to prosecute him. In another famous case, Helen Wilkinson had to organise a debate in Parliament to get ministers to agree to remove defamatory and untrue information about her from NHS computers. The minister assured the House that the libels had been removed; months later, they still had not been. Helen started www.TheBigOptOut.org to campaign for health privacy. In a typical recent case, a woman was tracked down by her ex-husband and seriously injured after his aunt looked up her name and address in NHS systems. Her case is currently before the courts.
Here are my most recent papers on the subject.
Civil servants started pushing for online access to everyone's records in 1992 and I got involved in 1995, when I started consulting for the British Medical Association on the safety and privacy of clinical information systems. Back then, the police were given access to all drug prescriptions, after the government argued that they needed it to catch doctors who misprescribed heroin. The police got their data, but they didn't catch Harold Shipman, and no-one was held accountable. The NHS slogan in 1995 was `a unified electronic patient record, accessible to all in the NHS'. The BMA campaigned against this, arguing that it would destroy patient privacy:
In 1996, the Government set up the Caldicott Committee to study the matter. Their report made clear that the NHS was already breaking confidentiality law by sharing data without consent; but the next Government just legislated (and regulated, and again) to give itself the power to share health data as the Secretary of State saw fit. (We objected and pointed out the problems the bill could cause; similar sentiments were expressed in a BMJ editorial, and a Nuffield Trust impact analysis, and BMJ letters here and here. Ministers claimed the records were needed for cancer registries: yet cancer researchers work with anonymised data in other countries – see papers here and here.) There was a storm of protest in the press: see the Observer, the New Statesman, and The Register. But that died down; the measure has now been consolidated as sections 251 and 252 of the NHS Act 2006, the Thomas-Walport review blessed nonconsensual access to health records (despite FIPR pointing out that this was illegal — a view later supported by the European Court). A government committee, the NHS Information Government Board now oversees this lawbreaking. Centralised, nonconsensual health records not only contravene the I v Finland judgement but also the Declaration of Helsinki on ethical principles for medical research and the Council of Europe recommendation no R(97)5 on the protection of medical data.
Two health IT papers by colleagues deserve special mention. Privacy in clinical information systems in secondary care describes a hospital system implementing something close to the BMA security policy (it is described in more detail in a special issue of the Health Informatics Journal, v 4 nos 3-4, Dec 1998, which I edited). Second, Protecting Doctors' Identity in Drug Prescription Analysis describes a system designed to de-identify prescription data for commercial use; although de-identification usually does not protect patient privacy very well, there are exceptions, such as here. This system led to a court case, in which the government tried to stop its owner promoting it &ndash as it would have competed with their (less privacy-friendly) offerings. The government lost: the Court of Appeal decided that personal health information can be used for research without patient consent, so long as the de-identification is done competently.
Resources on what's happening in the USA – where the stimulus bill has made medical privacy a very live issue &ndash include many NGOs: Patient Privacy Rights may have been the most influential, but see also EPIC, the Privacy Rights Clearinghouse, the Citizens' Council on Health Care, the Institute for Health Freedom. and CDT. Older resources include an NAS report entitled For the Record: Protecting Electronic Health Information, a report by the Office of Technology Assessment, a survey of the uses of de-identified records for the DHHS, and a GAO report on their use in Medicare. For information on what's happening in the German-speaking world, see Gerrit Bleumer's web page. As for the basic science, the American Statistical Association has a good collection of links to papers on inference control, also known as statistical security &ndash the protection of de-identified data.
I chair the Foundation for Information Policy Research, the UK's leading Internet policy think tank, which I helped set up in 1998. We are not a lobby group; our enemy is ignorance rather than the government of the day, and our mission is to understand IT policy issues and explain them to policy makers and the press. Here's an overview of the issues as we saw them in 1999, and a video of how we saw them ten years later in 2008. Some highlights of our work follow.
My pro-bono work has included sitting on Council, our University's governing body. I stood for election in 2002 because of incidents like this; to stop such things happening again, we founded the Campaign for Cambridge Freedoms, and campaigned against a proposal that most of the intellectual property generated by faculty members - from patents on bright ideas to books written up from lecture notes - would belong to the university rather than to its creator. The final vote approved a policy according to which academics keep copyright but the University gets 15% of patent royalties. I got re-elected in 2006, and in my second term we won an important vote to protect academic freedom. For more, see my article from the Oxford Magazine, and my Unauthorised History of Cambridge University.
My CV is here. I'm a Fellow of the Royal Society, the Royal Academy of Engineering, the Institution of Engineering and Technology, the Institute of Mathematics and its Applications, and the Institute of Physics. My h-index is tracked here. As for my academic genealogy, my thesis adviser was Roger Needham; his was Maurice Wilkes; then it runs back through Jack Ratcliffe, Edward Appleton, Ernest Rutherford, JJ Thomson, Lord Rayleigh, Edward Routh, William Hopkins, Adam Sedgwick, Thomas Jones, Thomas Postlethwaite, Stephen Whisson, Walter Taylor, Roger Smith, Roger Cotes, Isaac Newton Isaac Barrow and Vincenzo Viviani to Galileo Galilei.
Finally, here is my PGP key. If I revoke this key, I will always be willing to explain why I have done so provided that the giving of such an explanation is lawful. (For more, see FIPR.)
The second edition is now out! You can order it from Amazon.com and Amazon.co.uk.
Security engineering is about building systems to remain dependable in the face of malice, error or mischance. As a discipline, it focuses on the tools, processes and methods needed to design, implement and test complete systems, and to adapt existing systems as their environment evolves. My book has become the standard textbook and reference since it was published in 2001. You can download the first edition without charge here.
Security engineering is not just concerned with infrastructure matters such as firewalls and PKI. It's also about specific applications, such as banking and medical record-keeping, and about embedded systems such as automatic teller machines and burglar alarms. It's usually done badly: it often takes several attempts to get a design right. It is also hard to learn: although there were good books on a number of the component technologies, such as cryptography and operating systems, there was little about how to use them effectively, and even less about how to make them work together. Most systems don't fail because the mechanisms are weak, but because they're used wrong.
My book was an attempt to help the working engineer to do better. As well as the basic science, it contains details of many applications - and lot of case histories of how their protection failed. It contains a fair amount of new material, as well as accounts of a number of technologies which aren't well described in the accessible literature. Writing it was also pivotal in founding the now-flourishing field of information security economics: I realised that the narrative had to do with incentives and organisation at least as often as with the technology. The second edition incoporates the economic perspectives we've developed over the past six years, and new perspectives from the psychology of security, as well as updating the technological side of things.
I don't execute programs sent by strangers without good reason. So I don't read attachments in formats such as Word, unless by prior arrangement. I also discard emails asking for "summer research positions" or "internships", which we don't do; we're no longer able to employ overseas students on Tier 4 visas.
If you're contacting me about coming up to do a PhD, please read the relevant web pages first. If you just send me an email with your CV I will ignore it as spam.
You are viewing a mobilized version of this site...
View original page here