2.3.1. These increments/annexes must be validated by the validation authority for the base document as specified by the JSD. Sponsors cannot attach additional annexes without validation by the designated validation authority.

2.3.2. In an incremental development approach, each increment may require individual validation by the validation authority of the base CDD. If these are submitted over time, the Sponsor shall submit the base CDD along with the increment, but only the increment will be validated by the validation authority.

2.3.3. In a FoS approach, several annexes may be submitted with the base document and all annexes will be validated with the base document. If additional systems in the family are submitted for validation, they must be individually validated in a similar fashion to the incremental approach

2.3.4. Sponsors will ensure the Increment/Annex has all appropriate certifications or endorsements prior to validation.

2.4. Submission.

2.4.1. Sponsors who wish to submit incremental or FoS annexes should consult with the Joint Staff Gatekeeper prior to pursuing this approach. The Joint Staff Gatekeeper may reject an annex, if it is outside the scope of the base document.