DoD Microelectronics Quick Start Guide-1
DoD Microelectronics Quick Start Guide-1
DoD Microelectronics Quick Start Guide-1
DoD Microelectronics:
Field Programmable Gate Array
Level of Assurance
Quick Start Guide
October 2023
U/OO/208512-23
PP-23-3453
Version 1.0
National Security Agency | Cybersecurity Technical Report
FPGA Level of Assurance Quick Start Guide
Publication information
Author(s)
National Security Agency
Cybersecurity Directorate
Joint Federated Assurance Center
Contact information
Joint Federated Assurance Center: JFAC_HWA@radium.ncsc.mil
Cybersecurity Report Feedback / General Cybersecurity Inquiries: CybersecurityReports@nsa.gov
Defense Industrial Base Inquiries and Cybersecurity Services: DIB_Defense@cyber.nsa.gov
Media inquiries / Press Desk: Media Relations, 443-634-0721: MediaRelations@nsa.gov
Purpose
This document was developed in furtherance of NSA’s cybersecurity missions. This includes its
responsibilities to identify and disseminate threats to National Security Systems, Department of Defense
information systems, and the Defense Industrial Base, and to develop and issue cybersecurity
specifications and mitigations. This information may be shared broadly to reach all appropriate
stakeholders.
Contents
DoD Microelectronics: Field Programmable Gate Array Level of
Assurance Quick Start Guide................................................................................. i
Quick start guide purpose ............................................................................................ 2
Quick start steps ........................................................................................................... 3
Overview ...................................................................................................................... 3
1. Determine the appropriate LoA for the top-level system .......................................... 3
2. Determine the appropriate LoA for the FPGA device(s) ........................................... 4
3. Select the appropriate best practice guide ............................................................... 5
4. Apply the guidance................................................................................................... 6
Tables
Table 1: Level of Assurance best practice guidance Documents .................................... 2
Table 2: Top-level system LoA criteria as determined by national impact ....................... 3
Table 3: TSN criticality and corresponding Levels of Assurance ..................................... 4
Table 4: Mapping critical components to Levels of Assurance ........................................ 5
The following table lists the nine LoA documents and their purposes:
Table 1: Level of Assurance best practice guidance Documents
Document Purpose
DoD Microelectronics: Field Programmable Gate Array
Background
Overall Assurance Process
DoD Microelectronics: Levels of Assurance Definitions and
Background
Applications
DoD Microelectronics: Field Programmable Gate Array
Background
Best Practices – Threat Catalog
DoD Microelectronics: Field Programmable Gate Array
Guidance LoA1
Level of Assurance 1 Best Practices
DoD Microelectronics: Third-Party IP Review Process for
Guidance LoA1
Level of Assurance 1
DoD Microelectronics: Field Programmable Gate Array
Guidance LoA2
Level of Assurance 2 Best Practices
DoD Microelectronics: Third-Party IP Review Process for
Guidance LoA2
Level of Assurance 2
DoD Microelectronics: Field Programmable Gate Array
Guidance LoA3
Level of Assurance 3 Best Practices
DoD Microelectronics: Third-Party IP Review Process for
Guidance LoA3
Level of Assurance 3
The FPGA device should not be protected at a level higher than the system in which it
operates. A U.S. Government (USG) person with authority over the program should
select the appropriate LoA for the overall program using the criteria in the following
table:
Select the top-level LoA. This now represents the highest level at which the FPGA
device can be protected.
Although components can receive a lower LoA than the system, a component cannot
receive a higher LoA than the system. For example, an LoA1 system cannot require
LoA3 components.
Program analysts can refer to the following table to determine the appropriate LoA for a
given component having determined the TSN criticality level.