Threat DF.W.PDFIDADFI.0

URI: DF.W.PDFIDADFI.0

Package: DataLifecycle

< prev | next >

Description: 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.

Threat Type: Secondary Threat

Matching Pattern:

DF.W.PDFIDADFI.0
MP-PDFIDADFI

Finds a Process that receives a flow of Data from a data store or source that it does not get from local storage, and forwards it towards a data consumer. The Process is matched twice, so it can be referred to by either role name.

DF.W.PDFIDADFI.0
DF.IS.PDFFA.8

Flow of Data from FlowsFrom to FlowsTo is in service: if process FlowsFrom is in service and able to access the data, and all the steps in the chain of processes between FlowsFrom and FlowsTo are in service, then the flow of Data from FlowsFrom to FlowsTo will be in service and potentially subject to attack, unless disabled.
DF.W.PDFIDADFI.0
P.IS.HP.8

Process Process in service: if host Host is in service, then Process running on Host will also be in service and subject to attack, unless explicitly disabled.
DF.W.PDFIDADFI.0
P.IS.HPsAC.1

Process Process running on Host not disabled: if an attacker has the rights of Process on its host Host, then they can override a policy to disable Process by restarting it.
DF.W.PDFIDADFI.0
P.IS.HP.2

Process Process re-enabled on stolen device Host: if an attacker gains access to stolen device Host, they can restart Process, overriding the policy to disable Process.
DF.W.PDFIDADFI.0
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
DF.W.HPDADF.7

Malware insertion in flow of Data to FlowsTo by Process to : if process Process is infected by self-propagating malware, it may insert the malware into the copy of Data sent to process FlowsTo.
DF.W.PDFIDADFI.0
DF.W.HPDSDADF.0

Service Process serves an infected stored copy of data Data to FlowsTo: if the locally stored copy of Data on Host served by Process is infected by malware, so will the flow of Data served to FlowsTo.

        (empty)

        (empty)

CSG-AutoSuspendCorruptDataFlow

The flow of data Data from FlowsFrom to FlowsTo can be automatically disabled to prevent corrupt or malicious content (including malware) from disrupting the receipient FlowsTo. This strategy represents a contingency plan, which can be used to reduce risk from some threats but it also triggers other threats representing possible side effects, depending on how likely it is that the contingency plan will need to be activated.

CSG-AutoSuspendCorruptDataFlow-Implementation-Runtime

The flow of data Data from FlowsFrom to FlowsTo has been automatically disabled to prevent corrupt or malicious content (including malware) from disrupting the receipient FlowsTo. This strategy represents activation of a contingency plan at runtime, and can be enabled to discover what effect this would have on risk levels, allowing this to be used for decision support calculations. Activation at runtime requires FlowsTo to be managed by a suitable adaptation framework. The Disabled Data Flow control should be deselected if and when the flow of data is enabled once again.

CSG-SuspendCorruptDataFlow

The flow of data Data from FlowsFrom to FlowsTo can be temporarily blocked by the manager ProcessManager of recipient process FlowsTo to prevent corrupt or malicious content (including malware) from disrupting the process. This strategy represents a contingency plan, which can be used to reduce risk from some threats but it also triggers other threats representing possible side effects, depending on how likely it is that the contingency plan will need to be activated.

CSG-SuspendCorruptDataFlow-Implementation-Runtime

The flow of data Data from FlowsFrom to FlowsTo has been disabled by the manager ProcessManager of FlowsTo to prevent corrupt or malicious content (including malware) disrupting the process. This strategy represents activation of a contingency plan at runtime, and can be selected to discover what effect this would have on risk levels, allowing this to be used for decision support calculations. To activate it at runtime, signal user ProcessManager who is responsible for managing process FlowsTo. The Disabled Data Flow control should be deselected only when the flow of data is enabled again.