(Image from William Miller) Sources Transformation: End-Point Input Validation Ensuring integrity of data collected from sensors Real Time Security Monitoring Sensors can detect abnormal temperature/environmental conditions for packages with special requirements. They can also detect leaks/radiation. Data Discovery and Classification Secure Data Aggregation Aggregating data from sensors securely Transformation Uses: Privacy preserving data analytics and dissemination Sensor collected data can be private and can reveal information about the package and geo-information. Revealing such information needs to be privacy preserving. Compliance with regulations Govt access to data and freedom of expression concerns Dept of Homeland Security may monitor suspicious packages moving into/out of the country. Transformation Data Infrastructure: Data Centric Security such as identity/policy-based encryption Policy management for access control Private, sensitive sensor data, package data should only be available to authorized individuals. Third party companies like LoJack have low level access to the data. Computing on the encrypted data: searching/filtering/deduplicate/fully homomorphic encryption Audits Data Infrastructure: Securing Data Storage and Transaction logs Logging sensor data is essential for tracking packages. They should be kept in secure data stores. Key Management For encrypted data. Security Best Practices for Diversity of sensor types and data types may necessitate use of
audit records were retained for forensics & billing. Pharma Clinical Trial Data Sharing General Description of the Industry / Use Case: Under an industry trade group proposal, clinical trial data for new drugs will be shared outside intra-enterprise warehouses. Regulatory submissions commonly exceed “millions of pages.” Mapping to the Security Reference Architecture: RA Component Security & Privacy Topic Use Case Mapping Sources → Transformation End-Point Input Validation Opaque – company-specific Real Time Security Monitoring None Data Discovery and Classification Opaque – company-specific Secure Data Aggregation 3rd party aggregator Transformation → Uses Privacy-preserving Data Analytics Data to be reported in aggregate but preserving potentially small-cell demographics Compliance with Regulations Responsible developer & 3rd party custodian Govt access to data and freedom of expression concerns None considered: research limited community use; possible future public health data concern. Clinical Study Reports only, but possibly selectively at study-, patient-level Transformation ↔ Data Infrastructure Data Centric Security such as identity/policy-based encryption TBD Policy management for access control Internal roles; 3rd party custodian roles; researcher roles; participating patients’ physicians Computing on the encrypted data: searching/filtering/deduplicate/fully homomorphic encryption TBD Audits Release audit by 3rd party Securing Data Storage and Transaction logs TBD Key Management Internal varies by firm; external TBD Security Best Practices for non-relational data stores TBD
Common Core K-12 Student Reporting General Description of the Industry / Use Case: Cradle-to-grave student performance metrics for every student are now possible – at least within the community and probably beyond. This could include every test result ever administered. Mapping to the Security Reference Architecture: RA Component Security & Privacy Topic Use Case Mapping Sources → Transformation End-Point Input Validation Application-dependent. Spoofing is possible. Real Time Security Monitoring Vendor-specific monitoring of tests, test-takers, administrators & data. Data Discovery and Classification unknown Secure Data Aggregation Typical: Classroom level Transformation → Uses Privacy-preserving Data Analytics Various: e.g., teacher level analytics across all same-grade classrooms. Compliance with Regulations Parent-, student-, taxpayer disclosure & privacy rules apply Govt access to data and freedom of expression concerns Yes. May be required for grants, funding, performance metrics for teachers, administrators, districts. Transformation ↔ Data Infrastructure Data Centric Security such as identity/policy-based encryption Support both individual access (student) & partitioned aggregate Policy management for access control Vendor (e.g., Pearson) controls, state level policies, federal level policies; probably 20-50 roles? Computing on the encrypted data: searching/filtering/deduplicate/fully homomorphic encryption unknown Audits Support 3rd party audits by unions, state agencies, resp to subpoenas Data Infrastructure Securing Data Storage and Transaction logs Large enterprise security, trx controls – classroom to Feds Key Management CSO’s from classroom level to national Security Best Practices for non-relational data stores unknown Security against DoS attacks standard Data Provenance Traceability to measurement event requires capturing tests @ point in