1 / 7

ISE As An Implementation

ISE As An Implementation. Vijay Mehra. Slide 1 | Unclassified | Notional. Key Considerations. Information Sharing and Safeguarding focuses on ‘Data-in-Motion’; data as it is shared between mission applications

tracen
Download Presentation

ISE As An Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISE As An Implementation Vijay Mehra Slide 1 | Unclassified | Notional

  2. Key Considerations Information Sharing and Safeguarding focuses on ‘Data-in-Motion’; data as it is shared between mission applications Information Sharing Environment is not about building mission applications; its about enabling mission applications to share information, and make information offered by mission applications ‘Assured’, ‘Harmonized’, ‘Interoperable’, ‘Smart’, ‘Secure’, ‘Automated’, ‘Discoverable’, ‘Federated’ Business and Technical Standards enable Assured Information sharing in an interoperable environment, comprising of an ‘Information Sharing Stack of standards’ Consensus based development and adoption of technical standards required (including existing, under development, and gaps), and the portfolio of business and functional capabilities that implement these standards, driven by complexity of the exchange, and degree of maturity of the partnering organizations Technical capabilities need to be considered during design/planning phases of projects, to determine needs for implementation in mission applications, or as shared services, or both Slide 2 | Unclassified

  3. Anatomy of An Information Sharing FlowComponents of the message exchanged, and the corresponding technical standards Technical Standards Categories Needed (Not all messages use all categories) Current State/Gaps Work with SCC members to address Layered Encryption and Metadata Routing | Protocol Corresponding Industry Technical Standards All Web Services Standards, extensions and profiles like SOA, SoaML, GRA, UPDM, etc. Audit Audit Standards (??) Business Process | Linkages | DRM | Presentation • BPMN, XSLT, Linkage (??) • , DRM (??) Policy | Access | Identity | Obligations | Geo IDAM, BEA SAML, etc. IEPES, XACML, etc. Digest | Semantic Model NIEM, OWL, others (??) Content Model Tagging/Markings Privacy | Policy | Security Classification | Identity | Access | Geo Tagging – CUI, Policy, ?? Mission Data NIEM, UCORE, GML, ?? Slide 3 | Unclassified

  4. ISE Capabilities Model Procurement Process | Guidance | Language Normative Technical Standards and Reference Implementations Publish | Catalog Functional Standards Business Capabilities (Functional Standard with policy, programmatic, operational guidance) NSI - SAR TSC AWN Others… Technical Capabilities | Services Discovery Identity Security Federation Audit Enterprise Service Messaging Mediation Storage Collaboration Policy Content DRM Encryption Others… Routing | Protocol Audit Business Process | Linkages | DRM | Presentation Policy | Access | Identity | Obligations | Geo Digest | Semantic Model Privacy | Policy | Security Classification | Identity | Access | Geo Mission Data Slide 4 | Unclassified

  5. Outgoing - Build Stack Incoming- Teardown Stack Execution / Operational View Agency A Agency B Services Portfolio Services Portfolio Applications Portfolio Applications Portfolio Internal External External Internal 1 2 1 Discovery Discovery 1 1 2 3 4 2 Request 2 3 4 3 3 Data Sources Data Sources 4 4 Incoming- Teardown Stack Outgoing - Build Stack Response 1 2 1 2 5 5 3 4 6 6 3 4 Shared Services Security Identity Access Auditing Monitoring Classification Federation Others…

  6. Capability and StandardsLong term Strategy for Implementing the ISE 6-18 Months 12-24 Months 18-36 Months 6-9 Months Slide 6 | Unclassified

  7. Next Steps/Work in Progress Work with the members of SCC to fill gaps in the standards landscape as started previous slide Develop a sequence based on interdependencies among the standards initiatives Work with the SDOs to develop a timeline for each standard critical to ISE, leading to an overall multi-year plan to evolve the standards roadmap If more than one standard being develop, initiate conversations with the SDOs to help converge standards In case of multiple standards for each layer of the stack, develop interoperability profiles to enable information sharing using multiple standards Develop plans and incentives to motivate good behavior – for the government to Include standards in procurements, for the vendors to implement the standards, etc. Identify pilots to develop reference architectures and implementations to prove the standards Slide 7 | Unclassified

More Related