What it is
STANAG 4683 is the NATO Standardization Agreement on NATO Technical Sharable Software (NTSS). Edition 1, promulgated on 8 September 2009 under the sponsorship of CNAD, AC/225 NAAG, ICGIF, it covers the publication AOP-61.
NATO has not released STANAG 4683 publicly, so this page describes it from a public national implementation, the Czech defence standard ČOS 051661 (1st edition), which states that it introduces STANAG 4683 edition 1 into Czech use. A national implementation can add national requirements, so treat what follows as the Czech implementation's content, not as NATO's own text.
What the Czech implementation covers
ČOS 051661 describes NTSS as a set of software products designed for applications dealing with technical ballistics. Each NTSS product implements technology found in one or more STANAGs within the remit of NAAG Land Capability Group 3 (LCG-3), Sub-group 2, and the standard gives interior ballistics, exterior ballistics, firing-table generation and 6/7-degree-of-freedom trajectory simulation as example NTSS product areas.
The standard names related documents that NTSS technology draws on: STANAG 4119 (adoption of standard cannon artillery firing table format), STANAG 4355 (the modified point mass and five degrees of freedom trajectory models), STANAG 4367 (thermodynamic interior ballistic model with global parameters), STANAG 4400 (derivation of thermochemical values for interior ballistic calculation), STANAG 4618 (six/seven degrees of freedom guided projectile trajectory model) and STANAG 4655 (an engineering model to estimate aerodynamic coefficients), alongside AOP-61 itself.
Participating nations are responsible for developing and maintaining NTSS software through an NTSS configuration manager, who informs known users of updates, and an AOP is developed and kept current, defining the structure, technology and procedures for each NTSS product area. Any NATO government may hold NTSS software and documentation; sharing of databases is a decision for each NATO government and is granted only against a justified request. A nation that modifies NTSS software for its own needs must report the change to NAAG LCG/3 SG/2 so the standardised baseline stays aligned.
What the Czech implementation requires
ČOS 051661 sets a security marking for every element of NTSS. Source code is marked and handled as NATO RESTRICTED on any medium, and a member state that incorporates NTSS source code into a national application must protect the resulting source code at no less than that level. Object code carrying no debugging information is NATO/PfP UNCLASSIFIED; object code that does carry debugging information is NATO RESTRICTED. Executable code and NTSS documentation are both NATO/PfP UNCLASSIFIED, as are external database files, unless they are embedded in object or executable code, in which case they take that code's marking.
Release is controlled too. A participating state may give NTSS software to another NATO member government without other participating states' prior consent; release to a non-member government, or to a contractor, is subject to further conditions and approval. Any resulting agreement must forbid onward distribution of NTSS technology, information or code without official written authorisation from the responsible government, and must forbid reverse engineering to recover source or object code from executable or object code.