Threat CC.AX.CCC-nmCCS.6.1.5

URI: CC.AX.CCC-nmCCS.6.1.5

Package: ProcessComms

< prev | next >

Description: Client Client unable to authenticate via a trusted key pair with Service: the service Service requires that client connections are authenticated using an asymmetric cryptographic challenge against an X509 (or otherwise trusted) key pair, but here access is via a reverse proxy so there is no direct TLS connection.

Threat Type: Primary Threat

Matching Pattern:

MP-CCC-nmCCS

Finds a Client not acting as an authentication proxy with access via at least one proxy to a Service which is not using a separate authenticator, with a Client Channel between them and all associated proxy client channels (of which there must be at least one), plus the client and service hosts and optionally the Client user and Service manager.

Triggers Secondary Threats (6)

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

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

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.

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.