Threat CC.AX.CCCmSCS.0

URI: CC.AX.CCCmSCS.0

Package: ProcessComms

< prev | next >

Description: Communication failure between Client and Service: if there are no available network paths between client Client and service Service, Client will be unable to connect to Service.

Threat Type: Secondary Threat

Matching Pattern:

CC.AX.CCCmSCS.0
MP-CCCmSCS

Finds a Client and Service with a Client Channel between them and all associated Service Channels (of which there must be at least one), plus the client and service hosts and optionally the service manager and interactive client user.

CC.AX.CCCmSCS.0
SC.A.CCCmSCS.0

Client Client cannot access unavailable service Service: loss of availability in the service Service makes the connection from Client unavailable on all channels.
CC.AX.CCCmSCS.0
SC.A.CCfImSC.0

Connection from CHost to LogicalSubnet affects communication between Client and Service: if the connection of device CHost running Client and subnet LogicalSubnet is not available, this will affect the communication channel between client Client and service Service.
CC.AX.CCCmSCS.0
SC.A.CCtImSC.0

Connection from SHost to LogicalSubnet affects communication between Client and Service: if the connection of device SHost running Service and subnet LogicalSubnet is not available, this will affect the ccommunication hannel between client Client and service Service.
CC.AX.CCCmSCS.0
SC.A.HuSC.6.3

Suspended insecure path from Client to Service affects availability: firewall rules allowing access by Client to service Service via a network path may be suspended where communication on that path is exposed to snooping. However, this means the availability of Client-Service connections using this network path will be reduced if its communication security is under threat.
CC.AX.CCCmSCS.0
SC.A.LSmSC.0

Unavailable subnet LogicalSubnet affects client-service communication: if subnet LogicalSubnet is not available, it will interrupt client-service communications via that subnet.
CC.AX.CCCmSCS.0
SC.A.SC.6.1

Disabled channel from Client to Service is not available: if the firewall rules allowing access by client Client to service Service have been disabled, then Client will not be able to access Service via that channel.
CC.AX.CCCmSCS.0
SC.A.SgmSC.0

Unavailable route at gateway Gateway affects client-service communication: if the route via Gateway from FromSubnet to ToSubnet is not available, it will interrupt client-service communications that depends on this route.
CC.AX.CCCmSCS.0
SC.A.VC2HmSC.0

Loss of physical connectivity between LocalHost and RemoteHost affects client-service communications: if there is a loss of availability in physical network paths between LocalHost and RemoteHost supporting communications in subnet VirtualSubnet, then client-service communication via that virtual subnet will become unavailable.
CC.AX.CCCmSCS.0
SC.A.HuCAPmSC.6.2

Suspended channels from Client to vulnerable service Service via LogicalSubnet are not available: the firewall rules allowing access by client Client to service Service may be disabled if the risk of an expoit by an attacker on subnet LogicalSubnet is too high. . However, this cuts privileged network paths, so communication between Client and Service via that subnet will become unavailable.
CC.AX.CCCmSCS.0
SC.A.HuSAPmSC.6.2

Suspended channels to vulnerable service Service via LogicalSubnet cuts availability: the firewall rules allowing access to service Service via LogicalSubnet may be suspended if necessary to prevent attacks. However, this cuts privileged network paths, so communication with Service via that subnet will become unavailable.

CC.AX.CCCmSCS.0
CC.AX.CACSSaS.0

Client Client unable to access service Process because Process cannot access authorization service Service: the service Process requires that clients authenticate with a separate service Service, but Process cannot access Service to exchange the client token issued by Service for an access token granting rights at Process.
CC.AX.CCCmSCS.0
CC.AX.CACSScS.0

Client Client unable to authenticate with Service to access service Process: the service Process requires that clients authenticate with a separate service Service, which is inaccessible to client Client.
CC.AX.CCCmSCS.0
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.
CC.AX.CCCmSCS.0
DF.A.CC-iDFSC.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.
CC.AX.CCCmSCS.0
I.A.HLSISC.6.4

Authentication failure for device CHost at Service prevents connection to LogicalSubnet: the device CHost cannot connect to LogicalSubnet because it cannot authenticate with the authenticator service Service controlling access to the network.
CC.AX.CCCmSCS.0
P.A.HuirRACSPH.0

Loss of connectivity from Client to Service affects Process: because user Human interacts with Process via remote access client Client and the shell on SHost, if Client cannot connect to remote access service Service on SHost, Human will be unable to interact with Process which will be rendered non-operational.

        (empty)

        (empty)