02 - Exhibit A CDRLs 9 Nov 21.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

CONTRACT DATA REQUIREMENTS LIST (CDRL)

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

A TDP ____ TM _____ OTHER __X_______________________

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

TETRAS II FA2487-21-R-0006

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE GROUP

A033 OPERATION AND MAINTENANCE INSTRUCTIONS FOR

RESEARCH AND DEVELOPMENT (R&D) EQUIPMENT N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

TOTAL PRICE

DI-MISC-81414A SOW 1.3.1, 1.3.2, 1.3.3, 1.3.4 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

LT REQUIRED ASREQ SEE BLOCK 16

a. ADDRESSEE

b. COPIES

8. APP CODE

SEE BLOCK 16

11. AS OF DATE 13. DATE IF SUBSEQUENT SUBM.

Draft Final

A N/A SEE BLOCK 16 Reg Repro

16. REMARKS

BLK 4: TAILORING, IF REQUIRED, SHALL BE AS SPECIFIED FOR EACH INDIVIDUAL DELIVERY

ORDER.

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

BLKS 10, 12, 13 & 14: DELIVER AS SPECIFIED IN THE INDIVIDUAL DELIVERY ORDER.

BLKS 15: DELIVERY ORDER DEPENDENT

15. TOTAL ▬▬▬▬► 0 0 0

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

JULIE SLEZIA

30 Jul 2021

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 33 of 52 Pages

2021-08-18T18:28:27-0500

SLEZIA.JULIE.A.1008583109

DATA ITEM DESCRIPTION

Title: LESSON STRATEGY REPORT

Number: DI-MISC-81457A Approved Date: 20070927 AMSC Number: F9009 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: 11 Applicable Forms: N/A Use/Relationship: The Lesson Strategy Report describes the instructional strategies, subject matter content, instructional materials formats, and other guidance for authoring and producing the training materials for each lesson. It is used to guide the design of lessons and to prepare the Instructor Planning Document and the Student Guide.

a. This Data Item Description (DID) is applicable to all contracts requiring courseware development. It is used in conjunction with DI-MISC-81458, Instructor Planning Document;

DI-MISC-81456, Student Guide; DI-MISC-81459, Syllabus; and DI-ILSS-80569, Objectives and Media Analysis Report.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.

c. DI-MISC-81457A supersedes DI-MISC-81457.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the contract.

2. Format. The Lesson Strategy Report shall be in the contractor’s format.

3. Content. The Lesson Strategy Report shall include the following sections:

3.1 Introduction section. This section shall provide a brief description of the purpose and expected application of the Lesson Strategy Report.

3.2 Description of the lesson strategies. This section describes the lesson strategies for all instruction included in the course syllabus. Lesson strategies should ensure traceability to the training requirements. Air Force Manual (AFMAN) 36-2234 should be used for guidance.

Each lesson strategy shall include:

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:45Z

Check the source to verify that this is the current version before use.

DI-MISC-81457A

a. Cover sheet. This page shall include the title, classification, signatures of the author and approving authority, and date.

b. Lesson strategy organization and format. This section shall describe the organization and format of the lesson and segment strategies. It shall list the headers or section designators that are used, explain what each one means, and describe the type of information that is found under each. A key shall be used to explain the symbology. This explanation shall be supported with one or more illustrative examples. The lesson strategy shall exhibit traceability to the courseware development process and shall include:

(1) Lesson reference number. The lesson strategy shall consist of a reference number, a unit, and lesson number referenced item from the syllabus.

(2) Lesson title. The lesson strategy shall have a short title description of the subject to be covered that is taken from the syllabus lesson title.

(3) Lesson media. The medium or media shall be identified for each lesson. For lessons with multiple media, objectives for each medium shall be indicated.

(4) Lesson overview. A brief overview of the content of the lesson shall be provided for lesson authors, subject matter experts (SMEs), and students. Included should be an explanation of why the lesson is required, how it is related to previous lessons, and how it fits into the total program.

c. Learning objectives. This section shall describe the type of learning required for each lesson objective and learning event. A strategy for each lesson, learning event, activity, and testing procedure shall be provided. Each objective should have two numbers assigned: (1) a sequence number to indicate its order of presentation and (2) an identification number to indicate its rank in the objectives hierarchy.

d. Unit and lesson maps. The unit map shall contain a short flow diagram showing the sequences and relationships among lessons in the instructional unit. The lesson map shall include a short flow diagram showing the hierarchical relationships among lesson objectives.

e. Lesson design strategy. This section shall describe decision making processes and strategies to be used in designing and implementing the presentation of material and testing student mastery of subject matter. Specific strategies shall include methods of interaction, testing, and remediation. Segments to be tested shall be identified and the method of testing defined. Specific emphasis shall be placed on the design strategy for developing and implementing the interactive courseware (ICW) into the training program and equipment.

Training, learning and branching strategies shall also be included, when required. A section parts used shall be appropriately labeled and sequenced under the section part title, e.g., percentage of drill and practice, demonstration, and simulation. The lesson design strategy shall identify the conventional techniques, practices, principles, or procedures to be used throughout the design and development of the ICW module and lesson. The following information shall also be provided:

(1) Type of behavior. A statement of what the student must do in order to show mastery of the objective, e.g., remember, use aided, or use unaided.

(2) Generalities. This section shall include the facts to be memorized, the critical attributes of a concept, the steps to follow in applying a rule or procedure, or the cause and effect relationship of a principle. Aids shall be included in the instructional content to help the student remember and use the generality. This section shall list the most commonly made student errors when learning the generality or test items.

(3) Instance production. A description of each type of scenario that is to be included in the examples, practice, and test items shall be provided. A table shall be provided listing the total number of examples, practice, and test items that the lesson author must product for each type of instance.

f. Test items. This section shall include the type of test and the approach for feedback and remediation based on the lesson design strategy. A list of the test items to be used in measuring the student’s knowledge of the generality shall be provided and include a statement of the minimum acceptable passing criteria for the lesson or segment. A list of examples and practice exercises to be used in support of the instruction of the generality shall also be provided.

g. Lesson format guide. This section shall contain explanations of how each section of the lesson and segment specifications shall be used during lesson authoring. Special instructions or additional information shall be provided to ensure accurate communication of the content for authors and artists. It shall contain a description on the following items:

(1) Text and graphic layout conventions.

(2) Interpretation of lesson strategy sections.

(3) Data sources for expansion of lesson strategy sections.

(4) Learning strategy guidelines.

(5) Use of symbology.

(6) Titling information

(7) Figure numbering.

(8) Referencing conventions.

(9) Page numbering.

h. Prototype lesson. This section shall consist of a prototype lesson to demonstrate how the format guide is to be used in conjunction with a lesson strategy to produce authored lessons. A complete lesson strategy and resulting prototype lesson shall conform to the lesson format guide.

i. Resource requirements. The section shall contain a summary of resource requirements. Included in this discussion shall be a description of the types of personnel and their respective roles and responsibilities for lesson strategy development.

4. End of DI-MISC-81457A.

3.1 Introduction section. This section shall provide a brief description of the purpose and expected application of the Lesson Strategy Report.

3.2 Description of the lesson strategies. This section describes the lesson strategies for all instruction included in the course syllabus. Lesson strategies should ensure traceability to the training requirements. Air Force Manual (AFMAN) 36-2234 should be used for guidance. Each lesson strategy shall include:

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A034

LESSON STRATEGY REPORT N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-81457A SOW 1.3.2, 1.3.3 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

N/A NA SEE BLOCK 16 Reg Repro

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

30 JUL 2021

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 34 of 52 Pages

2021-08-18T18:29:07-0500

SLEZIA.JULIE.A.1008583109

Title: INSTRUCTOR PLAN Number: DI-MISC-81458B Approval Date: 20200423 AMSC Number: F10170 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/WNSE) Project Number: MISC-2018-011 Applicable Forms: N/A Use/Relationship: The Instructor Plan outlines the learning objectives, presentation techniques, media, and equipment for each lesson in a course. This plan is to be used to guide the instructor or to control the design of machine-implemented instructional direction.

a. This Data Item Description (DID) is applicable to all contracts requiring courseware development. This DID is used in conjunction with DI-MISC-81457, Lesson Strategy Report.

(Copies of DI-MISC-81457 are available online at https://quicksearch.dla.mil.)

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

c. This DID supersedes DI-MISC-81458A.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2. Format. Contractor format is acceptable.

3. Content. The Instructor Plan shall contain instructor information to support computer-based, interactive video and simulator instruction, and planning to support stand-up instruction.

These are further described in the following sections, which shall include:

3.1 Section I. This section shall provide technical data and course information to assist the instructor in the preparation of each lesson in the course.

a. Administrative information. Administrative information shall consist of:

(1) Course title

(2) Document number

(3) Security classification marking, as necessary, in accordance with Department of

Defense Manual (DoDM) 5200.01, Volume 2, DoD Information Security Program:

Marking of Information. (Copies of this document are available online at https://www.esd.whs.mil/.)

(4) Distribution statement, in accordance with DoD Instruction (DoDI) 5230.24, Distribution Statements on Technical Documents. (Copies of this document are available online at https://www.esd.whs.mil/.)

(5) Lesson topic (listed in the training course curriculum outline)

(6) Student allotted lesson time

(7) Classroom and laboratory location

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:46Z https://quicksearch.dla.mil/ https://www.esd.whs.mil/ https://www.esd.whs.mil/

DI-MISC-81458B

(8) References

(9) Preparation instructional materials

(10) Source documentation

(11) Instructional aids

(12) Preparation date

(13) Terminal objectives

(14) Enabling objectives

(15) Criterion test

(16) Student home

b. Outline of Instruction. The outline shall utilize a format that helps the instructor keep in mind what the students gain from each activity in the lesson in terms of progress toward terminal and enabling objectives. The outline shall contain detail either to support stand-up instruction or to be used as the instructor’s primary reference document for computer-based courseware. The outline shall also provide guidance on pre-brief and out-brief techniques for each lesson. At each key teaching point, the outline shall list an instructor aid (e.g., a reference to sources of more in-depth coverage of the point).

3.2 Section II. This section shall contain an outline for instructor-based instructions that provides definition of, and specific direction on, learning objectives, equipment, and instructional media requirements for the conduct of student training.

a. Administrative information. This section shall provide the administrative information required to prepare for and conduct the lesson and shall consist of:

(1) Course title

(2) Course number

(3) Curriculum

(4) Unit

(5) Lesson

(6) Author

(7) Date of preparation

(8) Topic or task

(9) Security classification marking, as necessary, in accordance with DoDM 5200.01, Volume 2

(10) Distribution statement, in accordance with DoDI 5230.24.

(11) Classroom laboratory schedule

(12) References

(13) Commonality

(14) Instructional format

(15) Instructional equipment

(16) Instructional aids and media

(17) Testing requirements

(18) Supporting publications

(19) Revision dates

(20) Trainee instructional materials

(21) Requirements for multiple instructors, as applicable

(22) Instructional guidance

(23) Student facility requirements

(24) Safety precautions

(25) Prerequisites

b. Introduction. The introduction shall provide the main points of the topic of interest. It shall focus attention on the subject and motivate the students, relate their needs and interests to the topic, and it shall consist of:

(1) Overview

(2) Lesson strategy

(3) Motivation

(4) Gain attention

(5) Statement of the objectives

(6) Prerequisite material review

c. Body. The body shall provide new instruction material sequenced to ensure the maximum transfer of knowledge and shall provide additional support for newly assigned instructional personnel. The body shall consist of:

(1) Presentation

(2) Outline of instruction

(3) Instructor and student participation activities

(4) Teaching points

(5) Applicability of content

(6) Evaluation

(7) Intermediate summaries, as required

(8) Media cues

(9) Helps

(10) Questions

(11) Answers to questions

(12) Practice

d. Conclusion. The conclusion shall provide a summary consisting of:

(1) Summary of the instructional material presented in the body (3.2c. above)

(2) Re-motivation for the topic

(3) Closing comments

(4) Student assignments

(5) Test and evaluation of objectives

(6) Course critique (if required)

e. Answer key. The answer key shall provide answers to test questions.

End of DI-MISC-81458B

3.1 Section I. This section shall provide technical data and course information to assist the instructor in the preparation of each lesson in the course.

3.2 Section II. This section shall contain an outline for instructor-based instructions that provides definition of, and specific direction on, learning objectives, equipment, and instructional media requirements for the conduct of student training.

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A035 INSTRUCTOR PLAN N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-81458B SOW 1.3.2, 1.3.3, 1.3.5 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 35 of 52 Pages

2021-08-18T18:29:44-0500

SLEZIA.JULIE.A.1008583109

Title: Key and Certificate Management Plan (KCMP)

Number: DI-MISC-81688A Approval Date: 20170110

AMSC Number: 9760 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: NS/I21/I213 Project Number: MISC-2017-001

Applicable Forms: N/A

Use/Relationship. The Key and Certificate Management Plan (KCMP) describes the use and control of cryptographic products and services used by a cryptographic application

(cryptographic engine, cryptographic module, End Cryptographic Unit (ECU), or system) throughout its lifetime. The KCMP also identifies and documents the capabilities that the cryptographic application requires from the current and planned key management infrastructure.

a. KCMP Related Guidance. As the vendor of a cryptographic application may have very little insight into the items in the KCMP, the Information Assurance Certification Manager (IACM) will ensure the vendor uses the KCMP Template included as part of this DID and has the applicable Telecommunications Security Requirements Document (TSRD) cited under

“Reference Documents.” The TSRD is intended for use with the KCMP template to detail other related and relevant information not covered here.

b. This Data Item Description (DID) contains the content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract, as the Key and Certificate Management Plan (KCMP).

c. This DID supersedes DI-MISC-81688.

Requirements:

1. Reference Documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

1.1 National Security Agency/Central Security Service (NSA/CSS) Policy Manual 1-52

1.2. Telecommunications Security Requirements (TSRD) Commercial Communications

Security (COMSEC) Evaluation Program (CCEP), Section 2.9

1.3. TSRD User Participation Program (UPP), Section 2.9

1.4. Information Assurance Directorate (IAD) Management Directive 110 (“Cryptographic

Key Protection”)

1.5. Key and Certificate Management Plan (KCMP) Template, Version 1.0

1.6. CNSSI No. 4001, “Controlled Cryptographic Items (CCI)”

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:49Z

DI-MISC-81688A

1.7. CNSSI No. 4031, “Cryptographic High Value Products (CHVP)”

1.8. CNSSI No. 4003, “Reporting and Evaluating COMSEC Incidents”

2. Format. The KCMP shall:

2.1 Be formatted strictly in accordance with the KCMP Template established for this purpose and that is referenced in paragraph 1.5 of this DID, under the “Reference

Documents” section.

2.2 Be appropriately classified and portion marked in accordance with National Security

Agency/Central Security Service (NSA/CSS) Policy Manual 1-52).

2.3. Be submitted in either Microsoft Word or Adobe PDF format. Adobe PDF format is preferred as it supports more efficient tracking and management of changes.

2.4. Not contain embedded files (i.e., Microsoft Visio drawings). All pictures and diagrams must be converted to a JPG or similar format.

2.5. Include a title page that minimally identifies the following:

a) Program Name

b) Contract Number

c) Contract Data Requirements List (CDRL) number

d) Revision and date

e) Program Manager’s name and telephone number and, if applicable, the NSA

IACM’s name and office designator

f) Classification

2.6. Include a Revision Page, listing all past changes to the document in reverse chronological order.

2.7. Include a list of Reference Documents. This would include all documents used to develop the KCMP, approved key specifications used by the cryptographic application, and any special exceptions/waivers granted to the program.

2.8. Include a Table of Contents.

2.9. Include a Table defining all abbreviations and acronyms.

2.10. Total page count for the KCMP should not exceed 30 pages, with font size and type 12

Times New Roman. NSA reserves the right to return KCMPs numbering 30 or more pages with instructions to make them more concise and readable.

3. Content. The KCMP shall:

3.1. Be completed using the Key and Certificate Management Plan (KCMP) Template, Version 1.0, included in this DID. NOTE: Not all requested information will apply.

3.2. Contain only that information specifically requested. Including other information not specifically requested will lengthen the review time and consequently the approval of the

KCMP.

4. The Key and Certificate Management Plan Template, Version 1.0, follows on the next page.

Key and Certificate Management Plan Template, Version 1.0

KEY AND CERTIFICATE MANAGEMENT

PLAN

FOR THE

NAME OF THE PRODUCT/SYSTEM BEING

CERTIFIED

UPA/MOA NUMBER: XXX

CDRL/ADRL: XXX

Project Classification: XXX

Submittal Date: XXX

Document ID: XXX

0N#: XXX

NSA IACM: XXX

Vendor Name POC: XXX

Vendor Name POC Phone #: XXX

ITAR Statement: (i.e., This technical data is controlled under the International Traffic in Arms

Regulations (ITAR) and may not be exported to a Foreign Person, either in the U.S. or abroad, without proper authorization by the U.S. Department of State.)

Proprietary Statement: (i.e. Proprietary Rights are involved in the subject matter of this material and all manufacturing, reproduction, use and sales rights pertaining to such matter are expressly reserved. It is submitted in confidence for a specified purpose, and the recipient, by accepting this material, agrees that this material will not be used, copied or reproduced in whole or in part, nor its contents revealed in any manner, or to any person, except for the purpose delivered.)

Vendor Name

Address goes here

Revision Page

Rev Description Approval Date

Initial Release

Table of Contents

PARAGRAPH PAGE

1. INTRODUCTION 8

1.1 Document Overview 8

1.2 Referenced Documents 8

1.2.1 Government Documents 8

1.2.2 Non-Government Documents 8

2. ABBREVIATIONS AND ACRONYMS 9

3. KEY AND CERTIFICATE MANAGEMENT PLAN PROCESS 9

3.1 Cryptographic Application Description and Security Services 9

3.1.1 Description/Purpose of Cryptographic Application 9

3.1.2 Level of Information the Cryptographic Application is Protecting 10

3.1.3 Security Services the Cryptographic Application Provides 10

3.1.3.1 Confidentiality 10

3.1.3.2 Integrity 10

3.1.3.3 Non-repudiation 10

3.1.3.4 Access Control 10

3.1.3.5 Identification and Authentication 10

3.1.3.6 Availability 10

3.1.4 Operational Environment 10

3.1.5 Requirement for Allied/Coalition Interoperability 10

3.2 Key Management Products and Services Requirements 11

3.2.1 Key Management Products and Service Types 11

3.2.2 Quantity/ECU to be Keyed 11

3.2.3 Projected Quantity of ECUs 11

3.2.4 Algorithms 11

3.2.5 Key Specification 11

3.2.6 Protective Techniques 11

3.2.7 Key Period 11

3.2.8 Classification 11

3.2.9 PKI Certificate Classes 11

3.2.10 Tokens 11

3.2.11 Need Dates 11

3.2.12 Controlling Authority 11

3.3 Key Management Products and Services Ordering 12

3.4 Key Management Products and Services Generation 12

3.5 Key Management Products and Services Distribution 12

3.6 Future Upgrade Capabilities? 12

1. INTRODUCTION

The Key and Certificate Management Plan (KCMP) describes the use and control of all key management products and services used by a cryptographic application (cryptographic engine, End Cryptographic Unit (ECU), or system) throughout its lifetime. The KCMP also documents the capabilities that the cryptographic application requires from the current and planned Key

Management Infrastructure (KMI). This ensures that any lifecycle key management services are supportable by and available from the KMI.

1.1 Document Overview

This KCMP document is organized to conform to the requirements of NSA DI-MISC-81688A, Data Item Description (DID) for the Key and Certificate Management Plan. This KCMP document provides a description of the cryptographic application functionality, background, and secure communication requirements; includes the key management products and services requirements; concludes with a description of the requirements for key management products and services ordering, handling and distribution.

1.2 Referenced Documents

The documents in the following subsections are applicable to this KCMP.

1.2.1 Government Documents

DI-MISC-81688A, Key and Certificate Management Plan (KCMP)

TSRD ##-YY, Rev #.#, Month DD, YYYY for the Name of Product

CDRL/ADRL ##-YY, Rev #.#, Month DD, YYYY for the Name of Product

NSA IASRD for the Name of Product, Month DD, YYYY, Rev #.#, IASRD ##-YY

Key Specification, etc. as appropriate

1.2.2 Non-Government Documents

Etc. as appropriate

2. ABBREVIATIONS AND ACRONYMS

Table 1 lists and describes abbreviations and acronyms used in this document.

Table 1. Abbreviations and Acronyms

Abbreviation/

Acronym Description

ADRL Agreement Data Requirements List

CDRL Contract Data Requirements List

DID Data Item Description

ECU End Cryptographic Unit

EKMS Electronic Key Management System

IACM Information Assurance Certification Manager

IASRD Information Assurance Security Requirements Document

ITAR International Traffic in Arms Regulation

KMI Key Management Infrastructure

KCMP Key and Certificate Management Plan (aka “KCMP”)

LMD/KP Local Management Device/Key Processor

MGC/AKP Client Management/Advanced Key Processor

MOA Memorandum of Agreement

N/A Not Applicable

NSA National Security Agency

POC Point of Contact

TSRD Telecommunications Security Requirements Document

UPA User Partnership Agreement

Xxx xxx

3. KEY AND CERTIFICATE MANAGEMENT PLAN PROCESS

3.1 Cryptographic Application Description and Security Services

3.1.1 Description/Purpose of Cryptographic Application

Provide a brief description of the purpose of the cryptographic application.

3.1.2 Level of Information the Cryptographic Application is Protecting

Describe all classification levels of information that the cryptographic application will be protecting.

3.1.3 Security Services the Cryptographic Application Provides

3.1.3.1 Confidentiality

Describe any requirements for confidentiality. If there are no requirements, state so.

3.1.3.2 Integrity

Describe any requirements for integrity. If there are no requirements, state so.

3.1.3.3 Non-repudiation

Describe any requirements for non-repudiation. If there are no requirements, state so.

3.1.3.4 Access Control

Describe any requirements for access control. If there are no requirements, state so.

3.1.3.5 Identification and Authentication

Describe any requirements for identification or authentication. If there are no requirements, state so.

3.1.3.6 Availability

Describe any requirements for availability. If there are no requirements, state so.

3.1.4 Operational Environment

Briefly describe the operational environment that the cryptographic application will be operated

in. Examples of operational environments could be a field deployed tactical environment, a

CONUS strategic SCIF environment, etc. Where will the device be used? Ships, the dessert, tactical, strategic, manpack, Humvee, SOC, controlled environments, etc.

3.1.5 Requirement for Allied/Coalition Interoperability

Describe any allied interoperability requirements. If there are interoperability requirements, discuss the overall allied interoperability strategy, particularly from a key distribution perspective. If there are none, state so and state why.

3.2 Key Management Products and Services Requirements

Table 2. Key Management Products and Services Requirements

Paragraph Product/Service Notes

3.2.1 Key Management

Products and

Service Types

Example: Test Keys, Operational

Keys, Contingency Keys, Certificates, Tokens

3.2.2 Quantity/ECU to

be Keyed

Example: # of keys per Key Type per

ECU

3.2.3 Projected Quantity

of ECUs

Example: 1 EDM, 1 Qualification

Unit, ~15 Production Units per year

3.2.4 Algorithms

Example: Algorithm used with each type of product/service required.

Specify which algorithm for which security service.

3.2.5 Key Specification

Example: Identify the Key

Specification for any keying product require.

3.2.6 Protective

Techniques

Example: Benign Fill, Black Key Fill, OTNK. If Red key is used, specify why. An IAD MD-110 waiver will be required.

3.2.7 Key Period

Example: Crypto Period and

Supersession Rate

3.2.8 Classification

Example: UNCLASSIED Test Key, UNCLASSIFIED and SECRET

Operational Key

3.2.9 PKI Certificate

Classes

Example: Medium S/W, Medium

H/W

3.2.10 Tokens

Example: Smart Card, USB Token, etc.

3.2.11 Need Dates

Developmental – MM/YYYY

(validated on MM/DD/YYYY)

Test – MM/YYYY

Maintenance – MM/YYYY

Operational – MM/YYYY

Contingency – MM/YYYY

3.2.12 Controlling

Authority

Example: NSA I22212 (COMSEC

ID#880691)

3.3 Key Management Products and Services Ordering

Provide enough detail to permit determination of long-term support for key orders. Who can order key? Will it always be the CONAUTH or which user can order? Authorized ID?

Generation order? Distribution order?

3.4 Key Management Products and Services Generation

Describe where the key management products and services will be generated. Do you require

Central Facility generation (i.e. NSA) or local generation (LMD KP/MGC AKP/Commercial

Key Generation)?

3.5 Key Management Products and Services Distribution

Describe the distribution of key management products and services from the generation source until consumption by the cryptographic application. The distribution plan will include:

When and where key management products and services are encrypted and unencrypted?

Key Management Products form (electronic, PROM, floppy, CD, etc.) NOTE:

A requirement for key on physical media will require strong written justification, Consideration of such a request may significantly delay KCMP approval and consequently NSA certification/approval.

3.6 Future Upgrade Capabilities?

If you are relying upon legacy key management, such as physical key distribution, describe any future upgrade capabilities. If not applicable, i.e., you are already intending to use EKMS/KMI and have no upgrade requirements, then states so.

END OF DI-MISC-81688A

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A036 KEY MANAGEMENT PLAN (KMP) N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-81688A SOW 1.3.1, 1.3.2, 1.3.3, 1.3.4 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 36 of 52 Pages

2021-08-18T18:30:32-0500

SLEZIA.JULIE.A.1008583109

Title: SITE SURVEY REPORT (SSR) Number: DI-MISC-82104 Approved Date: 20170309 AMSC Number: F9773 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/WINL) Project Number: MISC-2017-003 Applicable Forms: N/A Use/Relationship: The SSR documents the findings of the contractor’s site survey. The SSR is used to identify any discrepancies between conditions described by the contract and actual on-site conditions.

a. This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

b. The SSR is applicable to any acquisition of telecommunications equipment.

Requirements:

1. Reference documents. None.

2. Format. The SSR shall be in the contractor’s format.

3. Content. The SSR shall contain the following:

3.1 Title page. The title page shall contain the following information:

a. Title.

b. Contract data requirements list (CDRL) data item number.

c. Base name.

d. Identification of project.

e. Contract number.

f. Date.

3.2 Table of Contents. The Table of Contents shall identify all paragraphs and the corresponding page number.

3.3 Introduction. The Introduction shall contain the following information:

a. Purpose.

b. Location.

c. Dates of survey.

d. Personnel contacted.

DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:51Z

DI-MISC-82104

3.4 Results. The Results section shall be the main body of the report. It shall contain a complete listing of the contractor’s findings. This section shall include a summary of all anticipated minor construction required, findings on cable routes, and distances, and findings on availability of existing manholes and ducts. This shall also include a list of circuits and demarcation points which have not been finalized or which require additional coordination with end users. This section shall fully documents and explain any other findings concerning on-site conditions in this section.

3.5 Conclusions and recommendations. This section shall summarize the results of the survey and present conclusions. The conclusion shall also identify any discrepancies between the contract and survey results. This section shall contain any recommendations that contractor has based on the survey. Any actions required from the Government by the contractor shall be noted here.

End of DI-MISC-82104

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:51Z

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A037 SITE SURVEY REPORT N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-82104 SOW 1.3.1, 1.3.2, 1.3.3, 1.3.4 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

A NA SEE BLOCK 16 Reg Repro

BLBLK 4: TAILORING, IF REQUIRED, SHALL BE AS SPECIFIED FOR EACH INDIVIDUAL DELIVERY

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 37 of 52 Pages

2021-08-18T18:31:08-0500

SLEZIA.JULIE.A.1008583109

Title: Test Plan

Number: DI-NDTI-80566A Approval Date: 14 Nov 2006 AMSC Number: 7639 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The Test Plan outlines the plans and performance objectives at every level of testing on systems or equipment. It provides the procuring activity with the test concept, objectives and requirements to be satisfied, test methods, elements, responsible activities associated with the testing, measures required and recording procedures to be used.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID is applicable to system and equipment tests that include design evaluation tests, engineering tests, preliminary qualification tests, formal qualification tests, human factors tests, operational tests and acceptance tests.

This DID supersede DI-NDTI-80566.

Requirements:

1. Reference documents. None.

2. General. The test plan shall document in detail the contractor’s plan for conducting tests and analyzing the test results to show how the system, when fielded, will satisfy the requirements of the applicable design specification.

3. Format: The plan shall be in contractor’s format.

4. Contents. The plan shall contain the following:

4.1 Title page. The title page shall include the following:

a. Title of the test to be conducted.

b. Identification of system being tested.

c. Contractor’s name.

d. Contractor number.

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:52Z

DI-NDTI-80566A

e. Security classification.

f. Distribution statement.

4.2 Introduction. Consists of an overview of the objectives of the test plan, including flow diagrams, milestones, personnel participation, locations, schedules, and security measures to be observed. The plan shall include the following:

4.3 Flow diagrams. The flow diagrams will reflect a functional description of the test program using a block diagram portrayal of the functions that must be met to satisfy the total test program. Functions shall be numbered 1.0, 2.0, 3.0, etc.

4.4 Milestones. Identifies the start and expected completion dates of each test to be performed.

4.5 Participation. Identifies the government and contractor participation roles and responsibilties.

4.6 Location. Identifies the facilities where the testing will be performed.

4.7 Schedule. States when testing will be performed, whether testing is on schedule, and if not, what procedures will be taken to meet the schedule.

4.8 Security. Identify and state briefly any security measures of guidelines to be observed.

4.9 Master test list. Lists all tests to be accomplished in the order they are to be performed. A separate listing for each location shall be provided. Each listing shall include the following:

4.9.1 Test description. Name and brief description of test to be performed.

4.9.2 Applicable specification (s). The specifications shall be identified as follows:

a. Title and identification number.

b. Paragraph number associated with the tests.

c. Title of test.

d. Functional category of test.

4.9.3 Parameters. The number of cycles the test will be performed and selected parameters to be observed.

4.9.4 Special tests. Provides a list of special or unusual tests and examination necessary to verify satisfactory equipment performance to specifications.

DI-NDTI-80566A

4.9.5 Test classification category. State the functional area of each test performed.

4.9.6 Test objectives. Describes the objectives of each test performed, including the criteria, baseline, duration, and number of times each test should be performed.

a. Success/failure criteria.

b. Baseline.

c. Duration.

d. Quantity of test.

4.9.7 Test equipment. List all equipment to be used in the test and identify as follows:

a. Description.

b. Nomenclature.

c. Serial number.

4.9.8 Support equipment. List all support equipment that will be used to perform the tests and identify as follows:

a. Description.

b. Nomenclature.

c. Serial number.

d. Calibration constants.

e. Calibration procedures.

f. Operating instructions.

4.9.9 Special test equipment. List all special test equipment required to be designed or fabricated for use on the program as follows:

a. Description.

b. Nomenclature.

c. Data required.

4.9.10 Approach. Describe the steps used to perform each test.

4.9.11 Instrumentation. Indicates the type and recording devices that will be used and the number and types of parameters to be recorded.

4.9.12 Data reduction and analysis. Describes data to be recorded and the data reduction and analysis techniques that will be used to interpret the data.

4.9.13 Government test facilities. Identifies applicable facility and includes a reference to the appropriate facility requirements documents.

Validation procedure. An overview of the procedures that the contractor will use to validate the test results.

5. END OF DI-NDTI-80566A

DATA ITEM DESCRIPTION

Requirements:

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A038 TEST PLAN N/A

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-NDTI-80566A SOW 1.3.1, 1.3.2, 1.3.3, 1.3.4 96TSSQ/RNXC

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

BLK 9: MARK AS SPECIFIED IN EACH INDIVIDUAL DELIVERY ORDER.

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 38 of 52 Pages

2021-08-18T18:31:41-0500

SLEZIA.JULIE.A.1008583109

Title: Test Procedure

Number: DI-NDTI-80603A Approval Date: 14 Nov 2006 AMSC Number: 7637 Limitation: N/A DTIC Applicable: N/A GIDEP Applicable: None Office of Primary Responsibility: NS/DA023 Applicable Forms: N/A

Use/relationship:

The test procedure identifies the step-by-step testing operations to be preformed on items under going developmental, qualification, or acceptance testing. It identifies items to be tested, the test equipment and support required, the test conditions to be imposed, the parameters to be measured, and the pass/fail criteria against which the test results will be measured. The document is a compilation of individual test procedures for related elements of a system, subsystem, or equipment.

This Data Item Description (DID) contains the format and content preparation instructions for each tech data product generated by the specific and discrete task requirement as delineated in the contract.

This DID is applicable to contracts requiring tests to be preformed for the purpose of developmental or environmental evaluation, acceptance testing, and item qualification testing.

This DID supersede DI-NDTI-80603.

Requirements:

1. Reference documents: None

2. Format: The test procedures shall be in contractor’s format on 8 ½ x 11 inch paper. It shall be bound in such a manner that pages may be removed or inserted without damage or mutilation.

3. Content: The test procedure shall contain the following:

3.1 Front matter.

3.1.1 Cover and title page. The following information shall be included on the cover and title page:

Source: http://assist.dla.mil -- Downloaded: 2021-08-18T17:53Z

DI-NDTI-80603A

a. Date of issue.

b. Revision date (if applicable)

c. Procedure document identification number

d. Contract number

e. Contractor’s name and address

f. Type of procedure. Including purpose(e.g., first article test, developmental

Evaluation, qualification, environmental(specify), acceptance, or other)

g. Identification of the system, subsystem, or equipment to be tested.

h. Security classification (if applicable)

3.1.2 Record of changes. A record of change pages shall be included to provide for tracking of changes to the test procedures.

3.1.3 Table of contents. A table of contents is required when more that one test procedure is included in the test procedures document. It shall identify the page location of each procedure number, procedure title, and related equipment nomenclature.

3.2 Body of document. For each test procedure, the following information is required.

3.2.1 Procedure number. Each procedure shall have a unique number assigned to it.

3.2.2 Title of procedure. The title should relate to the purpose of the test.

3.2.3 Introduction. The following shall be addressed in the introduction:

3.2.3.1 Purpose of test. (As specified in the contract tasking document).

3.2.3.2 System, subsystem, or equipment to be tested. The following identification shall be provided.

a. Nomenclature

b. Model or part number

c. Type of test item(prototype, production item, laboratory model, etc)

d. Applicable specification

3.2.3.3 Test requirements. Included the following, each related to the prescribing contract requirement paragraph(specification, standard, plan, or work statement)

a. Required tests, and parameters to be measured.

b. Performance requirements, acceptance of compliance limits, and

Environmental criteria.

3.2.3.4 Referenced documents. A list by title, number, date, and source of those documents cited in the test procedure.

3.2.4 Required test equipment. Includes the following for each piece of test equipment required to perform the procedure:

a. Nomenclature

b. Use of test equipment

c. Model number(if applicable)

d. Manufacturer(if mandatory)

e. Accuracy and calibration requirements

f. Range or spectrum of measurements required

3.2.5 Table of tests. This table lists each test performed under the procedure in the sequence it is to be performed., identified to the procedure paragraph and the related specification/contract requirement.

3.2.6 Step-by-step procedure. The following shall be included for each step of the test procedure:

a. Test set-up diagrams, including test equipment connections.

b. Input and output instrumentation points.

c. Test item operating limits and test conditions to be imposed.

d. Performance parameters to be measured.

e. Step-by-step operations to obtain the required data.

f. Caution and safety warnings as appropriate.

3.2.7 Data sheets. Data sheets shall be included with the procedure, or be separately attached at the end of all procedures. They shall provide for:

a. Identification of item tested, including model and serial numbers.

b. Recording of test measurements

c. Identification of required or objective performance values, with

Tolerances.

d. Identification of applicable procedure paragraphs.

e. Date of test.

f. Signature of technician or inspector performing the tests/\.

3.2.8 Support requirements. Any special support requirement would be included in this section, such as:

a. Use of special facilities or test ranges.

b. Personnel requirements (numbers, types, qualifications).

c. Unusual electrical, hydraulic, pneumatic, etc, requirements

d. Support equipment requirements.

4. END OF DI-NDTI-80603A

DATA ITEM DESCRIPTION

The public reporting burden for this collection of information is…