How can we properly secure NRGship files on FileMaker Server?

With the recent cases of AI bots wreaking havoc on FileMaker hosting providers, we wanted to share some best practices for hosting NRGship files on FileMaker Server.


In admin console, check your settings.

  • Limit access to admin console to known IPs
  • Do not use common user/passwords for admin console (ex: admin/admin)
  • Notifications should be enabled to some admin that will actively monitor
  • "Filter databases in client applications" should be enabled
  • Disable connectors not in use. If you do not need WebDirect, the Data API or OData, disable them

We recently released a command-line tool which can be used to check your FileMaker Server for configuration issues externally using the same methods that AI bots are using. You can download the fmcheck tool on GitHub. It will check your files for exposure thru the Data API and then check for access using different methods.


While NRGship files use auto-login for ease of access, these accounts can be easily modified by logging into the NRGship files with access to database security. You can add/disable accounts, change passwords, or add external authentication groups. For ease of use, we highly recommend customers implement external authentication as you can simply create a NRGship group on your auth server and then add that group in NRGship to limit access to necessary users.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us