ORE Tech and Programmatic Sync 20220202 Notes
- Answered why the initial landing page at login is the ORE application instead of the orchestrated apps page
- Explained the function of the orchestrated apps page as an orchestration of gateways to different applications that each have their own storage and configurations
- Explained what applications are currently available and the difference between what is shown as an example based on what 2 Twelve currently has operating in the ORE and what the government is able to access
- Affirmed Brandon's understanding of the ORE's ability to present information pulled from different applications and presenting it in the ORE application using an automated process in order to provide visibility to governance level personnel
- Explained that the ORE environment has the ability to restrict access to important information such as DNS logs so that the only information given to contractors/vendors is what they need on their dashboard and not access to functions that could damage the system, and that can all be controlled centrally through automated processes
- Answered the question concerning integration - that 2 Twelve does not need to prove capability to integrate with WWT in order to demonstrate capability to integrate with core node once it is provisioned because the ORE is already integrated into multiple cloud environments and which is the benefit of the cloud native functionality of the ORE to be able to integrate with multiple environments. The ORE is already required in TO 1 to integrate into transformative, cloud native, ZT, modern encrypted (cloud native compute, storage, containers, vms, modern encryption protocols, and SDN) environments.
Updated by Jacob Halle about 2 years ago ยท 1 revisions