---
title: Security & Least Privilege
slug: security-and-least-privilege
docTags: 
createdAt: 2025-10-29T21:29:53.897Z
---

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.