Brief Energy

Dangote Feedstock Brief

ELDR Intelligence · Energy

Large-scale refining capacity in Nigeria has shifted a long-standing question from theoretical to operational: can a refinery of this scale source enough domestic crude reliably, or does it remain structurally dependent on imported feedstock priced and shipped on international terms?

The Dangote Refinery's emergence as one of the largest single-train refining complexes globally has made this a live structural issue for Nigerian energy policy, not just a commercial question for the refinery's own operations. The dynamics are worth understanding in general terms for any institution with downstream exposure to West African energy markets.

The Structural Tension

Domestic crude allocation policy, naira-denominated settlement mechanisms, and the logistics of moving crude from production fields to a coastal refining complex all interact in ways that determine whether a refinery of this scale can actually run primarily on domestic feedstock, or whether it ends up — at least for a meaningful share of throughput — sourcing from the international market despite operating in one of the world's significant crude-producing countries.

Why It Matters Beyond Nigeria

The outcome has implications well beyond one refinery's margins. Domestic refining capacity at this scale changes Nigeria's import/export balance for refined products, affects regional fuel pricing across West Africa, and shifts foreign exchange dynamics depending on how much feedstock and output settle in naira versus dollars. Institutions with exposure to Nigerian energy, logistics, or downstream distribution should track feedstock-sourcing patterns as a leading indicator of broader policy and currency dynamics, not just a refinery-specific operational detail.

The Takeaway

Feedstock sourcing for large-scale African refining capacity is a structural policy question with currency and trade-balance implications well beyond the refinery gate. ELDR Intelligence tracks this as part of our broader West African energy coverage.

Keep Reading

More from ELDR Insights.

All Insights Request Confidential Consultation

Research / Cybersecurity

Cybersecurity ELDR Whitepaper

The CISO's Documentation Problem

March 2026 · ELDR Intelligence · 12 min read · PDF ↓

The gap between what an organisation's security controls actually do and what its documentation says they do is one of the most consequential and least discussed vulnerabilities in enterprise cybersecurity. Auditors and regulators test documentation. Adversaries test controls. When the two diverge — when documentation describes a control environment that doesn't exist in operational reality — the organisation is simultaneously exposed on both fronts.

The Documentation Debt Problem

Most enterprise security programmes accumulate documentation debt the way most software programmes accumulate technical debt: incrementally, invisibly, and at accelerating cost. A control is implemented; the documentation follows later, or not at all. A control changes with a system update; the documentation isn't updated. A new regulatory requirement arrives; documentation is produced to satisfy the requirement but not connected to actual operational practice.

The result is a documentation portfolio that is formally complete but functionally unreliable — a risk that typically only becomes visible at audit time, during a regulatory examination, or after a security incident when incident response documentation turns out not to describe what anyone actually does.

The CISO who can hand an examiner a complete, current, operationally accurate documentation set on day one of an examination is communicating something important about the organisation's security maturity. The one who cannot is communicating something important too — just not something they want communicated.

Why Security Documentation Is Structurally Underfunded

Security documentation is underfunded for structural reasons that organisations should acknowledge rather than pretend to fix through effort and goodwill. First, documentation is rarely attributed a direct return on investment in security budgets — it is treated as overhead rather than as the governance infrastructure that makes everything else auditable and defensible. Second, the people best positioned to produce accurate documentation — the security engineers and architects who implement and maintain controls — are the least likely to prioritise it against operational demands.

Third, documentation tools are typically an afterthought in security programme architecture. Organisations invest heavily in SIEM, EDR, vulnerability management, and GRC platforms, then manage documentation in SharePoint folders or Confluence wikis with no governance, version control, or lifecycle management. The quality of output reflects the quality of the infrastructure.

The Documentation-First Security Architecture

A documentation-first security architecture inverts the standard approach: rather than implementing controls and then documenting them, it begins with documentation architecture — defining the structure, format, governance, and lifecycle of security documentation before the controls it describes are implemented.

In practice, this means adopting structured authoring standards for security documentation (DITA/XML or equivalent structured formats); implementing version-controlled documentation repositories with formal change management; defining documentation ownership at the control level; and establishing continuous documentation review cycles aligned with control change management processes rather than the annual audit cycle.

What Good Looks Like

The benchmark for documentation-first security governance is not a specific framework or standard — it is the question: if an examiner arrived tomorrow and requested documentation of any control in our environment, could we produce current, accurate, operationally verified documentation within two hours?

Organisations that can answer yes to that question have solved the CISO's documentation problem. They have done it not by writing more documents, but by building governance infrastructure that keeps documentation current as a natural output of operational processes rather than as a separate, episodically funded remediation exercise.

ELDR's advisory practice has developed a Documentation Infrastructure Assessment methodology that maps the gap between current documentation maturity and examination-ready capability, and produces a prioritised remediation roadmap. Contact ELDR Advisory for an assessment framework.