Inside Activate
Connectors
Security & Least Privilege
5 min
connectors interact with external systems and internal data tables, so applying least privilege principles ensures both performance and compliance general principles each connector should operate under a dedicated service account limit that account’s access to only the data source and actions required protect all credentials and connection strings via secure parameters in activate enable ssl/tls for all remote data connections (sql, api, etc ) avoid embedding secrets in xml workflow definitions database permissions component minimum required rights activate sql database db datareader, db datawriter, execute on connector stored procedures external sql source select access only on required views or stored procedures history tables insert only; read only access for audit purposes file system access limit connector accounts to read access for import file locations use secure folders or shared drives with audit logging ensure temporary or staging directories are periodically cleared api and web service access use oauth or api key authentication with least privilege scopes rotate api keys periodically and revoke old credentials immediately on role change restrict outbound network traffic from the activate server to required api hosts only credential storage store connection strings and api keys in secure parameters or windows credential manager avoid plaintext passwords within workflows or scripts use activate’s encrypted parameter types where available auditing and logging enable audit logging for connector workflow runs monitor change events in history tables and access logs implement alerting for abnormal access patterns or frequent retries compliance and review review access rights quarterly and remove unused accounts verify that connectors using personal or sensitive data align with data protection policies document data flows and system boundaries for each connector