Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 4559
Defence contractors and systems integrators building or connecting ISR systems under a contract that invokes AEDP-17, AEDP-18 or AEDP-19
STANAG 4559 is NATO's agreement committing member nations to implement one or more of AEDP-17, AEDP-18 and AEDP-19, the interfaces and services for exchanging ISR data between allied systems.
STANAG 4559 is a NATO Standardization Agreement, currently Edition 4, promulgated 28 March 2018. Like most STANAGs, it is not itself a technical specification. It is the agreement by which NATO nations commit to implement one or more of AEDP-17, AEDP-18 and AEDP-19, each Edition A, the publications that carry NATO's standard ISR (intelligence, surveillance and reconnaissance) library interfaces and services. The technical detail a reader wants sits inside whichever of those three publications a nation or contract specifies, not inside this short cover document. Read on its own, STANAG 4559 requires almost nothing of a contractor or integrator directly: its obligations run to nations, and it reaches a supplier only indirectly, once a nation has implemented it and a contract or tender brings AEDP-17, AEDP-18 or AEDP-19 into play.
STANAG 4559 is explicit that it binds nations, not suppliers. Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Ratification and implementation are separate steps, and once ratified, the agreement "is effective upon receipt and ready to be used by the implementing nations and NATO bodies." So "is STANAG 4559 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and, for a contractor, on whether a specific contract or tender then invokes AEDP-17, AEDP-18 or AEDP-19.
The stated aim is "to respond to the following interoperability requirements," and the requirement itself is direct: "to promote interoperability of North Atlantic Treaty Organization (NATO) intelligence, surveillance, and reconnaissance (ISR) library interfaces and services for the exchange of shared ISR data, products and schemas." Under "Agreement," participating nations "agree to implement one or more of the following standards," listed as AEDP-17, Edition A, AEDP-18, Edition A, and AEDP-19, Edition A. A nation can choose any one of the three, or more than one; STANAG 4559 does not require all three at once, and it sets out no interface, format or schema of its own.
Nations examine their own ratification of the STANAG and, where they have not already done so, advise the NATO Standardization Office (NSO) of their implementation intentions; they later provide their actual implementation details to the NSO as well. The STANAG counts itself implemented "when standard ISR library interfaces and services systems are incorporated into the nations' ... in accordance with the requirements of one or more of AEDP-17, AEDP-18 and AEDP-19, as documented in the national responses." Nations are invited to report their effective implementation using the form at Annex H to AAP-03(J); partner nations, invited to adopt the STANAG without the ratification obligation that binds a member nation, report their adoption using the form at Annex G to AAP-03(J).
This edition, Edition 4, supersedes the previous Edition 3 of STANAG 4559. "This STANAG is to be reviewed at least once every three years. The result of the review is recorded within the NSDD," and any nation or NATO body may propose a change at any time through a standardization proposal to the tasking authority, processed at the next review. It is supervised under NATO's Air Force Armaments Group (NAFAG, AC/224) and the Joint Capability Group on Intelligence, Surveillance and Reconnaissance (JCGISR); Germany is named as custodian.
STANAG 4559 names no certification or accreditation scheme, no assessment body and no audit of a contractor or product. The only accountability it describes is procedural: nations reporting their own ratification and implementation decisions to the NSO, and the periodic review of the agreement's own currency described above.
STANAG 4559 itself gives an integrator nothing to implement in software: it is an agreement between nations, and the interface and service detail sits in whichever of AEDP-17, AEDP-18 or AEDP-19 a contract calls up. Where ComplyTrain fits is the paperwork trail behind that work: documented procedures for how an ISR system's library interfaces are configured against the AEDP a contract specifies, records of the interoperability or data-exchange tests that show a system meets it, and training records showing the engineers who configure and maintain the interface understand what it requires.
ComplyTrain does not build, configure or test an ISR library interface, or decide which of AEDP-17, AEDP-18 or AEDP-19 a given contract requires - that work is done in the day-to-day engineering by the integrator and the nation concerned, working to whatever a specific contract requires. What applies to a specific programme is set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 4559 - if you are weighing up what a programme's data-exchange requirement actually calls for, we're glad to talk it through.
Tell us how you need to work with STANAG 4559 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.
Not on its own. A STANAG binds a nation once that nation has ratified and implemented it, and it reaches a contractor or integrator only once a contract or tender invokes AEDP-17, AEDP-18 or AEDP-19. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 4559 is the cover agreement: it commits nations to implement one or more of AEDP-17, AEDP-18 and AEDP-19 but contains no interface, format or schema detail itself. The three AEDPs are the publications that actually set out NATO's standard ISR library interfaces and services.
No. STANAG 4559 asks a nation to implement "one or more of the following standards," so a nation, and by extension a programme, can adopt just one of AEDP-17, AEDP-18 or AEDP-19 if that is what the contract or national implementation specifies.
No. STANAG 4559 describes no certification or accreditation scheme. Nations report their own ratification and implementation decisions to the NSO, and the only other stated check is a periodic review of the agreement's own currency, at least once every three years. NATO does not certify organisations or products against a STANAG.
Edition 4, promulgated 28 March 2018, is current. It supersedes the previous Edition 3 of STANAG 4559.
Partner nations are separately invited to adopt the STANAG and report their adoption using a different form, but adoption for a partner nation is voluntary rather than the ratification obligation that binds a member nation.
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.