Skip to main content

Currently Skimming:

Appendix E: Naval Information Assurance Architectural Considerations
Pages 165-173

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 165...
... This concept is part of FORCEnet, which is "the operational construct and architectural framework for naval warfare in 1ADM Gary Roughead, USN, Chief of Naval Operations; Gen James T Conway, USMC, Com mandant of the Marine Corps; and ADM Thad W
From page 166...
... ) , and new satellite communications capabilities, all of which require deliberate development and service acquisition strategies owing to their high cost and criticality to naval operations.
From page 167...
... The core exists in fiber-optic connectivity, which allows opera tions in the continental United States as well as at specific fixed regional sites such as military bases. The ability to reach naval forces responding to global conflicts requires communications capabilities beyond core networks, and for this the naval forces rely extensively on satellite communications (SATCOM)
From page 168...
... Some weapons and combat systems may have latency and data-processing volume requirements that necessitate tightly coupled, real-time, distributed applications and computing components, features that can be difficult to implement based on SOA design principles. However, the potential rigor of SOA configuration control can be useful in such conditions to ensure information availability and integrity; also, the capability of processing is increasing quickly enough that the inefficien cies of SOA could be overcome.
From page 169...
... From an IA perspective, the enterprise architecture must enable naval forces to keep pace with new trends in Department of Defense (DOD) computing, such as the movement toward Web services, and incorporate information assurance mechanisms that deal with threats related to these trends.
From page 170...
... WS-Security; WS-Policy Web Service (WS) -Security is a World Wide Web Consortium specification for protecting Web services messages that employ Extensible Markup Language (XML)
From page 171...
... has been created from a desire to make access control more dynamic.g Web services XML-based Web services are seen as an important trend in architecting distributed systems that cuts across many areas of IT and IA.h Examples of prominent Web services security standards include XML encryption and XML Signature for XML data-level security, the Security Assertions Markup Language (SAML) for expressing security assertions (e.g., assertions for authentication events, attributes, and access decisions)
From page 172...
... 2007. Guide to Web Services Security, NIST Special Publication 800-95, Computer Security Division, Information Technology Laboratory, National Institute of Standards and Technology, Gaithersburg, Md., August.
From page 173...
... 2009. "DON Enterprise Architecture Development Supports Naval Transformation," CHIPS, Vol.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.