Control X509

URI: X509

Package: Network

< prev | next >

Description: The host or process has an asymmetric key pair, and the association with the public key is attested by a suitably trusted means, often but not necessarily via an X509 certification authority.

Host	A device that can store, process, transmit or receive data.
Process	Represents a process (usually implemented by software running on a Host) that can read, update or create data, or exchange data with other processes.

CSG-NetworkAuthN-X509	To prevent network spoofing, a gateway *Gateway* providing the network can use an X509 (or otherwise trusted) key pair, verified by the supplicant device *Host*.
CSG-NetworkAuthN-X509-Optional	To prevent network spoofing, a gateway *Gateway* providing the network can use an X509 (or otherwise trusted) key pair, verified by the supplicant device *Host*.
CSG-NetworkEAP-TLS	Control access to subnet *LogicalSubnet* using authentication via X509 or otherwise trusted public-private key pairs. The gateway device *Gateway* providing the network has an (X509 certified) key, and a means to verify (X509 certified) keys registered by authorised supplicants. You should also specify that supplicant devices have (X509 certified) key pairs or they will be unable to connect.
CSG-NetworkEAP-TLS-Client	If subnet *LogicalSubnet* uses a EAP.TLS to control access, supplicant device *Host* can connect if it has an X509 certified (or similarly trusted) asymmetric key pair.
CSG-ServiceAuthN-X509	The client *Client* authenticates the service *Service* using an asymmetric cryptographic challenge against a public key registered to the service operator through a trusted means such as X509.
CSG-X509CertificationOfClient	Access to a service requires authentication using an asymmetric cryptographic challenge during a TLS connection establishment by *Client*, based on an X509 or other trusted public key belonging to the authorised user.
CSG-X509CertificationOfHost	Access to a service requires authentication using an asymmetric cryptographic challenge during a TLS connection establishment by *Client, based on an X509 or other trusted public key belonging to the authorised user. Here the client Client* is acting as a proxy for its host device, so the key is actually installed on *CHost*.