曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

To support interoperability using encrypted messages, products must share a common communications
protocol. This protocol must include common cryptographic message syntax, common cryptographic
algorithms, and common modes of operation (e.g., cipher-block chaining). The mechanisms to provide
the required security services are as follows.
Encryption Algorithms
Encryption algorithms are a set of mathematical rules for rendering information unintelligible by affecting
a series of transformations to the normal representation of the information through the use of variable
elements controlled by a key.
The following standard is mandated when the security policy or the program security profile requires this
level of protection, and Fortezza applications are in use:
􀂾 SKIPJACK and KEA Algorithm Specification, Version 2.0, NIST, 29 May 1998. [SUNSET] This
standard will be deleted when AES becomes the mandated standard.
For those systems required or desiring to use a cryptographic device to protect privacy-act information
and other unclassified information not covered by the Warner Amendment to Public Law 100-235, the
following standard is mandated:
􀂾 FIPS PUB 46-3, Data Encryption Standard, 25 October 1999. [SUNSET] This standard will be
deleted when AES becomes the mandated standard.
Signature Algorithms
A signature algorithm is an algorithm developed to assure message-source authenticity and integrity. The
intent of the signature is to provide a measure of assurance that the person signing the message actually
sent the message that is signed, and that the content of the message has not been changed. The following
standard is mandated when the security policy or program-security profile requires this level of
protection:
UAS ROADMAP 2005
APPENDIX E – INTEROPERABILITY STANDARDS
Page E-14
􀂾 FIPS PUB 186-2, Digital Signature Standard (DSS) Digital Signature Algorithm (DSA), 27 January
2000.
Signals Intelligence (SIGINT)
Many standards applicable to UA SIGINT data are addressed in Section 4 of the Joint Airborne SIGINT
Architecture (JASA) Version 2.0. Due to programmatic issues leading to cancellation of JSAF, the JASA
is being reviewed for future applicability and necessary changes. However, NATO Air Group IV has
initiated a study to examine the use of ELINT and ESM data within the community with an aim to
standardize the data formats of both aspects of electromagnetic collection.
Human Computer Interface
The objective of system design is to ensure system reliability and effectiveness. To achieve this objective,
the human must be able to effectively interact with the system. Operators, administrators, and maintainers
interact with software-based information systems using the system’s HCI. The HCI includes the
appearance and behavior of the interface, physical interaction devices, graphical interaction objects, and
other human-computer interaction methods. A good HCI is both easy to use and appropriate to the
operational environment. It exhibits a combination of user-oriented characteristics such as intuitive
operation, ease and retention of learning, facilitation of user-task performance, and consistency with user
expectations. The need to learn the appearance and behavior of different HCIs used by different
applications and systems increases both the training burden and the probability of operator error.
Interfaces that exhibit a consistent appearance and behavior both within and across applications and
systems are required.
When developing DoD automated systems, the GUI shall be based on one commercial user interface style
guide consistent with 5.6.1. Hybrid GUIs that mix user interface styles (e.g., Motif with Microsoft
Windows) shall not be created. A hybrid GUI is composed of toolkit components from more than one
user interface style. When selecting commercial off-the-shelf (COTS)/government off-the-shelf (GOTS)
applications for integration with developed DoD automated systems, maintaining consistency in the user
interface style shall be a goal. An application delivers the user interface style that matches the host
platform (i.e., Motif on a UNIX platform and Windows on an NT platform). This style conforms to
commercial standards, with consistency in style implementation regardless of the development
environment used to render the user interface. Applications that use platform-independent languages
(such as Java) deliver the same style as the native application on the host platform.
FLIGHT OPERATIONS STANDARDS
Flight operations standards are those standards required to operate the UA in the real world airspace
occupied by both manned and unmanned aircraft. These include the standards for flight clearance,
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：unmanned aircraft systems roadmap(99)