OpenBEDM Software Description

The outline below shows the planned topics. Follow a link in the outline to read and/or listen about a topic.

This description is mostly incomplete first because there was no time to complete the description and second the description could become redundant when the associated book "The Third Way" is completed. However, at present, neither is complete and more work is necessary.

When there is a linked item in the outline, the subitems under the item are topics that are described by the item. Otherwise, the outline is here for guiding future writing efforts.

Preliminary comments:

Outline

• Architecture Notions See also: "Conceptual Architecture".
• Data Local - Network Everywhere - Encryption Open-Ended
1. Data Local means local control and local security controls. No federated database.
2. Network Everywhere means information can move where needed without new or extraordinary measures.(J2EE network software libraries are used for implementation)
3. Encryption open-ended means encryption algorithms are generic interfaces until the best available encryption is loaded at run-time (n.b. this is standard J2EE architecture).
4. The architecture explicitly avoids harmful decisions. There is no distributed database. No new, untested network technology. No novel untested encryption.
• Concurrent Document Management Sessions
• Document Encryption Multilayered
1. Partial Encryption
2. 3-Key Encryption
3. 4-Key Encryption
• Peer-to-Peer Message-Oriented Distributed Computing
• Optional Message Agent Middleware (discuss security)
• Event-Driven State-Machine-Based Sequence Control
• Operations Concept See also an attempt to formalize: "Operations Requirements".
• Maintain Security Defenses
1. Maintain Site Security
2. Maintain Network Security between Sites
3. Encrypt Data At Rest
• Improve Security Defenses
1. Block Remote Access to Site Data
2. Introduce a Blind Agent to Identify Opportunities for Limited, Intelligent Data Sharing
3. Share Limited Data between Sites; Share only what is essential and relevant.
4. Utilize Black/White Composite Software Defenses
5. Utilize Zoned-Hardware Segregated-Software Defenses
• The Four Roles of the Blind Agent
1. Blind Facilitator for Negotiation of Information Sharing
2. Blind Discovery Agent
3. Blind Disclosure Agent
4. Blind Witness
• Policy Framework
• Freedom within the Framework
• Software Concepts
• Enterprise Integration
• Cryptographic Algorithm Requirements
• Program Configuration
• Scheduling and Work Flow Control
• Background and Interpretation

<<Return to Top