System Specifications Requirements


FieldValue
Version1.0
Effective DateApril 2026
Review CycleAnnual
Document OwnerChief Information Security Officer (CISO)
ClassificationCONFIDENTIAL — Internal Use Only
Applicable StandardSOC 2 Type II — Security, Availability, Confidentiality

1. Purpose and Scope

This document provides the technical specifications and requirements governing how data and items are stored, processed, and maintained within QA Touch. It serves as the authoritative technical reference for engineering, operations, and SOC 2 auditors, supporting Processing Integrity (PI1), Availability (A1), and Confidentiality (C1) Trust Service Criteria.

2. Application Tier Specifications

ComponentSpecification [VERIFY all values]
Application Framework[e.g., Node.js + Express / Ruby on Rails / Django / Spring Boot] — verify with engineering
API ProtocolRESTful HTTP/JSON; OpenAPI 3.0 specification maintained and published
Authentication FrameworkServer-side session tokens + JWT for specific flows; OAuth 2.0 for SSO and integrations
Background Job Queue[e.g., Sidekiq / Celery / BullMQ / AWS SQS] — used for async notifications, sync, export
Real-time / WebSocket[e.g., ActionCable / Socket.io / Pusher] — used for in-app notifications and run progress
ContainerisationDocker containers orchestrated via Kubernetes (EKS / GKE) or ECS [VERIFY]
Service Mesh / mTLS[e.g., Istio / AWS App Mesh] — mTLS for inter-service communication [VERIFY adoption]
Search EngineElasticsearch / OpenSearch [VERIFY] — full-text search for test cases and defects

3. Database Tier Specifications

SpecificationValue [VERIFY]
Primary DBMSPostgreSQL [VERIFY version] — managed service (RDS / Cloud SQL)
ORM / Query Layer[e.g., ActiveRecord / SQLAlchemy / TypeORM] — all queries parameterised
Connection PoolingPgBouncer or managed connection pooler [VERIFY]
Read ReplicasMinimum 1 read replica in separate availability zone [VERIFY]
Automated FailoverManaged service failover; RTO < 60 seconds for DB failover [VERIFY]
Point-in-Time RecoveryPITR enabled; minimum 7-day retention window [VERIFY]
Character EncodingUTF-8 enforced across all tables
Transaction IsolationRead Committed (default); Serializable for concurrent critical operations [VERIFY]
Multi-tenancy Enforcementworkspace_id column on all customer data tables; enforced at ORM and query layers

4. Object Storage Specifications

SpecificationValue [VERIFY]
ProviderAWS S3 / GCP Cloud Storage [VERIFY]
Durability99.999999999% (11 nines) per provider SLA
Bucket VersioningEnabled for attachment and backup buckets
Public Access BlockEnabled at bucket-level and account-level policies
Pre-signed URL TTL24–72 hours for exports; shorter for AI input files [VERIFY]
Lifecycle PoliciesAuto-deletion: import staging (24h); export packages (72h); log archives (per retention schedule)
Cross-Region Replication[VERIFY if configured for DR purposes]
EncryptionAES-256 SSE-S3 or SSE-KMS [VERIFY]

5. Network and Security Specifications

SpecificationValue [VERIFY]
CDN / WAFCloudflare / AWS CloudFront + WAF; OWASP Core Rule Set enabled
Load BalancerApplication Load Balancer (ALB / Cloud LB); TLS termination at load balancer layer
VPC / Network IsolationApplication in private subnets; database and cache not exposed to public internet
Ingress RulesPort 443 (HTTPS) only from internet; all other ports restricted to VPC internal traffic
DDoS ProtectionManaged by CDN / WAF provider
DNS[Route 53 / Cloud DNS]; DNSSEC enabled [VERIFY]
Internal NetworkPrivate subnets for application and data tiers; no direct internet access from internal services

6. Data Storage Format Requirements

Data TypeStorage FormatLocationSize Constraint
Test case text fieldsUTF-8 VARCHAR / TEXTPrimary DBTitle: 255; Description: 10,000 chars
Test stepsJSON array of step objectsPrimary DBPer step: 5,000 chars action + 5,000 expected [VERIFY]
File attachmentsBinary in object storage; metadata in DBObject Storage + DB20 MB per file [VERIFY]
Import files (upload)Original binary in temp object storageObject Storage (temp)10 MB per file [VERIFY]
Export filesGenerated .xlsx / .csv / .pdfObject Storage (TTL)Generation timeout applies [VERIFY]
Audit log eventsJSON document; append-onlySIEM / Log storeNo per-record limit
Session tokensOpaque random string; server-side storeRedis cache< 1 KB
Integration credentialsEncrypted; stored in secrets storeSecrets ManagerN/A
AI promptsTransient transmission; minimal QA Touch storage [VERIFY]LLM provider / minimal DB [VERIFY]Per prompt max length limit

7. Processing and Maintenance Requirements

  • All customer data changes must be written within ACID database transactions; no partial state allowed.
  • Async job queues process events in-order within workspace context; out-of-order processing prohibited for state-changing operations.
  • Search index updates must not block the primary write path; eventual consistency acceptable for search.
  • Reports query the primary database (not read replicas) for current record counts to guarantee accuracy.
  • Database vacuuming and index maintenance scheduled during off-peak hours (assumption: 02:00–04:00 UTC).
  • SSL/TLS certificate renewal automated (Let’s Encrypt / ACM [VERIFY]); expiry alert raised 30 days before deadline.