Filecatalyst Application Security |work| Jun 2026

| Role | Permissions | |------|--------------| | | Full system, user, and transfer rule management | | User | Own transfers only, predefined workflows | | Auditor | Read-only logs and transfer history | | API Client | Programmatic access with rate limiting |

To ensure the security of FileCatalyst applications, organizations should implement the following best practices: filecatalyst application security

Enterprises can maintain a "single source of truth" for user identities. This ensures that when an employee leaves the company, their access to FileCatalyst is revoked automatically. | Role | Permissions | |------|--------------| | |

| Component | Security Function | |-----------|------------------| | | Server daemon handling authentication, transfer logic, and encryption | | FileCatalyst Central | Web-based management UI with database back-end | | FileCatalyst Workflow | Automation engine with hotfolder monitoring and external integration | | Transfer Agent (client) | Endpoint software for send/receive operations | filecatalyst application security

1. The Core of FileCatalyst Security: UDP-Based Acceleration

The "handshake" and command instructions between the client and server are protected via SSL/TLS, preventing "man-in-the-middle" attacks from hijacking the session. 5. Ensuring Data Integrity