Model answer & approach
- Collective security and responsibility to protect (R2P) are similar but different in scope, goals and methods. Explain. (Answer in 250 words)
Introduction
Collective security guards states against aggression; the responsibility to protect guards populations against their own states. Both work through the Security Council, and both stall at the same veto, but they answer different questions.
Body
1. Origins: collective security runs from Articles 10-16 of the League Covenant to Chapter VII of the UN Charter, resting on Article 2(4)'s ban on force. R2P is far younger — the ICISS report (2001) and paragraphs 138-139 of the 2005 World Summit Outcome Document, built on Francis Deng's idea of sovereignty as responsibility.
2. Scope: collective security is inter-state and triggered by aggression, as in Korea (1950) and Kuwait (Resolution 678, 1990). R2P is intra-state and triggered by four named crimes: genocide, war crimes, ethnic cleansing and crimes against humanity.
3. Goal: the first protects sovereignty and territorial order; the second treats sovereignty as conditional on protecting one's own people.
4. Method: collective security is reactive and enforcement-first. R2P is graduated across three pillars — state responsibility, international assistance, and timely and decisive collective response — with force explicitly last.
5. Their shared weakness: both require Council authorisation, and both are hostage to the veto, as Syria's record of vetoes shows.
6. The credibility problem: Libya (Resolution 1973, 2011) turned protection into regime change, prompting Brazil's "responsibility while protecting" and hardening Indian, Russian and Chinese scepticism of the third pillar.
Conclusion
R2P is not a successor to collective security but a complement to it: one polices borders, the other what happens behind them. India's position captures the difference — full support for prevention and assistance, deep caution about coercion.
Open this in the study app →