Purpose
This section is intended for information security and security review personnel at customer organizations. It documents ARGOS Identity’s communication architecture and data security policies.- Uses standard security terminology and industry-standard protocol names
- Does not include internal resource identifiers (server names, function names, domains, etc.)
Target Audience
- Information security and security review personnel at customer organizations
- Personnel conducting data processing due diligence (data controller/processor relationships)
- Compliance / audit departments
- Backend development teams performing API integration
- Development teams building and operating Webhook receiving endpoints
ARGOS Service Categories
ARGOS Identity offers four service categories. The communication architecture and security policies for each category are covered in the sub-pages below.Liveform
End-to-end identity verification service including a UI. End User ↔ Liveform UI ↔ API Gateway ↔ Verification Processing Layer. Hybrid payload encryption (RSA-2048 + AES-256-GCM), API Gateway authentication, Cloudflare Turnstile, Private Token.
Restful API
Server-to-Server API with no UI. Standard REST (GET/POST/PATCH/DELETE), Custom Domain + ACM TLS termination, API Key validation, optional payload encryption (AES-256), Rate Limiting / Usage Plan.
Webhook
Asynchronous result notification from ARGOS to customers. Two-stage pipeline (convergence layer + dispatch layer), TLS 1.2+, optional body encryption (AES-256), retry (exponential backoff), dispatch audit log, IP allowlist recommended.
Database
Internal data storage layer (AWS DynamoDB). SigV4 invocation, dual encryption (server-side + application-layer AES-256-GCM), VPC Gateway Endpoint, IAM isolation, PITR / CloudTrail.