Home' RTCA Documents for Review : DO-356A Contents 92
© RTCA, 2018
and process the security log files in accordance with the ICA provided by DAH and with
applicable operational security regulatory material (eg., FAA AC 119-1).
Allocation of responsibility among stakeholders
Responsibilities for security event logging are allocated between the DAH, the Operator
(or maintainer or MRO when relevant) and the Regulatory Authorities.
The DAH defines and installs the security event logging function in compliance with the
applicable airworthiness security regulations (e.g. a Security Special Condition) and
applies to the Authority for an airworthiness approval. The DAH transmits ICA to the
Operator. In case of a reportable event or service difficulty reported by the Operator
(eg., system failure or malfunction, maintenance message, security event detection, ...),
the DAH may request security logs from the Operator for further investigation. In case
of an unsafe condition addressed by 14 CFR Part 21.3 / EASA Part 21.A.3A, the DAH
may include the results of the security investigation in the report submitted to the
The Operator applies to the Authority for an operational approval in accordance with
applicable operational security regulatory material (e.g . FAA AC 119-1). The Operator
operates and maintains security event logging in accordance with the DAH ICA. In case
of a reportable event or service difficulty reported by the Operator to the DAH, the
Operator may have to transmit security logs to the DAH upon request.
The Authority grants an airworthiness approval of the security event logging function to
the DAH and an operational approval of security event logging to the Operator. In the
case of an unsafe condition addressed by 14 CFR Part 21.3 / EASA Part 21.A.3A, the
Airworthiness Authority may retain the outcome of the security log analysis, if included
in the DAH investigations report, for agreement.
The security events to be logged are a DAH responsibility because the DAH is
responsible of the design of the aircraft security protections and responsible for the
necessary means and instructions to the operator in order to maintain the security of
the product and to comply with 14 CFR Part 21.3 / EASA Part 21.A.3A. Since they
strongly depend on aircraft architectures, the minimum required security data types to
be logged cannot be standardized through an international aeronautical standard.
STC and TSO holders are also the DAH in the context of this section.
Recommendation #6: The Security events to be logged should be defined by the DAH
only and should be described in the Security Guidance (ICA and non-ICA) transmitted
by the DAH to the Operator. The Security events to be logged are dependent on:
the aircraft architecture
the security measures
the security risk analysis outcomes
For easier management and use of common tools by the Operators, the format of the
security logs should be standardized by an international aeronautical standard and
therefore, should generally comply with the section 3 of the ARINC 852 standard.
Recommendation #7: The format of the security logs should comply with section 3 of
the ARINC 852 standard.
The Security Guidance about security events logging, transmitted by the DAH to the
Operator, should give necessary technical information about security log files in
accordance with ED-204 / DO-355 section 8.2.2 (“Monitoring and Detection”).
Recommendation #8: Necessary technical information about security log files and
associated tools should be described in the Security Guidance and should be compliant
with ED-204 / DO-355 section 8.2.2 (“Monitoring and Detection”).
For obtaining an operational authorization for an aircraft certified with airworthiness
security regulations (e.g., a security Special Condition), the Operator may be required
to set up an Aircraft Network Security Program (ANSP) or equivalent which considers
Links Archive Navigation Previous Page Next Page