Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2358
Defence and NATO medical planning staff working to a contract or tasking that invokes STANAG 2358 or the AMedP-7.2 publication it covers
STANAG 2358 is NATO's covering agreement by which member and partner nations commit to implement AMedP-7.2, Edition A, the publication it covers.
STANAG 2358 is NATO's covering agreement for AMedP-7.2, Edition A, "CBRN first aid handbook." This is Edition 5 of the STANAG, promulgated 15 February 2018, and it supersedes Edition 4.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical content itself. STANAG 2358's own text is short and administrative: an aim, an agreement, a list of related documents, and the ratification, implementation and review machinery. The publication it names, AMedP-7.2, Edition A, is where the operational content actually sits, and its own record is the place to look for what it covers.
The stated aim responds to an interoperability requirement: a coordinated response to CBRN incidents involving both military and civilian personnel, in support of NATO's Defence Against Terrorism programme. Participating nations agree to implement AMedP-7.2, Edition A, which is the standard named in the agreement clause. The cover also lists two other STANAGs as related documents: STANAG 2461, which covers AMedP-6, Volume I, on the medical aspects of NBC defensive operations, and STANAG 2873, which covers AMedP-7.6, a commander's guide on medical support to CBRN defensive operations.
STANAG 2358 binds nations, not suppliers. Nations are invited to examine their own ratification of the STANAG and, where they have not already done so, to advise the NATO Standardization Office of their intention regarding implementation; the responses are recorded in the NATO Standardization Document Database (NSDD). Implementation is a further, separate step, coming into effect once a nation has issued the orders and instructions needed to put the covered standard's content into practice. Nations report their effective implementation using a form in Annex H to AAP-03, suffixed "(J)" in this edition; partner nations report adoption using Annex G of the same publication. The STANAG is reviewed at least once every three years, with the result recorded in the NSDD, and any nation or NATO body may propose a change to the tasking authority at any time.
The tasking authority is the Military Committee Medical Standardization Board, through the Medical Standardization Working Group (MCMedSB, MedStdWG). The custodian is the United Kingdom, through its Chemical, Biological, Radiological and Nuclear Medical Working Group (CBRNMedWG).
STANAG 2358 describes no certification scheme and no audit. What it describes is nations reporting their ratification and implementation status to the NATO Standardization Office for the record; the document never uses the word "certified" or "certification." Where the operational content AMedP-7.2 sets out does get checked in practice, the assessor and the evidence required are set by that publication and by the contract or tasking that invokes it, not by this cover agreement.
STANAG 2358 covers AMedP-7.2, the Allied Medical Publication that carries the CBRN first aid content itself. Its "Other Related Documents" list STANAG 2461 (covering AMedP-6, Volume I, on the medical aspects of NBC defensive operations) and STANAG 2873 (covering AMedP-7.6, a commander's guide on medical support to CBRN defensive operations). Reports of ratification and implementation use forms in AAP-03.
STANAG 2358 itself is an agreement between nations, not a document an organisation implements day to day. The publication it covers, AMedP-7.2, is where the operational CBRN response content sits, and that is where any support answer specific to the content belongs.
What ComplyTrain does for this kind of covering agreement generally: hold the record of which edition an organisation is working to, the fact of its ratification or adoption status where a customer or contract references it, and a link through to the publication it covers so nobody is left checking against a superseded edition. It also gives a defence organisation one auditable place to hold the procedures, training records and audit findings that a contract's quality clause requires once AMedP-7.2 is in scope.
ComplyTrain does not determine whether a nation has ratified STANAG 2358, and it does not carry out or evidence the CBRN response work that AMedP-7.2 itself sets out. That is operational and medical planning work, done under the publication and the contract's own terms.
Which STANAGs and Allied Publications actually apply to a given contract is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 2358 and AMedP-7.2, 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 2358 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 and implemented it, and it reaches a supplier only where a contract or tasking invokes it or the AMedP-7.2 publication it covers. The STANAG itself sets no NATO-wide compliance date.
STANAG 2358 is the NATO agreement by which nations commit to implement AMedP-7.2, Edition A; AMedP-7.2 is the Allied Publication that carries the actual CBRN first aid content. Ratifying STANAG 2358 is how a nation commits to implement AMedP-7.2.
No. STANAG 2358 describes nations ratifying and reporting implementation to the NATO Standardization Office, recorded in the NATO Standardization Document Database. It describes no certification or audit scheme for a supplier or a product.
The document states that this edition supersedes STANAG 2358, Edition 4, but it does not itself describe what changed between the two editions.
The United Kingdom, acting through its Chemical, Biological, Radiological and Nuclear Medical Working Group (CBRNMedWG).
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.