Backup and Recovery Requirements.xlsx
XLSX spreadsheet 10 KB Posted
- Solicitation number
- Not on record
About this file
This document is a Request for Information (RFI) from the Department of the Navy Naval Air Systems Command for the F-35 OPERATIONAL DATA INTEGRATED NETWORK (ODIN) Maintenance Systems Backup and Recovery.
The key details are:
- This RFI is market research to gather information for a future production contract for ODIN Maintenance Systems Backup and Recovery components and assemblies. The Prime Contractor/Integrator is Lockheed Martin Aeronautics Company.
- The contract will require backup and recovery supply chain management and integration with the F-35 ODIN Maintenance System. The contractor must ensure the backup and recovery system interfaces with existing F-35 maintenance systems.
- The RFI requests information on government-furnished requirements, property, schedule, pricing estimates, company capabilities compared to requirements, and supply chain management plans.
- Responses to the RFI are voluntary, not considered offers, and will not be reimbursed. The government is under no obligation to award any contracts.
View the file
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
Sheet1
| ID | Subsystem | Requirement Text | Verification Method |
| BUR-1 | Core Infrastructure (CI) | The backup and recovery system shall have backup files that are immutable (data cannot be modified or deleted) | Penn Test |
| BUR-2 | Core Infrastructure (CI) | The backup and recovery system shall have backups that use a zero-trust architecture and are logical airgap to ensure they are invisible from the network. | Penn Test |
| BUR-3 | Core Infrastructure (CI) | The backup and recovery system shall be auditable in real time. | Demonstration |
| BUR-4 | Core Infrastructure (CI) | The backup and recovery system shall be 99.99% available | Analysis |
| BUR-5 | Core Infrastructure (CI) | The backup and recovery system shall have a real time alert system with fault detection. | Demonstration |
| BUR-6 | Core Infrastructure (CI) | The backup and recovery system shall be able to recover within 2 hours of determining a fault. | Test |
| BUR-7 | Core Infrastructure (CI) | The backup and recovery system shall be fully digital and not require personnel in the backup process. | Test |
| BUR-8 | Core Infrastructure (CI) | The backup and recovery system shall be scalable to recover any size server based system. | Analysis |
| BUR-9 | Core Infrastructure (CI) | The backup and recovery system shall not require third party license agreements. | Documentation |
| BUR-10 | Core Infrastructure (CI) | The backup and recovery system shall be FIPS 140-2 compliant and not run on Windows or a Virtual Machine | Analysis |
| BUR-11 | Core Infrastructure (CI) | The backup and recovery system shall encrypted data at rest and in transit | Analysis |
| BUR-12 | Core Infrastructure (CI) | The backup and recovery system shall have an append-only file system and run on a hardened OS | Analysis |
| BUR-13 | Core Infrastructure (CI) | The backup and recovery system shall have multifactor authentication for access | Demonstration |
| BUR-14 | Core Infrastructure (CI) | The backup and recovery system shall have a two-person rule to change permissions or retention periods | Demonstration |
| BUR-15 | Core Infrastructure (CI) | The backup and recovery system shall have a global SLA policy and auto-discover new databases and VMs as they are added | Test |
| BUR-16 | Core Infrastructure (CI) | The backup and recovery system shall collect data and its associated metadata to provide a time series view of the data | Test |
| BUR-17 | Core Infrastructure (CI) | The backup and recovery system shall be able to scan backups to find sensitive data stored | Demonstration |
| BUR-18 | Core Infrastructure (CI) | The backup and recovery system shall be able to scan backups to search for specific Indicators of Compromise (IOCs) and proactively alert on like events | Demonstration |
| BUR-19 | Core Infrastructure (CI) | The backup and recovery system shall hardware agnostic and needs to be able to be deployed on on-prem, and cloud resources | Analysis |
| BUR-20 | Core Infrastructure (CI) | The backup and recovery system shall be able to recover from an individual node of the backup recovery system failing. (IE kinetic disruption) | Analysis |
| BUR-21 | Core Infrastructure (CI) | The backup and recovery system shall have a verifiable supply chain for all hardware and software components | Analysis |
| BUR-21 | Core Infrastructure (CI) | The backup and recovery system shall be able to operate over a 4 week period without any network connections | Analysis |
| BUR-22 | Core Infrastructure (CI) | The backup and recovery system shall be scalable/upgradable to account for data accountability through 2080 | Analysis |
| BUR-22 | Core Infrastructure (CI) | The backup and recovery system shall be able to take a "snap shot" of the current configuration in the event of a catastrophic event (IE loss of aircraft) | Demonstration |
| BUR-23 | Core Infrastructure (CI) | The backup and recovery system shall be able to take a "snap shot" of the current configuration for troubleshooting fleet issues. | Demonstration |
File details come from the government source that posted it. Updated .