Control Strategy DataFlowEncryption

URI: CSG-DataFlowEncryption

Package: DataLifecycle

< prev | next >

Description: The data Data flowing between processes FlowsFrom and FlowsTo is encrypted by the two processes (i.e. not relying on transport level encryption).

        (empty)

CSG-DataFlowEncryption
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.
CSG-DataFlowEncryption
DF.A.PmDFO-kDADFO.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.
CSG-DataFlowEncryption
DF.Y.PDF-V.8

Flow of Data from FlowsFrom to Process is unencrypted: which means the inflowing copy of the data is not available for encrypted access.
CSG-DataFlowEncryption
DF.Auth.CCCSDF-VCCS-i.3

Flow of data from/via Process forged by compromised client Client via confused deputy Service: if client Client does not send data Data to its service Service, it is still possible to inject false content into the data flow via service Service using a confused deputy attack. The attack itself is responsible for the upstream loss of DeputyUserTW (see threat causes).
CSG-DataFlowEncryption
DF.Auth.CCCSPDF-VCCS-i.3

Flow of data from/via Process forged by compromised client Client via confused deputy Proxy: if client Client is compromised or impersonated, and does not send data Data via its service Proxy, it is still possible to get the data indirectly using a confused deputy attack via Proxy and Service. The attack itself is responsible for the upstream loss of DeputyUserTW (see threat causes), in this case propagated by at least one reverse proxy.
CSG-DataFlowEncryption
DF.C.ACDF-VCS-i.3.1

Compromised service Service reads the flow of data Data from FlowsFrom to FlowsTo sent from Client: if an attacker can compromise or impersonate service Service, they can read data in messages from Client.
CSG-DataFlowEncryption
DF.C.ACDF-VSC-i.3.2

Flow of data Data from FlowsFrom to FlowsTo leaked to false client of compromised service Service: if service Service is compromised by an attacker, they can allow a false client to request data by acting as Client.
CSG-DataFlowEncryption
DF.C.AC-iDF-VCS.3.2

Imposter posing as service Service intercepts flow of Data from FlowsFrom and FlowsTo sent by Client: if an attacker can impersonate service Service, they can intercept content in the flow of data Data between FlowsFrom and FlowsTo via the service and its client Client.
CSG-DataFlowEncryption
DF.C.AC-iDF-VCS.3.3

Snooped flow of data Data from FlowsFrom to FlowsTo between Client and Service: if communications between Client and Service are subject to snooping, the snooper could read data Data flowing from FlowsFrom to FlowsTo.
CSG-DataFlowEncryption
DF.C.AC-iDF-VSC.3.2

Compromised or impersonated client Client reads data Data flowing from FlowsFrom to FlowsTo when sent from Service: if an attacker can compromise or impersonate Client, they can read Data sent by FlowsFrom to FlowsTo in messages from Service.
CSG-DataFlowEncryption
DF.C.AC-iDF-VSC.3.3

Snooped flow of data Data from FlowsFrom to FlowsTo between Service and Client: if communications between Service and Client are subject to snooping, the snooper could read data Data flowing from FlowsFrom to FlowsTo.
CSG-DataFlowEncryption
DF.C.CCCSCCSDF-Vi.3

Flow of data from/via Process leaked to compromised client Client via confused deputy Service: if service Service does not send data Data to its client Client , it is still possible for the client to request the data flow using a confused deputy attack against Service. The attack itself is responsible for the upstream loss of DeputyUserTW (see threat causes).
CSG-DataFlowEncryption
DF.C.CCCSPCCSDF-Vi.3

Flow of data from/via Process leaked to compromised client Client via confused deputy Proxy: if client Client is compromised or impersonated, and does not receive data Data from its service Proxy, it is still possible to get the data indirectly using a confused deputy attack via Proxy and Service. The attack itself is responsible for the upstream loss of DeputyUserTW (see threat causes), in this case propagated by at least one reverse proxy.