This document defines the guidelines and controls governing how DCKAP Integrator is configured — both at the platform infrastructure level and at the individual customer integration level — to ensure that system processing meets accuracy, security, and performance requirements.
2. Platform-Level Configuration Standards
2.1 Infrastructure Configuration
Component
Configuration Standard
Owner
API Gateway
TLS 1.2+ enforced; rate limiting enabled; WAF rules active
Platform Engineering
Message Queue
Durable queues with at-least-once delivery; DLQ enabled
Platform Engineering
Processing Workers
Autoscaled; CPU/memory limits set; health checks every 30s
Platform Engineering
Database (Config Store)
Encrypted at rest (AES-256); daily backups; point-in-time recovery
Platform Engineering
Credential Vault
Secrets encrypted with customer-specific keys; access logged
Security Engineering
Logging Pipeline
PII masking applied before log storage; logs immutable for 90 days
Platform Engineering
2.2 Security Configuration Baseline
No default credentials in use — all service accounts require unique, rotated credentials.
Principle of least privilege enforced — each service has only the permissions it needs.
All configuration changes logged in the infrastructure change management system.
Production configuration changes require peer review and change advisory board (CAB) approval.
3. Customer Integration Configuration Guidelines
3.1 Connector Configuration
Each connector must have a dedicated, scoped API credential — shared credentials are not permitted.
API credentials are stored in the DCKAP Vault and never exposed in logs or UI after initial entry.
Connector endpoint URLs must use HTTPS — HTTP-only endpoints will be rejected by the platform.
Credential rotation must be performed at least annually or immediately upon suspected compromise.
3.2 Data Flow Configuration
Every integration flow must have at least one mandatory field defined — unmapped flows are blocked from activation.
Business rules must be tested in sandbox mode before activation on production data.
Customers are recommended to enable ‘strict mode’ which rejects records with any unmapped field.
Error notification email must be configured before an integration flow is activated.
3.3 Sync Schedule Configuration
Setting
Permissible Range
Default
Scheduled Sync Interval
1 minute to 24 hours
Every 1 hour
Retry Attempts
0 to 5
3
Retry Back-off
Exponential, 30s base, max 30 minutes
Exponential
Dead-letter Retention
1 to 30 days
7 days
Batch Size
1 to 5,000 records per API call
100
4. Configuration Change Management
All customer configuration changes are timestamped and attributed to the user who made them.
Configuration history is retained for 1 year and is available to customer admins in the portal.
Rollback to any previous configuration version is available within the configuration history view.
