Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

EMS Administration Guide

Using EMS integrated with FortiGate

You can integrate FortiGate with FortiClient EMS. When used together, FortiGate is used for endpoint control and network access compliance (NAC), and FortiClient EMS is used to deploy and manage FortiClient software on endpoints.

When FortiGate is configured for NAC, you can use FortiOS to create a FortiClient Compliance profile that defines compliance rules and non-compliance action. The compliance rules define what configuration FortiClient software and the endpoint must have for the endpoint to maintain access to the network through FortiGate.

FortiOS 6.0.0 and later versions use one of the following two methods to determine endpoint compliance. The FortiOS configuration determines which method is used. FortiOS versions prior to 6.0.0 only use the second method below to determine endpoint compliance. In both cases, FortiClient must be installed on the endpoint.

  1. An endpoint is considered compliant if FortiClient is managed by the EMS server authorized in FortiOS.
  2. An endpoint is considered compliant if it complies with the specific compliance rules configured in FortiOS.

The non-compliance action can be block or warn and defines what action FortiGate takes when endpoints fail to comply with the compliance rules. When the non-compliance action is block, FortiGate blocks endpoints from accessing the network when they fail to comply with the compliance rules. When the non-compliance action is warn, FortiGate warns the endpoint about non-compliance but allows network access after the endpoint user acknowledges the warning.

Although the compliance rules define what configuration FortiClient software and the endpoint must have, the FortiClient Compliance profile from FortiGate does not include any configuration information. The endpoint user or administrator is responsible for configuring FortiClient Console to adhere to the compliance rules. An administrator can use FortiClient EMS to configure FortiClient Console.

After you create a FortiClient Compliance profile using FortiOS, you can import the profile into FortiClient EMS and edit the profile to add a FortiClient installer and specify configuration information for FortiClient software. Then you can use FortiClient EMS to deploy the updated profile containing compliance rules and configuration information to endpoints.

To use EMS integrated with FortiGate:
  1. Using FortiGate running FortiOS 5.6 or a later version, define the compliance rules. Do one of the following:
    1. Configure FortiGate to consider an endpoint compliant if it has FortiClient installed and is reporting to a specified EMS server. Enter the desired FortiClient EMS server IP address or hostname. This option is only available for FortiOS 6.0.0 and later versions. If using this option, proceed to step 4.
    2. Define specific endpoint compliance rules.
  2. Using FortiClient EMS, import the FortiClient Compliance profile. See Importing FortiGate profiles.
  3. Review the compliance rules.
  4. Do one of the following:
    1. If you configured FortiGate to consider an endpoint compliant if its FortiClient is reporting to the specified EMS server, edit your endpoint profile as desired, then save. Add a FortiClient installer if needed.
    2. If importing a FortiGate profile, edit the imported profile to add configuration information that supports the compliance rules, and save the profile. You can add a FortiClient installer if needed.
  5. Create a gateway list that includes the gateway IP address or fully qualified domain name (FQDN) for the FortiGate. See Creating gateway lists.

    Each gateway list includes a list of one or more IP addresses or fully qualified domain names (FQDN) that FortiClient can use when connecting to EMS or FortiGate.

  6. Assign the gateway list to domains or workgroups as needed. See Assigning gateway lists to endpoints.

    FortiClient software uses the IP addresses in the gateway list to connect FortiClient Telemetry to EMS and/or FortiGate.

  7. Assign the profile to domains or workgroups as needed. See Assigning profiles.

    After the profile is assigned to endpoints, the settings are pushed to endpoints with the next Telemetry communication.

  8. Use FortiClient EMS to monitor and manage endpoints. See Viewing the Endpoints content pane.
  9. Use FortiClient EMS to update the profile as needed.

Using EMS integrated with FortiGate

You can integrate FortiGate with FortiClient EMS. When used together, FortiGate is used for endpoint control and network access compliance (NAC), and FortiClient EMS is used to deploy and manage FortiClient software on endpoints.

When FortiGate is configured for NAC, you can use FortiOS to create a FortiClient Compliance profile that defines compliance rules and non-compliance action. The compliance rules define what configuration FortiClient software and the endpoint must have for the endpoint to maintain access to the network through FortiGate.

FortiOS 6.0.0 and later versions use one of the following two methods to determine endpoint compliance. The FortiOS configuration determines which method is used. FortiOS versions prior to 6.0.0 only use the second method below to determine endpoint compliance. In both cases, FortiClient must be installed on the endpoint.

  1. An endpoint is considered compliant if FortiClient is managed by the EMS server authorized in FortiOS.
  2. An endpoint is considered compliant if it complies with the specific compliance rules configured in FortiOS.

The non-compliance action can be block or warn and defines what action FortiGate takes when endpoints fail to comply with the compliance rules. When the non-compliance action is block, FortiGate blocks endpoints from accessing the network when they fail to comply with the compliance rules. When the non-compliance action is warn, FortiGate warns the endpoint about non-compliance but allows network access after the endpoint user acknowledges the warning.

Although the compliance rules define what configuration FortiClient software and the endpoint must have, the FortiClient Compliance profile from FortiGate does not include any configuration information. The endpoint user or administrator is responsible for configuring FortiClient Console to adhere to the compliance rules. An administrator can use FortiClient EMS to configure FortiClient Console.

After you create a FortiClient Compliance profile using FortiOS, you can import the profile into FortiClient EMS and edit the profile to add a FortiClient installer and specify configuration information for FortiClient software. Then you can use FortiClient EMS to deploy the updated profile containing compliance rules and configuration information to endpoints.

To use EMS integrated with FortiGate:
  1. Using FortiGate running FortiOS 5.6 or a later version, define the compliance rules. Do one of the following:
    1. Configure FortiGate to consider an endpoint compliant if it has FortiClient installed and is reporting to a specified EMS server. Enter the desired FortiClient EMS server IP address or hostname. This option is only available for FortiOS 6.0.0 and later versions. If using this option, proceed to step 4.
    2. Define specific endpoint compliance rules.
  2. Using FortiClient EMS, import the FortiClient Compliance profile. See Importing FortiGate profiles.
  3. Review the compliance rules.
  4. Do one of the following:
    1. If you configured FortiGate to consider an endpoint compliant if its FortiClient is reporting to the specified EMS server, edit your endpoint profile as desired, then save. Add a FortiClient installer if needed.
    2. If importing a FortiGate profile, edit the imported profile to add configuration information that supports the compliance rules, and save the profile. You can add a FortiClient installer if needed.
  5. Create a gateway list that includes the gateway IP address or fully qualified domain name (FQDN) for the FortiGate. See Creating gateway lists.

    Each gateway list includes a list of one or more IP addresses or fully qualified domain names (FQDN) that FortiClient can use when connecting to EMS or FortiGate.

  6. Assign the gateway list to domains or workgroups as needed. See Assigning gateway lists to endpoints.

    FortiClient software uses the IP addresses in the gateway list to connect FortiClient Telemetry to EMS and/or FortiGate.

  7. Assign the profile to domains or workgroups as needed. See Assigning profiles.

    After the profile is assigned to endpoints, the settings are pushed to endpoints with the next Telemetry communication.

  8. Use FortiClient EMS to monitor and manage endpoints. See Viewing the Endpoints content pane.
  9. Use FortiClient EMS to update the profile as needed.