Generate Certificate (Strata Cloud Manager)

1. Log in to Strata Cloud Manager.
2. Select ConfigurationNGFW and Prisma AccessObjectsCertificate Management.
3. In the Custom Certificates section, click Generate.
4. Enter a unique Certificate Name.

   The name is case-sensitive and can have up to 63 characters. Use only letters, numbers, hyphens, and underscores.
5. For Common Name, enter the FQDN (recommended) or IP address of the interface where you will configure the service that uses this certificate.
6. For Signed By, select the root CA certificate that will issue the certificate.
7. To allow an NGFW to issue the certificate, enable Certificate Authority.

   Marking this certificate as a CA grants it the ability to sign other certificates.
8. For Certificate Use for, select Forward Trust Certificate, Forward UnTrust Certificate, or Trusted Root CA.
9. Configure the Cryptographic Settings.

   1. Select a key generation Algorithm:

      • RSA (default)
      • Elliptic Curve DSA (ECDSA)
        The Thales CipherTrust Manager integration with PAN-OS does not support ECDSA keys.
        ECDSA is recommended for client browsers and operating systems that support it.
      • ML-DSA (PAN-OS 12.1.2 and later)
      • SLH-DSA (PAN-OS 12.1.2 and later)
   2. (SLH-DSA only) Select Algorithm Parameters.

      These parameters define the hash function family (SHA2 or SHAKE), NIST security level (128 bits, 192 bits, or 256 bits), and digital signature size of the scheme.
   3. Select the Number of Bits (certificate key length):

      Higher numbers are more secure but require more processing time.

      SLH-DSA bits are preselected based on the Algorithm Parameters.

      • For RSA, select 512 bits, 1024 bits, 2048 bits, 3072 bits, or 4096 bits.
        If a managed NGFW is in FIPS-CC mode, RSA keys must be either 2048 or 3072 bits.
      • For Elliptic Curve DSA, select either 256 bits or 384 bits.
      • For ML-DSA, select 10496 bits, 15616 bits, or 20736 bits.
   4. Select a Digest algorithm.

      From most to least secure, the options are: sha512, sha384, sha256 (default), sha1, and md5.

      If you use client certificates for firewall services that rely on TLSv1.2, do not select sha512. Use sha384 or lower. If sha512 is required, set Max Version to TLSv1.1 in the SSL/TLS service profiles for the services.

      • For RSA, select md5, sha1, sha256, sha384, or sha512.
        If a managed NGFW is in FIPS-CC mode, you must select sha256, sha384, or sha512.
      • For Elliptic Curve DSA, ML-DSA, or SLH-DSA, select sha256, sha384, or sha512.
   5. For Expiration, enter the number of days (default is 365) the certificate is valid.
10. (Optional) Add (+) Certificate Attributes to uniquely identify the NGFW and service that uses the certificate.

    If you add a Host Name (DNS name) attribute, match it to the Common Name, because the hostname populates the Subject Alternate Name (SAN) field of the certificate and some browsers require the SAN to specify the domains the certificate protects; in addition, the Host Name matching the Common Name is mandatory for GlobalProtect.
11. (Optional) Select an OCSP Responder.
12. Save the certificate.

    The certificate displays in the Custom Certificates list.
13. To commit your changes, select Push ConfigPush.