For automated transfers (via FileCatalyst Workflow, CLI, or API), avoid embedding credentials in scripts. Use revocable transfer keys or short-lived tokens instead. Rotate them regularly.
Whether using FileCatalyst Direct, Agent, or Central, apply patches promptly. Updates often fix security vulnerabilities that attackers could exploit to bypass account controls.
If your FileCatalyst deployment (e.g., WebDAV or Central) supports MFA, turn it on. This adds a critical second layer—even if a password is stolen, attackers can’t log in without the second factor. filecatalyst account protection
Never reuse passwords from other services. FileCatalyst supports complex passwords—use a mix of uppercase, lowercase, numbers, and symbols. Consider a password manager.
Not every user needs admin rights. Assign minimal required permissions (read/write per folder, transfer quotas). Remove or disable accounts for departing employees immediately. For automated transfers (via FileCatalyst Workflow, CLI, or
A compromised FileCatalyst account can lead to data theft, ransomware injection, or malicious file distribution. Protect your account—protect your pipeline. For detailed configuration guides, refer to FileCatalyst Security Best Practices or contact your system administrator.
Always log out from shared workstations. Avoid saving passwords in browsers. When using FileCatalyst HotFolder or WebApp, ensure you’re on a trusted network (use VPN for remote access). Whether using FileCatalyst Direct, Agent, or Central, apply
Here’s a concise text on , suitable for an internal security memo, user guide, or awareness post. Keeping Your FileCatalyst Account Secure Your FileCatalyst account is a gateway to high-speed, mission-critical file transfers. Protecting it isn’t just IT’s responsibility—it’s yours. Follow these key practices to prevent unauthorized access and data breaches.