Web Services Gateway Digital Rights Management Monitoring, Alerting the access/visualization aspects of the Application Provider. Application Provider Application Layer Identity Web Services Gateway Data Transformation Digital Rights Management Monitoring, Alerting Application Provider interfaces between the Data Provider and Data Consumer. It takes part in all the secure interface protocols with these blocks as well as maintains secure interaction with the Framework Provider. Framework Provider Virtualization Layer Identity Identity Provider Encryption and Key Management Isolation/Containerization Storage Security Network Boundary Control Monitoring, Alerting Framework Provider is responsible for the security of data/computations for a significant portion of the life cycle of the data. This includes security of data at rest through encryption and access control; security of computations via isolation/virtualization; and security of communication with the Application Provider. NBDRA Subsection Scope: This section will contain a brief summary of the information in Appendix A (Full mapping of use cases to NBDRA). Possibly discuss what the mapping is, overall take away, and maybe run through the example use case. NBDRA Figure 6 provides an overview of several security and privacy topics with respect to some key NBDRA components and interfaces. The figure represents a beginning characterization of the interwoven nature of the Security and Privacy Fabric with the NBDRA components. It is not anticipated that Figure 6 will be further developed for Version 2 of this document. However, the relationships between the Security and Privacy Fabric and the NBDRA and the Security and Privacy Taxonomy and the NBDRA will be investigated for Version 2 of this document. Figure 6: Notional Security and Privacy Fabric Overlay to the NBDRA The groups and interfaces depicted in Figure 6 are described below. INTERFACE BETWEEN DATA PROVIDERS → BIG DATA APPLICATION PROVIDER Data coming in from data providers may have to be validated for integrity and authenticity. Incoming traffic may be maliciously used for launching DoS attacks or for exploiting software vulnerabilities on
Table 2: Classification of Cryptographic Technologies Technology Data Provider Application Provider Feature Visibility Homomorphic Encryption Encrypts data Stores encrypted data Capability to perform computations Only at Data Provider Functional Encryption Encrypts data Stores encrypted data Capability to perform computations Result of allowed computations visible at Application Provider Access Control Policy-Based Encryption Encrypts data Stores encrypted data No capability to perform computations Only for entities which have a secret key satisfying the access control policy Secure Computation Plaintext data Stores plaintext data Collaborative computation among multiple Application Providers Application Providers do not learn others’ inputs. They only learn the jointly computed function. Blockchain Plaintext or encrypted data Decentralized Immutable decentralized database Transaction logging in a decentralized, untrusted environment Hardware primitives for secure computations Encrypts data Stores encrypted data Capability to perform computations. Verified execution. Controllable visibility at Application Provider. Scenario: Data Provider has data to be kept confidential. Application Provider is requested to do computations on the data. Data Provider gets back results from Application Provider. Consider that a client wants to send all its sensitive data to a cloud: photos, medical records, financial records and so on. She could send everything encrypted, but this wouldn't be of much use if she wanted the cloud to perform some computations on them, such as how much did she spend on movies last month? With Fully Homomorphic Encryption (FHE), a cloud can perform any computation on the underlying Party
conjunction with encryption presents particular challenges (Reference here). Other columns may require cryptographic metadata for facilitating aggregation and deduplication. The HL7 standards organization is currently studying this set of related use cases. Application Provider → Data Consumer Privacy-preserving data analytics Searching on encrypted data and proofs of data possession. Identification of potential adverse experience due to clinical trial participation. Identification of potential professional patients. Trends and epidemics, and co-relations of these to environmental and other effects. Determination of whether the drug to be administered will generate an adverse reaction, without breaking the double blind. Patients will need to be provided with detailed accounting of accesses to, and uses of, their EHR data. Compliance with regulations HIPAA security and privacy will require detailed accounting of access to EHR data. Facilitating this, and the logging and alerts, will require federated identity integration with data consumers. Where applicable, compliance with US FDA CFR Title 21 Part 56 on Institutional Review Boards is mandated. Government access to data and freedom of expression concerns CDC, law enforcement, subpoenas and warrants. Access may be toggled based on occurrence of a pandemic (e.g., CDC) or receipt of a warrant (e.g., law enforcement). Data Provider ↔ Framework Provider Data-centric security such as identity/policy-based encryption Row-level and column-level access control Policy management for access control Role-based and claim-based. Defined for PHI cells Computing on the encrypted data: homomorphic encryption Privacy-preserving access to relevant events, anomalies, and trends for CDC and other relevant health organizations Audits Facilitate HIPAA readiness and HHS audits Framework Provider Securing data storage and transaction logs Need to be protected for integrity and privacy, but also for establishing completeness, with an emphasis on availability. Key management Federated across covered entities, with the need to manage key life cycles across multiple covered entities that are data sources Security best practices for data stores End-to-end encryption, with scenario-specific schemes that respect min-entropy to provide richer query operations without compromising patient privacy Security against distributed denial A mandatory requirement: systems must survive
freedom of expression concerns performance metrics for teachers, administrators, and districts. Data Provider ↔ Framework Provider Data-centric security such as identity/policy-based encryption Support both individual access (student) and partitioned aggregate Policy management for access control Vendor (e.g., Pearson) controls, state-level policies, federal-level policies; probably 20-50 different roles are spelled out at present. Computing on the encrypted data: homomorphic encryption Proposed Audits Support both internal and third-party audits by unions, state agencies, responses to subpoenas Framework Provider Securing data storage and transaction logs Large enterprise security, transaction-level controls—classroom to the federal government Key management CSOs from the classroom level to the national level Security best practices for data stores --- Security against DDoS attacks Standard Data provenance Traceability to measurement event requires capturing tests at a point in time, which may itself require a Big Data platform. Fabric Analytics for security intelligence Various commercial security applications Event detection Various commercial security applications Forensics Various commercial security applications Industrial: Aviation Sensor Data Storage and Analytics Mapping of sensor data storage and analytics is under development and will be included in future versions of this document. Transportation Cargo Shipping This use case provides an overview of a Big Data application related to the shipping industry for which standards may emerge in the near future. Table A-9: Mapping Cargo Shipping to the Reference Architecture NBDRA Component and Interfaces Security and Privacy Topic Use Case Mapping Data Provider → Application End-point input validation Ensuring integrity of data collected from sensors Real-time security monitoring Sensors can detect abnormal