Collective security and responsibility to protect (R2P) are similar but different in scope, goals and methods. Explain.

Collective security and responsibility to protect (R2P) are similar but different in scope, goals and methods. Explain. (2025, 15 Marks)

Collective security, given its modern form by Woodrow Wilson and written into Chapter VII of the UN Charter, commits all members to meet aggression by any state with their combined power. The Responsibility to Protect, framed by the International Commission on Intervention and State Sovereignty (ICISS, 2001) and adopted in narrower form at the 2005 World Summit (paragraphs 138–139), makes sovereignty conditional on shielding people from mass atrocity. They share a gatekeeper but differ on trigger, purpose and means.

Where they are similar

  • Collective coercion: certain conduct justifies a community response, not self-help.
  • One gatekeeper: force needs Security Council authorisation under Chapter VII. R2P was meant to end the unilateral “humanitarian intervention” of Kosovo (1999).
  • Graduated tools: diplomacy and Article 41 sanctions come before force.
  • One weakness: both are hostage to the veto.

Where they differ

CriterionCollective securityR2P
Scope (trigger)Any act of aggression or breach of the peace (Article 39)Four crimes: genocide, war crimes, ethnic cleansing, crimes against humanity
Direction of threatAcross borders, state against stateInside borders, usually a state against its people
GoalRestore the status quo, protect weaker statesProtect populations; territory and regime are incidental
SovereigntyInviolable, to be defendedConditional on responsibility
MethodsSanctions, then force against a named aggressorPrevention and capacity-building first; force last
Legal statusBinding Charter obligationPolitical commitment; no duty to act
  • Scope. Collective security is open about the act but blind to what a government does to its own citizens. R2P reaches inside the frontier, but the 2005 text confined it to four crimes to reassure post-colonial states.
  • Goals. One defends the inter-state order, as when Resolution 678 (1990) authorised the liberation of Kuwait. The other advances human security, drawing on Francis M. Deng’s Sovereignty as Responsibility (1996).
  • Methods. Collective security has no preventive limb. R2P runs on three pillars: the state’s own duty, international assistance, and timely collective response, with ICISS’s precautionary tests (right intention, last resort, proportional means, reasonable prospects) governing force.

The record

  • Libya, 2011: Resolution 1973 passed 10–0, with India, Brazil, Germany, China and Russia abstaining; the protection mandate ended in regime change. Brazil’s Responsibility while Protecting (2011) proposed sequencing and monitoring. Hardeep Singh Puri, then India’s Permanent Representative, made Libya a central case in Perilous Interventions (2016).
  • Syria and Myanmar show pillar three blocked by vetoes, as collective security stalls over Ukraine, where the aggressor is a permanent member.
  • At the Assembly’s R2P debate of 6 July 2026, 50 states spoke for 89; critics again pressed selective application, above all over Gaza.
  • India accepts the first two pillars and holds that only the Council may authorise force, never for regime change.

Conclusion

R2P extends collective security’s logic from states to people and from punishment to prevention, so the two are complementary but not identical. It inherits the same flaw: action depends on great-power consent. Its credibility now rests on pillar two and on accountability guardrails of the kind Brazil proposed.