index
int64 0
4.08k
| text
stringlengths 34
4.9k
⌀ | url
stringclasses 38
values |
|---|---|---|
3,355
|
System
Password for private
key
If supplied, this is used as an encryption password for the private key file.
Key Type Select RSA or Elliptic Curve.
Key Size When Key Type is RSA, select 1024, 1536, 2048, or 4096 for bitsize/strength. We recommend using at least 2048 if your CA can issue
certificates of that size.
Curve Name When Key Type is Elliptic Curve, select the elliptic curve type: secp256r1,
secp384r1, or secp521r1.
Enrollment Method Select one of the following methods that determines how the CSR will be
signed.
l File Based: this will generate a certificate in the certificate menu
under Local Certificate, which differs from the existing ones because
it has no Subject, Comments, Issuer, or Expires values in the table. It
will also show a Pending status because it is only a CSR at the
moment and cannot function as a certificate just yet. You can
download the CSR to provide to a CA for signing. If you open the CSR
file, it should look similar to this:
-----BEGIN CERTIFICATE REQUEST-----
MIIC7jCCAdYCAQAwgZUxCzAJBgNVBAYT (… )HEKjDX+Hg==
-----END CERTIFICATE REQUEST-----
Next. the CSR file is supplied to a CA for signing and the returned file
from the CA should be in .CER format. This file is then uploaded to
the FortiGate by going to System > Certificates > Import > Local
Certificate and uploading the CER file.
l Online SCEP: the Simple Certificate Enrollment Protocol (SCEP)
allows devices to enroll for a certificate by using a URL and a
password. The SCEP server works as a proxy to forward the
FortiGate’s request to the CA and returns the result to the FortiGate
(setting up an SCEP server is beyond the scope of this topic). Once
the request is approved by the SCEP server, the FortiGate will have a
signed certificate containing the details provided in the CSR.
3. Click OK.
The CSR generated, and can be downloaded from the local certificate list.
To generate a CSR in the CLI:
# execute vpn certificate local generate cmp-ec <certificate_name> <key_size> <server>
<path> <server_certificate> <auth_certificate> <user> <password> <subject> [SANs] [source_
IP]
# execute vpn certificate local generate cmp-rsa <certificate_name> <key_size> <server>
<path> <server_certificate> <auth_certificate> <user> <password> <subject> [SANs] [source_
IP]
# execute vpn certificate local generate ec <certificate_name> <curve_name> <subject>
<country> <state/province> <city> <organization> <OU> <email> [SANs] [options]
# execute vpn certificate local generate rsa <certificate_name> <key_size> <subject>
<country> <state/province> <city> <organization> <OU> <email> [SANs] [options]
FortiOS 7.6.2 Administration Guide 3356
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,356
|
System
cmp-ec Generate a ECDSA certificate request over CMPv2. To enable SSL/TLS, append
https:// to the server address.
cmp-rsa Generate a RSA certificate request over CMPv2. To enable SSL/TLS, append
https:// to the server address.
ec Generate an elliptic curve certificate request.
rsa Generate a RSA certificate request.
CA certificate
FortiGates come with many CA certificates from well-known certificate authorities pre-installed, just as most modern
operating systems like Windows and MacOS. Use this option to add private CA certificates to the FortiGate so that
certificates signed by this private CA are trusted by the FortiGate.
For example, a private CA can be used when two FortiGates are establishing a site-to-site VPN tunnel using a certificate
not signed by a public or trustworthy CA, or for your LDAPS connection to your corporate AD server that also uses a
certificate signed with a private CA in your domain. It is very common to upload a private CA when using PKI user
authentication, since most PKI user certificates will be signed by an internal CA.
To import a CA certificate in the GUI:
1. Go to System > Certificates and select Create/Import > CA Certificate.
2. Set the Type to Online SCEP or File.
l Online SCEP: Enter the URL of the SCEP server and optionally, the Optional CA Identifier. The FortiGate
contacts an SCEP server to request the CA certificate.
l File: Upload the CA certificate file directly from the management computer.
3. Click OK.
To import a CA certificate in the CLI:
# execute vpn certificate ca import auto <CA_server> [identifier] [source_ip] [fingerprint]
# execute vpn certificate ca import bundle <filename> <tftp_IP>
# execute vpn certificate ca import tftp <filename> <server_address>
# execute vpn certificate ems_ca import tftp <filename> <server_address>
auto Import CA certificate via SCEP.
bundle Import certificate bundle from a TFTP server.
tftp Import CA certificate from a TFTP server.
Remote certificate
Remote certificates are public certificates and contain only the public key. They are used to identify a remote device. For
example, when configuring your FortiGate for SAML authentication with the FortiGate as an identity provider (IdP), you
can optionally specify the service provider (SP) certificate. However, when configuring your FortiGate as a SP, you must
FortiOS 7.6.2 Administration Guide 3357
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,357
|
System
specify the certificate used by the IdP. Both these certificates can be uploaded to the FortiGate as a remote certificate,
since the private key is not necessary for its implementation.
To upload a remote certificate in the GUI:
1. Go to System > Certificates and select Create/Import > Remote Certificate.
2. Upload the remote certificate file directly from the management computer.
3. Click OK.
To upload a remote certificate in the CLI:
# execute vpn certificate remote import tftp <file_name> <server_address>
Certificate revocation list
Because it is not possible to recall a certificate, the certificate revocation list (CRL) details certificates signed by valid
CAs that should no longer be trusted. Certificates may be revoked for many reasons, such as if the certificate was issued
erroneously or if the private key of a valid certificate has been compromised.
To import a CRL in the GUI:
1. Go to System > Certificates and select Create/Import > CRL.
2. Set the Import Method to File Based or Online Updating.
l File Based: Upload the CRL file directly from the management computer. CAs publish files containing the list of
certificates that should no longer be trusted.
l Online Updating: This is the preferred method to keep the list of revoked certificates up to date. Configure the
protocols as required.
l HTTP: Enter the URL of the HTTP server.
l LDAP: Select the LDAP Server and enter the Username and Password.
l SCEP: Select the Certificate and enter the URL of the SCEP server.
3. Click OK.
To import a CRL in the CLI:
# execute vpn certificate crl import auto <CRL_name>
FortiOS 7.6.2 Administration Guide 3358
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,358
|
System
Export a certificate
Certificates can be downloaded to the management computer in the GUI and exported to a TFTP server in the CLI.
To back up a certificate in the GUI:
1. Go to System > Certificates.
2. Select the certificate from the list.
3. Click Download.
4. Save the file to the management computer.
To export the certificate in the CLI:
# execute vpn certificate ca export tftp <certificate_name> <filename> <tftp_IP>
# execute vpn certificate local export tftp <certificate_name> <file_type> <filename> <tftp_
server>
# execute vpn certificate remote export tftp <certificate_name> <filename> <tftp_server>
Uploading certificates using an API
There are several API methods to upload a certificate based on the type and purpose of the certificate. The parameters
of each method are available options, and some methods do not require all parameters to upload the certificate.
When uploading a certificate to the FortiGate using API, the certificate must be provided to the FortiGate in Base64
encoding. You must create a REST API user to authenticate to the FortiGate and use the generated API token in the
request.
api/v2/monitor/vpn-certificate/ca/import
{
"import_method": "[file|scep]",
"scep_url": "string",
"scep_ca_id": "string",
"scope": "[vdom*|global]",
"file_content": "string"
}
api/v2/monitor/vpn-certificate/crl/import
{
"scope": "[vdom*|global]",
"file_content": "string"
}
api/v2/monitor/vpn-certificate/local/import
{
"type": "[local|pkcs12|regular]",
"certname": "string",
"password": "string",
FortiOS 7.6.2 Administration Guide 3359
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,359
|
System
"key_file_content": "string",
"scope": "[vdom*|global]",
"acme-domain": "string",
"acme-email": "string",
"acme-ca-url": "string",
"acme-rsa-key-size": 0,
"acme-renew-window": 0,
"file_content": "string"
}
api/v2/monitor/vpn-certificate/remote/import
{
"scope": "[vdom*|global]",
"file_content": "string"
}
api/v2/monitor/vpn-certificate/csr/generate
{
"certname": "string",
"subject": "string",
"keytype": "[rsa|ec]",
"keysize": [1024|1536|2048|4096],
"curvename": "[secp256r1|secp384r1|secp521r1]",
"orgunits": [
"string"
],
"org": "string",
"city": "string",
"state": "string",
"countrycode": "string",
"email": "string",
"sub_alt_name": "string",
"password": "string",
"scep_url": "string",
"scep_password": "string",
"scope": "[vdom*|global]"
}
Example
In this example, a PKCS 12 certificate is uploaded as a local certificate using Postman as the API client. PowerShell is
used for the Base64 encoding.
To upload a PKCS 12 certificate using an API:
1. In PowerShell , encode the PKCS 12 certificate to Base64:
cd C:\users\username\desktop
$pkcs12cert = get-content 'C:\users\path\to\certificate\certificatename.p12' -Encoding
Byte
[System.Convert]::ToBase64String($pkcs12cert) | Out-File ‘base12encodedcert.txt’
These three lines of code do the following:
FortiOS 7.6.2 Administration Guide 3360
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,360
|
System
a. Changes to working directory to the location where the encoded certificate will be created. In this example, it is
the desktop.
b. Creates a variable called pkcs12cert and defines it as the certificate file by specifying the full path to the
certificate.
c. Creates a text file called base12encodedcert at the location specified in the first step. You will copy and
paste the contents of this as file_content later in Postman.
2. Generate an API token on the FortiGate by creating a REST API user. See Generate an API token on the Fortinet
Developer Network. A subscription to the Fortinet Developer Network is required to view this topic.
3. Open Postman and create a new request:
a. Click the +.
b. Click the Authorization tab and in the Type dropdown, select API Key.
c. For Key, enter access_token and enter the Value for the API user.
d. For Add to, select Query Params.
4. In the HTTP request dropdown, change the request from GET to POST, and enter the FortiGate’s IP address and
the URL of the API call.
5. Click the Body tab, and copy and paste the API parameters.
FortiOS 7.6.2 Administration Guide 3361
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,361
|
System
6. Remove unnecessary parameters (ACME related parameters and key_file_content) and enter the correct
settings for your certificate. Copy and paste the contents of the file generated by PowerShell earlier into file_
content.
7. Click Send. The lower window will return the results.
FortiOS 7.6.2 Administration Guide 3362
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,362
|
System
8. In FortiOS, go to System > Certificates and verify that the uploaded certificate is shown in the table (api_crt).
To debug using the HTTPS daemon:
# diagnose debug reset
# diagnose debug enable
# diagnose debug application httpsd -1
<output>
# diagnose debug disable
FortiOS 7.6.2 Administration Guide 3363
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,363
|
System
Procuring and importing a signed SSL certificate
A signed SSL certificate can be used when configuring SSL VPN, for administrator GUI access, and for other functions
that require a certificate.
Before creating a certificate, you must have a registered domain. With a valid FortiGuard
subscription, FortiDDNS can be used to register a domain; see DDNS on page 301 for more
information.
Follow these instructions to purchase, import, and use a signed SSL certificate:
l Obtain, setup, and download an SSL certificate package from a certificate authority
l Generate a CSR
l Import the signed certificate into your FortiGate
l Configure your FortiGate to use the signed certificate
Obtain, setup, and download an SSL certificate package from a certificate authority
SSL certificate packages can be purchased from any Certificate Authority (CA), such as DigiCert, GoDaddy, or
GlobalSign.
Let's Encrypt can be used to generate a free, trusted SSL certificate. See Automatically
provision a certificate on page 3346 for more information.
A third party CA might not sign a certificate with an intranet name or IP address. For details,
see Can I request a certificate for an intranet name or IP address?
The process for purchasing, setting up, and downloading a certificate will vary depending on the CA that is used, and if a
CSR must be generated on the FortiGate.
To purchase a certificate package:
1. Create an account with your chosen vendor, or use the account that you used to purchase your domain.
2. Locate the SSL Certificates page.
3. Purchase a basic SSL certificate for domain validation only. If required, a more secure SSL certificate can be
purchased.
4. If required, load the CSR, either by uploaded the text file or copying and pasting the contents into the requisite text
box. See Generate a CSR on page 3365 for information on generating the CSR on the FortiGate.
5. If required, set the server type to Other.
6. Verify the certificate per the requirements of the CA.
7. Download the signed certificate to your computer.
8. Import the signed certificate into your FortiGate; see Import the signed certificate into your FortiGate on page 3365.
FortiOS 7.6.2 Administration Guide 3364
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,364
|
System
Generate a CSR
Some CAs can auto-generate the CSR during the signing process, or provide tools for creating CSRs. If necessary, a
CSR can be created in your FortiGate device’s GUI.
To generate a CSR on your FortiGate:
1. Go to System > Certificates and select Create/Import > Generate CSR.
2. Configure the CSR:
l Ensure that the certificate has a unique name.
l Set the ID Type to Domain Name and enter a Domain Name.
l An email address is required.
l Ensure that the Key Size is set to 2048 Bit.
l Set the Enrollment Method to File Based.
3. Click OK.
The CSR will be added to the certificate list with a status of PENDING.
4. In the certificate list, select the new CSR then click Download to save the CSR to your computer.
The CSR file can be opened in any text editor, and will resemble the following:
-----BEGIN CERTIFICATE REQUEST-----
MIICuTCCAaECAQAwSzEcMBoGA1UEAxMTZm9ydGlzc2x2cG5kZW1vLmNvbTErMCkG
CSqGSIb3DQEJARYcZm9ydGlzc2x2cG5kZW1vQGZvcnRpbmV0LmNvbTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBAMtnpNoR20NH2+UEX/NsyCmZhQqc4af3
Be1u9iOoNbo9Fk42gw47r71moAN+1jTL/Tcp3hRhXtpgoI7Zh3vjZnBbD2wwU8Ow
U7d1h5MULyMehR9r4T6OAJl4KbKPt5u90r5SpIb6mM1OIKvzMncuRS66rW1St0KP
mp/f6QjpjMrthnyJkCejgyTA1YwWNuT9BcO6PTkxBqVMLaRP6TUH6He9uhOx1Cj/
5tzvSdAozZIr2moMieQy0lNd6oQcgpdzaB9QN41+cZOlUXRCMPoH7E4KUe3/Gnis
+NMdQ8rIBijvWCXrKj20wb6sUEjAGJkcXlqVHWYCKWXl6Owejmc4ipkCAwEAAaAp
MCcGCSqGSIb3DQEJDjEaMBgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBaAwDQYJKoZI
hvcNAQELBQADggEBAJKhtz2BPIKeHH9HcJKnfBKL+a6vu1l+1sW+YqnyD+3oR9ec
0eCmLnPxyyxsVel/tRsUg4DTfmooLNDhOjgfMsWxAGUQgrDH2k87cw6kiDAPCqv1
b+hFPNKZQSd09+HXAvOpXrMlrw5YdSaoRnau6Q02yUIYennKTIzFIscgh1mk4FSe
mb12DhPF+QydDCGDgtqnQbfxlDC0WmDcmxwa/0ZktoQhhhEbYgJ2O7l4TMqOxs/q
AZgwJlSNGBALLA2AxkIRUMKUteDdXz0QE8xNrvZpLTbWCNIpYJdRRqSd5C1w2VF4
CFgugTjFaJ13kYmBimeMRQsFtjLV5AxN+bUUsnQ=
-----END CERTIFICATE REQUEST-----
Import the signed certificate into your FortiGate
To import the signed certificate into your FortiGate:
1. Unzip the file downloaded from the CA.
There should be two CRT files: a CA certificate with bundle in the file name, and a local certificate.
2. Import the local certificate:
a. Go to System > Certificates and select Create/Import > Certificate.
b. Click Import Certificate.
c. Set Type to Local Certificate, upload the local certificate file, then click Create. See Local certificate on page
3352 for more information.
The status of the certificate will change from PENDING to OK.
FortiOS 7.6.2 Administration Guide 3365
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,365
|
System
3. Import the CA certificate:
a. Go to System > Certificates and select Create/Import > CA Certificate.
b. Set the Type to File, upload the CA certificate file, then click OK. See CA certificate on page 3357 for more
information.
The CA certificate will be listed in the CA Certificates section of the certificates list.
Configure your FortiGate to use the signed certificate
After the signed certificates have been imported, you can use it when configuring SSL VPN, for administrator GUI
access, and for other functions that require a certificate.
To configure your FortiGate to use the signed certificate for SSL VPN:
1. Go to VPN > SSL-VPN Settings.
2. Set Server Certificate to the new certificate.
3. Configure other settings as needed.
4. Click Apply.
For more information on configuring SSL VPN, see SSL VPN on page 2585 and the Setup SSL VPN video in the Fortinet
Video Library.
To configure using the certificate for administrator GUI access in the CLI:
config system global
set admin-server-cert fortisslvpndemo
end
To change the certificate that is used for administrator GUI access in the GUI:
1. Go to System > Settings.
2. In the Administration Settings section, change HTTPS server certificate as needed.
3. Click Apply. You will be logged out of FortiOS.
Microsoft CA deep packet inspection
In most production environments, you want to use a certificate issued be your own PKI for deep packet inspection (DPI).
An existing Microsoft root CA can be used to issue a subordinate CA (sub CA) certificate that is installed as a DPI
certificate on the FortiGate.
Complete the following steps to create your own sub CA certificate and use it for DPI:
1. Create a Microsoft sub CA certificate
2. Export the certificate and private key
3. Import the certificate and private key into the FortiGate
4. Configure a firewall policy for DPI
5. Verify that the sub CA certificate is being used for DPI
FortiOS 7.6.2 Administration Guide 3366
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,366
|
System
The FortiGate firewall uses information in the original web server certificate, then issues a new certificate signed by the
Microsoft DPI certificate. The FortiGate then sends this certificate with the issuing DPI certificate to the client's web
browser when the SSL session is being established.
The browser verifies that the certificate was issued by a valid CA, then looks for the issuing CA of the Microsoft DPI
certificate in its loca trusted root CA store to complete the path to trusted root CA.
The Microsoft CA root certificate is normally deployed to all client PCs in the Windows domain, so the client can
complete the certificate path up to a trusted root CA. The FortiGate now controls and can inspect the two HTTPS
sessions: one with the external web server, and one with the client PC.
Create a Microsoft sub CA certificate
A Microsoft sub CA certificate can be created on a Microsoft CA server, or remotely using a web browser.
Creating a certificate remotely requires that the web enrollment option is configured on the Microsoft CA server. Remote
certificate requests require HTTPS; requests are not allowed with HTTP.
To create a Microsoft sub CA certificate remotely:
1. Open a web browser and go to one of the following URLs:
l https://<FQDN-CA-server>/CertSrv
l https://<IP-CA-server>/CertSrv.
2. Log in to a domain administrator account that has web enrollment rights.
3. Click Request a certificate.
4. Click advanced certificate request.
5. Click Create and submit a request to this CA, then click Yes in the Web Access Confirmation warning.
6. For the Certificate Template, select Subordinate Certification Authority.
7. Enable Mark keys as exportable.
FortiOS 7.6.2 Administration Guide 3367
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,367
|
System
8. Fill out the remaining information according to your security policy.
9. Submit the request.
10. Click Yes in the Web Access Confirmation warning.
11. Click Install this certificate.
The certificate and private key are located in the current user's certificate store.
Export the certificate and private key
To export the certificate and private key:
1. Open the Microsoft Management Console (MMC) and add the Certificate Snap-in.
2. Go to the user's certificate store to locate the sub CA certificate that you just installed.
3. Right-click the certificate and select All Tasks > Export.
4. Click Next to start the Microsoft Certificate Export Wizard.
5. Follow the steps in the wizard:
l When asked, select Yes, export the private key.
l Only the PKCS #12 (.PFX) format is available, and it requires a password.
l When selecting the encryption type, select TripleDES-SHA1 if you are using an older version of FortiOS (5.6.9
FortiOS 7.6.2 Administration Guide 3368
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,368
|
System
and earlier). Otherwise, select AES256-SHA256.
6. Complete the wizard, and save the DPI certificate to a local folder.
Import the certificate and private key into the FortiGate
The certificate can be imported from the local computer using the GUI, or from a TFTP server using the CLI.
After importing the certificate, you can view it in the GUI to verify that it was successfully imported.
To import the certificate and private key into the FortiGate in the GUI:
1. Go to System > Certificates and select Create/Import > Certificate.
2. Click Import Certificate.
3. Set Type to PKCS #12 Certificate.
4. Click Upload, and locate the certificate on the management computer.
5. Enter the password, then confirm the password.
6. Optionally, customize the Certificate name.
7. Click OK.
To import the certificate and private key into the FortiGate in the CLI:
execute vpn certificate local import tftp fsso2019subca-AES256.pfx <tftp_IP> p12 <password>
To verify that the certificate was imported:
1. Go to System > Certificates.
2. Locate the newly imported certificate in the table.
3. Select the certificate and click View Details to view the certificate details.
FortiOS 7.6.2 Administration Guide 3369
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,369
|
System
Configure a firewall policy for DPI
The certificate is used in an SSL/SSH inspection profile that is then used in a firewall policy.
To configure a firewall policy for DPI:
1. Go to Security Profiles > SSL/SSH Inspection and click Create New.
2. Configure the inspection profile, selecting the new certificate
3. Click Apply.
4. Go to Policy & Objects > Firewall Policy.
5. Create a new policy, or edit an existing policy.
6. In the SSL Inspection field, select the new SSL inspection profile.
7. Configure the remaining settings as needed.
8. Click OK.
Verify that the sub CA certificate is being used for DPI
You can verify that the certificate is being used for resigning web server certificates when a user connects to an external
HTTPS website.
FortiOS 7.6.2 Administration Guide 3370
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,370
|
System
To verify that the certificate is being used:
1. On a client PC that is behind the FortiGate, go to an external HTTPS website.
When connecting to the website, no certificate warning should be shown.
2. In your web browser, view the certificate and certificate path.
The methods for doing this vary depending on the browser. See your browsers documentation for information.
Administrative access using certificates
Certificates can be used for administrative authentication.
Generated key pairs can also be used for this authentication. See Public key SSH access on page 2996 for information
about generating a key pair.
To log in to the FortiGate with a certificate private key:
1. On the PC, generate a certificate.
2. In FortiOS, import the PEM file for the remote certificate:
# execute vpn certificate remote import tftp certificate.pem 172.16.200.55
3. Display the imported remote certificate:
config certificate remote
edit "REMOTE_Cert_1"
next
end
4. Apply the remote certificate to the administrative user:
config system admin
edit "admin1"
set accprofile "prof_admin"
set vdom "root"
set ssh-certificate "REMOTE_Cert_1"
set password ************
next
end
5. On the PC, verify that the administrator can log in to the FortiGate with the SSH certificate:
root@PC05:~# ssh -i certificate-private.pem admin1@172.16.200.1
FortiGate-101F $ get system status
Version: FortiGate-101F v7.0.2,build0234,211019 (GA)
Creating certificates with XCA
This topic explains how to generate various certificates to be used in conjunction with a FortiGate, including:
l CA certificate
l Signing server and client certificates
l Issuing subordinate CAs for deep inspection
FortiOS 7.6.2 Administration Guide 3371
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,371
|
System
l Server certificate
l SSL/TLS web administration authentication
l VPN authentication
l Internal SSL server protection
l Client certificate
l End user authentication for SSL or IPsec VPN
XCA is an x509 certificate generation tool that handles RSA, DSA, and EC keys, as well as certificate signing requests
(PKCS #10) and CRLs.
There are several options for generating and managing certificates. This topic covers basic
certificate generation for XCA. It is not a comprehensive guide to its application and does not
explore all options available when generating a certificate.
Creating the XCA database
Before creating any certificates, you must create an XCA database to group the certificates in. You should use a different
database for each PKI you create.
To create the database:
1. Go to File > New Database.
2. Select a directory to store the created certificates and keys.
3. Enter a name. The provided password encrypts the private keys and is used to access the XCA database in the
future.
The remaining procedures in this topic assume you are using this XCA database.
Creating a CA certificate
A CA certificate marks the root of a certificate chain. If this CA certificate is trusted by an end entity, any certificates
signed by the CA certificate are also trusted.
FortiOS 7.6.2 Administration Guide 3372
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,372
|
System
To create a CA certificate:
1. Click the Certificates tab, then click New Certificate.
2. Edit the Source tab:
a. Set Template for the new certificate to [default] CA.
b. Click Apply extensions.
3. Edit the Subject tab:
a. Enter an Internal Name to reference this certificate within XCA.
b. Enter a commonName.
c. Optionally, click Add to add other distinguished name fields.
d. Since this XCA database does not contain any keys yet, click Generate a new key. The Private key field is now
FortiOS 7.6.2 Administration Guide 3373
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,373
|
System
populated.
4. Optionally, edit the Extensions tab:
a. Adjust the Time range if needed.
b. Click Apply.
5. Click OK.
Issuing a subordinate CA certificate for deep inspection
Subordinate CA certificates are similar to CA certificates because they are used to sign other certificates to establish
trust of the signed certificate's content. This trust of the signed certificate is only valid if the subordinate CA is also trusted
by the client.
When performing deep inspection on a FortiGate, the FortiGate proxies the connection between the endpoint and the
server. This is done transparently so that the end user believes they are communicating with the server, and the server
with the client. To do this, when the webpage is requested by a client, the FortiGate must present a certificate that
matches the requested website and is trusted by the client.
The certificate presented by the FortiGate is generated on-demand to match the requested website and is signed by this
subordinate CA to establish trust with the requesting endpoint. The subordinate CA must be installed on the ForitGate
(with the private key) and on the client device (without the private key).
A subordinate CA is used in place of a CA so that it may be revoked as necessary. This is critical since the subordinate
CA’s private key is exported and becomes susceptible of being compromised. If the CA private key becomes
compromised, you would be forced to re-create your entire PKI with a new root CA because root CAs cannot be revoked.
See Microsoft CA deep packet inspection on page 3366 for more information about using subordinate CA certificates.
FortiOS 7.6.2 Administration Guide 3374
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,374
|
System
To issue a subordinate CA certificate for deep inspection:
1. Click the Certificates tab, then click New Certificate.
2. Edit the Source tab:
a. Set Use this Certificate for signing to the CA created previously.
b. Set Template for the new certificate to [default] CA.
c. Click Apply extensions.
3. Edit the Subject tab:
a. Enter an Internal Name to reference this certificate within XCA.
b. Enter a commonName.
c. Optionally, click Add to add other distinguished name fields.
d. Click Generate a new key to create a new private key for the subordinate CA.
4. Optionally, edit the Extensions tab:
a. Adjust the Time range if needed.
b. Click Apply.
5. Click OK.
Creating a server host certificate
When a CA signs a host certificate, that CA is vouching for the credentials in the certificate. These credentials are what
identifies the host.
Some endpoints can generate a certificate signing request (CSR). A CSR is a certificate outline that specifies the details
of the endpoint, including its public key. This allows the CA to review the details and sign the request if they are true. This
request is then returned or uploaded to the generating endpoint to be used.
Since some endpoints cannot generate their own CSR, you can create the certificate manually in XCA. If you already
have a CSR, use the Certificate signing requests tab to import and then sign it.
FortiOS 7.6.2 Administration Guide 3375
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,375
|
System
To create a server host certificate:
1. Click the Certificates tab, then click New Certificate.
2. Edit the Source tab:
a. Set Template for the new certificate to [default] TLS_server.
b. Click Apply extensions.
c. In the Signing section, select Use this Certificate for signing and select the subordinate CA certificate.
3. Edit the Subject tab:
a. Enter an Internal Name to reference this certificate within XCA.
b. Enter the distinguished name fields as needed.
c. Click Generate a new key.
4. Edit the Extensions tab:
a. For X509v3 Subject Alternative Name, enter email:user@domain.tld.
5. Click OK.
FortiOS 7.6.2 Administration Guide 3376
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,376
|
System
6. Click the Certificates tab to view the certificate.
This certificate may be used to identify an SSL or TLS server by uploading the certificate and key pair to the server, such
as when the FortiGate presents the administrative webpage or for SSL VPN authentication (see Configure your
FortiGate to use the signed certificate on page 3366). Another use case for a server host certificate is to enable SSL
server protection so the FortiGate simulates the real server and brokers the connection (see Protecting an SSL server on
page 2150).
Creating a client host certificate
A client host certificate is used to identify an end entity in a more secure way than a username and password. Once the
client host certificate is generated, see SSL VPN with certificate authentication on page 2658 for more information about
using the certificate.
To create a client host certificate:
1. Click the Certificates tab, then click New Certificate.
2. Edit the Source tab:
a. In the Signing section, select Use this Certificate for signing and select the CA or subordinate CA.
b. Set Template for the new certificate to [default] TLS_client.
c. Click Apply extensions.
3. Edit the Subject tab:
a. Enter an Internal Name to reference this certificate within XCA.
b. Enter the distinguished name fields as needed.
FortiOS 7.6.2 Administration Guide 3377
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,377
|
System
c. Click Generate a new key.
4. Click OK.
5. Click the Certificates tab. The FortiGate and client certificates are listed under the signing CA certificate and are
ready to be exported.
6. Select a certificate and click Export.
7. Enter the file name and select an export format.
8. Click OK.
Certificate formats
Certificate file formats indicate what is contained in the file, how it is formatted, and how it is encoded. See Import a
certificate on page 3352 for more information about which formats the FortiGate expects for a given certificate type.
FortiOS 7.6.2 Administration Guide 3378
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,378
|
System
Enrollment over Secure Transport for automatic certificate management
The FortiGate supports Enrollment over Secure Transport (EST) and the RFC 7030 standards when generating a new
CSR request, performing automatic renewals, or manually regenerating a certificate. EST provides more security for
automatic certificate management than Simple Certificate Enrollment Protocol (SCEP), which is commonly used for
certificate enrollment.
Background
SCEP helps automate and simplify the process for obtaining a digital certificate from a certificate authority (CA).
However, SCEP does not natively support secure connections, and instead relies on the underlying transport protocol to
provide security. EST was developed, which uses TLS to establish a secure communication channel over which
subsequent certificate management protocol messages like initial certificate enroll and certificate renewal messages are
exchanged.
On the FortiGate, when generating a certificate signing request (CSR), you can use the SCEP method to send the
request to an SCEP server, or use EST to send the request to an EST server to be signed by a CA.
To configure the enrollment protocol settings for a local certificate:
config vpn certificate local
edit <name>
set enroll-protocol est
set est-server <string>
set est-ca-id <string>
set est-http-username <string>
set est-http-password <string>
set est-client-cert <certificate>
set est-server-cert <certificate>
set est-srp-username <string>
set est-srp-password <string>
next
end
est-server <string> Enter the address and port for EST server (such as https://example.com:1234).
est-ca-id <string> Enter the CA identifier of the CA server for signing with EST.
est-http-username
<string>
Enter the HTTP Authentication username for signing with EST.
est-http-password
<string>
Enter the HTTP Authentication password for signing with EST.
est-client-cert
<certificate>
Enter the certificate used to authenticate this FortiGate to the EST server.
est-server-cert
<certificate>
Enter the EST server's certificate that has to be verifiable by the specified
certificate on the FortiGate.
est-srp-username <string> Enter the EST SRP authentication username.
est-srp-password <string> Enter the EST SRP authentication password.
FortiOS 7.6.2 Administration Guide 3379
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,379
|
System
To manually generate a CSR for the EST server to be signed by a CA:
# execute vpn certificate local generate est {reqired_1} {reqired_2} {reqired_3} [options]
option 1 (required) Name of the local server certificate.
option 2 (required) Cryptography algorithm: rsa-1024, rsa-1536, rsa-2048, rsa-4096, ecsecp256r1, ec-secp384r1, or ec-secp521r1.
option 3 (required) URL and listening port of the remote EST responder.
option 4 (optional) Server certificate subject in the certificate enroll request. Separate fields by a
comma (,).
option 5 (optional) Subject Alternative Name (SAN). This can be an FQDN and/or IP. Use
DNS:<FQDN>,IP:<IP_address> for example. If the issuing CA does not support
SAN, this option will be ignored. Separate fields by a comma (,).
option 6 (optional) HTTP authentication username.
option 7 (optional) HTTP authentication password.
option 8 (optional) CA identifier.
option 9 (optional) CA certificate used to verify the remote EST responder server certificate and
certificates issued by a remote PKI.
option 10 (optional) Password for the private key.
option 11 (optional) Client certificate.
option 12 (optional) Source IP for communications to the CA server.
option 13 (optional) TLS-SRP username.
option 14 (optional) TLS-SRP password.
Example 1: enrolling for a new FortiGate server certificate with EST
To enroll for a new FortiGate server certificate with EST:
1. Verify that the FortiGate can communicate with remote EST responder (testrfc7030.com):
# execute ping testrfc7030.com
PING testrfc7030.com (54.70.32.33): 56 data bytes
64 bytes from 54.70.32.33: icmp_seq=0 ttl=31 time=13.6 ms
64 bytes from 54.70.32.33: icmp_seq=1 ttl=31 time=19.1 ms
64 bytes from 54.70.32.33: icmp_seq=2 ttl=31 time=16.5 ms
^C
--- testrfc7030.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 13.6/16.4/19.1 ms
2. Start running debugs to track the progress of the enrollment:
# diagnose debug application est -1
# diagnose debug enable
3. Create a new server CSR file locally and send it to the remote EST responder:
FortiOS 7.6.2 Administration Guide 3380
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,380
|
System
# execute vpn certificate local generate est est-test101 ec-secp256r1
https://testrfc7030.com:8443 CN=firewall-portal1,DC=local,DC=COM DNS:firewallportal1.local.ca,IP:172.18.60.184 estuser estpwd G_CA_Cert_1
The CA certificate (G_CA_Cert_1) is used to verify the remote EST responder server
certificate and certificates issued by a remote PKI.
testrfc7030.com is a self-signed CA, which by default is not in the local trusted root store
and must be imported prior to enrollment.
If the CA that issues the server certificate is not in the local root store, an error would
appear in the debug messages:
# diagnose debug application est -1
# diagnose debug enable
...
[1795] est_curl_req: Error buf: SSL certificate problem: self-signed
certificate in certificate chain,
[2402] est_simple_enroll: Failed to get ca certs: -1.
...
4. If the enrollment was successful, in a few seconds, a Done message appears. Verify the debugs to view the
enrollment process.
a. The remote CA's certificate is retrieved and stored locally in the EST configuration after being verified with the
CA in the trusted root store:
[1962] __est_curl_set_auth: trace
[2046] __est_curl_set_auth: HTTP Authentication username is set
[2050] __est_curl_set_auth: HTTP Authentication password is set
[2075] __est_get_ca_certs: ============STARTED============
[1728] est_curl_req: URL: https://testrfc7030.com:8443/.well-known/est/cacerts
[1776] est_curl_req: HTTP GET
[143] __curl_ssl_ctx_finalizer: global CAs are loaded.
[165] __curl_ssl_ctx_finalizer: SSL_CTX ex data is set.
[1651] curl_header_debug_func: Header received:HTTP/1.1 200 OK
b. The debug displays the CA used by the remote EST responder:
[1191] save_pkcs7_certs: Saving pkcs7 response
[505] est_print_pkcs7: Certs: (1 in total)
[507] est_print_pkcs7: Cert 1:
[427] est_print_x509: Version: 3 (0x2)
Serial Number:
ab:e8:32:e1:f6:6a:6b:43
Issuer: CN=estExampleCA
Subject: CN=estExampleCA
X509v3 extensions:
X509v3 Basic Constraints:
CA:TRUE
X509v3 Subject Key Identifier:
1A:DF:39:84:C2:56:E6:6C:CF:2A:B4:26:A5:FD:0C:D2:43:F5:3D:3E
[1220] save_pkcs7_certs: Received 1 certs
[1228] save_pkcs7_certs: Saving cert(s):
is_global:1
est_url:https://testrfc7030.com:8443
FortiOS 7.6.2 Administration Guide 3381
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,381
|
System
source_ip:NULL
ca_identifier:NULL
c. The CA certificate is imported. FortiOS sends a query to learn about the attributes supported by the CA in the
certificate request and will then create the CSR accordingly:
[1288] save_pkcs7_certs: CA certs imported!
[2101] __est_get_csr_attrs: ============STARTED============
[1728] est_curl_req: URL: https://testrfc7030.com:8443/.well-known/est/csrattrs
[1776] est_curl_req: HTTP GET
[1651] curl_header_debug_func: Header received:HTTP/1.1 200 OK
[1651] curl_header_debug_func: Header received:Status: 200 OK
[1651] curl_header_debug_func: Header received:Content-Type: application/csrattrs
[1651] curl_header_debug_func: Header received:Content-Transfer-Encoding: base64
[1651] curl_header_debug_func: Header received:Content-Length: 57
[1651] curl_header_debug_func: Header received:
[1787] est_curl_req: Response 200
[1788] est_curl_req: Buffer:MCYGBysGAQEBARYGCSqGSIb3DQEJAQYFK4EEACIGCWCGSAFlAwQCAg==
[1439] decode_csrattrs_callback: Decoding csrattrs, resp->len: 57
[1474] decode_csrattrs_callback: Object: 1.3.6.1.1.1.1.22 undefined
[1474] decode_csrattrs_callback: Object: 1.2.840.113549.1.9.1 emailAddress
[1474] decode_csrattrs_callback: Object: 1.3.132.0.34 secp384r1
[1474] decode_csrattrs_callback: Object: 2.16.840.1.101.3.4.2.2 sha384
d. The CSR information is generated, which is sent to the remote EST responder:
est_ctx: is_global:1
vfid:0
svr_original_url:https://testrfc7030.com:8443
svr_hostinfo:Exists
ca_identifier:(null)
http_username:estuser
http_password:*
clt_cert:(null)
svr_cert:(null)
srp_username:(null)
srp_password:(null)
source_ip:(null)
need_pop:0
newcert_name:est-test101
passwd:(null)
rsa_keysize:0
ec_curvename:secp256r1
subject:CN=firewall-portal1,DC=local,DC=COM
sub_alt_name:DNS:firewall-portal1.local.ca,IP:172.18.60.184
svr_cert_x509:NULL
csr_attrs:Exists
csr:NULL
pkey:NULL
header_ptr:NULL
tmp_p10:NULL
[2259] __est_simple_enroll: ============STARTED============
e. The CSR is sent to the EST responder:
[1728] est_curl_req: URL: https://testrfc7030.com:8443/.well-known/est/simpleenroll
[1753] est_curl_req: HTTP POST
[1651] curl_header_debug_func: Header received:HTTP/1.1 200 OK
FortiOS 7.6.2 Administration Guide 3382
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,382
|
System
[1651] curl_header_debug_func: Header received:Status: 200 OK
[1651] curl_header_debug_func: Header received:Content-Type: application/pkcs7-mime;
smime-type=certs-only
[1651] curl_header_debug_func: Header received:Content-Transfer-Encoding: base64
[1651] curl_header_debug_func: Header received:Content-Length: 585
[1651] curl_header_debug_func: Header received:
f. The CA issues the certificate and sends it back in a PKCS #7 structure:
[1787] est_curl_req: Response 200
[1788] est_curl_req:
Buffer:MIIBqwYJKoZIhvcNAQcCoIIBnDCCAZgCAQExADALBgkqhkiG9w0BBwGgggGAMIIB
fDCCASOgAwIBAgIDB0aXMAoGCCqGSM49BAMCMBcxFTATBgNVBAMTDGVzdEV4YW1w
...
g. The FortiGate decodes and displays the attributes of the certificate, then saves the certificate:
[1191] save_pkcs7_certs: Saving pkcs7 response
[505] est_print_pkcs7: Certs: (1 in total)
[507] est_print_pkcs7: Cert 1:
[427] est_print_x509: Version: 3 (0x2)
Serial Number: 476823 (0x74697)
Issuer: CN=estExampleCA
Subject: CN=firewall-portal1
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Subject Key Identifier:
9B:F8:39:D5:21:E6:FF:49:FF:AC:02:57:5B:FC:4C:1A:8B:1E:5D:8F
X509v3 Authority Key Identifier:
1A:DF:39:84:C2:56:E6:6C:CF:2A:B4:26:A5:FD:0C:D2:43:F5:3D:3E
[1220] save_pkcs7_certs: Received 1 certs
[1228] save_pkcs7_certs: Saving cert(s):
is_global:1
est_url:https://testrfc7030.com:8443
source_ip:NULL
ca_identifier:NULL
[1246] save_pkcs7_certs: Received 1 cert(s)
[427] est_print_x509: Version: 3 (0x2)
Serial Number: 476823 (0x74697)
Issuer: CN=estExampleCA
Subject: CN=firewall-portal1
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Subject Key Identifier:
9B:F8:39:D5:21:E6:FF:49:FF:AC:02:57:5B:FC:4C:1A:8B:1E:5D:8F
X509v3 Authority Key Identifier:
1A:DF:39:84:C2:56:E6:6C:CF:2A:B4:26:A5:FD:0C:D2:43:F5:3D:3E
[827] est_cmdb_update_cert: Cert est-test101 updated in CMDB
[1276] save_pkcs7_certs: The cert is saved!
FortiOS 7.6.2 Administration Guide 3383
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,383
|
System
[592] est_ctx_clear_tmp_data: trace
[2408] est_simple_enroll: POST ret:0
[592] est_ctx_clear_tmp_data: trace
Done.
Example 2: automatically renewing a FortiGate server certificate with EST
When the time for certificate renewal is up, the FortiGate will use the existing EST parameters to perform an automatic
renewal. This example demonstrates the renewal process through debugs.
To automatically renew a FortiGate server certificate with EST:
1. Verify the current local certificate configuration:
config vpn certificate local
(local) # get est-test101
name : est-test101
password : *
comments :
private-key : *
certificate :
Subject: CN = firewall-portal1
Issuer: CN = estExampleCA
Valid from: 2023-04-06 22:37:34 GMT
Valid to: 2024-04-05 22:37:34 GMT
Fingerprint: AE:67:11:CF:7D:F9:57:A4:09:8B:55:0A:F1:B1:7A:CF
...
state : OK
range : global
source : user
source-ip : 0.0.0.0
ike-localid-type : asn1dn
enroll-protocol : est
est-server : https://testrfc7030.com:8443
est-ca-id :
est-http-username : estuser
est-http-password : *
est-client-cert :
est-server-cert :
est-srp-username :
est-srp-password :
auto-regenerate-days: 0
auto-regenerate-days-warning: 0
Note that the current Valid to date and time is 2024-04-05 22:37:34 GMT, which is one year from the issue
date.
2. Start running debugs to track the progress of the renewal:
# diagnose debug application est -1
# diagnose debug enable
3. For demonstration purposes, update the auto-regenerate-days setting to 364 days to trigger the automatic
renewal on the FortiGate:
FortiOS 7.6.2 Administration Guide 3384
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,384
|
System
config vpn certificate local
edit est-test101
set auto-regenerate-days 364
next
end
4. Verify the debugs to confirm that the certificate was renewed.
a. The FortiGate uses the content of the current certificate to create a new CSR. User credentials used for the
initial enrollment are stored in local certificate configuration, but they are not used for renewal:
[1024] reconstruct_est_ctx: Reconstruction succeeded
est_ctx: is_global:1
vfid:0
svr_original_url:https://testrfc7030.com:8443
svr_hostinfo:NULL
ca_identifier:
http_username:estuser
http_password:*
clt_cert:
svr_cert:
srp_username:
srp_password:
source_ip:(null)
need_pop:0
newcert_name:est-test101
passwd:f51da8548af5fef820edfe6267b0c178e76f7c3eae40ee0900318fc77ab6bd
rsa_keysize:0
ec_curvename:(null)
subject:(null)
sub_alt_name:(null)
svr_cert_x509:NULL
csr_attrs:NULL
csr:NULL
pkey:NULL
header_ptr:NULL
tmp_p10:NULL
b. The FortiGate sends the current server certificate for authentication/authorization and not the
username/password used for initial enrollment:
[2453] est_simple_reenroll: Try to use est-test101 as client cert to authenticate
[1962] __est_curl_set_auth: trace
[2011] __est_curl_set_auth: Warning: cert est-test101 may not have the correct key
usage for TLS client authentication
[2014] __est_curl_set_auth: Will use cert est-test101 to prove my identity
...
[1651] curl_header_debug_func: Header received:
[1787] est_curl_req: Response 200
[1788] est_curl_req: Buffer:MCYGBysGAQEBARYGCSqGSIb3DQEJAQYFK4EEACIGCWCGSAFlAwQCAg==
[1439] decode_csrattrs_callback: Decoding csrattrs, resp->len: 57
[1474] decode_csrattrs_callback: Object: 1.3.6.1.1.1.1.22 undefined
[1474] decode_csrattrs_callback: Object: 1.2.840.113549.1.9.1 emailAddress
[1474] decode_csrattrs_callback: Object: 1.3.132.0.34 secp384r1
[1474] decode_csrattrs_callback: Object: 2.16.840.1.101.3.4.2.2 sha384
est_ctx: is_global:1
vfid:0
FortiOS 7.6.2 Administration Guide 3385
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,385
|
System
svr_original_url:https://testrfc7030.com:8443
svr_hostinfo:Exists
ca_identifier:
http_username:estuser
http_password:*
clt_cert:est-test101
svr_cert:
srp_username:
srp_password:
source_ip:(null)
need_pop:0
newcert_name:est-test101
passwd:f51da8548af5fef820edfe6267b0c178e76f7c3eae40ee0900318fc77ab6bd
rsa_keysize:0
ec_curvename:(null)
subject:(null)
sub_alt_name:(null)
svr_cert_x509:NULL
csr_attrs:Exists
csr:NULL
pkey:NULL
header_ptr:NULL
tmp_p10:NULL
[2274] __est_simple_reenroll: ============STARTED============
c. The CSR for renewal is successfully generated:
[965] est_generate_csr_from_cert: Successfully generated CSR for est-test101
[2200] __est_simple_post: Data to be posted:
|||MIIBQDCB5gIBAjAbMRkwFwYDVQQDDBBmaXJld2FsbC1wb3J0YWwxMFkwEwYHKoZI
zj0CAQYIKoZIzj0DAQcDQgAEQoJQmPedxPNUcfCyRvpqyt1oiiJX/me+TdButUSu
8hg+9nPF6+xNf+5LmtG/YKHeXyCKG6xB9OmJf255Zmx+5qBpMGcGCSqGSIb3DQEJ
DjFaMFgwCQYDVR0TBAIwADALBgNVHQ8EBAMCB4AwHQYDVR0OBBYEFJv4OdUh5v9J
/6wCV1v8TBqLHl2PMB8GA1UdIwQYMBaAFBrfOYTCVuZszyq0JqX9DNJD9T0+MAoG
CCqGSM49BAMCA0kAMEYCIQCK3Li51F7fXsyKZwtIcYMFvDobY3cKKTTDixtN7QZ2
jwIhAKUkqfWPAzwcxQaNQw6pyYvo18ymB9aEheeIXZfGI+tV
|||
[1728] est_curl_req: URL: https://testrfc7030.com:8443/.well-known/est/simplereenroll
[1753] est_curl_req: HTTP POST
[1651] curl_header_debug_func: Header received:HTTP/1.1 200 OK
[1651] curl_header_debug_func: Header received:Status: 200 OK
[1651] curl_header_debug_func: Header received:Content-Type: application/pkcs7-mime;
smime-type=certs-only
[1651] curl_header_debug_func: Header received:Content-Transfer-Encoding: base64
[1651] curl_header_debug_func: Header received:Content-Length: 590
[1651] curl_header_debug_func: Header received:
[1787] est_curl_req: Response 200
d. The new certificate is received in PKCS #7 and is saved:
[1788] est_curl_req:
Buffer:MIIBrQYJKoZIhvcNAQcCoIIBnjCCAZoCAQExADALBgkqhkiG9w0BBwGgggGCMIIB
fjCCASOgAwIBAgIDB0aYMAoGCCqGSM49BAMCMBcxFTATBgNVBAMTDGVzdEV4YW1w
...
[1191] save_pkcs7_certs: Saving pkcs7 response
[505] est_print_pkcs7: Certs: (1 in total)
...
FortiOS 7.6.2 Administration Guide 3386
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,386
|
System
[1220] save_pkcs7_certs: Received 1 certs
[1228] save_pkcs7_certs: Saving cert(s):
is_global:1
est_url:https://testrfc7030.com:8443
source_ip:NULL
ca_identifier:
[1246] save_pkcs7_certs: Received 1 cert(s)
[427] est_print_x509: Version: 3 (0x2)
Serial Number: 476824 (0x74698)
Issuer: CN=estExampleCA
Subject: CN=firewall-portal1
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
X509v3 Key Usage:
Digital Signature
X509v3 Subject Key Identifier:
9B:F8:39:D5:21:E6:FF:49:FF:AC:02:57:5B:FC:4C:1A:8B:1E:5D:8F
X509v3 Authority Key Identifier:
1A:DF:39:84:C2:56:E6:6C:CF:2A:B4:26:A5:FD:0C:D2:43:F5:3D:3E
[827] est_cmdb_update_cert: Cert est-test101 updated in CMDB
[1276] save_pkcs7_certs: The cert is saved!
[592] est_ctx_clear_tmp_data: trace
[2477] est_simple_reenroll: POST ret:0
[592] est_ctx_clear_tmp_data: trace
5. Verify the renewed local certificate configuration:
config vpn certificate local
(local) # get est-test101
name : est-test101
password : *
comments :
private-key : *
certificate :
Subject: CN = firewall-portal1
Issuer: CN = estExampleCA
Valid from: 2023-04-06 22:55:09 GMT
Valid to: 2024-04-05 22:55:09 GMT
Fingerprint: D9:51:6C:EF:04:E9:79:8D:A0:EE:10:23:4A:F4:46:B7
Root CA: No
Version: 3
Serial Num:
07:46:a5
Extensions:
Name: X509v3 Basic Constraints
Critical: no
Content:
Note that the Valid to date and time is now 2024-04-05 22:55:09 GMT.
Example 3: manually regenerating a local certificate with EST
Note that manually regenerating the certificate will not generate a new server key pair.
FortiOS 7.6.2 Administration Guide 3387
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,387
|
System
To manually regenerate a local certificate with EST:
1. Run the following command:
# execute vpn certificate local generate est est-test101
Certificate 'est-test101' already exists, re-generate will ignore all the options you
have provided.
Are you sure to re-generate the certificate?
Do you want to continue? (y/n) y
2. Verify the debugs to confirm that the certificate was generated:
# diagnose debug application est -1
# diagnose debug enable
...
[1024] reconstruct_est_ctx: Reconstruction succeeded
est_ctx: is_global:1
vfid:0
svr_original_url:https://testrfc7030.com:8443
svr_hostinfo:NULL
ca_identifier:
http_username:estuser
http_password:*
clt_cert:
svr_cert:
srp_username:
srp_password:
source_ip:(null)
need_pop:0
newcert_name:est-test101
passwd:f51da8548af5fef820edfe6267b0c178e76f7c3eae40ee0900318fc77ab6bd
rsa_keysize:0
ec_curvename:(null)
subject:(null)
sub_alt_name:(null)
svr_cert_x509:NULL
csr_attrs:NULL
csr:NULL
pkey:NULL
header_ptr:NULL
tmp_p10:NULL
[2453] est_simple_reenroll: Try to use est-test101 as client cert to authenticate
[1962] __est_curl_set_auth: trace
...
3. Once the certificate is saved, verify the local certificate configuration:
config vpn certificate local
(local) # get est-test101
name : est-test101
password : *
comments :
private-key : *
certificate :
Subject: CN = firewall-portal1
Issuer: CN = estExampleCA
Valid from: 2023-04-13 17:23:40 GMT
Valid to: 2024-04-12 17:23:40 GMT
FortiOS 7.6.2 Administration Guide 3388
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,388
|
System
Fingerprint: 4A:96:E1:73:6D:D3:64:FE:A3:A8:28:56:1D:39:05:37
Root CA: No
Version: 3
Serial Num:
07:47:02
Extensions:
Name: X509v3 Basic Constraints
Critical: no
Content:
CA:FALSE
Name: X509v3 Key Usage
Critical: no
Content:
Digital Signature
Name: X509v3 Subject Key Identifier
Critical: no
Content:
9B:F8:39:D5:21:E6:FF:49:FF:AC:02:57:5B:FC:4C:1A:8B:1E:5D:8F
Name: X509v3 Authority Key Identifier
Critical: no
Content:
1A:DF:39:84:C2:56:E6:6C:CF:2A:B4:26:A5:FD:0C:D2:43:F5:3D:3E
state : OK
range : global
source : user
source-ip : 0.0.0.0
ike-localid-type : asn1dn
enroll-protocol : est
est-server : https://testrfc7030.com:8443
est-ca-id :
est-http-username : estuser
est-http-password : *
est-client-cert :
est-server-cert :
est-srp-username :
est-srp-password :
auto-regenerate-days: 0
auto-regenerate-days-warning: 0
The Subject Key Identifier is the same, so no new key pair was generated.
Security
The following topics provide information about security:
l BIOS-level signature and file integrity checking on page 3390
l Real-time file system integrity checking on page 3394
l Running a file system check automatically on page 3397
FortiOS 7.6.2 Administration Guide 3389
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,389
|
System
l Built-in entropy source on page 3398
l FortiGate VM unique certificate on page 3399
l Closed network VM license security on page 3400
l Encrypt configuration files in the eCryptfs file system on page 3402
l FIPS-CC mode and OpenSSL FIPS provider on page 3402
BIOS-level signature and file integrity checking
The BIOS-level signature and integrity checking includes several checks that occur during different stages.
Stage Checks
BIOS-level signature and
integrity check during file upload
Dually-signed images such as the firmware image, AV engine file and IPS engine
file are verified during file upload while FortiOS is running.
BIOS-level signature and
integrity check during the boot
process
Dually-signed images such as the firmware image, AV engine file and IPS engine
file are verified during the boot process before the kernel is mounted.
BIOS-level file integrity check
during bootup as files are
mounted
Signed hashes of important files related to the kernel, filesystems and AV/IPS
engines and executables are verified during bootup as they are mounted and
loaded into user space.
Each FortiOS GA firmware image, AV engine file, and IPS engine file are dually-signed by the Fortinet CA and a thirdparty CA.
Signature checking occurs when the FortiOS firmware, AV, and IPS engine files are uploaded. This allows the FortiGate
to either warn users of potential risks involved with uploading an unauthenticated file, or block the file upload depending
on the BIOS security level.
During the boot process before the kernel is loaded, the BIOS also verifies that each file matches their secure hash as
indicated by their certificates. Users are warned when there is a failed integrity check, and the system may be prevented
from booting depending on the severity and the BIOS security level.
Once the signature check passes, important files are extracted, mounted and loaded into user space during the bootup.
All the important files are verified against their signed hashes to validate the integrity of the files before they can be
mounted or loaded into user space. The hash file containing hashes of all executables and shared libraries is also
verified to ensure the integrity of the file before the individual hashes are loaded into memory.
When the system is started, real-time protection kicks in. See Real-time file system integrity checking on page 3394 for
more details.
BIOS-level signature and integrity check on firmware images
The outcome of the signature and integrity check during file upload and boot process depends on the security level
configured in BIOS and the certificate authority that signed the file.
The following table summarizes the use cases and the potential outcome based on the security level.
FortiOS 7.6.2 Administration Guide 3390
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,390
|
System
Use case Certificate signed by Outcome based on security
level
Fortinet CA Third-party
CA
Level High Level Low
GA-Certified
(GA firmware, Beta firmware, Special
Technical Support final builds)
Yes Yes Accept Accept
Non-GA certified
(Special builds: Special Technical
Support and NPI quick builds)
Yes No Warning Accept
Interim and Dev builds, or unknown build No Yes or No Reject Warning
The security levels on the BIOS are:
FortiOS level Behavior
High FortiOS and BIOS only accept certified images.
Low FortiOS and BIOS only accept certified images without a warning and un-certified images
with a warning
On FortiGates without supported BIOS security levels, the device acts like security level High. For example, on a
FortiGate-VM that does not have BIOS, the security level is defaulted to level High.
Platforms with old BIOS versions will support security levels 0, 1, and 2, while FortiOS will support levels High and Low.
BIOS level 2 will correspond to the behaviors in Level High, and BIOS level 0 and 1 will correspond to behaviors in Level
Low.
Security levels can be verified using the command get system status.
Examples of BIOS-level signature and integrity check during file upload
The following examples outline the different use cases when upgrading firmware and AV files on a FortiGate model that
supports BIOS security levels, and a FortiGate model that does not support BIOS security levels.
For more information, see the Firmware & Registration on page 3008 section and Manual updates on page 3320.
Upgrading on a device with BIOS security levels
The following use cases are applicable when upgrading firmware and AV files on a FortiGate with BIOS security levels.
Firmware is upgraded using the System > Firmware & Registration page, and AV files are upgraded using the System
> FortiGuard page.
FortiOS 7.6.2 Administration Guide 3391
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,391
|
System
Security
Level
Use case Behavior
High Load certified GA image in TFTP
in boot menu
FortiGate boots up without warning messages.
High Restore certified GA image in CLI FortiGate boots up without warning messages.
High Load certified non-GA image in
TFTP in boot menu
FortiGate boots up with a warning message:
Warning: Non GA FOS image!
High Restore certified non-GA image
in CLI
FortiGate displays a warning upon upload:
Warning: This firmware image is no GA certified!
FortiGate boots up with a warning message:
Warning: Non GA FOS image!
High Load un-certified interim image in
TFTP in boot menu
The upload is blocked.
A warning is displayed:
Checking image… This firmware image is not
certified!
Aborting firmware installation. Please power
cycle. System halted.
High Restore un-certified interim
image in CLI
The upload is blocked.
A warning is displayed:
Image verification failed!
…
Low Load certified GA or non-GA
image in TFTP in boot menu
FortiGate boots up without warning messages.
Low Restore certified GA or non-GA
image in CLI
FortiGate boots up without warning messages.
Low Load un-certified interim image in
TFTP in boot menu
FortiGate outputs a warning message, but the upload is allowed
to proceed:
Warning: Image decode failed. Try to continue
under security level 1…
OK
This firmware image is not certified!
Save as Default firmware/Backup firmware/Run
image without saving [D/B/R]?
After boot up:
System file integrity init check failed!
Low Restore un-certified interim
image in CLI
FortiGate outputs a warning message, but the upload is allowed
to proceed:
FortiOS 7.6.2 Administration Guide 3392
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,392
|
System
Security
Level
Use case Behavior
Image verification failed!
...
Please continue only if you understand and are
willing to accept the risks.
Do you want to continue? (y/n)
During boot up:
Warning: FOS is not authenticated! Continue
booting under security level 1...
Initializing firewall...
After boot up:
System file integrity init check failed!
Upgrading on a device without BIOS security levels
The following use cases are applicable when upgrading firmware and AV files on a FortiGate without BIOS security
levels. Firmware is upgraded using the System > Firmware & Registration page, and AV files are upgraded using the
System > FortiGuard page. A FortiGate 60F is used in these examples and acts like it has security level 1.
When upgrading from 7.2.4 to 7.4.0 with a dually-signed firmware image, FortiOS verifies the certificates and accepts
the image.
When upgrading from 7.2.4 to 7.4.0 with an unsigned firmware image in the GUI, FortiOS is unable to verify the
certificates and the image fails verification. A warning dialog is displayed indicating that This firmware failed signature
validation, but the user can click Continue to use the firmware.
When running 7.4.0 and uploading an unsigned AV engine file on the System > FortiGuard page, FortiOS is unable to
verify the certificates and the file fails verification. A warning dialog is displayed indicating that This package file has no
signature for validation, but the user can click OK to use the file.
BIOS-level file integrity check on important file-system and object files
During bootup, the kernel is required to verify the signed hashes of important file-system and object files. This prevents
unauthorized changes to file-systems to be mounted and other unauthorized objects to be loaded into user space on
bootup.
This verification does not depend on the security level of the device. The verification will always run when the firmware
image type is a GA, SA, Beta, or Top3 image. If the signed hash verification fails, the system will halt during bootup.
Example
Upon detection of an altered IPS library file upon bootup, the system will halt as follows:
FortiGate-60F (18:03-01.27.2017)
Ver:05000012
Serial number: FGT60FTK1804xxxx
CPU: 1000MHz
Total RAM: 2 GB
Initializing boot device...
FortiOS 7.6.2 Administration Guide 3393
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,393
|
System
Initializing MAC... nplite#0
Please wait for OS to boot, or press any key to display configuration menu......
Booting OS...
Reading boot image... 2891501 bytes.
Initializing firewall...
fos_ima: System Integrity check failed....
CPU3: stopping
CPU1: stopping
CPU0: stopping
The exact display in the CLI may vary depending on the device model, security level, or
reasons for the failed verification.
Real-time file system integrity checking
Real-time file system integrity checking has two main purposes:
l Prevent unauthorized modification of important binaries.
l Detect unauthorized binaries and prevent them from running.
How it works
A hash of all executable binary files and shared libraries are taken during image build time. The file containing these
hashes, called the executable hash, is also hashed. This new hash is signed together with other important files like the
FortiOS firmware, AV and IPS engine files.
When the FortiGate boots, the system performs a BIOS level integrity check on the firmware image, the AV engine file,
and the IPS engine file. These files are signed by the process described in BIOS-level signature and file integrity
checking on page 3390, and the BIOS verifies their signature against their certificates. The hash of the executable hash
will also follow the BIOS-level signature and integrity check during the boot process, to prevent any unauthorized
changes from being loaded.
Once these files are verified to be authentic, the BIOS can extract and boot the root filesystem and other executables
and libraries, which then go through another file integrity check.
Once the file integrity checks passes, the corresponding hashes of every executable and shared library can be extracted
from the executable hash and loaded into memory. The system is started and real-time protection begins.
The important executables and binaries are protected from write access and any modifications. It also blocks the kernel
from loading any modules. Any unauthorized loading of modules is blocked. If violations are found, logs are triggered.
When each executable and shared library is initialized, it will be verified against its respective hashes to ensure integrity.
If there is a hash mismatch when attempting to run a binary, that binary is blocked from running, and the system is
rebooted. A log will be generated with ID 20234.
If there is a missing hash when attempting to run a binary, then the system is rebooted. A log will be generated with ID
20223.
The system also runs a periodic check to verify the integrity of important binaries and AV and IPS engines.
FortiOS 7.6.2 Administration Guide 3394
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,394
|
System
Log summary
The following logs are recorded when specific actions take place.
Log Description
20230 - LOG_ID_SYS_
SECURITY_WRITE_
VIOLATION 432
The root filesystem is read only. Any modification triggers this log.
20231 - LOG_ID_SYS_
SECURITY_HARDLINK_
VIOLATION 432
An attacker trying to replace symlink triggers this log.
20232 - LOG_ID_SYS_
SECURITY_LOAD_MODULE_
VIOLATION 433
Only the kernel can load modules. Any unusual loading of modules triggers this
log.
20233 - LOG_ID_SYS_
SECURITY_FILE_HASH_
MISSING 434
File hashes are generated for legitimate files during bootup. If a hash cannot be
found, the file may be suspicious as it could be a new routine inserted by an
attacker. The binary is blocked.
20234 - LOG_ID_SYS_
SECURITY_FILE_HASH_
MISMATCH 434
File hashes are generated for legitimate files during bootup. If a hash does not
match when the file is exercised, it is an indication that it could have been
modified by an attacker. The system is rebooted.
Detection examples
Example 1: system reboots due to mismatched hash
fos_ima: fos_process_appraise 110: Executable File(/bin/node) doesn't match previous hash,
it has been changed
Restarting system.
…
fos_ima: fos_process_appraise 110: Executable File(/lib/libc.so.6) doesn't match previous
hash, it has been changed
Restarting system.
…
Logs similar to the following are captured:
date="2023-06-16" time="12:01:44" id=7245222014288399309 bid=471609558 dvid=6533
itime=1686909705 euid=3 epid=3 dsteuid=3 dstepid=3 logver=604132092 logid="0100020234"
type="event" subtype="system" level="alert" msg="Hash of executable file(/bin/init) doesn't
match the previous." logdesc="Integrity check of Run/loading Excutable File failed without
Integrity measure" severity="alert" eventtime=1686909705825483706 tz="+0200"
devid="xxxxxxxxx" vd="root" devname="xxxxxxxxx"
date="2023-06-15" time="09:57:54" id=7244819017507013700 bid=470303007 dvid=1431
itime=1686815875 euid=3 epid=3 dsteuid=3 dstepid=3 logver=604132092 logid="0100020234"
type="event" subtype="system" level="alert" msg="Hash of executable file(/lib/libc.so.6)
doesn't match the previous." logdesc="Integrity check of Run/loading Excutable File failed
without Integrity measure" severity="alert" eventtime=1686815874936267770 tz="+0200" devid="
xxxxxxxxx " vd="root" devname=" xxxxxxxxx”
FortiOS 7.6.2 Administration Guide 3395
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,395
|
System
Example 2: suspected compromise due to an observed indicator of compromise (IoC)
fos_ima: fos_process_appraise 99: Suspicous Executable File(/data2/libcrashpad.so) is
missing hash
…
fos_ima: fos_process_appraise 99: Suspicous Executable File(/data2/flatkc_info) is missing
hash
…
No logs are found.
Corrective action
In the previous examples where a mismatched or missing hash occurs, alert technical support straight away so that they
may gather information to start a forensic analysis with our internal PSIRT team. There are two possible outcomes:
1. The firewall is reporting a false positive, in which a bug causes a mismatched or missing hash.
Once verified by technical support, the corrective action may to be upgrade to a newer build where the bug is fixed
2. An actual compromise has occurred, or is occurring.
The system could be blocking an offending binary that causes the system to malfunction, or the system could reboot
to protect itself from compromise.
In either case, contact technical support for further forensic analysis. If an IoC is detected and it is determined that the
persistent threat resides on the FortiGate, a reflash and reload of the firmware may be recommended.
Unauthorized firmware modification attempt reporting
In the rare event that unauthorized modification is detected in the firmware, the system will immediately log and report
the modification attempt to FortiGuard through a secure channel. Payloads are encrypted to ensure the security of the
transferred information. Information about the attempted modification of firmware helps Fortinet Inc. proactively
investigate the incident and protect future malicious attempts at compromising the system.
After reporting the modification attempt, the FortiGate real-time file system integrity checking feature continues with the
required actions based on the assessed threat. This may involve reverting the change and rebooting the firewall to
mitigate the threat.
Example
This example demonstrates when an attempt to alter files in the 'bin' directory was made by a threat actor.
Captured log:
1: date=2024-02-16 time=18:29:15 eventtime=1708136955710925685 tz="-0800" logid="0100020230"
type="event" subtype="system" level="alert" vd="vd1" logdesc="Write Permission Violation"
msg="[Write Violation: try to write readonly file](/bin/lspci)."
The FortiGate sends an encrypted report to FortiGuard with information about the affected platform and the Modification
Attempt such as:
l FortiGate serial number
l Model number
l FortiOS firmware
FortiOS 7.6.2 Administration Guide 3396
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,396
|
System
l Type of modification attempt (such as Write violation)
l File path (such as /bin/lspci)
l File size
l Time of access and modification
Running a file system check automatically
There is an option in FortiOS to enable automatic file system checks if the FortiGate shuts down ungracefully.
By default, the automatic file system check is disabled. When an administrator logs in after an ungraceful shutdown, a
warning message appears advising them to manually run a file system check. A warning also appears in the CLI:
WARNING: File System Check Recommended! Unsafe reboot may have caused inconsistency in disk
drive.
It is strongly recommended that you check file system consistency before proceeding.
Please run 'execute disk scan 17'
Note: The device will reboot and scan during startup. This may take up to an hour
Enabling automatic file system checks
You can enable automatic file system checks in both the GUI and CLI.
To enable automatic file system checks in the GUI:
1. Go to System > Settings.
2. In the Start Up Settings section, enable Auto file system check.
3. Click Apply.
To enable automatic file system checks using the CLI:
config system global
set autorun-log-fsck enable
end
FortiOS 7.6.2 Administration Guide 3397
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,397
|
System
Built-in entropy source
FortiOS includes a built-in entropy source, which eliminates the need for a physical USB entropy token when booting up
in FIPS mode on any platform. This enhancement continues to meet the requirements of FIPS 140-3 Certification by
changing the source of entropy to CPU jitter entropy.
The entropy-token parameter under config system fips-cc is removed if the
FortiGate is a SoC3, SoC4, or CP9 device.
To verify that jitter entropy is used:
1. Enable FIPS-CC mode, which will cause the FortiGate to reboot:
config system fips-cc
set status enable
end
Please enter admin administrator password:********
Please re-enter admin administrator password:********
Warning: most configuration will be lost,
do you want to continue?(y/n) y
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system.
...
Reading boot image 2919154 bytes.
Initializing firewall...
System is starting...
FIPS-CC mode: Starting self-tests.
Running Configuration/VPN Bypass test... passed
Running AES test... passed
Running SHA1-HMAC test... passed
Running SHA256-HMAC test... passed
Running SHA384/512-HMAC test... passed
Running RSA test... passed
Running ECDSA test... passed
Running TLS1.1-KDF test... passed
Running TLS1.2-KDF test... passed
Running SSH-KDF test... passed
Running IKEv1-KDF test... passed
Running IKEv2-KDF test... passed
Running Primitive-Z test... passed
Running Firmware integrity test... passed
Running RBG-instantiate test... passed
Running RBG-reseed test... passed
Running RBG-generate test... passed
Self-tests passed
2. Verify the entropy token user event logs:
FortiOS 7.6.2 Administration Guide 3398
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,398
|
System
# execute log filter category event
# execute log filter field logid 0102038012
# execute log display
3 logs found.
3 logs returned.
1: date=2023-07-18 time=20:27:56 eventtime=1689737275853093806 tz="-0700"
logid="0102038012" type="event" subtype="user" level="notice" vd="root" logdesc="Seeding
from entropy source" user="system" action="reseeding" msg="Reseeding PRNG from JitterEnt
entropy"
2: date=2023-07-18 time=20:26:56 eventtime=1689737146847643497 tz="-0700"
logid="0102038012" type="event" subtype="user" level="notice" vd="root" logdesc="Seeding
from entropy source" user="system" action="seeding" msg="Seeding PRNG from JitterEnt
entropy"
3: date=2023-07-18 time=19:29:25 eventtime=1689733702417108422 tz="-0700"
logid="0102038012" type="event" subtype="user" level="notice" vd="root" logdesc="Seeding
from entropy source" user="system" action="seeding" msg="Seeding PRNG from JitterEnt
entropy"
FortiGate VM unique certificate
To safeguard against certificate compromise, FortiGate VM and FortiAnalyzer VM use the same deployment model as
FortiManager VM where the license file contains a unique certificate tied to the serial number of the virtual device.
A hardware appliance usually comes with a BIOS certificate with a unique serial number that identifies the hardware
appliance. This built-in BIOS certificate is different from a firmware certificate. A firmware certificate is distributed in all
appliances with the same firmware version.
Using a BIOS certificate with a built-in serial number provides a high trust level for the other side in X.509 authentication.
Since a VM appliance has no BIOS certificate, a signed VM license can provide an equivalent of a BIOS certificate. The
VM license assigns a serial number in the BIOS equivalent certificate. This gives the certificate an abstract access
ability, which is similar to a BIOS certificate with the same high trust level.
Sample configurations
Depending on the firmware version and VM license, the common name (CN) on the certificate will be configured
differently.
License Firmware
6.0 6.2 and later
6.0 CN = FortiGate CN = FortiGate
6.2 and later CN = FortiGate CN = serial number
To view validated certificates:
1. Go to System > Certificates.
2. Double-click on a VM certificate. There are two VM certificates:
FortiOS 7.6.2 Administration Guide 3399
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,399
|
System
l Fortinet_Factory
l Fortinet_Factory_Backup
The Certificate Detail Information window displays.
Closed network VM license security
The CMS signature is verified immediately after the license is loaded. This ensures that the license is from FortiCare and
confirms the authenticity of the license's contents and contracts, enhancing license integrity and customer trust.
If a valid offline license with a CMS signature is loaded:
FGVM2VTM22222222# get system status
Version: FortiGate-VM64-KVM v7.6.0,build9999,240524
First GA patch build date: 230509
Security Level: 0
Firmware Signature: not-certified
...
Serial-Number: FGVM2VTM22222222
License Status: Valid
License Expiration Date: 2024-08-02
VM Resources: 1 CPU/2 allowed, 1992 MB RAM
...
FGVM2VTM22222222# diagnose debug vm-print-license
SerialNumber: FGVM2VTM22222222
CreateDate: Wed Mar 20 18:47:49 2024
License expires: Fri Aug 2 00:00:00 2024
Expiry: 134
UUID: fdbf7aa999999999a9999aa578127e67
Default Contract:
FMWR:6:20230802:20240804,ENHN:20:20230802:20240804,...,IPMC:6:20230802:20240804
Key: yes
Cert: yes
Key2: yes
Cert2: yes
Signature: yes
Model: 2V (6)
CPU: 2
MEM: 2147483647
VDOM license:
permanent: 2
subscription: 0
If an old offline license without a CMS signature is loaded:
FGVM2VTM22222222# get system status
Version: FortiGate-VM64-KVM v7.6.0,build9999,240524
First GA patch build date: 230509
Security Level: 0
Firmware Signature: not-certified
...
Serial-Number: FGVM2VTM22222222
License Status: Invalid
License Expiration Date: 2024-08-02
FortiOS 7.6.2 Administration Guide 3400
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,400
|
System
VM Resources: 1 CPU/2 allowed, 1992 MB RAM
...
FGVM2VTM22222222# diagnose debug vm-print-license
SerialNumber: FGVM2VTM22222222
CreateDate: Wed Aug 2 20:18:51 2023
License expires: Fri Aug 2 00:00:00 2024
Expiry: 365
UUID: fdbf7aa999999999a9999aa578127e67
Default Contract:
FMWR:6:20230802:20240804,ENHN:20:20230802:20240804,...,IPMC:6:20230802:20240804
Key: yes
Cert: yes
Key2: yes
Cert2: yes
Model: 2V (6)
CPU: 2
MEM: 2147483647
VDOM license:
If an offline license with a modified CMS signature is loaded the license is invalid and there is no
signature:
FGVM2VTM22222222# get system status
Version: FortiGate-VM64-KVM v7.6.0,build9999,240524
First GA patch build date: 230509
Security Level: 0
Firmware Signature: not-certified
...
Serial-Number: FGVM2VTM22222222
License Status: Invalid
License Expiration Date: 2024-08-02
VM Resources: 1 CPU/2 allowed, 1992 MB RAM
...
FGVM2VTM22222222# diagnose debug vm-print-license
SerialNumber: FGVM2VTM22222222
CreateDate: Wed Mar 20 18:47:49 2024
License expires: Fri Aug 2 00:00:00 2024
Expiry: 134
UUID: fdbf7aa999999999a9999aa578127e67
Default Contract:
FMWR:6:20230802:20240804,ENHN:20:20230802:20240804,...,IPMC:6:20230802:20240804
Key: yes
Cert: yes
Key2: yes
Cert2: yes
Model: 2V (6)
CPU: 2
MEM: 2147483647
VDOM license:
permanent: 2
subscription: 0
FortiOS 7.6.2 Administration Guide 3401
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,401
|
System
Encrypt configuration files in the eCryptfs file system
Configuration files are encrypted in the eCryptfs file system when the system reboots or shuts down, and are decrypted
when the system boots up and has to load the configuration to CMDB.
If the device supports TPM, the 32 byte eCryptfs encryption key is randomly generated and stored in the TPM, like the
private-data-encryption key. If the device does not support TPM, the key is generated by the cryptographically secure
pseudorandom number generator (CSPRNG) and stored on the disk. See Trusted platform module support on page
3066 and TPM support for FortiGate-VM on page 4007 for more information.
FIPS-CC mode and OpenSSL FIPS provider
When the device is in FIPS-CC mode, the OpenSSL FIPS provider is installed globally at startup, ensuring that any
OpenSSL application is automatically compliant with FIPS regulations. An OpensSSL FIPS provider test (ossl-fipsprovider-test) is added, and the self-test runs automatically at startup. The TLSv1.1 KDF self-test is removed.
The system defaults to the more secure TLSv1.2 and TLSv1.3 protocols instead of SSL3.0 and TLS1.1, and only DiffieHellman parameters of 2048 bits or higher are permitted, ensuring a robust security posture and aligning with industry
standards.
When configuring a RADIUS server, Authentication method (auth-type) can only be set to PAP (password
authentication protocol), and transport-protocol can only be set to tls.
To manually run the OpenSSL FIPS provider self-test:
# execute fips kat ossl-fips-provider-test
HMAC : KAT_Integrity : Pass
HMAC : Module_Integrity : Pass
SHA1 : KAT_Digest : Pass
SHA2 : KAT_Digest : Pass
SHA3 : KAT_Digest : Pass
AES_GCM : KAT_Cipher : Pass
AES_ECB_Decrypt : KAT_Cipher : Pass
RSA : KAT_Signature : Pass
ECDSA : KAT_Signature : Pass
ECDSA : KAT_Signature : Pass
FortiOS 7.6.2 Administration Guide 3402
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,402
|
System
DSA : KAT_Signature : Pass
TLS13_KDF_EXTRACT : KAT_KDF : Pass
TLS13_KDF_EXPAND : KAT_KDF : Pass
TLS12_PRF : KAT_KDF : Pass
PBKDF2 : KAT_KDF : Pass
SSHKDF : KAT_KDF : Pass
KBKDF : KAT_KDF : Pass
HKDF : KAT_KDF : Pass
SSKDF : KAT_KDF : Pass
X963KDF : KAT_KDF : Pass
X942KDF : KAT_KDF : Pass
HASH : DRBG : Pass
CTR : DRBG : Pass
HMAC : DRBG : Pass
DH : KAT_KA : Pass
ECDH : KAT_KA : Pass
RSA_Encrypt : KAT_AsymmetricCipher : Pass
RSA_Decrypt : KAT_AsymmetricCipher : Pass
RSA_Decrypt : KAT_AsymmetricCipher : Pass
Running OSSL-FIPS-TEST test... passed
Configuration scripts
Configuration scripts are text files that contain CLI command sequences. They can be created using a text editor or
copied from a CLI console, either manually or using the Record CLI Script function.
Scripts can be used to run the same task on multiple devices. For example, if your devices use the same security
policies, you can enter or record the commands to create those policies in a script, and then run the script on each
device. You could also create the policies in the GUI, and then copy and paste the CLI commands from the CLI Console
using the show command.
If the FortiGate is managed by FortiManager, scripts can be uploaded to FortiManager and then run on any other
FortiGates that are managed by that FortiManager. See Scripts in the FortiManager Administration Guide.
A comment line in a script starts with the number sign (#). Comments are not executed.
To run a script using the GUI:
1. Click on your username and select Configuration > Scripts.
2. Click Run Script.
3. Select the text file containing the script on your management computer, then click OK.
The script runs immediately, and the Script Execution History table is updated, showing if the script ran
successfully.
FortiOS 7.6.2 Administration Guide 3403
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,403
|
System
Workspace mode
Workspace mode allows administrators to make a batch of changes that are not implemented until the transaction is
committed. Prior to committing, the changes can be reverted or edited as needed without impacting current operations.
When an object is edited in workspace mode it is locked, preventing other administrators from editing that object. A
warning message will be shown to let the administrator know that the object is currently being configured in another
transaction.
All administrators can use workspace mode; their permissions in workspace mode are the same as defined in their
account profile.
A workspace mode transaction times out after five minutes if there is no activity. When a transaction times out, all
changes are discarded. A warning message will be shown to let the administrator know that a timeout is imminent, or has
already happened:
config transaction id=1 will expire in 30 seconds
config transaction id=1 will expire in 20 seconds
config transaction id=1 will expire in 10 seconds
config transaction id=1 has expired
The following commands are not changeable in a workspace transaction:
config system console
config system resource-limits
config system elbc
config system global
set split-port
set vdom-admin
set management-vdom
set wireless-mode
set internal-switch-mode
end
config system settings
set opmode
end
config system npu
config system np6
config system wireless
set mode
end
config system vdom-property
config system storage
The execute batch command cannot be used in or to start workspace mode.
FortiOS 7.6.2 Administration Guide 3404
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,404
|
System
To use workspace mode:
1. Start workspace mode:
execute config-transaction
Once in workspace mode, the administrator can make configuration changes, all of which are made in a local CLI
process that is not viewable by other processes.
2. Commit configuration changes:
execute config-transaction commit
After performing the commit, the changes are available for all other processes, and are also made in the kernel.
3. Abort configuration changes:
execute config-transaction abort
If changes are aborted, no changes are made to the current configuration or the kernel.
Diagnose commands
diagnose sys config-transaction show txn-meta
Show config transaction meta information. For example:
# diagnose sys config-transaction show txn-meta
txn_next_id=8, txn_nr=2
diagnose sys config-transaction show txn-info
Show config transaction information. For example:
# diagnose sys config-transaction show txn-info
current_jiffies=680372
txn_id=6, expire_jiffies=706104, clicmd_fpath='/dev/cmdb/txn/6_EiLl9G.conf'
txn_id=7, expire_jiffies=707427, clicmd_fpath='/dev/cmdb/txn/7_UXK6wY.conf'
diagnose sys config-transaction show txn-entity
Show config transaction entity. For example:
# diagnose sys config-transaction show txn-entity
vd='global', cli-node-oid=37(system.vdom), txn_id=7. location: fileid=0, storeid=0,
pgnr=0, pgidx=0
vd='global', cli-node-oid=46(system.interface), txn_id=7. location: fileid=3,
storeid=0, pgnr=0, pgidx=0
diagnose sys config-transaction show txn-lock
Show transaction lock status. For example:
# diagnose sys config-transaction show txn-lock
type=-1, refcnt=0, value=256, pid=128
diagnose sys config-transaction status
Show the transaction status in the current CLI.
FortiOS 7.6.2 Administration Guide 3405
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,405
|
System
Custom languages
Custom languages can be uploaded and used for SSL VPN web portals. Custom languages must be enabled before
they can be added in the GUI.
To enable custom languages:
config system global
set gui-custom-language enable
end
To configure a custom language in the GUI:
1. Go to System > Custom Languages and click Create New.
2. Enter the name of the language.
3. Optionally, enter a comment.
4. Click Upload and upload the language JSON file from your management computer.
5. Click OK.
To configure a language in an SSL VPN web portal in the GUI:
1. Go to VPN > SSL-VPN Portals.
2. Edit an existing portal, or click Create New to create a new one.
3. Enable Enable Web Mode, then select the language from the Language field.
4. Click OK.
To configure a custom language in the CLI:
config system custom-language
edit <language>
set filename <file>
FortiOS 7.6.2 Administration Guide 3406
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,406
|
System
next
end
To configure a language in an SSL VPN web portal in the GUI:
config vpn ssl web portal
edit <portal>
set web-mode enable
set custom-lang <language>
next
end
RAID
Most FortiGate devices with multiple disk drives (SSD or HHD) can be configured to use RAID.
Enabling or disabling RAID, and changing the RAID level, erases all data on the log disk and
reboots the device.
To verify that the FortiGate has multiple disks:
l List disk devices and partitions:
# execute disk list
Disk SSD1 ref: 255 223.6GiB type: SSD [ATA INTEL SSDSC2KB24] dev: /dev/sda
partition ref: 1 220.1GiB, 219.0GiB free mounted: Y label: LOGUSEDXA707476A dev:
/dev/sda1 start: 2048
Disk SSD2 ref: 16 223.6GiB type: SSD [ATA INTEL SSDSC2KB24] dev: /dev/sdb
partition ref: 17 62.7GiB, 62.4GiB free mounted: Y label: WANOPTXX1FEBBFA1 dev:
/dev/sdb1 start: 2048
partition ref: 18 63.7GiB, 63.7GiB free mounted: N label: dev: /dev/sdb2 start:
133625856
partition ref: 19 85.0GiB, 85.0GiB free mounted: N label: dev: /dev/sdb3 start:
267249664
l Display information about all of the disks:
# diagnose hardware deviceinfo disk
Disk SSD1 ref: 255 223.6GiB type: SSD [ATA INTEL SSDSC2KB24] dev: /dev/sda
partition ref: 1 220.1GiB, 219.0GiB free mounted: Y label: LOGUSEDXA707476A dev:
/dev/sda1 start: 2048
Disk SSD2 ref: 16 223.6GiB type: SSD [ATA INTEL SSDSC2KB24] dev: /dev/sdb
partition ref: 17 62.7GiB, 62.4GiB free mounted: Y label: WANOPTXX1FEBBFA1 dev:
/dev/sdb1 start: 2048
partition ref: 18 63.7GiB, 63.7GiB free mounted: N label: dev: /dev/sdb2 start:
133625856
partition ref: 19 85.0GiB, 85.0GiB free mounted: N label: dev: /dev/sdb3 start:
FortiOS 7.6.2 Administration Guide 3407
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,407
|
System
267249664
Disk SYSTEM(boot) 14.9GiB type: SSD [ATA 16GB SATA Flash] dev: /dev/sdc
partition 247.0MiB, 155.0MiB free mounted: N label: dev: /dev/sdc1(boot) start: 1
partition 247.0MiB, 154.0MiB free mounted: Y label: dev: /dev/sdc2(boot) start: 524289
partition ref: 35 14.2GiB, 14.0GiB free mounted: Y label: dev: /dev/sdc3 start:
1048577
Disk USB-6(user-usb) ref: 48 28.6GiB type: USB [SanDisk Ultra] dev: /dev/sdd
<<<<<<===this info for usb disk because i have usb disk on FGT301E
partition ref: 49 28.6GiB, 28.6GiB free mounted: Y label: dev: /dev/sdd1 start: 0
Total available disks: 4
Max SSD disks: 2 Available storage disks: 2
To check the RAID status:
l RAID enabled:
# execute disk raid status
RAID Level: Raid-1
RAID Status: OK (Background-Synchronizing) (9%)
RAID Size: 239GB
Disk 1: OK Used 228GB
Disk 2: OK Used 228GB
l RAID disabled:
# execute disk raid status
RAID Level: Unavailable
RAID Status: Unavailable
RAID Size: 0GB
Disk 1: OK Not-Used 228GB
Disk 2: OK Not-Used 228GB
To enable RAID:
# execute disk raid enable
This will erase all data on the log disk, and system will reboot!
Do you want to continue? (y/n)y
Dependent storage SSD2 removed.
Dependent storage SSD1 removed.
Raid-0 created with 2 disks.
Performing raid on the requested disk(s) and rebooting, please wait.. .
Configuring raid...
- unmounting /data2 : ok
- unmounting /var/log : ok
- unmounting /usb : ok
- unmounting /var/storage/SSD2-WANOPTXX0EA0EF17 : ok
Formatting the disk...
- unmounting /usb : ok
FortiOS 7.6.2 Administration Guide 3408
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,408
|
System
Formatting /dev/md0 ... done
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system.
To rebuild the RAID:
# execute disk raid rebuild
To rebuild the RAID to another level:
1. Check the supported RAID levels:
# execute disk raid rebuild-level
<RAID level> supported: Raid-0, Raid-1
2. Rebuild the RAID to the required level:
# execute disk raid rebuild-level Raid-1
This will erase all data on the log disk, and system will reboot!
Do you want to continue? (y/n)y
Dependent storage RAID removed.
Raid-1 created with 2 disks.
Performing raid on the requested disk(s) and rebooting, please wait...
Configuring raid...
- unmounting /data2 : ok
- unmounting /var/log : ok
- unmounting /usb : ok
Formatting the disk...
- unmounting /usb : ok
Formatting /dev/md0 ... done
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system.
To disable RAID:
# execute disk raid disable
This will erase all data on the log disk, and system will reboot!
Do you want to continue? (y/n)y
Dependent storage RAID removed.
Performing format on the requested disk(s) and rebooting, please wait...
Configuring raid...
- unmounting /data2 : ok
FortiOS 7.6.2 Administration Guide 3409
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,409
|
System
- unmounting /var/log : ok
- unmounting /usb : ok
Formatting the disk...
Partitioning and formatting /dev/sda label LOGUSEDX3D36836D ... done
Partitioning and formatting /dev/sdb label WANOPTXX1FEBBFA1 ...
Sending request for partno=0 start=2048 stop=133624230
Sending request for partno=1 start=133625856 stop=267248460
Sending request for partno=2 start=267249664 stop=445414150
done
The system is going down NOW !!
Please stand by while rebooting the system.
Restarting system.
FortiGate-301E (11:11-04.30.2018)
.
Reading boot image 3017355 bytes.
Initializing firewall...
System is starting...
FortiGate encryption algorithm cipher suites
FortiGates use SSL/TLS encryption for HTTPS and SSH administrative access, and SSL VPN remote access. When
establishing an SSL/TLS or SSH connection, you can control the encryption level and the ciphers that are used in order
to control the security level.
HTTPS access
HTTP administrative access encryption is controlled using the following commands:
config system global
set strong-crypto {enable | disable}
set admin-https-ssl-versions {tlsv1-1 tlsv1-2 tlsv1-3}
set admin-https-ssl-ciphersuites {<cipher_1> ... <cipher_n>}
set admin-https-ssl-banned-ciphers {<cipher_1> ... <cipher_n>}
end
When strong encryption is enabled, only TLS 1.2 and TLS 1.3 are allowed. If strong encryption is then disabled, TLS 1.1
has to be manually enabled.
Setting admin-https-ssl-ciphersuites controls which cipher suites are offered in TLS 1.3. TLS 1.2 and lower are
not affected by this command. To disable all TLS 1.3 cipher suites, remove TLS1-3 from admin-https-sslversions.
Setting admin-https-ssl-banned-ciphers controls which cipher technologies will not be offered for TLS 1.2 and
lower.
Specific cipher suites are supported by each TLS version:
FortiOS 7.6.2 Administration Guide 3410
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,410
|
System
TLS version Supported cipher suites
TLS 1.11
ECDHE-RSA-AES256-SHA1 AES256-SHA1
ECDHE-RSA-AES128-SHA1 AES128-SHA1
TLS 1.2
ECDHE-RSA-AES256-GCM-SHA384 AES256-GCM-SHA3841
ECDHE-RSA-AES128-GCM-SHA256 AES128-GCM-SHA2561
ECDHE-RSA-CHACHA20-POLY1305 AES256-SHA256
ECDHE-RSA-AES256-SHA384 AES128-SHA256
ECDHE-RSA-AES128-SHA256 AES256-SHA1
ECDHE-RSA-AES256-SHA1 AES128-SHA1
ECDHE-RSA-AES128-SHA1
TLS 1.3
TLS-AES-128-GCM-SHA256 TLS-AES-128-CCM-8-SHA256
TLS-AES-256-GCM-SHA384 TLS-CHACHA20-POLY1305-SHA256
TLS-AES-128-CCM-SHA256
1 Disabled if strong encryption (strong-crypto) is enabled.
SSH access
SSH access encryption is controlled using the following command:
config system global
set admin-ssh-v1 {enable | disable}
set strong-crypto {enable | disable}
end
config system ssh-config
set ssh-enc-algo <algo_1> [<algo_2> ... <algo_n>]
set ssh-hsk-algo <algo_1> [<algo_2> ... <algo_n>]
set ssh-kex-algo <algo_1> [<algo_2> ... <algo_n>]
set ssh-mac-algo <algo_1> [<algo_2> ... <algo_n>]
end
The algorithms available when configuring set ssh-enc-algo are affected by set strong-crypto as follows:
Strong encryption
setting Supported ciphers
Enabled aes256-gcm@openssh.com aes256-ctr
FortiOS 7.6.2 Administration Guide 3411
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,411
|
System
Strong encryption
setting Supported ciphers
Disabled
chacha20-poly1305@openssh.com aes128-ctr
aes192-ctr aes256-ctr
arcfour256 arcfour128
aes128-cbc 3des-cbc
blowfish-cbc cast128-cbc
aes192-cbc aes256-cbc
arcfour rijndael-cbc@lysator.liu.se
aes128-gcm@openssh.com aes256-gcm@openssh.com
The following options are available for the ssh-hsk-algo algorithm based on the strong encryption setting:
Strong encryption
setting Supported ciphers
Enabled
ecdsa-sha2-nistp521 ecdsa-sha2-nistp384
ecdsa-sha2-nistp256 rsa-sha2-256
rsa-sha2-512 ssh-ed25519
Disabled
ssh-rsa ecdsa-sha2-nistp521
ecdsa-sha2-nistp384 ecdsa-sha2-nistp256
rsa-sha2-256 rsa-sha2-512
ssh-ed25519
The following options are available for the ssh-kex-algo algorithm based on the strong encryption setting:
Strong encryption
setting Supported ciphers
Enabled
diffie-hellman-group14-sha256 diffie-hellman-group16-sha512
diffie-hellman-group18-sha512 diffie-hellman-group-exchange-sha256
curve25519-sha256@libssh.org ecdh-sha2-nistp256
ecdh-sha2-nistp384 ecdh-sha2-nistp521
FortiOS 7.6.2 Administration Guide 3412
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,412
|
System
Strong encryption
setting Supported ciphers
Disabled
diffie-hellman-group14-sha1 diffie-hellman-group14-sha256
diffie-hellman-group16-sha512 diffie-hellman-group18-sha512
diffie-hellman-group-exchange-sha1 diffie-hellman-group-exchange-sha256
curve25519-sha256@libssh.org ecdh-sha2-nistp256
ecdh-sha2-nistp384 ecdh-sha2-nistp521
The following options are available for the ssh-mac-algo algorithm based on the strong encryption setting:
Strong encryption
setting Supported ciphers
Enabled
hmac-sha2-256 hmac-sha2-256-etm@openssh.com
hmac-sha2-512 hmac-sha2-512-etm@openssh.com
Disabled
hmac-md5 hmac-md5-etm@openssh.com
hmac-md5-96 hmac-md5-96-etm@openssh.com
hmac-sha1 hmac-sha1-etm@openssh.com
hmac-sha2-256 hmac-sha2-256-etm@openssh.com
hmac-sha2-512 hmac-sha2-512-etm@openssh.com
hmac-ripemd160 hmac-ripemd160@openssh.com
hmac-ripemd160-etm@openssh.com umac-64@openssh.com
umac-128@openssh.com umac-64-etm@openssh.com
umac-128-etm@openssh.com
SSL VPN
For SSL VPN connections, the TLS versions and cipher suites are controlled using the following commands:
config vpn ssl setting
set algorithm {high | medium | low}
set ssl-max-proto-ver {tls1-0 | tls1-1 | tls1-2 | tls1-3}
set ssl-min-proto-ver {tls1-0 | tls1-1 | tls1-2 | tls1-3}
set ciphersuite {TLS-AES-128-GCM-SHA256 TLS-AES-256-GCM-SHA384 TLS-CHACHA20-POLY1305-
SHA256 TLS-AES-128-CCM-SHA256 TLS-AES-128-CCM-8-SHA256}
end
Only cipher suites supported by TLS 1.3 can be set using the set ciphersuite command.
FortiOS 7.6.2 Administration Guide 3413
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,413
|
System
When the SSL VPN security level (algorithm) is set to high, only high levels are allowed. When it is set to medium,
high and medium levels are allowed. When it is set to low, any level is allowed.
The strong encryption (strong-crypto) command has no effect on the SSL VPN encryption level or ciphers.
Specific cipher suites are supported by each TLS version:
TLS version Supported cipher suites
TLS 1.0
ECDHE-RSA-AES256-SHA DHE-RSA-CAMELLIA128-SHA
DHE-RSA-AES256-SHA AES128-SHA
DHE-RSA-CAMELLIA256-SHA SEED-SHA1
AES256-SHA CAMELLIA128-SHA
CAMELLIA256-SHA ECDHE-RSA-DES-CBC3-SHA1*
ECDHE-RSA-AES128-SHA EDH-RSA-DES-CBC3-SHA1*
DHE-RSA-AES128-SHA1 DES-CBC3-SHA1*
DHE-RSA-SEED-SHA
TLS 1.1
ECDHE-RSA-AES256-SHA DHE-RSA-CAMELLIA128-SHA
DHE-RSA-AES256-SHA AES128-SHA
DHE-RSA-CAMELLIA256-SHA SEED-SHA1
AES256-SHA CAMELLIA128-SHA
CAMELLIA256-SHA ECDHE-RSA-DES-CBC3-SHA1*
ECDHE-RSA-AES128-SHA EDH-RSA-DES-CBC3-SHA1*
DHE-RSA-AES128-SHA DES-CBC3-SHA1*
DHE-RSA-SEED-SHA1
FortiOS 7.6.2 Administration Guide 3414
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,414
|
System
TLS version Supported cipher suites
TLS 1.2
ECDHE-RSA-AES256-GCM-SHA384 ECDHE-RSA-AES128-SHA
ECDHE-RSA-AES256-SHA384 DHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES256-SHA DHE-RSA-AES128-CCM8
DHE-RSA-AES256-GCM-SHA384 DHE-RSA-AES128-CCM
ECDHE-RSA-CHACHA20-POLY1305 AES128-CCM8
DHE-RSA-CHACHA20-POLY1305 AES128-CCM
DHE-RSA-AES256-CCM8 DHE-RSA-AES128-SHA256
DHE-RSA-AES256-CCM DHE-RSA-AES128-SHA
DHE-RSA-AES256-SHA256 ECDHE-RSA-CAMELLIA128-SHA256
DHE-RSA-AES256-SHA DHE-RSA-CAMELLIA128-SHA256
ECDHE-RSA-CAMELLIA256-SHA384 DHE-RSA-SEED-SHA1
DHE-RSA-CAMELLIA256-SHA256 DHE-RSA-CAMELLIA128-SHA
DHE-RSA-CAMELLIA256-SHA AES128-GCM-SHA256
AES256-GCM-SHA384 AES128-SHA256
AES256-CCM8 AES128-SHA
AES256-CCM CAMELLIA128-SHA256
AES256-SHA256 SEED-SHA1
AES256-SHA CAMELLIA128-SHA
CAMELLIA256-SHA256 ARIA128-GCM-SHA256
CAMELLIA256-SHA DHE-RSA-ARIA128-GCM-SHA256
ARIA256-GCM-SHA384 ECDHE-ARIA128-GCM-SHA256
DHE-RSA-ARIA256-GCM-SHA384 ECDHE-RSA-AES256-GCM-SHA384
ECDHE-ARIA256-GCM-SHA384 ECDHE-RSA-DES-CBC3-SHA1*
ECDHE-RSA-AES128-GCM-SHA256 EDH-RSA-DES-CBC3-SHA1*
ECDHE-RSA-AES128-SHA256 DES-CBC3-SHA1*
TLS 1.3
TLS_AES_256_GCM_SHA384 TLS_AES_128_CCM_SHA256
TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_8_SHA256
TLS_AES_128_GCM_SHA256
1 This cipher is not available when the SSL VPN security level (algorithm) is set to high.
* This cipher is not available when the SSL VPN security level (algorithm) is set to medium.
FortiOS 7.6.2 Administration Guide 3415
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,415
|
System
Additional features
Security hardening for other FortiOS features can also be achieved by managing the encryption level or ciphers. See
SSL algorithm security level on page 3417 for more information about different levels of security.
An asterisk (*) represents the default values for each feature.
Some of these features are described next.
WAN optimization
For WAN optimization tunnel connections, the encryption algorithm is controlled using the following commands:
config wanopt settings
set tunnel-ssl-algorithm {high* | medium | low}
end
Explicit FTP proxy
For explicit FTP proxy, the encryption algorithm is controlled using the following commands:
config ftp-proxy explicit
set ssl-algorithm { high* | medium | low}
end
Explicit web proxy
For explicit web proxy, the encryption algorithm is controlled using the following commands:
config web-proxy explicit
set ssl-algorithm {high | medium | low*}
end
SSL Server
For SSL server, the TLS versions and the encryption algorithm are controlled using the following commands:
config firewall ssl-server
edit <name>
set ssl-algorithm {high* |medium | low}
set ssl-max-version {tls-1.0* |tls-1.1 | tls-1.2 | tls-1.3}
set ssl-min-version {tls-1.0 |tls-1.1 | tls-1.2 | tls-1.3*}
next
end
VIP
For VIP, the TLS versions and the encryption algorithm are controlled using the following commands:
FortiOS 7.6.2 Administration Guide 3416
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,416
|
System
config firewall vip
set ssl-max-version {ssl-3.0|tls-1.1 | tls1-2 | tls-1.3* | client}
set ssl-min-version {ssl-3.0|tls-1.1* | tls1-2 | tls-1.3 |client}
set ssl-algorithm {high* | medium | low | custom}
config ssl-cipher-suites
edit <priority>
set cipher {TLS-AES-128-GCM-SHA256 | TLS-AES-256-GCM-SHA384|...}
set versions {option1}, {option2}, ...
next
end
set ssl-server-max-version [ssl-3.0|tls-1.1 | tls1-2 | tls-1.3 | client*}
set ssl-server-min-version [ssl-3.0|tls-1.1 | tls1-2 | tls-1.3 | client*}
set ssl-server-algorithm {high | medium | low | custom | client* }
config ssl-server-cipher-suites
edit <priority>
set cipher {TLS-AES-128-GCM-SHA256 | TLS-AES-256-GCM-SHA384|...}
set versions {option1}, {option2}, ...
next
end
next
end
The command config ssl-cipher-suites is available only under certain conditions:
l When set type is set to either server-load-balance or access-proxy
l When set ssl-algorithm is set to custom
Similarly, the command config ssl-server-cipher-suites is available only under
certain conditions:
l When set type is set to server-load-balance
l When set ssl-mode is set to full
l When set ssl-algorithm is set to custom
VoIP
For VoIP, the TLS versions and the encryption algorithm are controlled using the following commands:
config voip profile
edit <name>
config sip
set ssl-algorithm {high* |medium | low}
set ssl-max-version {ssl-3.0 | tls-1.0* |tls-1.1 | tls-1.2 | tls-1.3}
set ssl-min-version {ssl-3.0 | tls-1.0 |tls-1.1 | tls-1.2 | tls-1.3*}
next
end
SSL algorithm security level
Option Description
high High encryption. Allow only AES and ChaCha.
FortiOS 7.6.2 Administration Guide 3417
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,417
|
System
Option Description
medium Medium encryption. Allow AES, ChaCha, 3DES, and RC4.
low Low encryption. Allow AES, ChaCha, 3DES, RC4, and DES.
*custom Custom encryption. Use ssl-server-cipher-suites to select the cipher
suites that are allowed.
*client Use the same encryption algorithms for both client and server sessions.
The SSL algorithm security levels marked with an asterisk (*) are not supported across
different FortiOS features.
Other Products
The security level of communication to and from FortiOS can be managed by controlling the encryption level and ciphers
used. See Encryption algorithm security level on page 3419 for more information about different levels of security.
An asterisk (*) represents the default value for each product.
Some products that commonly interact with the FortiGate device are listed next.
syslog server
For syslog server, the TLS versions and the encryption algorithm are controlled using the following commands:
config log syslogd setting
set enc-algorithm {high-medium | high | low | disable*}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2}
end
config log syslogd override-setting
set enc-algorithm {high-medium | high | low | disable*}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2}
end
The command ssl-min-proto-version set to default means that the system global
setting will be followed.
FortiCloud
For logging to FortiCloud, the TLS versions and the encryption algorithm are controlled using the following commands:
FortiOS 7.6.2 Administration Guide 3418
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,418
|
System
config log fortiguard setting
set enc-algorithm {high-medium | high* | low}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2}
end
FortiAnalyzer Cloud
For FortiAnalyzer Cloud, the TLS versions and the encryption algorithm are controlled using the following commands:
config log fortianalyzer-cloud setting
set enc-algorithm {high-medium | high* | low}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2 | TLSv1-3}
end
FortiAnalyzer
For FortiAnalyzer, the TLS versions and the encryption algorithm are controlled using the following commands:
config log fortianalyzer setting
set enc-algorithm {high-medium | high* | low}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2 | TLSv1-3}
end
config log fortianalyzer override-setting
set enc-algorithm {high-medium | high* | low}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2 | TLSv1-3}
end
FortiSandbox
For FortiSandbox, the TLS versions and the encryption algorithm are controlled using the following commands:
config system fortisandbox
set enc-algorithm {default* | high | low}
set ssl-min-proto-version {default* | SSLv3 | TLSv1 | TLSv1-1 | TLSv1-2}
end
FortiManager
For central management, the TLS versions and the encryption algorithm are controlled using the following commands:
config system central-management
set enc-algorithm {default | high* | low}
end
Encryption algorithm security level
Option Description
*high-medium/ default SSL communication with high and medium encryption algorithms.
FortiOS 7.6.2 Administration Guide 3419
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,419
|
System
Option Description
high SSL communication with high encryption algorithm
low SSL communication with low encryption algorithms.
*disable Disable SSL communication.
Encryption algorithm security levels marked with an asterisk (*) are not supported across
different products.
Conserve mode
Each FortiGate model has a specific amount of memory that is shared by all operations. If most or all of that memory is in
use, system operations can be affected in unexpected ways. To control how FortiOS functions when the available
memory is very low, FortiOS enters conserve mode. This causes functions, such as antivirus scanning, to change how
they operate to reduce the functionality and conserve memory without compromising security.
Three memory thresholds can be configured:
config system global
set memory-use-threshold-extreme <integer>
set memory-use-threshold-green <integer>
set memory-use-threshold-red <integer>
end
memory-use-thresholdextreme <integer>
The threshold at which memory usage is considered extreme and new sessions are
dropped, in percent of total RAM (70 - 97, default = 95).
memory-use-thresholdgreen <integer>
The threshold at which memory usage forces the FortiGate to leave conserve mode,
in percent of total RAM (70 - 97, default = 82).
memory-use-thresholdred <integer>
The threshold at which memory usage forces the FortiGate to enter conserve mode,
in percent of total RAM (70 - 97, default = 88).
Proxy inspection in conserve mode
The FortiGate's proxy-based inspection behavior while in conserve mode is configured with the antivirus failopen
command.
config system global
set av-failopen {pass | off | one-shot}
end
pass This is the default settings.
FortiOS 7.6.2 Administration Guide 3420
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,420
|
System
Bypass the antivirus proxy and allow traffic to continue to its destination. Because traffic bypasses
the proxy, security profiles that require the antivirus proxy are also bypassed. Security profiles that
do not use the antivirus proxy continue to function normally.
Use this setting when access is more important than security while the issue is resolved.
off Force the FortiGate to stop all traffic that uses the antivirus proxy. New sessions are blocked, but
active sessions continue to be processed normally unless they request more memory and are then
terminated.
If a security policy is configured to use antivirus scanning, then the traffic that it permits is blocked
while in conserve mode. So, a policy with only IPS scanning enabled will continue normally, but a
policy with both IPS and antivirus scanning is blocked because antivirus scanning requires the
antivirus proxy.
Use this setting when security is more important than access while the issue is resolved.
one-shot Continue to bypass the antivirus proxy after the FortiGate is out of conserve mode, until the failopen
setting is changed or the FortiGate is restarted.
Flow inspection in conserve mode
The FortiGate's flow-based inspection behavior while in conserve mode is configured with the IPS failopen command.
config ips global
set fail-open {enable | disable}
end
l When disabled (default), the IPS engine drops all new sessions that require flow-based inspection.
l When enabled, the IPS engine does not perform any scans and allows new packets.
Diagnostics
When in conserve mode, FortiOS generates conserve mode log messages and SNMP traps, and a conserve mode
banner is shown in the GUI.
To view current information about memory conservation status:
# diagnose hardware sysinfo conserve
memory conserve mode: on
total RAM: 997 MB
memory used: 735 MB 73% of total RAM
memory freeable: 173 MB 17% of total RAM
memory used + freeable threshold extreme: 947 MB 95% of total RAM
memory used threshold red: 877 MB 88% of total RAM
memory used threshold green: 817 MB 82% of total RAM
FortiOS 7.6.2 Administration Guide 3421
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,421
|
System
To view logs:
1. Go to Log & Report > System Events in the GUI.
2. If historical FortiView is enabled, select the Logs tab.
3. If the GUI is unresponsive due to high memory usage, making the logs inaccessible, they can be viewed in the CLI:
# execute log filter category 1
# execute log display
1: date=2022-11-02 time=16:58:37 eventtime=1667433517502192693 tz="-0700"
logid="0100022011" type="event" subtype="system" level="critical" vd="root"
logdesc="Memory conserve mode entered" service="kernel" conserve="on" total=997 MB
used=707 MB red="877 MB" green="698 MB" msg="Kernel enters memory conserve mode
To view the crash log in the CLI:
# diagnose debug crashlog read
1: 2022-10-27 14:22:36 service=kernel conserve=on total="997 MB" used="720 MB" red="877 MB"
2: 2022-10-27 14:22:36 green="817 MB" msg="Kernel enters memory conserve mode"
Using APIs
Administrators can use API calls to a FortiGate to:
l Retrieve, create, update, and delete configuration settings
l Retrieve system logs and statistics
l Perform basic administrative actions, such as a reboot or shut down through programming scripts.
Token-based authentication
FortiGate supports only token-based authentication for API calls. Token-based authentication requires the administrator
to generate a token, which is then included in each API request for authentication. A token is automatically generated
when a new API administrator is created in FortiOS.
Once the API administrator is created and the token displays, there is no way for the FortiGate
to provide this token again. Ensure you record the token, and store it in a safe location;
otherwise, you will have to generate a new token.
Creating the API administrator and generating the API token
When creating an API administrator, it is best practice to provide this account (and the associated token) with the
minimum permissions required to complete the function. For example, if you only plan to use API calls to retrieve
statistics or information from the FortiGate, the account should have read permissions.
The API administrator account used in this topic's examples has full permissions strictly to
illustrate various call types and does not adhere to the preceding recommendation.
FortiOS 7.6.2 Administration Guide 3422
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,422
|
System
See REST API administrator on page 2984 for detailed steps to create a REST API administrator.
Best Practices
Using API tokens with a request header
The API token can be included in any REST API request in either the request header or URL parameter. For added
security, it is strongly recommended to use API tokens in the request header or transition your applications to include the
API token in the request header instead of the URL parameter.
To pass the API token in the request header, the user needs to explicitly add the following field to the request header:
Authorization: Bearer <YOUR-API-TOKEN>
Configuring security options when creating a REST API administrator
In addition to using API tokens in the request header, for added security when creating a new REST API administrator,
one or more of the following fields should be configured, listed in order of configuration difficulty from easy to difficult:
l Trusted Hosts
To ensure that only trusted hosts/subnets can access the FortiGate REST API, you should configure the Trusted
Hosts field when creating a new REST API administrator. You need your Source Address to create the trusted host.
l CORS Allow Origin
Cross Origin Resource Sharing (CORS) allows third-party web apps to make API requests to the FortiGate using
the token. For this field, specify the Access-Control-Allow-Origin on API responses. If possible, avoid using
‘*’.
l PKI Group
Configure a PKI group to enable peer authentication using certificate matching, which provides an extra layer of
security. Both the client certificate and token must match to be granted access to the API. The PKI group is typically
specified as the name of a peer group defined under config user group which has PKI members. See
Configuring a PKI user on page 2940 for details.
Making an API call to retrieve information from the FortiGate
The newly created API token is used to query the FortiGate for all firewall addresses. Many applications can be used for
this query; this example uses the curl and Postman clients to demonstrate the functionality.
To ensure maximum security when using API tokens, HTTPS is enforced. HTTP cannot be
used.
Replace the placeholders below with values for your FortiGate:
l <FortiGate_address> is the IP address or hostname of your FortiGate as well as the HTTPS port number
(default = 443 and does not need to be explicitly specified).
l <API-TOKEN> is the token you generated.
FortiOS 7.6.2 Administration Guide 3423
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,423
|
System
General API call
One of the simplest API calls is api/v2/cmdb/firewall/address, which returns all information about all firewall
addresses.
To make a general API call using curl:
curl --insecure \
-H "Accept: application/json" \
-H "Authorization: Bearer <API-TOKEN>" https://<FortiGate_
address>/api/v2/cmdb/firewall/address
The backslash (\) allows for multiline commands in curl. You can choose to enter the backslashes or enter the
commands into a single wrapping line.
To make a general API call using Postman:
1. Open the Postman client.
2. Go to Settings > General and turn off SSL certificate verification.
3. Click on New and select HTTP
4. In the new request, click on the Authorization tab, select Type as Bearer Token and enter <YOUR-API-TOKEN> in
the Token field.
5. Enter a URL like the one below:
https://<YOUR-FORTIGATE-ADDRESS>/api/v2/cmdb/firewall/address
6. Click Send.
Results of the general API call:
curl and Postman display the output similar to the following (output shortened for brevity):
{
"http_method": "GET",
"size": 17,
"limit_reached": false,
"matched_count": 17,
"next_idx": 16,
"revision": "bd002ee1735120907182831e7528dc8b",
"results": [
{
"name": "EMS_ALL_UNKNOWN_CLIENTS",
"q_origin_key": "EMS_ALL_UNKNOWN_CLIENTS",
"uuid":"********-****-****-****-************"
"type": "dynamic",
"route-tag": 0,
"sub-type": "ems-tag",
"clearpass-spt": "unknown",
"macaddr": [],
"country": "",
"cache-ttl": 0,
"sdn": "",
"fsso-group": [],
"interface": "",
FortiOS 7.6.2 Administration Guide 3424
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,424
|
System
"obj-tag": "",
"obj-type": "ip",
"tag-detection-level": "",
"tag-type": "",
"dirty": "clean",
"hw-vendor": "",
"hw-model": "",
"os": "",
"sw-version": "",
"comment": "",
"associated-interface": "",
"color": 0,
"filter": "",
"sdn-addr-type": "private",
"node-ip-only": "disable",
"obj-id": "",
"list": [],
"tagging": [],
"allow-routing": "disable",
"fabric-object": "disable"
},
{
"name": "EMS_ALL_UNMANAGEABLE_CLIENTS",
"q_origin_key": "EMS_ALL_UNMANAGEABLE_CLIENTS",
"uuid":"********-****-****-****-************",
Formatting an API call
Since a general API call for address objects returns a large amount of information, it may be beneficial to format the API
call to display certain information using the format parameter. In this example, the format parameter is used to display
the name and comment for each firewall address.
To use the format parameter in an API call using curl:
curl --insecure \
-H "Accept: application/json" \
-H "Authorization: Bearer <API-TOKEN>" https://<FortiGate_
address>/api/v2/cmdb/firewall/address?format="name|comment"
The backslash (\) allows for multiline commands in curl. You can choose to enter the backslashes or enter the
commands into a single wrapping line.
To use the format parameter in an API call using Postman:
1. Open the Postman client.
2. Go to Settings > General and turn off SSL certificate verification.
3. Click on New and select HTTP
4. In the new request, click on the Authorization tab, select Type as Bearer Token and enter <YOUR-API-TOKEN> in
the Token field.
5. Enter a URL like the one below:
https://<FortiGate_address>/api/v2/cmdb/firewall/address/? format=name|comment.
6. Click Send.
FortiOS 7.6.2 Administration Guide 3425
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,425
|
System
Results of the formatted API call:
curl and Postman display the output similar to the following (output shortened for brevity):
{
"http_method": "GET",
"size": 17,
"limit_reached": false,
"matched_count": 17,
"next_idx": 16,
"revision": "bd002ee1735120907182831e7528dc8b",
"results": [
{
"name": "EMS_ALL_UNKNOWN_CLIENTS",
"q_origin_key": "EMS_ALL_UNKNOWN_CLIENTS",
"comment": ""
},
{
"name": "EMS_ALL_UNMANAGEABLE_CLIENTS",
"q_origin_key": "EMS_ALL_UNMANAGEABLE_CLIENTS",
"comment": ""
},
{
"name": "FABRIC_DEVICE",
"q_origin_key": "FABRIC_DEVICE",
"comment": "IPv4 addresses of Fabric Devices."
},
Filtering an API call
The filter parameter can be used to specify a field and a keyword to limit what results match and are returned by a call. In
this example, the preceding call is used with a filter to return only names and comments for address objects with the
word Sales in the name.
To use the filter parameter in an API call using curl:
curl --insecure \
-H "Accept: application/json" \
-H "Authorization: Bearer <API-TOKEN>" https://<FortiGate_
address>/api/v2/cmdb/firewall/address?format="name|comment&filter=name=@SSLVPN"
The backslash (\) allows for multiline commands in curl. You can choose to enter the backslashes or enter the
commands into a single wrapping line.
To use the filter parameter in an API call using Postman:
1. Open the Postman client.
2. Go to Settings > General and turn off SSL certificate verification.
3. Click on New and select HTTP
4. In the new request, click on the Authorization tab, select Type as Bearer Token and enter <YOUR-API-TOKEN> in
the Token field.
5. Enter a URL like the one below:
FortiOS 7.6.2 Administration Guide 3426
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,426
|
System
https://<FortiGate_address>/api/v2/cmdb/firewall/address/?
format=name|comment&filter=name=@SSLVPN.
6. Click Send.
Results of the formatted API call:
curl and Postman display the output similar to the following (output shortened for brevity):
{
"http_method": "GET",
"size": 17,
"limit_reached": false,
"matched_count": 1,
"next_idx": 5,
"revision": "bd002ee1735120907182831e7528dc8b",
"results": [
{
"name": "SSLVPN_TUNNEL_ADDR1",
"q_origin_key": "SSLVPN_TUNNEL_ADDR1",
"comment": ""
}
],
"vdom": "root",
"path": "firewall",
"name": "address",
"status": "success",
"http_status": 200,
"serial": "****************",
"version": "******",
"build": ****}
For a complete list of API calls, see the Fortinet Development Network (FNDN). A subscription is required to access the
FNDN.
Configuration backups and reset
Once you successfully configure the FortiGate, it is extremely important that you back up the configuration. In some
cases, you may need to reset the FortiGate to factory defaults or perform a TFTP upload of the firmware, which will erase
the existing configuration. In these instances, the configuration on the device must be recreated, unless a backup can be
used to restore it.
You can use the GUI or CLI to back up the configuration in FortiOS or YAML format. You have the option to save the
configuration file in FortiOS format to various locations including the local PC, USB key, FTP, and TFTP server. FTP and
TFTP are only configurable through the CLI. In YAML format, configuration files can be backed up or restored on an
FTP or TFTP server through the CLI.
This topic includes the following information:
l Backing up and restoring configurations from the GUI on page 3428
l Backing up and restoring configurations from the CLI on page 3431
l Configuration revision on page 3435
FortiOS 7.6.2 Administration Guide 3427
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,427
|
System
l Restore factory defaults on page 3436
l Secure file copy on page 3436
Administrators can back up a configuration file when using an admin profile with access
permissions for System set to Read/Write. Therefore, administrators using admin profiles with
access permissions for System set to Read cannot back up a config file from the FortiGate or
through SCP.
For more granularity within the admin profile, set access permission for System to Custom to
access additional fields. When System is set to Custom, the Administrator Users field dictates
whether the config file can be backed up in the GUI. Whereas the Configuration field dictates
whether the config file can be backed up in the CLI.
Backing up and restoring configurations from the GUI
Configurations can be backed up using the GUI to your PC or a USB disk.
Field Description
Scope When the FortiGate is in multi-vdom mode and a user is logged in as a global
administrator.
Backup to You can choose where to save the configuration backup file.
l Local PC: Save the configuration file to your PC.
l USB Disk: Save the configuration file to an external USB disk. This option is
not available if there is no USB drive inserted in the USB port.
You can also back up to FortiManager using the CLI.
File format The configuration file can be saved in FortiOS or YAML format.
Password mask Use password masking when sending a configuration file to a third party. When
password masking is enabled, passwords and secrets will be replaced in the
configuration file with FortinetPasswordMask.
Encryption Enable Encryption to encrypt the configuration file. A configuration file cannot be
restored on the FortiGate without a set password.
Encryption is performed using AES-GCM algorithm.
To back up the configuration in FortiOS format using the GUI:
1. Click on the user name in the upper right-hand corner of the screen and select Configuration > Backup.
2. Direct the backup to your Local PC or to a USB Disk.
The USB Disk option will not be available if no USB drive is inserted in the USB port. You can also backup to the
FortiManager using the CLI.
3. If VDOMs are enabled, indicate whether the scope of the backup is the entire FortiGate configuration (Global) or
only a specific VDOM configuration (VDOM).
If backing up a VDOM configuration, select the VDOM name from the list.
4. Enable Encryption.
FortiOS 7.6.2 Administration Guide 3428
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,428
|
System
This is recommended to secure your backup configurations and prevent unauthorized
parties from reloading your configuration.
5. Enter a password, and enter it again to confirm it. This password will be required to restore the configuration.
6. Click OK.
7. When prompted, select a location on the PC or USB disk to save the configuration file. The configuration file will
have a .conf extension.
To back up the configuration in YAML format using the GUI:
1. Click on the user name in the upper right-hand corner of the screen and select Configuration > Backup.
2. Direct the backup to your Local PC or to a USB Disk.
3. Select YAML for the File format.
4. Click OK.
When backing up a configuration that will be shared with a third party, such as Fortinet Inc. Support, passwords and
secrets should be obfuscated from the configuration to avoid information being unintentionally leaked. Password
masking can be completed in the Backup System Configuration page and in the CLI. When password masking is
enabled, passwords and secrets will be replaced in the configuration file with FortinetPasswordMask.
To mask passwords in the GUI:
1. Click on the username in the upper right-hand corner of the screen and select Configuration > Backup.
2. Select YAML as the File format.
3. Enable Password mask. A warning message is displayed.
4. Click OK. The configuration file is saved to your computer with passwords and secrets obfuscated.
The following is an example of output with password masking enabled:
config system admin
edit "1"
set accprofile "prof_admin"
set vdom "root"
set password FortinetPasswordMask
next
end
config vpn ipsec phase1-interface
edit "vpn-1"
set interface "port1"
FortiOS 7.6.2 Administration Guide 3429
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,429
|
System
set peertype any
set net-device disable
set proposal aes128-sha256 aes256-sha256 aes128-sha1 aes256-sha1
set comments "VPN: vpn-1 (Created by VPN wizard)"
set wizard-type static-fortigate
set remote-gw 172.16.200.55
set psksecret FortinetPasswordMask
next
end
config wireless-controller vap
edit "ssid-1"
set passphrase FortinetPasswordMask
set schedule "always"
next
end
Restoring configuration files from the GUI
Configuration files can be used to restore the FortiGate to a previous configuration in the Restore System Configuration
page.
To restore the FortiGate configuration using the GUI:
1. Click on the user name in the upper right-hand corner of the screen and select Configuration > Restore.
2. Identify the source of the configuration file to be restored: your Local PC or a USB Disk.
The USB Disk option will not be available if no USB drive is inserted in the USB port. You can restore from the
FortiManager using the CLI.
3. Click Upload, locate the configuration file, and click Open.
4. Enter the password if required.
5. Click OK.
When restoring a configuration file that has password masking enabled, obfuscated passwords and secrets will be
restored with the password mask.
Restoring the FortiGate with a configuration with passwords obfuscated is not recommended.
To restore an obfuscated YAML configuration using the GUI:
1. Click on the user name in the upper right-hand corner of the screen and select Configuration > Restore.
2. Click Upload. The File Explorer is displayed.
3. Navigate to the configuration file and click Open.
FortiOS 7.6.2 Administration Guide 3430
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,430
|
System
4. (Optional) Enter the file password in the Password field.
5. Click OK. The Confirm pane is displayed with a warning.
6. Toggle the acknowledgment.
7. Click OK.
Backing up and restoring configurations from the CLI
Configuration backups in the CLI are performed using the execute backup commands and can be backed up in
FortiOS and YAML format.
Configuration files can be backed up to various locations depending on the command:
l flash: Backup the configuration file to the flash drive.
l ftp: Backup the configuration file to an FTP server.
l management-station: Backup the configuration file to a management station, such as FortiManager or FortiGate
Cloud.
l sftp: Backup the configuration file to a SFTP server.
l tftp: Backup the configuration file to a TFTP server.
l usb: Backup the configuration file to an external USB drive.
l usb-mode: Backup the configuration file for USB mode.
Command Description
# execute backup config Back up the configuration in FortiOS format.
Backup your configuration file to:
l flash
l ftp
l management-station
l sftp
l tftp
l usb
l usb-mode
# execute backup fullconfig
Backup the configuration, including backups of default configuration settings.
FortiOS 7.6.2 Administration Guide 3431
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,431
|
System
Command Description
Backup your configuration file to:
l ftp
l sftp
l tftp
l usb
l usb-mode
# execute backup yamlconfig
Backup the configuration in YAML format.
Backup your configuration file to:
l ftp
l tftp
# execute backup
obfuscated-config
Backup the configuration with passwords and secrets obfuscated.
Backup your configuration file to:
l ftp
l management-station
l sftp
l tftp
l usb
# execute backup
obfuscated-full-config
Backup the configuration (including default configuration settings) with passwords
and secrets obfuscated.
Backup your configuration file to:
l ftp
l sftp
l tftp
l usb
# execute backup
obfuscated-yaml-config
Backup the configuration in YAML format with passwords and secrets obfuscated.
Backup your configuration file to:
l ftp
l tftp
To back up the configuration in FortiOS format using the CLI:
For FTP, note that port number, username are optional depending on the FTP site:
# execute backup config ftp <backup_filename> <ftp_server>[<:ftp_port>] [<user_name>]
[<password>] [<backup_password>]
or for TFTP:
# execute backup config tftp <backup_filename> <tftp_servers> [<backup_password>]
or for SFTP:
# execute backup config sftp <backup_filename> <sftp_server>[<:sftp_port>] <user> <password>
[<backup_password>]
or:
FortiOS 7.6.2 Administration Guide 3432
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,432
|
System
# execute backup config management-station <comment>
or:
# execute backup config usb <backup_filename> [<backup_password>]
Use the same commands to backup a VDOM configuration by first entering the commands:
config vdom
edit <vdom_name>
See Backing up and restoring configurations in multi-VDOM mode on page 3087 for more information.
When backing up a configuration in YAML format, if it is not already specified in the file name, .yaml will be appended to
the end. For example, if the file name entered is 301E.conf, the name will become 301E.conf.yaml after the
configuration is backed up.
To back up the configuration in YAML format using the CLI:
# execute backup yaml-config {ftp | tftp} <filename> <server> [username] [password]
For example:
# execute backup yaml-config tftp 301E.conf 172.16.200.55
Please wait...
The suffix '.yaml' will be appended to the filename if user does not add it
specifically.
Connect to tftp server 172.16.200.55 ...
#
Send config file to tftp server OK.
Configuration files can be configured with obfuscated passwords and secrets to not unintentionally leak information
when sharing configuration files with third parties.
To mask passwords in a configuration backup in the CLI:
# execute backup obfuscated-config {ftp | management-station | sftp | tftp | usb}
To mask passwords in the full configuration backup in the CLI:
# execute backup obfuscated-full-config {ftp | sftp | tftp | usb}
To mask passwords in a configuration backup with YAML formatting in the CLI:
# execute backup obfuscated-yaml-config {ftp | tftp}
If a configuration is being backed up on a server, server information must be included with the
command. Other information that may be required with an execute backup command
includes file names, passwords, and comments.
Restoring configuration files from the CLI
Configuration files can be used to restore the FortiGate using the CLI.
FortiOS 7.6.2 Administration Guide 3433
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,433
|
System
Command Description
# execute restore config Restore a configuration that is in FortiOS or YAML format. The file format is
automatically detected when it is being restored.
Configurations can be loaded from:
l flash: Load the configuration file from flash to firewall.
l ftp: Load the configuration file from an FTP server.
l management-station: Load the configuration from a management
station.
l tftp: Load the configuration from from a TFTP server.
l usb: Load the configuration file from an external USB disk to firewall.
l usb-mode: Load the configuration file from an external USB disk and reboot.
To restore the FortiGate configuration using the CLI:
For FTP, note that port number, username are optional depending on the FTP site:
# execute restore config ftp <backup_filename> <ftp_server>[<:port>] [<user_name>]
[<password>] [<backup_password>]
or for TFTP:
# execute restore config tftp <backup_filename> <tftp_server> [<backup_password>]
For restoring the configuration from FortiManager or FortiGate Cloud:
# execute restore config management-station normal <revision ID>
or:
# execute restore config usb <backup_filename> [<backup_password>]
The FortiGate will load the configuration file and restart. Once the restart has completed, verify that the configuration has
been restored.
Troubleshooting
When restoring a configuration, errors may occur, but the solutions are usually straightforward.
Error message Reason and Solution
Configuration file error This error occurs when attempting to upload a configuration file that is
incompatible with the device. This may be due to the configuration file being for a
different model or being saved from a different version of firmware.
Solution: Upload a configuration file that is for the correct model of FortiGate
device and the correct version of the firmware.
Invalid password When the configuration file is saved, it can be protected by a password. The
password entered during the upload process is not matching the one associated
with the configuration file.
Solution: Use the correct password if the file is password protected.
FortiOS 7.6.2 Administration Guide 3434
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,434
|
System
Configuration revision
You can manage multiple versions of configuration files on models that have a 512MB flash memory and higher.
Revision control requires either a configured central management server or the local hard drive, if your FortiGate has this
feature. Typically, configuration backup to local drive is not available on lower-end models.
Central management server
The central management server can either be a FortiManager unit or FortiGate Cloud.
If central management is not configured on your FortiGate, a message appears instructing you to either enable central
management, or obtain a valid license.
To enable central management from the GUI:
1. Go to Security Fabric > Fabric Connectors and double-click the Central Management card.
2. Set the Status to Enabled and select a Type.
3. Click OK.
To enable central management from the CLI:
config system central-management
set type {fortimanager | fortiguard}
set mode backup
set fmg <IP address>
end
To backup to the management server:
# execute backup config management-station <comment>
To view a backed up revision:
# execute restore config management-station normal 0
To restore a backed up revision:
# execute restore config management-station normal <revision ID>
Backing up to a local disk
When revision control is enabled on your FortiGate unit, and configuration backups have been made, a list of saved
revisions of those backed-up configurations appears.
Configuration backup occurs by default with firmware upgrades but can also be configured to occur every time you log
out.
FortiOS 7.6.2 Administration Guide 3435
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,435
|
System
To configure configuration backup when logging out:
config system global
set revision-backup-on-logout enable
end
To manually force backup:
# execute backup config flash <comment>
Configuration revisions are viewed by clicking on the user name in the upper right-hand corner of the screen and
selecting Configuration > Revisions.
To view a list of revisions backed up to the disk from the CLI:
# execute revision list config
To restore a configuration from the CLI:
# execute restore config flash <revision ID>
Restore factory defaults
There may be a need to reset the FortiGate to its original defaults; for example, to begin with a fresh configuration. There
are two options when restoring factory defaults:
# execute factoryreset Reset the device to factory default configuration.
The firmware version and antivirus and IPS attack definitions are not changed.
# execute factoryreset2 Reset to factory default configuration without losing management access to the
FortiGate.
Interface and VDOM configurations, as well as the firmware version and antivirus
and IPS attack definitions, are not changed.
Secure file copy
You can also back up and restore your configuration using Secure File Copy (SCP). See How to download a FortiGate
configuration file and upload firmware file using secure file copy (SCP).
You enable SCP support using the following command:
config system global
set admin-scp enable
end
For more information about this command and about SCP support, see config system global.
FortiOS 7.6.2 Administration Guide 3436
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,436
|
Fortinet Security Fabric
The Fortinet Security Fabric provides an intelligent architecture that interconnects discrete security solutions into an
integrated whole to detect, monitor, block, and remediate attacks across the entire attack surface. It delivers broad
protection and visibility into every network segment and device, be they hardware, virtual, or cloud based.
l The physical topology view shows all connected devices, including access layer devices. The logical topology view
shows information about the interfaces that each device is connected to.
l Security rating checks analyze the Security Fabric deployment to identify potential vulnerabilities and highlight best
practices to improve the network configuration, deploy new hardware and software, and increase visibility and
control of the network.
l Fabric connectors provide integration with multiple SDN, cloud, and partner technology platforms to automate the
process of managing dynamic security updates without manual intervention.
l Automation pairs an event trigger with one or more actions to monitor the network and take the designated actions
automatically when the Security Fabric detects a threat.
As part of improvements to reducing memory usage, FortiGate models with 2 GB RAM can
authorize up to five devices when serving as a Fabric root.
The affected models are the FortiGate 40F, 60E, 60F, 80E, and 90E series devices and their
variants.
A maximum of 35 downstream FortiGates is recommended.
Components
As part of improvements to reducing memory usage, FortiGate models with 2 GB RAM can
authorize up to five devices when serving as a Fabric root.
The affected models are the FortiGate 40F, 60E, 60F, 80E, and 90E series devices and their
variants.
The Fortinet Security Fabric consists of different components that work together to secure you network.
The following devices are required to create a Security Fabric:
Device Description
FortiGate FortiGates are the core of the Security Fabric and can have one of the following roles:
l Root: the root FortiGate is the main component in the Security Fabric. It is typically
located on the edge of the network and connects the internal devices and networks to the
FortiOS 7.6.2 Administration Guide 3437
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,437
|
Fortinet Security Fabric
Device Description
internet through your ISP. From the root FortiGate, you can see information about the
entire Security Fabric on the Physical and Logical Topology pages in the GUI.
l Downstream: after a root FortiGate is installed, all other FortiGate devices in the
Security Fabric act as Internal Segmentation Firewalls (ISFWs), located at strategic
points in your internal network, rather than on the network edge. This allows extra
security measures to be taken around key network components, such as servers that
contain valuable intellectual property. ISFW FortiGates create network visibility by
sending traffic and information about the devices that are connected to them to the root
FortiGate.
A maximum of 35 downstream FortiGates is recommended.
See Configuring the root FortiGate and downstream FortiGates on page 3442 for more
information about adding FortiGate devices in the Security Fabric.
FortiGate documentation: https://docs.fortinet.com/product/fortigate
FortiAnalyzer* FortiAnalyzer gives you increased visibility into your network, centralized monitoring, and
awareness of threats, events, and network activity by collecting and correlating logs from all
Security Fabric devices. This gives you a deeper and more comprehensive view across the
entire Security Fabric.
See Configuring FortiAnalyzer on page 3451 for more information about adding FortiAnalyzer
devices in the Security Fabric.
FortiAnalyzer documentation: https://docs.fortinet.com/product/fortianalyzer
Cloud Logging* There are two options for cloud logging: FortiAnalyzer Cloud and FortiGate Cloud. Either can
be used to enable the Security Fabric root device; however, if using FortiGate Cloud, all
downstream devices must belong to the same FortiCloud account.
See Configuring cloud logging on page 3454 for more information about configuring a
Security Fabric with FortiGate Cloud.
FortiGate Cloud documentation: https://docs.fortinet.com/product/fortigate-cloud
* FortiAnalyzer or Cloud Logging is a required component for the Security Fabric. Either FortiAnalyzer, FortiAnalyzer
Cloud, or FortiGate Cloud can be used to met this requirement.
The following devices are recommended:
Device Description
FortiClient FortiClient adds endpoint control to devices that are located in the Security Fabric, allowing
only traffic from compliant devices to flow through the FortiGate. FortiClient compliance
profiles are applied by the first FortiGate that a device’s traffic flows through. Device
registration and on-net status information for a device that is running FortiClient appears only
on the FortiGate that applies the FortiClient profile to that device.
FortiClient documentation: https://docs.fortinet.com/product/forticlient
FortiClient EMS FortiClient EMS is used in the Security Fabric to provide visibility across your network,
securely share information, and assign security profiles to endpoints.
See Configuring FortiClient EMS on page 3462 for more information about adding FortiClient
EMS devices in the Security Fabric.
FortiClient EMS documentation: https://docs.fortinet.com/product/forticlient
FortiOS 7.6.2 Administration Guide 3438
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,438
|
Fortinet Security Fabric
Device Description
FortiAP Add FortiAP devices to extend the Security Fabric to your wireless devices. Devices
connected to a FortiAP appear in the Physical and Logical Topology pages in the Security
Fabric menu.
See Configuring LAN edge devices on page 3484 for more information about adding FortiAP
devices in the Security Fabric.
FortiAP documentation: https://docs.fortinet.com/product/fortiap
FortiSwitch A FortiSwitch can be added to the Security Fabric when it is managed by a FortiGate that is in
the Security Fabric with the FortiLink protocol, and connected to an interface with Security
Fabric Connection enabled. FortiSwitch ports to become logical extensions of the FortiGate.
Devices connected to the FortiSwitch appear in the Physical and Logical Topology pages in
the Security Fabric menu, and security features, such as FortiClient compliance profiles, are
applied to them.
See Configuring LAN edge devices on page 3484 for more information about adding
FortiSwitch devices in the Security Fabric.
FortiSwitch documentation: https://docs.fortinet.com/product/fortiswitch
FortiExtender FortiExtender cellular gateways provide ultra-fast LTE and 5G wireless to connect and scale
any WAN edge.
See Configuring LAN edge devices on page 3484 for more information about adding
FortiExtender devices in the Security Fabric.
FortiExtender documentation: https://docs.fortinet.com/product/fortiextender
FortiManager Add FortiManager to simplify the network management of devices in the Security Fabric by
centralizing management access in a single device. This allows you to easily control the
deployment of security policies, FortiGuard content security updates, firmware revisions, and
individual configurations for devices in the Security Fabric.
See Configuring central management on page 3485 for more information about adding
FortiManager devices in the Security Fabric.
FortiManager documentation: https://docs.fortinet.com/product/fortimanager
FortiSandbox Add FortiSandbox to your Security Fabric to improve security with sandbox inspection.
Sandbox integration allows FortiGate devices in the Security Fabric to automatically receive
signature updates from FortiSandbox and add the originating URL of any malicious file to a
blocked URL list.
See Configuring sandboxing on page 3490 for more information about adding FortiSandbox
devices in the Security Fabric.
FortiSandbox documentation: https://docs.fortinet.com/product/fortisandbox
FortiADC FortiADC devices optimize the availability, user experience, and scalability of enterprise
application delivery. They enable fast, secure, and intelligent acceleration and distribution of
even the most demanding enterprise applications.
FortiADC documentation: https://docs.fortinet.com/product/fortiadc
FortiDDoS FortiDDoS is a Network Behavior Anomaly (NBA) prevention system that detects and blocks
attacks that intend to disrupt network service by overutilizing server resources.
FortiDDoS documentation: https://docs.fortinet.com/product/fortiddos
FortiOS 7.6.2 Administration Guide 3439
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,439
|
Fortinet Security Fabric
Device Description
FortiDeceptor FortiDeceptor automatically lays out a layer of decoys and lures, which helps conceal
sensitive and critical assets behind a fabricated deception surface to confuse and redirect
attackers while revealing their presence on your network.
See Configuring FortiDeceptor on page 3506 for more information about adding
FortiDeceptor devices in the Security Fabric.
FortiDeceptor documentation: https://docs.fortinet.com/product/fortideceptor
FortiMail FortiMail antispam processing helps offload from other devices in the Security Fabric that
would typically carry out this process.
See Configuring FortiMail on page 3508 for more information about adding FortiMail devices
in the Security Fabric.
FortiMail documentation: https://docs.fortinet.com/product/fortimail
FortiMonitor FortiMonitor is a holistic, SaaS-based digital experience and network performance monitoring
solution. It facilitates deep analysis of both network health metrics and application
performance to identify potential problem areas that impact user access.
See Configuring FortiMonitor on page 3508for more information about adding FortiMonitor
devices in the Security Fabric.
FortiMonitor documentation: https://docs.fortinet.com/product/fortimonitor
FortiNAC FortiNAC provides visibility to all administrators to see everything connected to their network,
and the ability to control those devices and users, including dynamic, automated responses.
See Configuring FortiNAC on page 3510 for more information about adding FortiNAC devices
in the Security Fabric.
FortiNAC documentation: https://docs.fortinet.com/product/fortinac
FortiNDR FortiNDR (formerly FortiAI) uses artificial neural networks (ANN) that can deliver sub-second
malware detection and a verdict. Add FortiNDR to your Security Fabric to automatically
quarantine attacks.
See Configuring FortiNDR on page 3511 for more information about adding FortiNDR devices
in the Security Fabric.
FortiNDR documentation: https://docs.fortinet.com/product/fortindr
FortiPolicy FortiPolicy is a containerized security platform that implements and automates security
orchestration with full-flow inspection and segmented and microsegmented policy
enforcement while auto-scaling to accommodate infrastructure changes.
See Configuring FortiPolicy on page 3513 for more information about adding FortiPolicy
devices in the Security Fabric.
FortiPolicy documentation: https://docs.fortinet.com/product/fortipolicy
FortiTester FortiTester can be used for performance testing and validating network security infrastructure
and services. It provides a comprehensive range of application test cases to evaluate
equipment and right-size infrastructure.
See Configuring FortiTester on page 3516 for more information about adding FortiTester
devices in the Security Fabric.
FortiTester documentation: https://docs.fortinet.com/product/fortitester
FortiOS 7.6.2 Administration Guide 3440
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,440
|
Fortinet Security Fabric
Device Description
FortiWeb FortiWeb defends the application attack surface from attacks that target application exploits.
You can also configure FortiWeb to apply web application firewall features, virus scanning,
and web filtering to HTTP traffic to help offload from other devices in the Security Fabric that
would typically carry out these processes.
See Configuring FortiWeb on page 3518 for more information about adding FortiWeb devices
in the Security Fabric.
FortiWeb documentation: https://docs.fortinet.com/product/fortiweb
FortiWLC FortiWLC delivers seamless mobility and superior reliability with optimized client distribution
and channel utilization. Both single and multi channel deployment options are supported,
maximizing efficiency to make the most of available wireless spectrum.
FortiWLC documentation: https://docs.fortinet.com/product/wireless-controller
FortiVoice FortiVoice includes integrated high-definition voice, conferencing, and fax capabilities that
enables organizations to communicate and collaborate easily and securely.
See Configuring FortiVoice on page 3517 for more information about adding FortiVoice
devices in the Security Fabric.
FortiVoice documentation: https://docs.fortinet.com/product/fortivoice-enterprise
Other Fortinet
products
Other Fortinet products can be added to the Security Fabric, including FortiAuthenticator,
FortiToken, FortiCache, and FortiSIEM.
Documentation: https://docs.fortinet.com/
Third-party
products
Third-party products that belong to the Fortinet Fabric-Ready Partner Program can be added
to the Security Fabric.
Security Fabric connectors
This section contains information about how to configure the following devices as part of the Fortinet Security Fabric:
l Configuring the root FortiGate and downstream FortiGates
l Configuring logging and analytics on page 3450
l Configuring FortiAnalyzer on page 3451
l Configuring cloud logging on page 3454
l Configuring FortiClient EMS on page 3462
l Synchronizing FortiClient ZTNA tags on page 3481
l Configuring LAN edge devices on page 3484
l Configuring central management on page 3485
l Configuring sandboxing on page 3490
l Configuring supported connectors on page 3497
l Configuring FortiNDR on page 3511
l Configuring FortiDeceptor on page 3506
l Configuring FortiMail on page 3508
l Configuring FortiMonitor on page 3508
FortiOS 7.6.2 Administration Guide 3441
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,441
|
Fortinet Security Fabric
l Configuring FortiNAC on page 3510
l Configuring FortiTester on page 3516
l Configuring FortiVoice on page 3517
l Configuring FortiWeb on page 3518
l Configuring FortiPolicy on page 3513
l Allowing FortiDLP Agent communication through the FortiGate on page 3520
System requirements
To set up the Security Fabric, the devices that you want to include must meet the Product Integration and Support
requirements in the FortiOS Release Notes.
Some features of the Security Fabric are only available in certain firmware versions and models. Not all FortiGate
models can run the FortiGuard Surface Attack Security Rating Service if they are the root FortiGate in a Security Fabric.
For more information, see the Special Notices in the FortiOS Release Notes.
Prerequisites
l If devices are not already installed in your network, complete basic installation and configuration tasks by following
the instructions in the device documentation.
l FortiGate devices must be operating in NAT mode.
Configuring the root FortiGate and downstream FortiGates
The following procedures include configuration steps for a typical Security Fabric implementation, where the edge
FortiGate is the root FortiGate with other FortiGates that are downstream from the root FortiGate.
For information about the recommended number of downstream FortiGates, see the FortiOS Best Practices.
As part of improvements to reducing memory usage, FortiGate models with 2 GB RAM can
authorize up to five devices when serving as a Fabric root.
The affected models are the FortiGate 40F, 60E, 60F, 80E, and 90E series devices and their
variants.
Prerequisite
l The FortiGates must be operating in NAT mode.
Configuring the root FortiGate
The edge FortiGate is typically configured as the root FortiGate, as this allows you to view the full topology of the
Security Fabric from the top down. The following steps describe how to add the FortiGate to serve as the root device.
FortiOS 7.6.2 Administration Guide 3442
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,442
|
Fortinet Security Fabric
To configure the root FortiGate:
1. On the root FortiGate, go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
2. Set the Security Fabric role to Serve as Fabric Root.
3. Enter a Fabric name.
4. Ensure Allow other Security Fabric devices to join is enabled.
5. Select the interfaces that will be listening for device join requests. Enabling an interface here has the same effect as
going to Network > Interfaces, editing an interface, and enabling Security Fabric Connection under Administrative
Access.
6. Optionally, enable Allow downstream device REST API access to allow access to the REST API of the root
FortiGate for API requests coming from downstream Security Fabric devices. This option must be enabled to use
certain supported devices (such as FortiDeceptor, FortiMonitor, and FortiNAC) and the Fabric event trigger.
7. Click OK.
Using the root FortiGate with disk to store historic user and device information
This backend implementation allows the root FortiGate in a Security Fabric to store historic user and device information
in a database on its disk. This will allow administrators to visualize users and devices over a period of time.
The daemon, user_info_history, stores this data on the disk. The information source for the historical data will be the
user_info daemon, which would be recorded on the disk when user_info notifies user_info_history that a user has logged
out or the device is no longer connected.
Adding downstream devices
Downstream device serial numbers can be pre-authorized from the root FortiGate, or allowed to join by request. New
authorization requests include the device serial number, IP address, and HA members. HA members can include up to
FortiOS 7.6.2 Administration Guide 3443
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,443
|
Fortinet Security Fabric
four serial numbers and is used to ensure that, in the event of a fail over, the secondary FortiGate is still authorized. A
downstream device's certificate can also be used to authorize the device by uploading the certificate to the root
FortiGate.
The LAN Edge Devices card on the Fabric Connectors page displays a summary about the FortiGates, FortiAPs,
FortiSwitches, and FortiExtenders in the Fabric. Information about the device type, number of devices, and number of
unregistered and unauthorized devices is displayed. If there are devices that do not have a green checkmark in the
Status column, hover over the status message to view the tooltip with required action. In this example, there is a
downstream FortiGate that require authorization. The tooltip includes a link to the System > Firmware & Registration
page to authorize the FortiGates.
The Supported Connectors card displays the icons of different Fortinet devices that support full Security Fabric
integration. See Configuring supported connectors on page 3497 for more information about configuring supported
Fabric connectors.
Pre-authorizing the downstream FortiGate
When a downstream Fortinet device's serial number or certificate is added to the trusted list on the root FortiGate, the
device can join the Security Fabric as soon as it connects. After the new device is authorized, connected FortiAP and
FortiSwitch devices are automatically included in the topology, where they can be authorized with one click.
The interface that connects to the downstream FortiGate must have Security Fabric Connection enabled.
To pre-authorize a FortiGate:
1. On the root FortiGate, go to Security Fabric > Fabric Connectors and double-click the Security Fabric Setup card.
2. In the Device authorization field and click Edit. The Device Authorization pane opens.
3. Click Create New to add a new device for pre-authorization.
4. Enter the device name in the Name field.
5. Select the Authorization type, either Serial Number or Certificate.
FortiOS 7.6.2 Administration Guide 3444
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,444
|
Fortinet Security Fabric
6. If Certificate is selected, click Browse to upload the downstream device's certificate from the management
computer.
7. Set the Action to Accept.
8. Click OK and add more devices as required.
9. Click OK.
To configure a downstream FortiGate to connect to an upstream FortiGate:
1. Configure the downstream FortiGate:
a. On the downstream FortiGate, go to Security Fabric > Fabric Connectors and double-click the Security Fabric
Setup card.
b. Set the Security Fabric role to Join Existing Fabric.
c. Enter the IP address of the root FortiGate in the Upstream FortiGate IP/FQDN field.
d. Click OK.
2. On the root FortiGate, go to Security Fabric > Physical Topology and verify that the downstream FortiGate that you
FortiOS 7.6.2 Administration Guide 3445
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,445
|
Fortinet Security Fabric
added appears in the Security Fabric topology.
Authorizing a downstream FortiGate
When you log in to an unauthorized downstream FortiGate, the log in prompt includes the option to authorize the device
on the root FortiGate.
To authorize a downstream FortiGate:
1. Log in to the unauthorized, downstream device.
2. In the Fabric Setup step, click Review Authorization on Root FortiGate.
A pop-up window opens to a log in screen for the root FortiGate.
3. Enter the log in credentials for the root FortiGate, then click Login.
A list of pending authorizations is shown.
FortiOS 7.6.2 Administration Guide 3446
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,446
|
Fortinet Security Fabric
4. Select Allow and then click OK to authorize the downstream FortiGate. You can also select Deny to reject the
authorization, or Later to postpone the decision to the next time that you log in.
When authorization is allowed, the pop-up window closes, and the log in prompt shows that the downstream
FortiGate has been authorized.
5. Click Done to log in to the downstream FortiGate.
Triggering authorization from the GUI
A downstream device can be authorized in the root FortiGate's GUI by using the Firmware & Registration page (see
Authorizing devices on page 3030 for more information).
To authorize a downstream FortiGate from the Firmware & Registration page:
1. Go to System > Firmware & Registration.
2. Select the unauthorized device and click Authorization > Authorize.
FortiOS 7.6.2 Administration Guide 3447
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,447
|
Fortinet Security Fabric
A notification appears in the top-right corner once the device is authorized.
3. Refresh the page. The FortiGate's status is now Online.
Registering the downstream devices to FortiCloud
In this example, a downstream FortiGate has just been authorized, but it is not registered to a FortiCloud account. A
device can be registered on the root FortiGate to a FortiCloud account.
To register the downstream FortiGate from the root:
1. Log in to the root FortiGate and go to System > Firmware & Registration
2. Select an unregistered device and click Register. The Device Registration pane opens.
3. Enter the required information (password, country/region, reseller, and end-user type).
4. Click Submit. The Registration Summary pane opens.
5. Click Close.
You can use IPAM to automatically assign subnets to downstream FortiGates to prevent
duplicate IP addresses from overlapping within the same Security Fabric. See Configure IPAM
locally on the FortiGate on page 176.
Deauthorizing a device
A device can be deauthorized to remove it from the Security Fabric in the root FortiGate's GUI by using the Firmware &
Registration page (see Authorizing devices on page 3030 for more information).
FortiOS 7.6.2 Administration Guide 3448
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,448
|
Fortinet Security Fabric
To deauthorize a device from the Firmware & Registration page:
1. Go to System > Firmware & Registration.
2. Select the authorized device and click Authorization > Deauthorize.
A notification appears in the top-right corner once the device is deauthorized.
3. Refresh the page. The FortiGate is moved to the bottom of the list, and it's status is Unauthorized.
After a device is deauthorized, the serial number is saved in a trusted list that can be viewed in the CLI using the show
system csf command. For example, this result shows a deauthorized FortiSwitch:
show system csf
config system csf
set status enable
set group-name "Office-Security-Fabric"
set group-password ************
config trusted-list
edit "FGT6HD391800000"
next
edit "S248DF3X1700000"
set action deny
next
end
end
CLI commands
Use the following commands to view, accept, and deny authorization requests, to view upstream and downstream
devices, and to list or test Fabric devices:
Command Description
diagnose sys csf
authorization
pending-list
View pending authorization requests on the root FortiGate.
diagnose sys csf
authorization accept
<serial number>
[name]
Authorize a device to join the Security Fabric.
FortiOS 7.6.2 Administration Guide 3449
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,449
|
Fortinet Security Fabric
Command Description
diagnose sys csf
authorization deny
<serial number>
[name]
Deny a device from joining the Security Fabric.
diagnose sys csf
downstream
Show connected downstream FortiGates.
diagnose sys csf
downstream-devices
<device type>
Show downstream fabric devices.
diagnose sys csf upstream Show connected upstream devices.
diagnose sys csf fabricdevice list
List all known Fabric devices.
diagnose sys csf global Show a summary of all connected members in Security Fabric.
Desynchronizing settings
By default, the settings for FortiAnalyzer logging, central management, sandbox inspection, and FortiClient EMS are
synchronized between all FortiGates in the Security Fabric.
To disable automatic synchronization:
config system csf
set configuration-sync local
end
Configuring logging and analytics
FortiAnalyzer or Cloud Logging is a required component for the Security Fabric. Either FortiAnalyzer, FortiAnalyzer
Cloud, or FortiGate Cloud can be used to met this requirement. These settings are configured on the Logging & Analytics
card on the Security Fabric > Fabric Connectors page. If there are multiple services enrolled on the FortiGate, the
preference is: FortiAnalyzer Cloud logging, FortiAnalyzer logging, then FortiGate Cloud logging.
The following topics provide more information about configuring the logging and analytics connector:
l Configuring FortiAnalyzer on page 3451
l Configuring cloud logging on page 3454
Logs Sent daily chart for remote logging sources
The Logs Sent widget displays a chart for a select remote logging source (FortiAnalyzer, FortiGate Cloud, and
FortiAnalyzer Cloud). Once configured, the same data is available on the FortiAnalyzer and Cloud Logging tabs of the
Logging & Analytics card.
FortiOS 7.6.2 Administration Guide 3450
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,450
|
Fortinet Security Fabric
To add the Logs Sent widget:
1. Go to Dashboard > Status and click Add Widget.
2. Search for Logs Sent and click to add the widget to the dashboard.
3. Select a Logging Source (FortiAnalyzer, FortiAnalyzer Cloud, or FortiGate Cloud). FortiAnalyzer Cloud is used in
this example.
4. Click OK and click Close. The FortiAnalyzer Logs Sent Daily widget is displayed in the dashboard.
To view the chart on the Logging & Analytics card:
1. Go to Security Fabric > Fabric Connectors and double-click the Logging & Analytics card.
The Logging Settings pane is displayed.
2. Go to the FortiAnalyzer or Cloud Logging tabs to view the Remote Logs Sent Daily chart. FortiAnalyzer Cloud is
used in this example.
3. Click OK to close the pane.
Configuring FortiAnalyzer
FortiAnalyzer allows the Security Fabric to show historical data for the Security Fabric topology and logs for the entire
Security Fabric. For more information about using FortiAnalyzer, see the FortiAnalyzer Administration Guide.
FortiOS 7.6.2 Administration Guide 3451
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,451
|
Fortinet Security Fabric
To authorize a FortiAnalyzer in the Security Fabric:
1. In FortiAnalyzer, configure the authorization address and port:
a. Go to System Settings > Settings.
b. In the Fabric Authorization section, enter an Authorization Address and Authorization Port. This is used to
access the FortiAnalyzer login screen.
c. Click Apply.
2. In FortiOS, go to Security Fabric > Fabric Connectors and double-click the Logging & Analytics card.
3. On the FortiAnalyzer tab, set the Status to Enabled.
4. Enter the FortiAnalyzer IP in the Server field.
5. Optionally, configure the remaining log settings:
Upload option Select the frequency of log uploads to the remote device:
l Real Time: logs are sent to the remote device in real time.
l Every Minute: logs are sent to the remote device once every minute. This
option is unavailable if the Security Fabric connection is configured.
l Every 5 Minutes: logs are sent to the remote device once every five
minutes. This is the default option. This option is unavailable if the
Security Fabric connection is configured.
l store-and-upload: store logs to a local disk before uploading to
FortiAnalyzer or FortiManager at a scheduled time. This option is only
available in the CLI.
Allow access to FortiGate
REST API
Define access to FortiGate REST API:
l Enable: the REST API accesses the FortiGate topology and shares data
and results.
l Disable: the REST API does not share data and results.
Verify FortiAnalyzer certificate Define the FortiAnalyzer certificate verification process:
l Enable: the FortiGate will verify the FortiAnalyzer serial number against
the FortiAnalyzer certificate. When verified, the serial number is stored in
the FortiGate configuration.
l Disable: the FortiGate will not verify the FortiAnalyzer certificate against
the serial number.
6. Click OK. The FortiAnalyzer Connection status is Unauthorized and a pane might open to verify the FortiAnalyzer's
serial number.
FortiOS 7.6.2 Administration Guide 3452
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,452
|
Fortinet Security Fabric
7. Click Accept.
8. Double-click the Logging & Analytics card again.
9. Click OK in the confirmation popup to open a window to authorize the FortiGate on the FortiAnalyzer.
A login screen opens in a new browser window.
10. Enter the username and password, then click Login.
The authorization dialog opens.
11. Select Approve in the row for the FortiGate, and then click OK to authorize the FortiGate.
12. In FortiOS, Connection status is now Authorized on the Logging Settings pane.
FortiOS 7.6.2 Administration Guide 3453
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,453
|
Fortinet Security Fabric
FortiGates with a FortiAnalyzer Cloud license can send all logs to FortiAnalyzer Cloud.
Configuring cloud logging
There are two options available in the Cloud Logging tab of the Logging & Analytics connector card: FortiGate Cloud and
FortiAnalyzer Cloud. If there are multiple services enrolled on the FortiGate, the preference is: FortiAnalyzer Cloud
logging, FortiAnalyzer logging, then FortiGate Cloud logging.
This topic covers the following cloud logging aspects:
l Configuring FortiGate Cloud
l Registration and activation
l Enabling logging to FortiGate Cloud
l Logging into the FortiGate Cloud portal
l Configuring a Security Fabric with FortiGate Cloud logging
l Cloud sandboxing
l Configuring FortiAnalyzer Cloud
Configuring FortiGate Cloud
FortiGate Cloud is a hosted security management and log retention service for FortiGate devices. It provides centralized
reporting, traffic analysis, configuration management, and log retention without the need for additional hardware or
software.
FortiGate Cloud offers a wide range of features:
l Simplified central management
FortiGate Cloud provides a central GUI to manage individual or aggregated FortiGate and FortiWiFi devices.
Adding a device to the FortiGate Cloud management subscription is straightforward. FortiGate Cloud has detailed
traffic and application visibility across the whole network.
l Hosted log retention with large default storage allocated
Log retention is an integral part of any security and compliance program, but administering a separate storage
system is onerous. FortiGate Cloud takes care of this automatically and stores the valuable log information in the
FortiOS 7.6.2 Administration Guide 3454
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
3,454
|
Fortinet Security Fabric
cloud. Different types of logs can be stored, including Traffic, System Events, Web, Applications, and Security
Events.
l Monitoring and alerting in real time
Network availability is critical to a good end-user experience. FortiGate Cloud enables you to monitor your FortiGate
network in real time with different alerting mechanisms to pinpoint potential issues. Alerting mechanisms can be
delivered via email.
l Customized or pre-configured reporting and analysis tools
Reporting and analysis are your eyes and ears into your network’s health and security. Pre-configured reports are
available, as well as custom reports that can be tailored to your specific reporting and compliance requirements.
The reports can be emailed as PDFs, and can cover different time periods.
l Maintain important configuration information uniformly
The correct configuration of the devices within your network is essential for maintaining optimum performance and
security posture. In addition, maintaining the correct firmware (operating system) level allows you to take advantage
of the latest features.
l Service security
All communication (including log information) between the devices and the cloud is encrypted. Redundant data
centers are always used to give the service high availability. Operational security measures have been put in place
to make sure your data is secure — only you can view or retrieve it.
For more information, refer to the FortiGate Cloud documentation.
For FortiGates managed by FortiGate Cloud, automatic firmware patch may be enabled
depending on the FortiGate Cloud version and portal in use. See the Administration Guide for
the applicable FortiGate Cloud version and portal:
l Standard Portal Administration Guide
l 25.1.a Portal (Beta) Administration Guide
l Premium Portal Administration Guide
Registration and activation
Before you can activate a FortiGate Cloud account, you must register your device first.
FortiGate Cloud accounts can be registered manually through the FortiGate Cloud website, https://www.forticloud.com,
or you can easily register and activate your account directly from your FortiGate.
To activate your FortiGate Cloud account:
1. On your device, go to Dashboard > Status.
2. In the FortiGate Cloud widget, click the Not Activated > Activate button in the Status field.
3. A pane will open asking you to register your FortiGate Cloud account. Click Create Account, enter your information,
view and accept the terms and conditions, and then click OK.
4. A second dialogue window opens, asking you to enter your information to confirm your account. This sends a
confirmation email to your registered email. The dashboard widget then updates to show that confirmation is
required.
FortiOS 7.6.2 Administration Guide 3455
Fortinet Inc.
|
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/3afdbab8-dcdc-11ef-8766-ca4255feedd9/FortiOS-7.6.2-Administration_Guide.pdf
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.