DOCSLIB.ORG

NGLD-M) System Requirements Document (SRD)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
NGLD-M) System Requirements Document (SRD) UNCLASSIFIED//FOR OFFICIAL USE ONLY System Requirements Document (SRD) Next Generation Load Device – Medium (NGLD -M) Date: Authenticated by: _____________________________________ First Name MI. Last Name Prepared by: Chief or Lead Engineer Day Month Year Product Lead COMSEC (Ex: 01 May 2019) Project Lead, Network Enabler Aberdeen Proving Ground, MD 21005 Approved by: _____________________________________ DISTRIBUTION STATEMENT X: Distribution authorized to U.S. Government agencies and private First Name MI. Last Name individualsNGLD -orM enterprises SRD eligible to obtain export-controlled technical Program Manager 1 dataSource in accordance Selection Information with regulations - See FAR implementing2.101 and 3.104 10 U.S.C.Use 140c. or disclosure of data contained onDay this sheet Month is subject toYear the restriction on the title page of this proposal. Other requests must be referred to SFAE-CCC-MC. UNCLASSIFIED//FOR OFFICIAL(Ex: USE ONLY01 May 2019) UNCLASSIFIED//FOR OFFICIAL USE ONLY Next Generation Load Device – Medium (NGLD-M) System Requirements Document (SRD) CHANGE HISTORY Change Version Date Initial - RFI 1.0 01/10/2019 Draft RFP 2.0 05/20/2019 Draft RFP - Final 3.0 05/29/2019 NGLD-M SRD ii Source Selection Information - See FAR 2.101 and 3.104 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal. UNCLASSIFIED//FOR OFFICIAL USE ONLY UNCLASSIFIED//FOR OFFICIAL USE ONLY Next Generation Load Device – Medium (NGLD-M) System Requirements Document (SRD) Contents 1. (U) SCOPE.............................................................................................................................. 1 1.1 (U) System Identification ............................................................................................. 1 1.2 (U) System Overview ................................................................................................... 1 1.3 (U) Document Overview .............................................................................................. 2 2. (U) APPLICABLE DOCUMENTS ........................................................................................ 3 2.1 (U) General .................................................................. Error! Bookmark not defined. 2.2 (U) Government Documents ....................................... Error! Bookmark not defined. 2.2.1 (U) Specifications, Standards, and Handbooks........ Error! Bookmark not defined. 2.2.2 (U) Other Government Documents, Drawings, and Publications. Error! Bookmark not defined. 2.3 (U) Non-Government Publications .............................. Error! Bookmark not defined. 2.4 (U) Order of Precedence .............................................. Error! Bookmark not defined. 3. (U) SYSTEM OR SUBSYSTEM REQUIREMENTS ........................................................... 6 3.1 (U) Required States and Modes .................................................................................... 6 3.1.1 (U) High-Level Modes ............................................................................................. 7 3.1.2 (U//FOUO) NGLD-M and Medium Assurance Mode ............................................ 11 3.1.3 (U) NGLD-M and High Assurance Mode .............................................................. 14 3.2 (U) System or Subsystem Functional Requirements .................................................. 17 3.2.1 (U) Power-Up.......................................................................................................... 19 3.2.2 (U) User (Human User and Device User) Management ......................................... 19 3.2.3 (U) Managing ......................................................................................................... 20 3.2.4 (U) Receiving .......................................................................................................... 26 3.2.5 (U) Storage .............................................................................................................. 32 3.2.6 (U) Distributing ....................................................................................................... 32 3.2.7 (U) Cryptography .................................................................................................... 41 3.2.8 (U) Discrete Operation ............................................................................................ 44 3.2.9 (U) Built-In Test and Health Status ........................................................................ 45 3.2.10 (U) Alarm ................................................................................................................ 45 3.2.11 (U) Configuration Management .............................................................................. 45 3.2.12 (U) Zeroization........................................................................................................ 46 3.2.13 (U) Multi-Domain Support ..................................................................................... 46 NGLD-M SRD iii Source Selection Information - See FAR 2.101 and 3.104 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal. UNCLASSIFIED//FOR OFFICIAL USE ONLY UNCLASSIFIED//FOR OFFICIAL USE ONLY Next Generation Load Device – Medium (NGLD-M) System Requirements Document (SRD) 3.2.14 (U) ECU-Profile Management ................................................................................ 46 3.2.15 (U) Legacy Interfaces/Backward Compatibility ..................................................... 47 3.2.16 (U) Accessory ......................................................................................................... 47 3.2.17 (U) Power-Down ..................................................................................................... 47 3.2.18 (U) Seeking Help .................................................................................................... 47 3.2.19 (U) General User Interface...................................................................................... 47 3.3 (U) System External Interface Requirements ............................................................. 48 3.3.1 (U) Interface Identification and Diagrams .............................................................. 48 3.3.2 (U) Physical External Interfaces ............................................................................. 52 3.3.3 (U) Logical (Networked) External Interfaces ......................................................... 54 3.4 (U) System Internal Interface Requirements .............................................................. 56 3.5 (U) System Internal Data Requirements ..................................................................... 57 3.6 (U) Adaptation Requirements ..................................................................................... 57 3.7 (U) Environmental, Safety, and Operational Health (ESOH) Requirements ............. 57 3.7.1 (U) Chemical, Biological, Radiological, and Nuclear (CBRN).............................. 57 3.8 (U) Security and Privacy Requirements ..................................................................... 57 3.8.1 (U) General Security and Privacy ........................................................................... 58 3.8.2 (U) Tamper.............................................................................................................. 58 3.8.3 (U) TEMPEST ........................................................................................................ 58 3.8.4 (U) Information Assurance Standards and Certification ........................................ 58 3.8.5 (U) NGLD-M Operational Security Doctrine (OSD) ............................................. 58 3.8.6 (U) Risk Management Framework (RMF) ............................................................. 58 3.9 (U) System Environment Requirements ..................................................................... 59 3.9.1 (U) Environment ..................................................................................................... 59 3.9.2 (U) High-Altitude Electromagnetic Pulse (HEMP) ................................................ 59 3.10 (U) Computer Resource Requirements ....................................................................... 59 3.10.1 (U) Computer Hardware Requirements .................................................................. 59 3.10.2 (U) Computer Hardware Resource Utilization Requirements ................................ 59 3.10.3 (U) Computer Software Requirements ................................................................... 59 3.10.4 (U) Computer Communications Requirements ...................................................... 59 3.11 (U) System Quality Factors ........................................................................................ 60 3.11.1 (U) Reliability, Availability, Maintainability (RAM) ............................................. 60 NGLD-M SRD iv Source Selection Information - See FAR 2.101 and 3.104 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal. UNCLASSIFIED//FOR OFFICIAL USE ONLY UNCLASSIFIED//FOR OFFICIAL USE ONLY Next Generation Load Device – Medium (NGLD-M) System Requirements Document (SRD) 3.11.2 (U) Expandability.................................................................................................... 60 3.11.3 (U) Performance.....................................................................................................
Load more

Recommended publications
  • Principal Technical Characteristics of U.S. Marine Corps Communication-Electronics Equipment
    TM 2000-OD/2C U.S. MARINE CORPS TECHNICAL MANUAL PRINCIPAL TECHNICAL CHARACTERISTICS OF U.S. MARINE CORPS COMMUNICATION-ELECTRONICS EQUIPMENT THIS PUBLICATION IS REQUIRED FOR OFFICIAL USE OR FOR ADMINISTRATIVE OR OPERATIONAL PURPOSES. DISTRIBUTION IS LIMITED TO U.S. GOVERNMENT AGENCIES ONLY. OTHER REQUESTS FOR THIS DOCUMENT MUST BE REFERRED TO: COMMANDANT OF THE MARINE CORPS (ARD) WASHINGTON, D.C. 20380-0001. DESTRUCTION NOTICE: FOR UNCLASSIFIED, LIMITED DOCUMENTS, DESTROY BY ANY METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENTS. FOR OFFICIAL USE ONLY DECEMBER 2005 PCN 180 002310 00 TM 2000-OD/2C UNITED STATES MARINE CORPS Marine Corps Systems Command Quantico, Virginia 22134-5010 30 December 2005 1. This Technical Manual (TM), authenticated for Marine Corps use and effective upon receipt, provides technical characteristics information for Marine Corps Communication-Electronics Equipment. 2. This manual supersedes TM 2000-15/2B dated April 1993. 3. Submit notice of discrepancies or suggested changes on a NAVMC 10772. The NAVMC may be submitted via the Internet using website https://pubs.ala.usmc.mil/navmc, scrolling down to the NAVMC 10772 Tracking Program and following instructions provided. It may also be submitted by electronic mail to [email protected], or by mailing paper copy NAVMC 10772 in an envelope addressed to Commander, Marine Corps Systems Command, Attn: Assistant Commander Acquisition and Logistics (LOG/TP), 814 Radford Blvd, Suite 20343, Albany, Georgia 31704-0343. BY DIRECTION OF THE COMMANDER MARINE CORPS SYSTEMS COMMAND OFFICIAL: KATRINA G. WAHL JAMES L. RIORDAN Product Group Director, PGD-11 Product Group Director, PGD-12 Marine Corps Systems Command Marine Corps Systems Command DISTRIBUTION: PCN 180 002310 00 1/(2 blank) RECORD OF CHANGES CHANGE DATE TITLE OR BRIEF ENTERED BY NO.
    [Show full text]
  • 0303140N Information Systems Security Program (ISSP)
    UNCLASSIFIED CLASSIFICATION: EXHIBIT R-2, RDT&E Budget Item Justification DATE: February 2006 APPROPRIATION/BUDGET ACTIVITY R-1 ITEM NOMENCLATURE RESEARCH DEVELOPMENT TEST & EVALUATION, NAVY / BA-7 0303140N Information Systems Security Program (ISSP) COST ($ in Millions) FY 2005 FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Total PE Cost 25.696 21.569 23.037 28.535 33.100 31.316 32.601 0734 Information Systems Security 15.799 18.196 21.038 26.347 30.955 29.119 30.371 0734 Communications Security 2.089 2.073 1.999 2.188 2.145 2.197 2.230 9999 Congressional Plus Up 7.808 1.300 Quantity of RDT&E Articles (U) A. MISSION DESCRIPTION AND BUDGET ITEM JUSTIFICATION: (U) The goal of the Navy Information Systems Security Program (ISSP) is to ensure the continued protection of Navy and Joint information, telecommunications, and information systems from hostile exploitation and attack. The ISSP is the Navy’s implementation of statutory and regulatory requirements specified in Presidential Decision Directive 63, the Computer Security Act of 1987 (Public Law 100-235), Appendix III of Office of Management and Budget (OMB) Circular A-130, and DOD Directive 8500.1. ISSP activities address the triad of Defensive Information Operations defined in Joint Publication 3-13; protection, detection, and reaction. Evolving detection and reaction responsibilities extend far beyond the traditional ISSP role in protection or Information Security (INFOSEC). Focused on FORCEnet supporting the highly mobile forward-deployed subscriber, the US Navy’s implementation of Network-Centric Warfare (NCW) places demands upon the ISSP, as the number of users dramatically increases and the criticality of their use escalates.
    [Show full text]
  • KYK-13 Operation
    KYK-13 Homepage Crypto KYK-13 Index Electronic Transfer Device - Wanted item Enigma The KYK-13 is a small electronic transfer device used by the military for the distribution of cryptographic material, commonly refererred to as Transmission Encryption Keys (TEK). It was developed by the US Hagelin National Security Agency (NSA) and uses the DS-102 protocol for key transfer. TheKYK-13 is also Fialka known by its National Stock Number NSN 5810-01-026-9618. Siemens The KYK-13 was very popular because of its KYK-13 key loader simplicity, small size and ease of use. A total of 6 Philips TEK variables can be stored in the internal memory Nema of the KYK-13, making it suitable for a variety of crypto devices, such as the KY-57 (Vinson), KY-99, Racal some SINCGARS radios, KG-84, BID/250 STK (Lamberton) and even the latest KIV-7. Transvertex It was also used with the STU-II/B, KY-68, Spendex-40, Spendex-50 (DBT) and some other Gretag crypto phones. In normal use, the device itself is Telsy filled with cryptographic material from of a key management system (KMS) or another KYK-13. Tadiran There has been some debate in the past as to the maximum length of the keys that can be stored inside USA the KYK-13. In some publications it is stated that it is only suitable for 90-bit keys and that later devices USSR (e.g. the CYZ-10) had to be used for the modern 128-bit keys [1]. This can not be true however, as all crypto phones above use the 128-bit key based SAVILLE algorithm.
    [Show full text]
  • Unclassified// for Official Use Only National Security
    UNCLASSIFIED//FOR OFFICIAL USE ONLY NATIONAL SECURITY AGENCY NAG-16F (U) FIELD GENERATION AND OVER-THE-AIR DISTRIBUTION OF COMSEC KEY IN SUPPORT OF TACTICAL OPERATIONS AND EXERCISES (U) HANDLING INSTRUCTIONS 1. (U) This document is effective upon receipt and supersedes NAG-16E, dated January 1999, which should be destroyed. 2. (U) Changes to this document will be promulgated by printed or message amendments that are to be entered upon receipt. Persons entering such amendments are expected to record entry on the Record of Amendments page. 3. (U) This document in not accountable in the COMSEC Material Control System. It may be reproduced without report, and extracts from it that are marked “UNCLASSIFIED//FOR OFFICIAL USE ONLY” may be made for official purposes. 4. (U) This document and its extracts may be used in aircraft. 5. (U) Foreign release of this document must be approved by the Director, National Security Agency. MAY 2001 UNCLASSIFIED//FORUNCLASSIFIED// OFFICIAL USE ONLY FOR OFFICIAL USE ONLY UNCLASSIFIED NAG-16F RECORD OF AMENDMENTS DATE AMEND NO. BY WHOM ENTERED ENTERED UNCLASSIFIED ORIGINAL UNCLASSIFIED//FOR OFFICIAL USE ONLY NAG-16F (U) FOREWORD 1. (U//FOUO) Where Are We Heading? - A major evolution in communications security (COMSEC) keying technology has begun. Under the Electronic Key Management System (EKMS) program, standards, hardware, and applications are being developed to apply state of the art automation to generate, distribute, load, control, and account for COMSEC key. The program incorporates sufficient backward compatibility to assure that both future, automated key and existing, common electronic key can be handled. EKMS hardware is being fielded, but full development of tailored tactical key generation and distribution programs may take several more years.
    [Show full text]
  • Radio Operator Handbook for Soldiers Assigned, Attached, Or Task-Organized As Radio Operators
    U.S. UNCLASSIFIED REL NATO, GCTF, ISAF, MCFI, ABCA For Official Use Only Handling Instructions for CALL Electronic Media and Paper Products Center for Army Lessons Learned (CALL) authorizes official use of this CALL product for operational and institutional purposes that contribute to the overall success of U.S., coalition, and allied efforts. The information contained in this product reflects the actions of units in the field and may not necessarily be approved U.S. Army policy or doctrine. This product is designed for official use by U.S., coalition, and allied personnel and cannot be released to the public without the expressed written consent of CALL. This product has been furnished with the expressed understanding that it will be used for official defense-related purposes only and that it will be afforded the same degree of protection that the U.S. affords information marked “U.S. UNCLASSIFIED, For Official Use Only [FOUO]” in accordance with U.S. Army Regulation (AR) 380-5, section 5-2. Official military and civil service/government personnel, to include all coalition and allied partners may paraphrase; quote; or use sentences, phrases, and paragraphs for integration into official products or research. However, integration of CALL “U.S. UNCLASSIFIED, For Official Use Only [FOUO]” information into official products or research renders them FOUO, and they must be maintained and controlled within official channels and cannot be released to the public without the expressed written consent of CALL. This product may be placed on protected UNCLASSIFIED intranets within military organizations or units, provided that access is restricted through user ID and password or other authentication means to ensure that only properly accredited military and government officials have access to these products.
    [Show full text]