IAW 509 BW R-EFB Program.pdf
PDF 93 KB Posted
- Attached to
- 509 OG iPad Redaction
- Solicitation number
- FA462525Q1075
About this file
This document is a Concept of Operations (CONOP) for B-2 R-EFB (Redacted Electronic Flight Bag) and PWTR device security, dated 15 October 2021. The document outlines strict security protocols for electronic devices used in the B-2 cockpit, which only contain Controlled Unclassified Information (CUI). Key requirements include physical redaction of baseline Electronic Flight Bag (EFB) devices by a 509 BW/APO-approved contractor, involving the removal of cameras, microphones, WiFi hardware, and Bluetooth hardware.
The CONOP specifies that approved devices must be selected according to AFGSCI 11-270, avoiding transmission and recording technologies beyond basic functions. Redacted devices will be visually distinguished from other EFBs and housed in unique cases. Battery packs used with these devices must be government-owned, approved for B-2 cockpit use, and exclusively used with B-2 R-EFBs and PWTR devices. The document also mandates a 5 cm exclusion area from classified systems and limits data transfer to USB connections within a Special Access Program Facility (SAPF).
View the file
Other files
| File | Type | Posted |
|---|---|---|
| iPad Redaction PWS 3Sep25.pdf | ||
| Updated Ipad Redaction Sources Sought.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
B-2 R-EFB SECURITY CONOP 15 October 2021 5
Chapter 2
R-EFB and PWTR Operations
2.1. Overview. The B-2 R-EFBs and PWTR devices only contain Controlled Unclassified Information (CUI). The primary mitigation measure – to prevent SAP information from being compromised IAW para 1.3. – is physical redaction of the hardware capable of collecting data IAW para 2.3. Once redacted, the only means of data transfer is through a USB connection to another information system within the SAPF. That residual risk is mitigated via specific exclusions and approvals on what the R-EFBs and PWTR devices may be connected to IAW para 2.6.
Although the physical redaction of the R- EFBs removes all antennas capable of receiving data, the R-EFBs and PWTRs will still use the Air Force Network Integration Center (AFNIC)-assessed 5 cm exclusion area from classified systems for EFBs that utilize software redaction of wireless capabilities.
2.2. Approved Baseline EFB Devices. Baseline EFB devices will be an approved device IAW AFGSCI 11-270, Electronic Flight Bag Operations. Baseline EFB devices should be selected that do not include transmission and/or recording technology beyond camera, microphone, WiFi, and Bluetooth. (e.g. cellular radios, near field communication [NFC], etc.). If no baseline EFB device meets this requirement, 509 OG/OGV will coordinate with 509 BW/APO to establish a new redaction process and update this CONOP.
2.3. Device Redaction. In order to be an approved B-2 R-EFB, a baseline EFB device must be physically redacted. Redaction will be accomplished by a 509 BW/APO-approved contractor. A record of redaction, by device serial number, will be maintained as long as the device is used as a B-2 R-EFB. Redaction will include the physical removal of the following components from the baseline EFB device:
2.3.1. Camera
2.3.2. Microphone
2.3.3. WiFi hardware
2.3.4. Bluetooth hardware
2.4. Identification. Once redacted, the device will be referenced as a B-2 R-EFB to avoid confusion with the baseline EFBs utilized by the T-38 Companion Trainer Program (CTP).
Additionally, B-2 R-EFBs will be housed in a case that ensures visual distinction from T-38 CTP EFBs.
2.5. Batteries. Battery packs may be connected to B-2 R-EFBs and PWTR devices in-flight, provided they are government owned and have been approved for introduction and use in the B-2 cockpit through appropriate channels. Battery packs used with B-2 R-EFBs and PWTRs will not be used with any other device.
File details come from the government source that posted it. Updated .