NBDRA Table 1 represents a preliminary mapping of the operational taxonomy to the NBDRA components. The topics and activities listed for each operational taxonomy element (Section 4.2) have been allocated to a NBDRA component under the Activities column in Table 1. The description column provides additional information about the security and privacy aspects of each NBDRA component. Table Draft Security Operational Taxonomy Mapping to the NBDRA Components Activities Description System Orchestrator Several security functions have been mapped to the Policy Enforcement System Orchestrator block, as they require Security Metadata Model architectural level decisions and awareness. Aspects of Data Loss Prevention, Detection these functionalities are strongly related to the Security Data Lifecycle Management Fabric and thus touch the entire architecture at various Threat and Vulnerability Management points in different forms of operational details. Mitigation Such security functions include nation-specific Configuration Management compliance requirements, vastly expanded demand for Monitoring, Alerting forensics, and domain-specific, privacy-aware business Malware Surveillance and Remediation risk models. Resiliency, Redundancy and Recovery Accountability Compliance Forensics Business Risk Model Data Provider Data Providers are subject to guaranteeing authenticity Device, User, Asset, Services, Applications of data and in turn require that sensitive, copyrighted, Registration or valuable data be adequately protected. This leads to Application Layer Identity operational aspects of entity registration and identity End User Layer Identity Management ecosystems. End Point Input Validation Digital Rights Management Monitoring, Alerting Data Consumer Data Consumers exhibit a duality with Data Providers Application Layer Identity in terms of obligations and requirements only they End User Layer Identity Management – face the access/visualization aspects of the Application Web Services Gateway Provider. Digital Rights Management Monitoring, Alerting Application Provider Application Provider interfaces between the Data Application Layer Identity Provider and Data Consumer. It takes part in all the Web Services Gateway secure interface protocols with these blocks as well as Data Transformation maintains secure interaction with the Framework Digital Rights Management Provider. Monitoring, Alerting Framework Provider Framework Provider is responsible for the security of Virtualization Layer Identity data/computations for a significant portion of the Identity Provider
NBDRA Table 1 represents a preliminary mapping of the operational taxonomy to the NBDRA components. The topics and activities listed for each operational taxonomy element (Section 4.2) have been allocated to a NBDRA component under the Activities column in Table 1. The description column provides additional information about the security and privacy aspects of each NBDRA component. Table Draft Security Operational Taxonomy Mapping to the NBDRA Components Activities Description System Orchestrator Policy Enforcement Security Metadata Model Data Loss Prevention, Detection Data Lifecycle Management Threat and Vulnerability Management Mitigation Configuration Management Monitoring, Alerting Malware Surveillance and Remediation Resiliency, Redundancy and Recovery Accountability Compliance Forensics Business Risk Model Several security functions have been mapped to the System Orchestrator block, as they require architectural level decisions and awareness. Aspects of these functionalities are strongly related to the Security Fabric and thus touch the entire architecture at various points in different forms of operational details. Such security functions include nation-specific compliance requirements, vastly expanded demand for forensics, and domain-specific, privacy-aware business risk models. Data Provider Device, User, Asset, Services, Applications Registration Application Layer Identity End User Layer Identity Management End Point Input Validation Digital Rights Management Monitoring, Alerting Data Providers are subject to guaranteeing authenticity of data and in turn require that sensitive, copyrighted, or valuable data be adequately protected. This leads to operational aspects of entity registration and identity ecosystems. Data Consumer Application Layer Identity End User Layer Identity Management Web Services Gateway Digital Rights Management Monitoring, Alerting Data Consumers exhibit a duality with Data Providers in terms of obligations and requirements – only they face 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 Framework Provider is responsible for the security of data/computations for a significant portion of the