Cloud Connector for Azure Security Guide
Security guidance for operating Cloud Connector for Azure with Key Vault, network controls, authentication, monitoring, and incident response.
- Key Vault guidance
- Network restrictions
- Monitoring and incident response
Azure proof
Use Azure Functions and Blob workflows for fast integration with enterprise controls
The documented Azure pattern combines Azure Functions, direct and Blob Storage modes, and Microsoft-native security controls so teams can support application and Power Automate workflows inside their own subscription.
50 MB
speed path
Direct mode supports request-body PDF sealing for documents up to 50 MB when teams want a simple application call path.
Blob
scale model
Blob Storage mode supports larger files and reusable storage-based workflows, including Power Automate-driven handoff.
AAD
security controls
The docs cover Key Vault, Azure AD, API Management, IP restrictions, and network controls for production rollout.
Digest
data boundary
The Function computes the digest locally and only the signing digest leaves your Azure environment.
Security Guide
Overview
This guide covers security best practices for deploying and operating Cloud Connector for Azure in production environments.
API Key Management
Obtaining API Keys
- Visit https://secure.trusted-signatures.com
- Create an account or sign in
- Generate API keys with appropriate permissions
- Note the expiration date (maximum 1 year)
Storage and Rotation
Azure Key Vault (Recommended)
| |
Rotation Schedule
- Set up automated rotation 30 days before expiration
- Use Azure Logic Apps or Azure Automation for rotation workflows
- Maintain two active keys during rotation periods
- Test new keys before deactivating old ones
Least Privilege Access
Function App Permissions
| |
Storage Account Access
- Use managed identity for storage access
- Limit blob permissions to specific containers
- Enable soft delete for blob recovery
- Configure firewall rules to restrict access
Network Security
Function App Security
IP Restrictions
| |
VNet Integration
| |
Private Endpoints
| |
Authentication Options
Option 1: Function Keys (Basic)
| |
Usage:
| |
Option 2: Azure AD Authentication (Recommended)
| |
Option 3: API Management (Enterprise)
| |
Monitoring and Auditing
Application Insights
| |
Security Monitoring Queries
| |
Alerts
| |
Data Protection
Encryption
- In Transit: HTTPS enforced (TLS 1.2+)
- At Rest: Azure Storage encryption enabled by default
- In Memory: PDFs processed in memory only, not persisted
Data Residency
| |
Compliance
- GDPR: No personal data stored; PDFs processed transiently
- SOC 2: Azure compliance inherited
- ISO 27001: Azure compliance inherited
Incident Response
Security Event Playbook
- Detect: Monitor alerts and logs
- Assess: Determine impact and scope
- Contain: Disable compromised keys/access
- Investigate: Review audit logs
- Recover: Rotate credentials, update access
- Learn: Update security measures
Emergency Procedures
| |
Compliance Checklist
- API keys stored in Azure Key Vault
- Managed identity configured for storage access
- Network access restrictions implemented
- Application Insights monitoring enabled
- Security alerts configured
- API key rotation schedule established
- Incident response plan documented
- Regular security reviews scheduled
- Backup and recovery procedures tested
- Compliance requirements validated
Need architectural review?
Book a technical walkthrough
For enterprise rollout, we can review trust model, controls, and integration patterns with your team.