Refine Your Search

Topic

Search Results

Journal Article

The Missing Link: Aircraft Cybersecurity at the Operational Level

2020-07-25
Abstract Aircraft cybersecurity efforts have tended to focus at the strategic or tactical levels without a clear connection between the two. ...CSSEP’s process model postulates that security is best achieved by a balance of cybersecurity, cyber resiliency, defensibility, and recoverability and that control is best established by developing security constraints versus attempting to find every vulnerability. ...CSSEP identifies the major functions needed to do effective aircraft cybersecurity and provides a flexible framework as the “missing link” to connect the strategic and tactical levels of aircraft cybersecurity.
Training / Education

DO-326A and ED-202A An Introduction to the New and Mandatory Aviation Cyber-Security Essentials

2021-03-08
The international standards D-326A (U.S.) and ED-202A (Europe) titled "Airworthiness Security Process Specification" are the cornerstones of the "DO-326/ED-202 Set" and they are the only Acceptable Means of Compliance (AMC) by FAA & EASA for aviation cyber-security airworthiness certification, as of 2019. The "DO-326/ED-202 Set" also includes companion documents DO-356A/ED-203A: "Airworthiness Security Methods and Considerations" & DO-355/ED-204: "Information Security Guidance for Continuing Airworthiness" (U.S. & Europe) and ED-201: "Aeronautical Information System Security (AISS) Framework Guidance" & ED-205: "Process Standard for Security Certification / Declaration of Air Traffic Management / Air Navigation Services (ATM/ANS) Ground Systems“ (Europe only).
Standard

GUIDANCE FOR SECURITY EVENT LOGGING IN AN IP ENVIRONMENT

2017-06-21
CURRENT
ARINC852
This report sets forth guidance for IP-based onboard networks and systems residing in the Airline Information Services (AIS) and Passenger Information and Entertainment Services (PIES) Domains by establishing a common set of security related data elements and format(s) that are produced by aircraft systems, suitable for use by airline IT and/or avionic supplier analytical ground tools.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Architecture Description

2020-07-14
CURRENT
AS6512A
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Library Revision A or, simply, the UCS Architecture. The architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library Revision A are: AS6513A, AS6518A, AS6522A, and AS6969A.
Standard

Requirements for a COTS Assembly Management Plan

2020-08-03
CURRENT
EIA933C
This document applies to the development of Plans for integrating and managing COTS assemblies in electronic equipment and Systems for the commercial, military, and space markets; as well as other ADHP markets that wish to use this document. For purposes of this document, COTS assemblies are viewed as electronic assemblies such as printed wiring assemblies, relays, disk drives, LCD matrices, VME circuit cards, servers, printers, laptop computers, etc. There are many ways to categorize COTS assemblies1, including the following spectrum: At one end of the spectrum are COTS assemblies whose design, internal parts2, materials, configuration control, traceability, reliability, and qualification methods are at least partially controlled, or influenced, by ADHP customers (either individually or collectively). An example at this end of the spectrum is a VME circuit card assembly.
Standard

Airworthiness Assurance for Airborne Electronic Hardware (AEH) Containing Commercial-off-the-shelf (COTS) Electronic Components

2018-12-19
WIP
ARP7495
This document addresses issues related to assurance that COTS electronic hardware components will perform their intended function in the AEH equipment or system in which they are installed. Those issues may impact system design, reliability assessment, quality, testing, production or support; but this document is not intended to be specific to any of those disciplines. This document is focused on the hardware issues raised in DOT/FAA/TC-16/57; it does not include issues related to software, firmware, etc. This document is intended to fit within the development process for civil aircraft and systems. This document can be used to support design and analysis activities in RTCA DO-254/EUROCAE ED-80 and RTCA DO-297/EUROCAE ED-124, as well as SAE ARP4754. This document addresses twelve (12) of the twenty-six (26) specific issues described in DOT/FAA/TC-16/57.
Standard

Standard for Preparing a DMSMS Management Plan

2017-04-14
WIP
STD0016A
This document defines the requirements for developing a DMSMS Management Plan, hereinafter also called the Plan, to assure customers that the Plan owner is using a proactive DMSMS process for minimizing the cost and impact that part and material obsolescence will have on equipment delivered by the Plan owner. The technical requirements detailed in clause 5 ensure that the Plan owner can meet the requirement of having a process to address obsolescence as required by Industry Standards such as EIA-4899 "Standard for Preparing an Electronic Components Management Plan" and DoD Programs as required by MIL-STD-3018 "Parts Management". Owners of DMSMS Management Plans include System Integrators, Original Equipment Manufacturers (OEM), and logistics support providers.
Journal Article

An Approach to Verification of Interference Concerns for Multicore Systems (CAST-32A)

2020-03-10
2020-01-0016
The avionics industry is moving towards the use of multicore systems to meet the demands of modern avionics applications. In multicore systems, interference can affect execution timing behavior, including worst case execution time (WCET), as identified in the FAA CAST-32A position paper. Examining and verifying the effects of interference is critical in the production of safety-critical avionics software for multicore architectures. Multicore processor hardware along with aerospace RTOS providers increasingly offers robust partitioning technologies to help developers mitigate the effects of interference. These technologies enable the partitioning of cores for different applications at different criticalities and make it possible to run multiple applications on one specific core. When incorporated into system-design considerations, these partitioning mechanisms can be used to reduce the effects of interference on software performance.
Article

New university-led Air Force Center of Excellence focuses on securing autonomous systems operating in contested environments

2019-05-22
The researchers at the COE for Assured Autonomy in Contested Environments – all of which histories of innovation for Department of Defense problems of interest – will focus on the availability, integrity, and effective use of information by leveraging its diverse expertise in dynamics, mathematics, control theory, information theory, communications, and computer science.
Article

Software needs security, and security needs software: a scientific overview

2019-04-22
Software needs security. That's a consequence of using software to control critical systems. It's difficult because software is inherently a complex artifact, even when the code just consists of a single sequential program in a single programming language, with well-defined inputs and outputs. Of course, actual software rarely if ever has such a simple structure. Security needs software. That's a consequence of the complexity just mentioned. No process can ensure security at scale unless it is automated by using software itself: programming languages, verification tools, software platforms.
Article

SAE International anti-counterfeit standards integral to obsolescence management

2018-07-25
Counterfeit parts prevention is integral to an effective obsolescence management plan, and the focus of anti-counterfeit standards – including Counterfeit Avoidance Standard (AS5553) and Counterfeit Detection Standard (AS6081) – from SAE International in Warrendale, Pa. SAE International officials are bringing the anti-counterfeit discussion and sharing best practices, which include adherence to critical standards, to the Future of Obsolescence Management (FOM) event on October 10 and 11 in Washington.
Article

Nvidia partners with AdaCore to secure self-driving firmware

2019-02-14
As mobility software becomes increasingly complex and connected, so does the risk of human error and system safety. To combat this, New York-based software company AdaCore will work with Nvidia Corporation of Santa Clara, California to apply open-source Ada and SPARK programming languages for select software security firmware elements in highly-complex, safety-critical systems like Nvidia’s DRIVE AGX automated and autonomous vehicle solutions.
X