Show Summary Details
Page of

(p. 87) 7. Critical Security Studies: A Schismatic History 

(p. 87) 7. Critical Security Studies: A Schismatic History
Chapter:
(p. 87) 7. Critical Security Studies: A Schismatic History
Author(s):

David Mutimer

DOI:
10.1093/hepl/9780198708315.003.0007
Page of

PRINTED FROM OXFORD POLITICS TROVE (www.oxfordpoliticstrove.com). © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Politics Trove for personal use (for details see Privacy Policy and Legal Notice).

date: 24 October 2020

This chapter provides a partial history of the label ‘Critical Security Studies’ and the way it has developed and fragmented since the early 1990s. It considers the primary claims of the major divisions that have emerged within the literatures to which the label has been applied: constructivism, critical theory, and poststructuralism. It looks at the 1994 conference held at York University in Toronto entitled Strategies in Conflict: Critical Approaches to Security Studies, which spawned a book called Critical Security Studies: Concepts and Cases (1997b), and Security: A New Framework for Analysis (1998), which was published to serve as a relatively comprehensive statement of ‘securitization studies’, or the Copenhagen School. The chapter argues that Critical Security Studies needs to foster an ‘ethos of critique’ in either the study or refusal of security. Finally, it examines Ken Booth’s views on poststructuralism as part of a broad Critical Security Studies.

Access to the complete content on Politics Trove requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.