Claris has recently warned of ongoing password-spraying attacks targeting FileMaker Servers worldwide. These automated attacks attempt to gain unauthorized access by testing commonly used passwords against multiple accounts, particularly on servers with services exposed to the internet.
Although the warning does not indicate that every FileMaker Server is vulnerable or compromised, it highlights an often-overlooked aspect of business applications: the infrastructure behind them.
For companies relying on FileMaker to manage orders, production, customer information, or other essential operations, security is only one part of a broader concern. Performance, availability, backups, and maintenance all depend on how the application is hosted and managed.
When the application isn’t the problem
Businesses often invest in improving their FileMaker applications while leaving the underlying infrastructure largely unchanged. Over time, growing numbers of users, remote access requirements, and new integrations can put additional pressure on environments that were originally designed for very different needs.
The consequences aren’t always dramatic. Sometimes they appear as slower performance, unreliable connections, or increasingly complicated maintenance. In other cases, they become visible only when an update fails or an unexpected interruption affects daily operations.
We encountered a similar situation with a French agricultural company whose FileMaker environment was experiencing performance and reliability challenges. Rather than replacing an application that continued to meet its business needs, Direct Impact Solutions helped the company migrate to a more suitable cloud infrastructure and improve its backup arrangements.
The project, described in our Secure Cloud Migration of Claris FileMaker Client Wins story, illustrates how infrastructure improvements can extend the useful life of an existing application.
Who is responsible for keeping FileMaker running?
The recent attacks make this question particularly relevant.
In many organizations, application development, server administration, and network management are handled by different people or providers. This arrangement can work well, provided responsibilities are clearly defined and the environment is regularly reviewed.
Security configurations, software updates, backups, and recovery procedures should not become concerns only when something goes wrong.
Nor does every organization need to move to the cloud. An appropriately maintained on-premises server can be a valid choice, just as specialized hosting may be more suitable for businesses without dedicated FileMaker infrastructure expertise.
What matters is understanding the requirements of the application and ensuring that its infrastructure continues to meet them.
For organizations considering changes, our FileMaker Server Migration Checklist explores the practical aspects of moving an existing environment.
An opportunity to reassess
Claris’s warning deserves attention, particularly from organizations running internet-accessible FileMaker Servers. Reviewing access restrictions, monitoring login attempts, and verifying backup arrangements are sensible immediate precautions.
But the broader lesson goes beyond this particular threat. As FileMaker applications become increasingly important to business operations, their infrastructure deserves the same attention as the applications themselves.
At Direct Impact Solutions, we regularly help organizations evaluate and improve existing FileMaker environments, whether through application modernization, infrastructure optimization, or FileMaker hosting.
Sometimes, the most valuable improvement isn’t a new feature. It’s making sure the system everyone already depends on continues to work.