Answer framework · PSIR Paper II
Collective security and the responsibility to protect
“Collective security and responsibility to protect (R2P) are similar but different in scope, goals and methods. Explain.”
The platform’s own guidance for planning an answer. It is not an official or model answer.
01What the question asks
Directive. Explain asks for clear definitions and an account of how the two ideas relate. The question supplies its own structure, similar but different in scope, goals and methods: use those three words as the headings of the comparison, and establish the similarity first.
Scope. Collective security as the principle of the League Covenant and of Chapter VII of the UN Charter; the responsibility to protect (R2P) as formulated by the International Commission on Intervention and State Sovereignty (2001) and endorsed by the 2005 World Summit. Practice (Korea, Kuwait, Libya, Syria) is evidence, not the subject.
The trap. Three common errors: confusing collective security with collective defence, an alliance against an outside threat such as NATO's Article 5; treating R2P as a synonym for humanitarian intervention, when its first two pillars concern prevention and assistance; and listing differences without the similarity the question asserts.
02The approach
Begin with what the two share. Both are universalist doctrines of shared responsibility; both qualify state sovereignty; both depend in the last resort on the Security Council, and therefore on the agreement of its five permanent members.
Then compare on the question's three axes.
- Scope. Collective security addresses threats to international peace, above all aggression by one state against another. R2P is confined to four crimes, usually committed within states: genocide, war crimes, ethnic cleansing and crimes against humanity.
- Goals. Collective security restores and preserves order among states; its referent is the state and the system. R2P protects populations, including from their own governments; its referent is the human being. This is why R2P is described as a reconception of sovereignty as responsibility, an idea associated with Francis Deng.
- Methods. Collective security works by deterrence and, if deterrence fails, by enforcement, all against the aggressor, through the non-military and military measures of Articles 41 and 42. R2P works along the continuum set out in Ban Ki-moon's report of 2009: the state's own responsibility (pillar one), international assistance and capacity-building (pillar two), and timely and decisive collective response through the Council, case by case, when a state manifestly fails (pillar three). Force is the last element of R2P but the defining element of collective security.
Close with practice, which shows both the distinction and the common weakness. Collective security operated in Korea in 1950 only because the Soviet Union was boycotting the Council, and against Iraq in 1990; R2P was invoked over Libya in 2011 and then blocked over Syria. Both work only when the great powers agree, which is the realist objection to both. See Key Concepts in International Relations and United Nations.
03Competing viewpoints
R2P as collective security completed
Advocates such as Gareth Evans, co-chair of the 2001 Commission, present R2P as the Charter's promise extended to the people it was meant to protect. Rwanda (1994) and Srebrenica (1995) showed that a system designed against aggression between states had nothing to say about mass killing within them. On this view R2P supplies what collective security lacked: a principled threshold, a preference for prevention and a clear rule that coercion should pass through the Council.
R2P as a licence for the powerful
Critics in the Global South, and some in the West, see R2P as humanitarian intervention renamed. Libya is their evidence: resolution 1973 (2011) authorised the protection of civilians, and the NATO-led campaign ended with the overthrow of Gaddafi. India abstained on the resolution, as did Brazil, China, Germany and Russia, and Brazil proposed later that year that a 'responsibility while protecting' should discipline the use of force. On this view collective security, which targets aggression between states, is the safer doctrine because it does not license judgements about how states govern their own people.
The realist view of both
For realists such as Morgenthau, collective security assumes that states will judge every act of aggression alike and fight for the status quo even against friends; Carr treated the League's version as the ideology of satisfied powers. R2P inherits the flaw. Russian and Chinese vetoes on Syria from October 2011 onwards show that both doctrines operate only when no permanent member's interest is at stake.
04Structure
- 1
Introduction
Define both in a sentence each, with their sources: collective security in Article 16 of the League Covenant and Chapter VII of the Charter; R2P in the 2001 Commission report and paragraphs 138–139 of the 2005 World Summit Outcome. State the thesis: they share a logic of collective responsibility and a dependence on the Security Council, but differ in what they protect, why and how.
- 2
Similarities
Universalism; qualified sovereignty; Security Council authorisation; vulnerability to the veto. A short paragraph is enough, but it comes first because the question asserts it.
- 3
Scope
Inter-state aggression and threats to international peace against four atrocity crimes inside states. Note the overlap since the 1990s, when the Council began to treat internal crises as threats to international peace.
- 4
Goals
Order among states against the protection of people; state security against human security; sovereignty as a right against sovereignty as responsibility.
- 5
Methods
Deterrence and enforcement by all against one (Articles 41 and 42) against the three-pillar continuum of prevention, assistance and collective response, in which force is a last resort decided case by case.
- 6
Practice and assessment
Korea (1950) and Kuwait (resolution 678, 1990) for collective security; Libya (resolution 1973, 2011) and Syria for R2P. India's abstention on resolution 1973 shows a reading common among developing states: acceptance of the protective principle, wariness of coercion that stretches the Council's mandate.
- 7
Conclusion
R2P is best understood as collective security turned inward: a different object and a gentler sequence of means, with the same dependence on great-power consent.
05Evidence and examples
- League of Nations Covenant, Article 16: a member that resorted to war in disregard of its covenants was deemed to have committed an act of war against all other members.
- UN Charter, Chapter VII (Articles 39–51): the Security Council determines threats to the peace, breaches of the peace and acts of aggression and decides on non-military (Article 41) and military (Article 42) measures; Article 51 preserves the right of individual or collective self-defence.
- Korea, 1950: the Council recommended assistance to South Korea while the Soviet Union was boycotting it; the General Assembly's Uniting for Peace resolution (377 A) followed in November 1950.
- Kuwait, 1990: resolution 678 authorised member states to use 'all necessary means' to expel Iraq.
- International Commission on Intervention and State Sovereignty, The Responsibility to Protect (December 2001), co-chaired by Gareth Evans and Mohamed Sahnoun.
- 2005 World Summit Outcome, paragraphs 138–139: each state's responsibility to protect its populations from genocide, war crimes, ethnic cleansing and crimes against humanity, and collective action through the Security Council, case by case, when national authorities manifestly fail.
- Ban Ki-moon, Implementing the Responsibility to Protect (2009): the three pillars.
- Somalia, 1992: resolution 794 authorised force under Chapter VII to secure humanitarian relief, an internal crisis treated as a threat to international peace.
- Libya, 2011: resolution 1973 authorised measures to protect civilians; India abstained, as did Brazil, China, Germany and Russia.
- Syria: Russia and China vetoed draft resolutions from October 2011 onwards.
Counterarguments
The distinction can be overdrawn. Since the early 1990s the Security Council has treated internal crises, such as Somalia's famine and civil war (resolution 794, 1992), as threats to international peace, so collective security's machinery reached inside states before R2P was named. R2P's third pillar uses that same machinery, which suggests that the difference lies in justification rather than method.
The opposite objection is that R2P differs too much to be compared on equal terms. It is a political commitment adopted by the General Assembly, not a Charter obligation, and it creates no duty to act; collective security is written into the Charter's binding provisions. On this reading R2P is a norm about when collective security should be used, not a rival to it.
Evaluation
A strong answer judges the relationship rather than merely stating it. Collective security concerns the order of states and R2P the safety of people; collective security begins with force, R2P ends with it. Their shared dependence on the Council explains their shared record: effective when the permanent members agree, as over Kuwait, and paralysed when one of them objects, as over Syria.
R2P's normative gain, the acceptance in 2005 that sovereignty carries responsibilities, has outlasted its operational credibility after Libya. Where the Council is blocked, the search for accountability has moved to courts: The Gambia's genocide case against Myanmar (The Gambia v Myanmar: the Rohingya genocide case at the World Court) and German prosecutions of Syrian officials under universal jurisdiction (Universal jurisdiction: Syria's torturers in German courts). For India the comparison explains a consistent instinct: support for the Charter's collective machinery, and caution about coercion justified by the internal conduct of states.
Conclusion
Conclude that the two are siblings rather than twins. R2P borrows collective security's institutions and its last-resort instruments but turns them towards a different object, people rather than states, and a different sequence, prevention before coercion. Because both rest on great-power agreement, R2P has reproduced collective security's central weakness: its success depends less on the principle than on the politics of the Security Council.
An illustrative answer
Show an illustrative answer written for this platform
Written to show the framework in use. It is one way to answer, not the answer, and it is not an official or model answer.
Collective security and the responsibility to protect are both doctrines of shared responsibility under the United Nations. Collective security, written into Article 16 of the League Covenant and Chapter VII of the Charter, commits all states to act against any aggressor. R2P, formulated by the International Commission on Intervention and State Sovereignty in 2001 and endorsed by the 2005 World Summit, holds that states must protect their populations from atrocity crimes and that the international community must act when they manifestly fail.
The similarities are real. Both claim universal validity, both qualify sovereignty and both depend on Security Council authorisation, and therefore on the five permanent members.
They differ in scope, goals and methods. Collective security concerns aggression between states; R2P covers only genocide, war crimes, ethnic cleansing and crimes against humanity, usually within a state. Collective security aims to restore order among states; R2P aims to protect people, even against their own government, recasting sovereignty as responsibility. Collective security works through deterrence and enforcement, all against one, as against Iraq in 1990 under resolution 678. R2P works along three pillars, prevention, assistance and collective response, with force only as a last resort decided case by case.
Practice shows the shared weakness. Libya (2011) turned protection into regime change in the eyes of many states, including India, which abstained on resolution 1973; Russian and Chinese vetoes then blocked action on Syria. R2P is collective security turned inward: a different object, a gentler sequence of means and the same dependence on great-power consent.
Sources
- 01Charter of the United Nations, Chapter VII. United Nations, 1945
- 02International Commission on Intervention and State Sovereignty, The Responsibility to Protect, 2001
- 03UN General Assembly, 2005 World Summit Outcome (A/RES/60/1), paragraphs 138–139. United Nations, 2005
- 04UN Secretary-General, Implementing the Responsibility to Protect. United Nations, 2009
- 05Inis L. Claude, Jr., Swords into Plowshares: The Problems and Progress of International Organization, 1956
- 06Gareth Evans, The Responsibility to Protect: Ending Mass Atrocity Crimes Once and For All, 2008
- 07UPSC, Civil Services (Main) Examination 2025, Political Science and International Relations Paper II, question paper (opens in a new tab). Union Public Service Commission