NIST.SP.800-161

Recommendations

Info

Special Publication 800-161 Supply Chain Risk Management Practices for Federal Information Systems and Organizations ________________________________________________________________________________________________________ Threat Agent Scenario Examples Services Appendix D Scenario 3) or modifying existing functionality) to be used when the system is operational to gather information or subvert 14 system or mission operations. Terrorists Unauthorized access Terrorists seek to penetrate or disrupt the ICT supply chain and may implant unwanted functionality to obtain information or cause physical disablement and destruction through ICT. Industrial Espionage/Cyber Criminals Industrial Espionage/Intellectual Property Loss (see Appendix D Scenario 2) Industrial spies/cyber criminals seek ways to penetrate ICT supply chain to gather information or subvert system or mission operations (e.g., exploitation of an HVAC contractor to steal credit card information). Agencies can identify and refine ICT SCRM-specific threats in all three tiers. Table 2-3 provides examples of threat considerations and different methods that can be used to characterize ICT supply chain threats at different tiers. Table 2-3: Supply Chain Threat Considerations Tier Threat Consideration Methods Tier 1 Organization’s business and mission Strategic supplier relationships Geographical considerations related to the extent of the organization’s ICT supply chain Establish common starting points for identifying ICT supply chain threat. Establish procedures for countering organization-wide threats such as insertion of counterfeits into critical systems and components. Tier 2 Mission functions Geographic locations Types of suppliers (COTS, external service providers, or custom, etc.) Technologies used organization-wide Identify additional sources of threat information specific to organizational mission functions. Identify potential threat sources based on the locations and suppliers identified through examining available agency ICT supply chain information (e.g., from supply chain map.) Scope identified threat sources to the specific mission functions, using the agency the ICT supply chain information. Establish mission-specific preparatory procedures for countering threat 14 Examples of subverting operations include gaining unauthorized control to ICT supply chain or flooding it with unauthorized service requests to reduce or deny legitimate access to ICT supply chain. CHAPTER 2 PAGE 28
Special Publication 800-161 Supply Chain Risk Management Practices for Federal Information Systems and Organizations ________________________________________________________________________________________________________ Tier Threat Consideration Methods adversaries/natural disasters. Tier 3 SDLC Base the level of detail with which threats should be considered on the SDLC phase. Identify and refine threat sources based on the potential for threat insertion within individual SDLC processes. Vulnerabilities A vulnerability is a weakness in an information system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat source [FIPS 200], [NIST SP 800-34 Rev. 1], [NIST SP 800-53 Rev 4], [NIST SP 800-53A Rev. 4], [NIST SP 800-115]. Within the ICT SCRM context, it is any weakness in the system/component design, development, manufacturing, production, shipping and receiving, delivery, operation, and component end-of life that can be exploited by a threat agent. This definition applies to both the systems/components being developed and integrated (i.e., within the SDLC) and to the ICT supply chain infrastructure, including any security mitigations and techniques, such as identity management or access control systems. ICT supply chain vulnerabilities may be found in: The systems/components within the SDLC (i.e., being developed and integrated); The development and operational environment directly impacting the SDLC; and The logistics/delivery environment that transports ICT systems and components (logically or physically). Organizations should identify approaches used to characterize ICT supply chain vulnerabilities, consistent with the characterization of threat sources and events and with the overall approach used by the organization for characterizing vulnerabilities. Appendix C provides examples of ICT supply chain threat events, based on [NIST SP 800-30 Rev. 1, Appendix B]. All three organizational tiers should contribute to determining the organization’s approaches to characterize vulnerabilities, with progressively more detail identified and documented in the lower tiers. Table 2-4 provides examples of considerations and different methods that could be used to characterize ICT supply chain vulnerabilities at different tiers. Table 2-4: Supply Chain Vulnerability Considerations Tier Vulnerability Consideration Methods Tier 1 Organization’s mission/business Supplier relationships (e.g., system integrators, COTS, external services) Geographical considerations related to the extent of the organization’s ICT supply chain Enterprise/Security Architecture Criticality Baseline Examine agency ICT supply chain information including that from supply chain maps to identify especially vulnerable locations or organizations. Analyze agency mission for susceptibility to potential supply chain vulnerabilities. Examine system integrator and supplier relationships for susceptibility to potential CHAPTER 2 PAGE 29
Page 1 and 2: NIST Special Publication 800-161 Su
Page 3 and 4: Special Publication 800-161 Supply
Page 31 and 32: System Mission/Business Process Ent
Page 35: Special Publication 800-161 Supply
Page 87 and 88:
Special Publication 800-161 Supply
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Market participants (System Integra
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
show all

NIST.SP.800-161

Create successful ePaper yourself

Delete template?

Save as template?