International (NATO; ratifying nations and NATO bodies; FMN)

NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding)

37 controls. 167 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

37 controls 167 frameworks share controls with it International (NATO; ratifying nations and NATO bodies; FMN) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

NATO STANAG 4774 and 4778 Confidentiality Labelling Evidence & Implementation Kit

37 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
STANAG-1STANAG 4774 Confidentiality Label Schema and XML Structure129
STANAG-2STANAG 4778 Metadata Binding Mechanism and Cryptographic Binding168
STANAG-3Label Authoring, Originator Identification, and Policy Identifier0
STANAG-4Cross-Domain Label Translation and Interoperability Testing0
STANAG-5Label Verification on Ingress and Label Preservation Through Processing0
STANAG-6Label Handling in Email, Documents, and Storage0
STANAG-7Incident Response, User Training, and Label Audit0
STANAG-8Label Caveats, Releasability, and Conditions0
4774-5Apply the governing-policy constraints and the PUBLIC policy for unlabelled external information0
4774-A1.1Bind every confidentiality label to its information and use the three label roles correctly0
4774-A1.2Give each label a creation time and either a review date or succession handling0
4774-A1.3Populate the mandatory label content: ConfidentialityInformation and CreationDateTime0
4774-A1.4Express confidentiality information through the policy identifier, classification, privacy mark and categories0
4774-A1.5Type every category as restrictive, permissive or informative and use GenericValue only0
4774-A1.6Validate labels against the registered schema and namespace0
4774-A2.1Label NATO information under the NATO policy identifier with its classification and privacy-mark rules0
4774-A2.2Include exactly one Context value in every NATO-policy label, flagged Releasable when releasability applies0
4774-A2.3Use Only to narrow and Releasable To to widen dissemination0
4774-A2.4Carry Additional Sensitivity and Administrative markings as categories0
4778-2.2Implement bindings that meet the five minimum binding requirements0
4778-3.2Choose encapsulating, embedded or detached binding and cryptographic protection to the required assurance0
4778-3.5Apply the four inheritance rules for granular binding in composite objects0
4778-4.3Structure the Metadata Binding with a container, bindings, metadata and data components0
4778-4.3.4Encode embedded content and resolve references with the prescribed attributes and XPath rules0
4778-4.5Wrap the binding and any signatures in a BindingInformation element0
4778-4.6Keep every BDO locatable and resolvable by information management services0
4778.1-3Label top-down and apply the XPath node rules to granular XML labels0
4778.1-5Canonicalize data before signing or verifying bindings0
4778.2-12Label common XML artefacts, including security policy information files0
4778.2-2Protect bindings cryptographically per the cryptographic artefact profile0
4778.2-3Bind labels to email with the Binding-Data header (SMTP profile)0
4778.2-4Bind labels to XMPP message and IQ stanzas (XMPP profile)0
4778.2-5Bind labels to Office documents and generic packages (OOXML and OPC profiles)0
4778.2-6Bind labels to web service messages (SOAP, REST and WSMP profiles)0
4778.2-9Bind labels to arbitrary files with sidecar or XMP files0
STANDARDSSTANAG 4774 and STANAG 4778: the standards and their purpose0
STATUSStatus: Edition 1 of both STANAGs with Edition A Version 1 of both ADatPs are current; no 'Edition 2 (2020)' exists0

Tell me when NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Customer agreement clauses
  • Processing instructions log
  • Use restriction policy
  • Audit trail
  • QA checklist
  • Reviewer signoff
  • Key management procedures
  • Data protection and classification
  • Encryption of data at rest and in transit
  • Key management

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for NATO STANAG 4774 (Confidentiality Metadata Labels) and STANAG 4778 (Metadata Binding), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition