TU Testing Updates Failures and Controls 13 shows the set of security controls that are recommended to address each communication-based failure mode identified in Section . The first three columns correspond to the ID, textual description, and examples of each communication-based failure mode from Table 7. The last two columns correspond to the ID and name of security controls from Table 11. Each failure mode is mapped to one or more security controls; the combination of controls is recommended to mitigate the failure mode (i.e., it does not identify a set of options). Table Communication-Based Failure Modes and Controls – Failure Failure Mode Example Control Control Name Mode ID ID FC1 Message to or from DDoS, Spurious message QSE Quality of Service Enforcement [Role] is blocked, generation, Authorized QSS Quality of Service Specification dropped, or delayed network device consuming because the network is network resources TCF Traffic Control and Filtering saturated ENS Emergency Network Segmentation EI Endpoint Isolation Network underprovisioned; NM Network Monitoring network over-allocated (e.g., addition of devices/functionality over time) FC2 Message to or from Insufficient ESP Protection [Role] is blocked, ratio, electromagnetic dropped, or delayed interference because of interference on the network medium FC3 Message to or from Incorrect firmware update, CSM Concurrent Session Management [Role] is blocked, DNS not available RIS Remote Interactive Sessions dropped, or delayed SD Session Duration because a device or service in the network ULA Unsuccessful Login Attempts infrastructure is not NOC Network Operations Continuity available or functional BPR Backup Requirement FC4 Message to or from SIn Incorrect Systems configuration. Inventory [Role] is inappropriately Traffic is getting to a router or CuC Current Configuration
TU Testing Updates Failures and Controls 13 shows the set of security controls that are recommended to address each communication-based failure mode identified in Section . The first three columns correspond to the ID, textual description, and examples of each communication-based failure mode from Table 7. The last two columns correspond to the ID and name of security controls from Table 11. Each failure mode is mapped to one or more security controls; the combination of controls is recommended to mitigate the failure mode (i.e., it does not identify a set of options). Table – Communication-Based Failure Modes and Controls Failure Mode ID Failure Mode Example Control ID Control Name FC1 Message to or from [Role] is blocked, dropped, or delayed because the network is saturated DDoS, Spurious message generation, Authorized network device consuming network resources QSE Quality of Service Enforcement QSS Quality of Service Specification TCF Traffic Control and Filtering ENS Emergency Network Segmentation EI Endpoint Isolation Network underprovisioned; network over-allocated (e.g., addition of devices/functionality over time) NM Network Monitoring FC2 Message to or from [Role] is blocked, dropped, or delayed because of interference on the network medium Insufficient ratio, electromagnetic interference ESP Protection FC3 Message to or from [Role] is blocked, dropped, or delayed because a device or service in the network infrastructure is not available or functional Incorrect firmware update, DNS not available CSM Concurrent Session Management RIS Remote Interactive Sessions SD Session Duration ULA Unsuccessful Login Attempts NOC Network Operations Continuity BPR Backup Requirement FC4 Message to or from [Role] is inappropriately Incorrect configuration. Traffic is getting to a router or SIn Systems Inventory CuC Current Configuration
SA%20Security%20Profile%20-%20v0_15%20-%2020120930.docx