Threat Hu.T.HuirPvDF.0.2

URI: Hu.T.HuirPvDF.0.2

Description: User Human affected by unavailable data Data from FlowsFrom received by Process: if the flow of data Data to Process is interrupted, that would have been displayed to user Human, they may make decisions based on the out of date information.

Threat Type: Secondary Threat

Matching Pattern:

MP-HuirPvDF

Finds a (possibly remote) user of an interactive process that views data received by the process in a data flow.

DF.A.PDF.6.2

Loss of availability from suspending the flow of unauthentic data Data from FlowsFrom to Process: if a contingency plan is used in which the flow of Data between FlowsFrom to Process is disabled if the data was subject to malicious tampering, then the flow of data Data from FlowsFrom to Process will become unavailable.

DF.A.HPDF-VDI.6

Process Process cannot consume encrypted data Data from FlowsFrom: the flow of Data from FlowsFrom to Process is encrypted, so it cannot be consumed without a key.

DF.A.HPDODF-V.6.1

Process Process cannot encrypt output Data for transmission to FlowsTo: the flow of output data Data from Process to FlowsTo should be encrypted, but Process has no means to encrypt the data before sending it.

DF.A.HPDODF-V.6.2

Process Process cannot decrypt output Data computed in the encrypted domain: the flow of output data Data from Process to FlowsTo should be decrypted, but process Process computed it in an encrypted domain (using a secure computation method such as homomorphic encryption) and has no means to decrypt the result before sending it.

DF.A.HPDSDADF.0

Service Process cannot serve unavailable data Data to FlowsTo: the locally stored copy of Data on Host used by Process is not available, so cannot be sent in a data flow to FlowsTo.

DF.A.HPDSDADF-V.6

Service Process cannot send unencrypted data Data to FlowsTo: because the stored copy of Data on Host is not encrypted, and FlowsTo expects an encrypted version, it is not possible for Process to send it without a key.

DF.A.HPDS-VDADF.6

Service Process cannot decrypt data Data for transmission to FlowsTo: the stored copy of Data on Host is encrypted, but FlowsTo expects an unencrypted version, and Process has no means to decrypt the data before sending it.

DF.A.PDF.6.1

Loss of availability in the disabled flow of data Data from FlowsFrom to Process: the flow of Data between FlowsFrom to Process has been disabled to maintain security or prevent a breach of regulations, but as a result the data flow is now unavailable.

DF.A.PDF.6.3

Loss of availability from suspending the flow of corrupt data Data from FlowsFrom to Process: if a contingency plan is used in which the flow of Data between FlowsFrom to Process is disabled if the data is corrupt, then the flow of data Data from FlowsFrom to Process will become unavailable.

DF.A.PDF.6.4

Loss of availability from suspending the flow of infected data Data from FlowsFrom to Process: if a contingency plan is used in which the flow of Data between FlowsFrom to Process is disabled if the data becomes infected with malware, then the flow of data Data from FlowsFrom to Process will become unavailable.

DF.A.PmDFIDADFI.0

Data Data cannot be forwarded by Process to FlowsTo because the incoming data flow is not available: if the flow of data Data to Process is unavailable, the flow of the same data from Process to FlowsTo will also be unavailable.

DF.A.PmDFIDADFI-k.6

Unencrypted data Data cannot be forwarded by Process to FlowsTo: if the flow of data Data to Process is not encrypted, it cannot be forwarded to FlowsTo which expects it to be encrypted.

DF.A.PmDFI-kDADFI.6

Encrypted data Data cannot be forwarded by Process to FlowsTo: if the flow of data Data to Process is encrypted, it cannot be forwarded to FlowsTo which expects it to be unencrypted.

DF.A.PmDFODADFO.0

DF.A.PmDFODADFO-k.6

DF.A.PmDFO-kDADFO.6

DF.A.DScSePDmFF.3

Malicious control of Sensor prevents generation of sensed output Data: if an attacker can tamper with the stored control inputs to sensor Sensor, they may be able to prevent measurement of the environment by Sensor.

DF.A.CCDFCS.6.3

Flow of data Data from FlowsFrom to FlowsTo via untrustworthy Service disabled: if the system operates a policy to disable the flow of data Data from FlowsFrom if there is a perceived loss of trustworthiness in a recipient Service, then there will also be a loss of availability if Service is untrustworthy.

DF.A.CCDFSC.6.3

Flow of data Data from FlowsFrom to FlowsTo via untrustworthy process Client disabled: if the system operates a policy to disable the flow of data Data from FlowsFrom if there is a perceived loss of trustworthiness in the recipient Client, then there will also be a loss of availability if Client is untrustworthy.

DF.A.CC-iDFCS.0

Flow of data Data from FlowsFrom to FlowsTo interrupted because Client cannot access Service: if client Client cannot access service Service, the end to end flow of data Data from FlowsFrom to FlowsTo that uses this client-service connection will be interrupted.

DF.A.CC-iDFC-SS.0

Flow of data Data from FlowsFrom to FlowsTo interrupted by unavailable process Client: if process Client is not available then it will be unable to initiate or forward the flow of Data between FlowsFrom to FlowsTo.

DF.A.CC-iDFSC.0

DF.T.HuirPiDF.0

User Human interacting with Process provides out of date input Data: user Human provides out of date input Data to Process, due to having not previously received data in a timely fashion from the system.

DS.T.HuirPiDS.0

User Human interacting with Process provides stale input Data: user Human provides input Data which is stored by Process on Host, so if Human is working on outdated information, the stored copy will also be out of date.

P.T.HuirPiD-DF-DS.0

User Human provides out of date input Data affecting Process: user Human, working on the basis of outdated information, provides out of date input Data, which is consumed (not saved or forwarded) by and affects Process.

(empty)

LossOfTimeliness at Role_Human