Key management Managed by project chief security officer (CSO). Separate key pairs issued for customers and internal users. Security best practices for Regular data integrity checks via XML schema data stores validation Security against DoS attacks Industry-standard webhost protection provided for query subsystem. Data provenance Unique Fabric Analytics for security intelligence No project-specific initiatives Event detection N/A Forensics Usage, cube-creation, and device merge audit records were retained for forensics and billing Web Traffic Analytics Visit-level webserver logs are of high granularity and voluminous. Web logs are correlated with other sources, including page content (buttons, text, and navigation events) and marketing events such as campaigns and media classification. Table E-3: Mapping Web Traffic Analytics to the Reference Architecture NBDRA Security and Privacy Topic Use Case Mapping Component and Interfaces Data Provider End-point input validation Device-dependent. Spoofing is often easy → Application Real-time security monitoring Web server monitoring Provider Data discovery and classification Some geospatial attribution Secure data aggregation Aggregation to device, visitor, button, web event, and others Application Privacy-preserving data analytics IP anonymizing and time stamp degrading. Provider Data Content-specific opt-out → Consumer Compliance with regulations Anonymization may be required for EU compliance. Opt-out honoring Government access to data and Yes freedom of expression concerns Data Provider Data-centric security such as Varies depending on archivist ↔ Framework identity/policy-based encryption Provider Policy management for access System- and application-level access controls control Computing on the encrypted data: Unknown searching/filtering/deduplicate/ FHE Audits Customer audits for accuracy and integrity are supported Framework Securing data storage and Storage archiving—this is a big issue Provider transaction logs Key management CSO and applications
Key management Managed by project chief security officer (CSO). Separate key pairs issued for customers and internal users. Security best practices for data stores Regular data integrity checks via XML schema validation Security against DoS attacks Industry-standard webhost protection provided for query subsystem. Data provenance Unique Fabric Analytics for security intelligence No project-specific initiatives Event detection N/A Forensics Usage, cube-creation, and device merge audit records were retained for forensics and billing Web Traffic Analytics Visit-level webserver logs are of high granularity and voluminous. Web logs are correlated with other sources, including page content (buttons, text, and navigation events) and marketing events such as campaigns and media classification. Table E-3: Mapping Web Traffic Analytics to the Reference Architecture NBDRA Component and Interfaces Security and Privacy Topic Use Case Mapping Data Provider → Application Provider End-point input validation Device-dependent. Spoofing is often easy Real-time security monitoring Web server monitoring Data discovery and classification Some geospatial attribution Secure data aggregation Aggregation to device, visitor, button, web event, and others Application Provider → Data Consumer Privacy-preserving data analytics IP anonymizing and time stamp degrading. Content-specific opt-out Compliance with regulations Anonymization may be required for EU compliance. Opt-out honoring Government access to data and freedom of expression concerns Yes Data Provider ↔ Framework Provider Data-centric security such as identity/policy-based encryption Varies depending on archivist Policy management for access control System- and application-level access controls Computing on the encrypted data: searching/filtering/deduplicate/ FHE Unknown Audits Customer audits for accuracy and integrity are supported Framework Provider Securing data storage and transaction logs Storage archiving—this is a big issue Key management CSO and applications