Libya's risk is structural rather than kinetic. Large-scale fighting is episodic, but the country is governed by two competing administrations with overlapping armed constituencies, and the operational question is which authority controls the specific airport, port, road or district you intend to use.
Political and security drivers
- Rival administrations in Tripoli and the east, with periodic armed clashes between Tripoli-based formations.
- Contested control of oil facilities and of the central bank, with production shutdowns used as political use.
- Militia checkpoints and detention practices affecting movement, particularly for migrants and for local staff.
- Migration-route criminality, trafficking and associated corruption exposure across the coastal corridor.
- Explosive remnants of war in previously contested urban areas, and residual Islamic State activity in the south.
Compliance exposure
Sanctions listings, opaque beneficial ownership and the interpenetration of armed groups and commercial entities make counterparty due diligence a first-order requirement in Libya, not a procurement formality. Payment routes and local partner selection carry more organisational risk here than movement planning does.
In Libya the due diligence file is the security control. Everything else is downstream of who you paid.
Operating implications
- Screen every partner, landlord, contractor and intermediary against consolidated sanctions and PEP data, then re-screen periodically.
- Map control of each facility you use, airport, port, warehouse, guesthouse, and review after any political shift.
- Plan for abrupt airport closures and border restrictions with an alternative exit route always identified.
- Manage local staff detention risk explicitly, including which authority to approach and through whom.
- Treat flood and infrastructure failure, as seen at Derna, as a live contingency rather than an outlier event.