Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2590
NATO member nations that ratify and implement AJP-3.28, the Allied joint doctrine for the military contribution to stabilization, into national doctrine and training
STANAG 2590 is NATO's ratification agreement committing member nations to implement AJP-3.28, the Allied joint doctrine for the military contribution to stabilization.
STANAG 2590 is the NATO Standardization Agreement covering AJP-3.28, the Allied joint doctrine for the military contribution to stabilization operations. This is Edition 2, promulgated 25 January 2023, superseding Edition 1 of 14 December 2015.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical or operational specification itself. STANAG 2590's own text is short and administrative: an aim, one interoperability requirement, the ratification and implementation machinery, and nothing else. The planning and execution detail the doctrine actually sets out lives in a separate publication, AJP-3.28, Edition A, which the STANAG names as the standard participating nations "agree to implement". Anyone looking for that operational content needs AJP-3.28 itself, not this cover agreement.
The stated aim is interoperability. The interoperability requirement reads: "To provide NATO/Coalition forces with a common doctrine for the planning and execution of stabilization operations in support of a host nation's government." Under the agreement clause, participating nations commit to a single named standard, AJP-3.28, Edition A. No other related document is listed, and this edition supersedes STANAG 2590, Edition 1, dated 14 December 2015.
STANAG 2590 binds a nation only once that nation ratifies it, and ratification and implementation are tracked as two distinct steps, both recorded in the NATO Standardization Document Database (NSDD). Nations are invited to examine their ratification and advise the NATO Standardization Office of their ratification and implementation intentions. Implementation is defined concretely: AJP-3.28 being included into national doctrine, promulgated nationally, included in national education and training programmes, and used by the personnel and units that would operate in NATO operations or exercises. Allied nations and NATO bodies are then obliged to report implementation details through NATO's electronic reporting tool; partner nations are only invited to do the same. No NATO Effective Date applies to this edition, so there is no Alliance-wide deadline attached to either step.
STANAG 2590 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status to NATO for the record, and periodic review of the STANAG itself under AAP-03, with the result recorded in the NSDD. Nobody is "STANAG 2590 certified", and the document never uses that language. It says nothing about how conformity with AJP-3.28's own doctrine is checked in practice - that is a matter for whatever contract or tasking brings the doctrine into scope.
STANAG 2590 covers AJP-3.28, the Allied joint doctrine that carries the actual planning and execution content. Its own periodic review runs under AAP-03, which the STANAG names as the procedure its review follows, not as a source of technical content.
STANAG 2590 carries no technical or operational content of its own to evidence: everything to work against sits in AJP-3.28, the doctrine this agreement brings into force.
Where an organisation needs to show that its procedures, exercises or training follow a NATO-ratified doctrine, ComplyTrain holds that documentation - procedures, training records, exercise reports - with version history and an audit trail, ready for whoever asks to see it.
ComplyTrain does not tell you whether a given nation has ratified STANAG 2590, and it does not map to requirements in AJP-3.28 itself: neither is something a compliance platform can state on a nation's behalf.
Which STANAGs and Allied Publications actually apply to a given programme is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 2590 and AJP-3.28, and talk to us about the evidence trail once you know which ones are in your contract.
Tell us how you need to work with STANAG 2590 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
Only where a nation has ratified it and a contract or tasking invokes AJP-3.28. A STANAG binds a nation once ratified; it reaches a supplier through whatever tender or contract clause names the doctrine, not automatically.
STANAG 2590 is the ratification agreement; AJP-3.28 is the doctrine itself. STANAG 2590's own text sets out no planning or execution detail - it commits participating nations to implement AJP-3.28.
Edition 2, promulgated 25 January 2023. It supersedes STANAG 2590, Edition 1, dated 14 December 2015.
No. The document names no certification scheme; NATO's own role is limited to recording nations' ratification and implementation status in the NSDD and reviewing the STANAG under AAP-03.
No. Its "NATO Effective Date (NED)" is marked "Not applicable" in this edition, so there is no Alliance-wide date attached; whatever deadline applies comes from a nation's own timetable or a contract that invokes the doctrine.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.