Threat DF.IS.PDFFA.8

(empty)

DF.Auth.HDCDF.0

Cached flow of data Data from FlowsFrom to FlowsTo altered on Host: if the flow of Data from FlowsFrom to FlowsTo is cached on Host, and an attacker is able to tamper with the cache, the data flow will be affected. This is a secondary threat whereby changes to the cache propagate to the data flow - the attack will be what caused the cache to lose authenticity.

DF.Auth.PDFIDADFI.0

Unauthentic data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is unauthentic, so is the forwarded flow to FlowsTo.

DF.Auth.PDFODADFO.0

Unauthentic data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is unauthentic, so is the forwarded flow to FlowsTo.

DF.I.HDCDF.0

Cached flow of data Data from FlowsFrom to FlowsTo corrupted on Host: if the flow of Data from FlowsFrom to FlowsTo is cached on Host, and the cache is corrupt, the data flow will be affected. This is a secondary threat whereby changes to the cache propagate to the data flow - the cause is whatever caused the cache to lose integrity.

DF.I.PDFIDADFI.0

Corrupt data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is corrupt, so is the forwarded flow to FlowsTo.

DF.I.PDFODADFO.0

Corrupt data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is corrupt, so is the forwarded flow to FlowsTo.

DF.W.HDCDF.0

Cached flow of data Data from FlowsFrom to FlowsTo infected on Host: if the flow of Data from FlowsFrom to FlowsTo is cached on Host, and the cache gets infected by malware, the data flow will be affected. This is a secondary threat whereby changes to the cache propagate to the data flow - the cause is whatever infected the cache.

DF.W.PDFIDADFI.0

Infected data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is infected by malware, so is the forwarded flow to FlowsTo.

DF.W.PDFODADFO.0

Infected data Data from FlowsFrom forwarded by Process to FlowsTo: if the flow of data Data from process FlowsFrom to process Process is infected by malware, so is the forwarded flow to FlowsTo.

DS.Auth.HPDFDADS.0

Flow of unauthentic data Data from FlowsFrom is stored by data service Process: if the flow of data Data from FlowsFrom to Process is unauthentic, then so will be the copy saved locally on device Host by Process.

DS.I.HPDFDADS.0

Flow of corrupt data Data from FlowsFrom is stored by data service Process: if the flow of data Data from FlowsFrom to Process is corrupt, then so will be the copy saved locally on device Host by Process.

DS.W.HPDFDADS.0

Flow of infected data Data from FlowsFrom is stored by data service Process: if the flow of data Data from FlowsFrom to Process is infected by malware, then so will be the copy saved locally on device Host by Process.

Hu.U.HuirPvDF.0

User Human affected by corrupt data Data from FlowsFrom received by Process: if the flow of data Data to Process is corrupt, and this is displayed to user Human, they may make decisions based on the incorrect information.

P.U.P-iDFDI.0

Loss of reliability at process Process due to corrupt input Data from FlowsFrom: process Process uses the copy of Data sent by FlowsFrom as input so if this is corrupt, Process may become unreliable.

DF.O.CCDS2TC.0

Excessive demand for data Data via Client propagates via Service: if the flow of data Data requested by Client from Service is excessive, then Service will forward the request for an excessive amount of data to StepFrom.

(empty)

InService at Role_DataFlow

CSG-DisableDataFlow

The flow of data Data from FlowsFrom to FlowsTo has been disabled. This control strategy represents a permanent restriction introduced by design, or a temporary situation created following activation of a contingency plan. In the latter case, this control strategy should not itself be selected, because its controls will be fulfilled by the contingency plan activation strategy.