Before you begin
Before installing the Neo endpoint and setting up your Dynamic User Protection service, verify that the antivirus software allows Neo and that Neo can communicate with Amazon Web Services.
Before you begin Neo installation, check the antivirus software and open the required ports.
- Some antivirus software may flag Neo. To ensure that installation can complete successfully, add the following executables and exclusions to the allow list for your antivirus software.
- For Windows:
- fpneoclient.exe
- fpneocommonsvc.exe
- fpneonetworksvc.exe
- fpneoprotectionsvc.exe
- fpneotextextractor.exe
- setwebconnectivitymode.exe
- fpneoxengine.exe
- fpneostophdrv.exe
- fpneodiagnostic.exe
- openssl.exe
- %programfiles%\Forcepoint\
- %programdata%\Forcepoint\
- %systemroot%\system32\drivers\fpepdc.sys
- %systemroot%\System32\drivers\fpepdci.sys
- %systemroot%\System32\drivers\fpepflt.sys
- %systemroot%\System32\drivers\fpeph.sys
- For macOS:
- com.forcepoint.neo.es
- com.forcepoint.neo.ne
- fpneoprotectiond
- fpneonetworkd
- fpneocommond
- com.forcepoint.neo.privilege-helper
- fpneotextextractor
- fpneoxengine
- The Neo endpoint communicates with managed Amazon Web Services (AWS) Cloud Services. If you have a proxy or a special network, ensure that Neo can connect to the following URLs based on the tenant region. You can find the tenant region using the .
Note: In case the organization has proxy that requires authentication, before installing the Forcepoint
Neo endpoint, the administrator should add the proxy information on the . Post this download the package which will contain the updated proxy configuration.