; (ii) which metadata data records should be universally sent to Big Data Platform instances and which metadata data records, if any, should be locally retained; and (iii) expeditiously and efficiently transmitting metadata records to the Big Data Platform instances, including the acquisition and installation of further data bandwidth; (D) determine the appropriate number, organization, and functions of separate Big Data Platform instances, and whether the Big Data Platform instances that are currently managed by Department of Defense components, including the military services, should instead be jointly and regionally organized; (E) determine the appropriate roles of the Defense Information Systems Agency’s Acropolis and United States Cyber Command’s Scarif Big Data Platforms as enterprise-wide real-time cybersecurity situational awareness capabilities, as complements or replacements for component-level Big Data Platform instances; (F) ensure that all Big Data Platform instances are engineered and approved to enable standard access and query capabilities by the Unified Platform, the network defense service providers, and the Cyber Mission Forces, with centrally managed authentication and authorization services; (G) prohibit barriers to information sharing, distributed query, data analysis, and collaboration across Big Data Platform instances, such as incompatible interfaces, interconnection service agreements, and the imposition of accreditation boundaries; (H) transition all Big Data Platform instances to a cloud computing environment in alignment with the cloud strategy of the Chief Information Officer of the Department of Defense; (I) consider whether packet capture databases should continue to be maintained separately from the Big Data Platform instances, managed at the secret level of classification, and treated as malware-infected when the packet data are copies of packets extant in the Department of Defense Information Network