Security Certifications Compliance. Cisco FXOS Firepower Chassis Manager
Werbung
Werbung
C H A P T E R
6
Security Certifications Compliance
•
Security Certifications Compliance, page 39
•
•
Enable Common Criteria Mode, page 40
•
Generate the SSH Host Key, page 40
•
Configure IPSec Secure Channel, page 41
•
Configure Static CRL for a Trustpoint, page 46
•
About the Certificate Revocation List Check, page 47
•
Set the LDAP Key Ring Certificate, page 51
Security Certifications Compliance
United States federal government agencies are sometimes required to use only equipment and software complying with security standards established by the U.S. Department of Defense and global certification organizations. The FXOS chassis supports compliance with several of these security certification standards.
See the following topics for steps to enable features that support compliance with these standards:
•
•
Enable Common Criteria Mode, on page 40
•
Configure IPSec Secure Channel, on page 41
•
Configure Static CRL for a Trustpoint, on page 46
•
About the Certificate Revocation List Check, on page 47
•
Set the LDAP Key Ring Certificate, on page 51
•
Configure Minimum Password Length Check, on page 28
•
Set the Maximum Number of Login Attempts, on page 27
•
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
39
Security Certifications Compliance
Enable FIPS Mode
Note
Note that these topics discuss enabling certifications compliance on the FXOS chassis only. Enabling certification compliance on the FXOS chassis does not automatically propagate compliance to any of its attached logical devices.
Enable FIPS Mode
Perform these steps to enable FIPS mode on your FXOS chassis.
Procedure
What to Do Next
Prior to FXOS release 2.0.1, the existing SSH host key created during first-time setup of a device was hard coded to 1024 bits. To comply with FIPS and Common Criteria certification requirements, you must destroy this old host key and generate a new one using the procedure detailed in
Generate the SSH Host Key, on page
40 . If you do not perform these additional steps, you will not be able to connect to the Supervisor using SSH after the device has rebooted with FIPS mode enabled. If you performed initial setup using FXOS 2.0.1 or later, you do not have to generate a new host key.
Enable Common Criteria Mode
Perform these steps to enable Common Criteria mode on your FXOS chassis.
Procedure
What to Do Next
Prior to FXOS release 2.0.1, the existing SSH host key created during first-time setup of a device was hard coded to 1024 bits. To comply with FIPS and Common Criteria certification requirements, you must destroy this old host key and generate a new one using the procedure detailed in
page 40
. If you do not perform these additional steps, you will not be able to connect to the Supervisor using
SSH after the device has rebooted with Common Criteria mode enabled. If you performed initial setup using
FXOS 2.0.1 or later, you do not have to generate a new host key.
Generate the SSH Host Key
Prior to FXOS release 2.0.1, the existing SSH host key created during initial setup of a device was hard-coded to 1024 bits. To comply with FIPS and Common Criteria certification, you must destroy this old host key and generate a new one. See
or
Enable Common Criteria Mode, on page 40
for more information.
Perform these steps to destroy the old SSH host key and generate a new certifications-compliant one.
40
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
Configure IPSec Secure Channel
Procedure
Step 1
From the FXOS CLI, enter services mode:
scope system scope services
Step 2
Delete the SSH host key:
delete ssh-server host-key
Step 3
Commit the configuration:
commit-buffer
Step 4
Set the SSH host key size to 2048 bits:
set ssh-server host-key rsa
2048
Step 5
Commit the configuration:
commit-buffer
Step 6
Create a new SSH host key:
create ssh-server host-key commit-buffer
Step 7
Confirm the new host key size:
show ssh-server host-key
Host Key Size: 2048
Configure IPSec Secure Channel
You can configure IPSec on your FXOS chassis to provide end-to-end data encryption and authentication service on data packets going through the public network. This option is one of a number offered for achieving
Common Criteria certification compliance on your system. For more information, see
.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
41
Security Certifications Compliance
Configure IPSec Secure Channel
Note
If you elect to configure enforcement of matching cryptographic key strength between IKE and SA connections (set sa-strength-enforcement to yes in the below procedure):
If SA enforcement is enabled then when IKE negotiated key size is less then ESP negotiated key size, the connection fails.
then when IKE negotiated key size is large or equal than ESP negotiated key size, SA enforcement check passes and the connection is successful.
If SA enforcement is disabled then SA enforcement check passes and the connection is successful.
Perform these steps to configure an IPSec secure channel.
Procedure
Step 1
From the FXOS CLI, enter security mode:
scope system scope security
Step 2
Create the keyring:
enter keyring ssp
! create certreq subject-name subject-name ip ip
Step 3
Enter the associated certificate request information:
enter certreq
Step 4
Set the country:
set country country
Step 5
Set the DNS:
set dns dns
Step 6
Set the email:
set e-mail email
Step 7
Set the IP information:
set fi-a-ip fi-a-ip
set fi-a-ipv6 fi-a-ipv6
set fi-b-ip fi-b-ip
set fi-b-ipv6 fi-b-ipv6
set ipv6 ipv6
Step 8
Set the locality:
set locality locality
42
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
Configure IPSec Secure Channel
Step 9
Set the organization name:
set org-name org-name
Step 10
Set the organization unit name:
set org-unit-name org-unit-name
Step 11
Set the password:
! set password
Step 12
Set the state:
set state state
Step 13
Set the subject name for the certreq:
set subject-name subject-name
Step 14
Exit:
exit
Step 15
Set the modulus:
set modulus modulus
Step 16
Set the regeneration for the certificate request:
set regenerate { yes | no }
Step 17
Set the trustpoint:
set trustpoint interca
Step 18
Exit:
exit
Step 19
Enter the newly created trustpoint:
enter trustpoint interca
Step 20
Genterate certificate signing request:
set certchain
Example:
-----BEGIN CERTIFICATE-----
MIIF3TCCA8WgAwIBAgIBADANBgkqhkiG9w0BAQsFADBwMQswCQYDVQQGEwJVUzEL
MAkGA1UECAwCQ0ExDDAKBgNVBAcMA1NKQzEOMAwGA1UECgwFQ2lzY28xDTALBgNV
BAsMBFNUQlUxCzAJBgNVBAMMAkNBMRowGAYJKoZIhvcNAQkBFgtzc3BAc3NwLm5l dDAeFw0xNjEyMDgxOTMzNTJaFw0yNjEyMDYxOTMzNTJaMHAxCzAJBgNVBAYTAlVT
MQswCQYDVQQIDAJDQTEMMAoGA1UEBwwDU0pDMQ4wDAYDVQQKDAVDaXNjbzENMAsG
A1UECwwEU1RCVTELMAkGA1UEAwwCQ0ExGjAYBgkqhkiG9w0BCQEWC3NzcEBzc3Au bmV0MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA2ukWyMLQuLqTvhq7 zFb3Oz/iyDG/ui6mrLIYn8wE3E39XcXA1/x9IHCmxFKNJdD7EbsggfOuy0Bj+Y4s
+uZ1VapBXV/JrAie7bNn3ZYrI29yuyOrIqoi9k9gL/oRBzH18BwBwGHBOz3hGrSK
Yc2yhsq9y/6yI3nSuLZm6ybmUKjTa+B4YuhDTz4hl/I9x/J5nbGiab3vLDKss1nO xP9+1+Lc690Vl8/mNPWdjCjDI+U/L9keYs/rbZdRSeXy9kMae42+4FlRHDJjPcSN
Yw1g/gcR2F7QUKRygKckJKXDX2QIiGYSctlSHj18O87o5s/pmQAWWRGkKpfDv3oH cMPgI2T9rC0D8NNcgPXj9PFKfexoGNGwNTO85fK3kjgMOdWbdeMG3EihxEEOUPD0
Fdu0HrTM5lvwb+vr5wE9HsAiMJ8UuujmHqH5mlwyy3Me+cEDHo0hLeNs+AFrqEXQ e9S+KZC/dq/9zOLpRsVqSfJsAuVl/QdPDbWShjflE/fP2Wj01PqXywQydzymVvgE wEZaoFg+mlGJm0+q4RDvnpzEviOYNSAGmOkILh5HQ/eYDcxvd0qbORWb31H32ySl
Ila6UTT9+vnND1f838fxvNvr8nyGD2S/LVaxnZlO4jcSIvtdizbbT8u5B4VcLKIC
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
43
Security Certifications Compliance
Configure IPSec Secure Channel
x0vkqjo6RvNZJ52sUaD9C3UodTUCAwEAAaOBgTB/MC8GA1UdHwQoMCYwJKAioCCG
Hmh0dHA6Ly8xOTIuMTY4LjQuMjkvcm9vdGNhLmNybDAdBgNVHQ4EFgQU7Jg01A74 jpx8U0APk76pVfYQQ5AwHwYDVR0jBBgwFoAU7Jg01A74jpx8U0APk76pVfYQQ5Aw
DAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAgEAvI8ky2jiXc4wPiMuxIfY
W7DRmszPUWQ7edor7yxuCqzHLVFFOwYRudsyXbv7INR3rJ/X1cRQj9+KidWWVxpo pFahRhzYxVZ10DHKIzGTQS3jiHgrF3Z8ohWbL15L7PEDlrxMBoJvabPeQRgTmY/n
XZJ7qRYbypO3gUMCaCZ12raJc3/DIpBQ29yweCbUkc9qiHKA0IbnvAxoroHWmBld
94LrJCggfMQTuNJQszJiVVsYJfZ+utlDp2QwfdDv7B0JkwTBjdwRSfotEbc5R18n
BNXYHqxuoNMmqbS3KjCLXcH6xIN8t+UkfP89hvJt/fluJ+s/VJSVZWK4tAWvR7wl
QngCKRJW6FYpzeyNBctiJ07wO+Wt4e3KhIjJDYvA9hFixWcVGDf2r6QW5BYbgGOK
DkHb/gdr/bcdLBKN/PtSJ+prSrpBSaA6rJX8D9UmfhqqN/3f+sS1fM4qWORJc6G2 gAcg7AjEQ/0do512vAI8p8idOg/Wv1O17mavzLpcue05cwMCX9fKxKZZ/+7Pk19Y
ZrXS6uMn/CGnViptn0w+uJ1IRj1oulk+/ZyPtBvFHUkFRnhoWj5SMFyds2IaatyI
47N2ViaZBxhU3GICaH+3O+8rs9Kkz9tBZDSnEJVZA6yxaNCVP1bRUO20G3oRTmSx
8iLBjN+BXggxMmG8ssHisgw=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIFqDCCA5CgAwIBAgIBBDANBgkqhkiG9w0BAQsFADBwMQswCQYDVQQGEwJVUzEL
MAkGA1UECAwCQ0ExDDAKBgNVBAcMA1NKQzEOMAwGA1UECgwFQ2lzY28xDTALBgNV
BAsMBFNUQlUxCzAJBgNVBAMMAkNBMRowGAYJKoZIhvcNAQkBFgtzc3BAc3NwLm5l dDAeFw0xNjEyMTUyMTM0NTRaFw0yNjEyMTMyMTM0NTRaMHwxCzAJBgNVBAYTAlVT
MQswCQYDVQQIDAJDQTEPMA0GA1UECgwGbmV3c3RnMRAwDgYDVQQLDAduZXdzdGJ1
MRMwEQYDVQQDDAppbnRlcm0xLWNhMSgwJgYJKoZIhvcNAQkBFhlpbnRlcm0xLWNh
QGludGVybTEtY2EubmV0MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA wLpNnyEx5I4P8uDoWKWF3IZsegjhLANsodxuAUmhmwKekd0OpZZxHMw1wSO4IBX5
4itJS0xyXFzPmeptG3OXvNqCcsT+4BXl3DoGgPMULccc4NesHeg2z8+q3SPA6uZh iseWNvKfnUjixbQEBtcrWBiSKnZuOz1cpuBn34gtgeFFoCEXN+EZVpPESiancDVh
8pCPlipc/08ZJ3o9GW2j0eHJN84sguIEDL812ROejQvpmfqGUq11stkIIuh+wB+V
VRhUBVG7pV57I6DHeeRp6cDMLXaM3iMTelhdShyo5YUaRJMak/t8kCqhtGXfuLlI
E2AkxKXeeveR9n6cpQd5JiNzCT/t9IQL/T/CCqMICRXLFpLCS9o5S5O2B6QFgcTZ yKR6hsmwe22wpK8QI7/5oWNXlolb96hHJ7RPbG7RXYqmcLiXY/d2j9/RuNoPJawI hLkfhoIdPA28xlnfIB1azCmMmdPcBO6cbUQfCj5hSmk3StVQKgJCjaujz55TGGd1
GjnxDMX9twwz7Ee51895Xmtr24qqaCXJoW/dPhcIIXRdJPMsTJ4yPG0BieuRwd0p i8w/rFwbHzv4C9Fthw1JrRxH1yeHJHrLlZgJ5txSaVUIgrgVCJaf6/jrRRWoRJwt
AzvnzYql2dZPCcEAYgP7JcaQpvdpuDgq++NgBtygiqECAwEAAaNBMD8wDAYDVR0T
BAUwAwEB/zAvBgNVHR8EKDAmMCSgIqAghh5odHRwOi8vMTkyLjE2OC40LjI5L2lu dGVybS5jcmwwDQYJKoZIhvcNAQELBQADggIBAG/XujJh5G5UWo+cwTSitAezWbJA h1dAiXZ/OYWZSxkFRliErKdupLqL0ThjnX/wRFfEXbrBQwm5kWAUUDr97D1Uz+2A
8LC5I8SWKXmyf0jUtsnEQbDZb33oVL7yXJk/A0SF0jihpPheMA+YRazalT9xj9KH
PE7nHCJMbb2ptrHUyvBrKSYrSeEqOpQU2+otnFyV3rS9aelgVjuaWyaWOc3lZ1Oi
CC2tJvY3NnM56j5iesxUCeY/SZ2/ECXN7RRBViLHmA3gFKmWf3xeNiKkxmJCxOaa
UWPC1x2V66I8DG9uUzlWyd79O2dy52aAphAHC6hqlzb6v+gw1Tld7UxaqVd8CD5W
ATjNs+ifkJS1h5ERxHjgcurZXOpR+NWpwF+UDzbMXxx+KAAXCI6ltCd8Pb3wOUC3
PKvwEXaIcCcxGx71eRLpWPZFyEoi4N2NGE9OXRjz0K/KERZgNhsIW3bQMjcw3aX6
OXskEuKgsayctnWyxVqNnqvpuz06kqyubh4+ZgGKZ5LNEXYmGNz3oED1rUN636Tw
SjGAPHgeROzyTFDixCei6aROlGdP/Hwvb0/+uThIe89g8WZ0djTKFUM8uBO3f+II
/cbuyBO1+JrDMq8NkAjxKlJlp1c3WbfCue/qcwtcfUBYZ4i53a56UNF5Ef0rpy/8
B/+07Me/p2y9Luqa
-----END CERTIFICATE-----
ENDOFBUF
Step 21
Show the certificate signing request:
show certreq
Example:
44
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
Configure IPSec Secure Channel
Firepower-chassis# /security/keyring # show certreq
Certificate request subject name: SSP
Certificate request ip address: 192.168.0.111
Certificate request FI A ip address: 0.0.0.0
Certificate request FI B ip address: 0.0.0.0
Certificate request e-mail name:
Certificate request ipv6 address: ::
Certificate request FI A ipv6 address: ::
Certificate request FI B ipv6 address: ::
Certificate request country name: US
State, province or county (full name): CA
Locality name (eg, city): SJC
Organisation name (eg, company): Cisco
Organisational Unit Name (eg, section): Sec
DNS name (subject alternative name):
Request:
-----BEGIN CERTIFICATE REQUEST-----
MIICwTCCAakCAQAwVTELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMQwwCgYDVQQH
DANTSkMxDjAMBgNVBAoMBUNpc2NvMQ0wCwYDVQQLDARTVEJVMQwwCgYDVQQDDANT
U1AwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDq292Rq3t0laoxPbfE p/lTKr6rxFhPqSSbtm6sXer//VZFiDTWODockDItuf4Kja215mIS0RyvEYVeRgAs wbN459wm0BASd8xCjIhsuHDV7yHu539BnvRW6Q2o+gHeSRwckqjClK/tsIxsPkV0
6OduZYXk2bnsLWs6tNk3uzOIT2Q0FcZ1ET66C8fyyKWTrmvcZjDjkMm2nDFsPlX9
39TYPItDkJE3PocqyaCqmT4uobOuvQeLJh/efkBvwhb4BF8vwzRpHWTdjjU5YnR1 qiR4q7j1RmzVFxCDY3IVP/KDBoa5NyCLEUZECP5QCQFDzIRETZwVOKtxUVG0Nljd
K5TxAgMBAAGgJzAlBgkqhkiG9w0BCQ4xGDAWMBQGA1UdEQQNMAuCA1NTUIcEwKgA rjANBgkqhkiG9w0BAQsFAAOCAQEARtRBoInxXkBYNlVeEoFCqKttu3+Hc7UdyoRM
2L2pjx5OHbQICC+8NRVRMYujTnp67BWuUZZl03dGP4/lbN6bC9P3CvkZdKUsJkN0 m1Ye9dgz7MO/KEcosarmoMl9WB8LlweVdt6ycSdJzs9shOxwT6TAZPwL7gq/1ShF
RJh6sq5W9p6E0SjYefK62E7MatRjDjS8DXoxj6gfn9DqK15iVpkK2QqT5rneSGj+
R+20TcUnT0h/S5K/bySEM/3U1gFxQCOzbzPuHkj28kXAVczmTxXEkJBFLVduWNo6
DT3u0xImiPR1sqW1jpMwbhC+ZGDtvgKjKHToagup9+8R9IMcBQ==
-----END CERTIFICATE REQUEST-----
Step 22
Enter IPSec mode:
scope ipsec
Step 23
Set the log verbose level:
set log-level log_level
Step 24
Create and enter an IPSec connection:
enter connection connection_name
Step 25
Set IPSec mode to tunnel or transport:
set mode tunnel_or_transport
Step 26
Set the local IP address:
set local-addr ip_address
Step 27
Set the remote IP address:
set remote-addr ip_address
Step 28
If using tunnel mode, set the remote subnet:
set remote-subnet ip/mask
Step 29
(Optional) Set the remote identity:
set remote-ike-ident remote_identity_name
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
45
Security Certifications Compliance
Configure Static CRL for a Trustpoint
Step 30
Set the keyring name:
set keyring-name name
Step 31
(Optional) Set the keyring password:
set keyring-passwd passphrase
Step 32
(Optional) Set the IKE-SA lifetime in minutes:
set ike-rekey-time minutes
The
minutes
value can be any integer between 60-1440, inclusive.
Step 33
(Optional) Set the Child SA lifetime in minutes (30-480):
set esp-rekey-time minutes
The
minutes
value can be any integer between 30-480, inclusive.
Step 34
(Optional) Set the number of retransmission sequences to perform during initial connect:
set keyringtries retry_number
The
retry_number
value can be any integer between 1-5, inclusive.
Step 35
(Optional) Enable or disable the certificate revocation list check:
set revoke-policy { relaxed | strict }
Step 36
Enable the connection:
set admin-state enable
Step 37
Reload all connections:
reload-conns
Step 38
(Optional) Add the existing trustpoint name to IPsec:
create authority trustpoint_name
Step 39
Configure the enforcement of matching cryptographic key strength between IKE and SA connections:
set sa-strength-enforcement yes_or_no
Configure Static CRL for a Trustpoint
Revoked certifications are kept in the Certification Revocation List (CRL). Client applications use the CRL to check the authentication of a server. Server applications utilize the CRL to grant or deny access requests from client applications which are no longer trusted.
You can configure your FXOS chassis to validate peer certificates using Certification Revocation List (CRL) information. This option is one of a number offered for achieving Common Criteria certification compliance on your system. For more information, see
Security Certifications Compliance, on page 39
.
Perform these steps to validate peer certificates using CRL information.
Procedure
Step 1
From the FXOS CLI, enter security mode:
scope security
46
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
About the Certificate Revocation List Check
Step 2
Enter trustpoint mode:
scope trustpoint trustname
Step 3
Enter revoke mode:
scope revoke
Step 4
Download the CRL file(s):
import crl protocol ://
user_id
@
CA_or_CRL_issuer_IP
/tmp/
DoDCA1CRL1.crl
Step 5
(Optional) Show the status of the import process of CRL information:
show import-task detail
Step 6
Set the certificate revocation method to CRL-only:
set certrevokemethod {crl}
About the Certificate Revocation List Check
You can configure your Certificate Revocation List (CRL) check mode to be either strict or relaxed in IPSec and secure LDAP connections.
Dynamic (non-static) CRL information is harvested from the CDP information of an X.509 certificate, and indicates dynamic CRL information. Static CRL information is downloaded by system administration manually, and indicates local CRL information in the FXOS system. The dynamic CRL information is only processed against the current processing certificate in the certificate chain. The static CRL is applied to the whole peer certificate chain.
For steps to enable or disable certificate revocation checks for your secure LDAP and IPSec connections, see
Configure IPSec Secure Channel, on page 41
and
Creating an LDAP Provider, on page 102
.
Note
• If the Certificate Revocation Check Mode is set to Strict, static CRL is only applicable when the peer certificate chain has a level of 1 or higher. (For example, when the peer certificate chain only contains the root CA certificate and the peer certificate signed by the root CA.)
• When configuring static CRL for IPSec, the Authority Key Identifier (authkey) field must be present in the imported CRL file. Otherwise, IPSec considers it invalid.
• Static CRL takes precedence over Dynamic CRL from the same issuer. When validating the peer certificate, if a valid (determined) static CRL of the same issuer exists, the CDP in the peer certificate is ignored.
The following tables describe the connection results, depending on your certificate revocation list check setting and certificate validation.
Table 1: Certificate Revocation Check Mode set to Strict without a local static CRL
Without local static CRL
Checking peer certificate chain
LDAP Connection
Full certificate chain is required
IPSec Connection
Full certificate chain is required
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
47
Security Certifications Compliance
About the Certificate Revocation List Check
Without local static CRL
Checking CDP in peer certificate chain
LDAP Connection
Full certificate chain is required
CDP checking for Root CA certificate of the peer certificate chain
Yes
Any certificate validation failure in the peer certificate chain
Connection fails with syslog message
Any certificate revoked in the peer certificate chain
Connection fails with syslog message
One CDP is missing the peer certificate chain
Connection fails with syslog message
IPSec Connection
Full certificate chain is required
Not applicable
Connection fails with syslog message
Connection fails with syslog message
Peer certificate: connection fails with syslog message
Intermediate CAs: connection succeeds
Connection succeeds One CDP CRL is empty in the peer certificate chain with valid signature
Connection fails with syslog message
Any CDP in the peer certificate chain cannot be downloaded
Connection fails with syslog message
Certificate has CDP, but the CDP server is down
Certificate has CDP, server is up, and CRL is on CDP, but the CRL has an invalid signature
Connection fails with syslog message
Connection fails with syslog message
Peer certificate: Connection fails with syslog message
Intermediate CA: connection succeeds
Peer certificate: Connection fails with syslog message
Intermediate CA: connection succeeds
Peer certificate: Connection fails with syslog message
Intermediate CA: connection succeeds
Table 2: Certificate Revocation Check Mode set to Strict with a local static CRL
With local static CRL
Checking peer certificate chain
LDAP Connection
Full certificate chain is required
Checking CDP in peer certificate chain
Full certificate chain is required
IPSec Connection
Full certificate chain is required
Full certificate chain is required
48
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
About the Certificate Revocation List Check
With local static CRL
CDP checking for Root CA certificate of the peer certificate chain
LDAP Connection
Yes
Any certificate validation failure in the peer certificate chain
Connection fails with syslog message
Any certificate revoked in the peer certificate chain
Connection fails with syslog message
One CDP is missing the peer certificate chain (Certificate Chain level is 1)
Connection succeeds
One CDP CRL is empty in the peer certificate chain (Certificate Chain level is 1)
Connection succeeds
Any CDP in the peer certificate chain cannot be downloaded
(Certificate Chain level is 1)
Connection succeeds
Certificate has CDP, but the CDP server is down (Certificate Chain level is 1)
Connection succeeds
Certificate has CDP, server is up, and CRL is on CDP, but the CRL has an invalid signature (Certificate
Chain level is 1)
Connection succeeds
Peer Certificate Chain level is higher than 1
Connection fails with syslog message
IPSec Connection
Not applicable
Connection fails with syslog message
Connection fails with syslog message
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
If combined with CDP, connection succeeds
If there is no CDP, connection fails with syslog message
Table 3: Certificate Revocation Check Mode set to Relaxed without a local static CRL
Without local static CRL
Checking peer certificate chain
Checking CDP in peer certificate chain
LDAP Connection
Full certificate chain
Full certificate chain
IPSec Connection
Full certificate chain
Full certificate chain
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
49
Security Certifications Compliance
About the Certificate Revocation List Check
Without local static CRL
CDP checking for Root CA certificate of the peer certificate chain
LDAP Connection
Yes
Any certificate validation failure in the peer certificate chain
Connection fails with syslog message
Any certificate revoked in the peer certificate chain
Connection fails with syslog message
One CDP is missing the peer certificate chain
Connection succeeds
One CDP CRL is empty in the peer certificate chain
Connection succeeds
Any CDP in the peer certificate chain cannot be downloaded
Connection succeeds
Certificate has CDP, but the CDP server is down
Connection succeeds
Certificate has CDP, server is up, and CRL is on CDP, but the CRL has an invalid signature
Connection succeeds
IPSec Connection
Not applicable
Connection fails with syslog message
Connection fails with syslog message
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
Table 4: Certificate Revocation Check Mode set to Relaxed with a local static CRL
With local static CRL
Checking peer certificate chain
Checking CDP in peer certificate chain
CDP checking for Root CA certificate of the peer certificate chain
LDAP Connection
Full certificate chain
Full certificate chain
Yes
Any certificate validation failure in the peer certificate chain
Connection fails with syslog message
Any certificate revoked in the peer certificate chain
Connection fails with syslog message
IPSec Connection
Full certificate chain
Full certificate chain
Not applicable
Connection fails with syslog message
Connection fails with syslog message
50
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Security Certifications Compliance
Set the LDAP Key Ring Certificate
With local static CRL LDAP Connection
One CDP is missing the peer certificate chain (Certificate Chain level is 1)
Connection succeeds
One CDP CRL is empty in the peer certificate chain (Certificate Chain level is 1)
Connection succeeds
Any CDP in the peer certificate chain cannot be downloaded
(Certificate Chain level is 1)
Connection succeeds
Certificate has CDP, but the CDP server is down (Certificate Chain level is 1)
Connection succeeds
Certificate has CDP, server is up, and CRL is on CDP, but the CRL has an invalid signature (Certificate
Chain level is 1)
Connection succeeds
Peer Certificate Chain level is higher than 1
Connection fails with syslog message
IPSec Connection
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
Connection succeeds
If combined with CDP, connection succeeds
If there is no CDP, connection fails with syslog message
Set the LDAP Key Ring Certificate
You can configure a secure LDAP client key ring certificate to support a TLS connection on your FXOS chassis. This option is one of a number offered for achieving Common Criteria certification compliance on your system. For more information, see
Security Certifications Compliance, on page 39
.
Note
If Common Criteria mode is enabled, you must have SSL enabled, and you must use the server DNS information to create the key ring certificate.
If SSL is enabled for the LDAP server entry, key ring information is referenced and checked when forming a connection.
LDAP server information has to be DNS information in the CC mode for the secure LDAP connection (with
SSL enabled).
Perform these steps to configure a secure LDAP client key ring certificate:.
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
51
Set the LDAP Key Ring Certificate
Procedure
Step 1
From the FXOS CLI, enter security mode:
scope security
Step 2
Enter LDAP mode:
scope ldap
Step 3
Enter LDAP server mode:
enter server {server_ip|server_dns}
Step 4
Set the LDAP key ring:
set keyring keyring_name
Step 5
Commit the configuration:
commit-buffer
Security Certifications Compliance
52
Cisco FXOS Firepower Chassis Manager Configuration Guide, 2.0(1)
Herunterladen
Werbung