Accelerating Time-to-Market
Utilizing the OMG DDS open standard enables the ability to rapidly assemble loosely coupled ( distributed ) software components into a working system
As a part of this project , we have built several reference architectures that demonstrate the utility of this approach .
General purpose computing , operating systems , inherent language features ( e . g ., C memory allocation ), and software quality issues have led to a lack of inherent security and resiliency in systems throughout industry . This has resulted in many security breaches that have had dire consequences to national security . It is necessary to design assured systems based on appropriate techniques and tools by applying sound security and engineering principles .
Generally speaking , building an assured system entails a thorough understanding of the problem domain , deep analysis of domain-specific workflows and requirements , careful architectural considerations and design trade-offs , vetted development , proper configuration and managed deployment of the final product . This level of care will also be needed throughout the product lifecycle . Specifically related to system architecture , leveraging hardware and software techniques and tools for enhanced security boils down to applying sound security principles to suitable targets such as memory access ( e . g ., the Principles of Open Design , Least Privilege , Separation of Privilege , and Complete Mediation ). Other research and development efforts may adopt different applications of such principles to their particular environments and design goals .
One common theme in developing a trustworthy system architecture is related to secure communications , which include communications of the system with external parties and those among internal entities of the system itself . It is relatively straightforward for a developer to adopt the Complete Mediation principle and check integrity and confidentiality using some cryptographic methods , especially for external communications . For internal communications , some kind of broadcast via a bus interface ( e . g ., MIL-STD-1553 ) is usually adopted due to reasons such as legacy support and easy integration . These practices are not sufficient to provide the needed security , resiliency , assurance or even efficiency .
First , while the cryptographic algorithms are standardized , correct application of cryptography , particularly key management , remains a major challenge in implementation . Example vulnerabilities related to inappropriate use of cryptography abound . Moreover , broadcast-based bus interfaces are well known to be vulnerable to myriad attacks , since by nature the bus is an “ open-party-line ” that each module attached to the bus can listen to , receive and send messages . A well vetted and standardized way to apply cryptography is needed , and security should be applied to bus-based communications .
Journal of Innovation 87