No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - Security

AR500, AR510, and AR530 V200R007

This document describes the configurations of Security, including AAA, DAA,NAC, BRAS Access, ACL, Firewall, Deep Security Defense, Local Attack Defense;Attack Defense, Traffic Suppression, ARP Security, Port Security, DHCP Snooping, IPSG, URPF, PKI, SSL, HTTPS, Keychain, separating the management plane from the service plane, security risks.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuration Task Summary

Configuration Task Summary

After the PKI configurations are complete, the device can obtain the digital certificates for identity verification, data encryption, and data signing.

Table 15-2 lists the PKI configuration tasks. The device obtains certificates in one of the following ways. The certificates include CA certificates and device certificate. The device uses the device certificate to show its own identity, and uses the CA certificates to verify the validity of the device certificate.

Table 15-2  Configuration task summary




Applying for certificates

An entity submits the identity information to the CA server and obtains the certificates. In this process, the entity submits the identity information and public key to the CA server. The CA server adds the identity information and public key into the certificate issued to the entity. Depending on whether there is a reachable route between the device and CA server, two ways to apply for certificates are available:

  • Online: When a reachable route exists between the device and CA server, the device communicates with the CA server through SCEP to obtain certificates.

  • Offline: When no reachable route exists between the device and CA server, the user needs to manually generate a certificate request file on the device, and sends the file to the CA server through disk or email.

  1. Configuring a PKI Entity

  2. Configuring a PKI Domain

  3. Configuring Certificate Registration and Obtaining

  4. Configuring Certificate Authentication

Importing certificates

The user imports the obtained certificates to the device memory. This mode is applicable when the user has bought certificates from the IAOPC or has obtained certificates from the CA server.

Importing a Certificate

Self-signed certificate

A self-signed certificate is issued by the device. That is, the certificate requester and issuer are the same. This mode is applicable when the user requires a temporary certificate or has low requirement on data security.

Creating a Self-signed Certificate or Local Certificate

To ensure that the encrypted data can be decrypted by the two parties, import the certificates to both the two parties. You can upload the certificates of the remote device to the storage device on the local device through FTP or TFTP, and then import the certificates to memory. Alternatively, you can open the certificate files, and copy the certificate contents on the screen to import the certificates to memory. For details about importing the certificates of the remote device, see Configuring the Device to Import or Release a Digital Certificate of the Remote Device.

Updated: 2019-05-25

Document ID: EDOC1000097287

Views: 14687

Downloads: 40

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next