Learn about the security requirements associated with this challenge.
| Overview | Link | |
|---|---|---|
|
FIPS 200 |
Minimum Security Requirements for Federal
Information and Information Systems
|
|
|
FIPS 199 |
Standards for Security Categorization of
Federal Information and Information Systems
|
Performance Considerations
Bandwidth
The Network Architecture must prepare for the possibility that most vehicles in the NAS generates reports as frequently as once per second via the internet, and all such reports pass into this system. Assuming (3-5 years in the future) 2 million participating vehicles, a peak load of 1% operating simultaneously, and a message size of up to 1KB, this would generate approximately 160Mbps-200Mbps. This load would be spread over multiple connections between the FAA and potential service suppliers. Continuous traffic means that the total volume will also be large, estimated at 3TB-4TB per month. Furthermore, this data may be shared with additional partners by the FAA. A reasonable assumption of three such partners and 50% increase in data due to included packaging by the FAA could result in up to 1000 Mbps and 10TB-20TB per month (outbound streams). While the load is expected to be spread across multiple potential service suppliers, the number could vary over time. This number is expected to range from anywhere from five up to 100 different potential service suppliers.
Security
The architecture must follow information security requirements defined by National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) Publication 200, Minimum Security Requirements for Federal Information and Information Systems, and be secured at a FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, Moderate Impact Level or equivalent or higher security level. Any data in transit must be protected.
Availability
The architecture must support an essential service level of availability (0.999) and commensurate service monitoring. The service may be necessary for various types of operations and therefore must achieve such a high level of availability.
Scalability
The architecture must be scalable and flexible to adapt to variations and future changes. For example, there may be season variations in traffic processed by the system. Additionally, future products may be built into the architecture, and the number of connected potential partners may increase with time.
Storage
The architecture must be designed for retention of the last six months of data.
Service Monitoring
The architecture must be designed to support monitoring, including performance.
Lifecycle Management
The architecture must be designed to support lifecycle management. Run-time management should address tracking usage and control access using appropriate controls.