← Back to gillside.com

Security at Gillside

How we protect tenant data, what we monitor, and how to report vulnerabilities. This page reflects the platform's current state and is updated when controls change.

Architecture summary

Encryption

TLS 1.2+ end-to-end (Cloudflare → CloudFront → API Gateway → Lambda). RDS encrypted at rest, SSL forced. S3 SSE-AES256. Cross-region DR backups encrypted with customer-managed KMS key.

Tenant isolation

Per-tenant DB schema + DB user with scoped grants. Per-tenant Cognito user pool. Per-tenant IAM Lambda role. Row-level security policies on shared platform tables.

Identity

AWS Cognito with PBKDF2-stored credentials. Short-lived JWTs. Email verification on sign-up. Admin (Tier-1) accounts are invite-only — no anonymous account creation.

Monitoring

AWS GuardDuty for threat detection. CloudTrail multi-region trail with alarms on root login, IAM changes, security-group changes. Structured JSON logs with baseline tags.

OWASP Top 10 (2021) mitigations

Per-category review of how the platform mitigates each risk. Click a row to expand details.

Compliance & attestations

  • SOC 2:Not yet attested. We follow the SOC 2 control framework as guidance; formal Type 1 attestation will be scoped when a customer pipeline justifies the cost (~$15-30k first year).
  • GDPR:Data Processing Agreement template under development. Right-to-be-forgotten workflows will be supported per-tenant.
  • Pen test:Annual third-party pen test scheduled for the first paying tenant onboarding window. Findings + remediations will be summarised here.
  • Industry:Designed against OWASP Top 10 (above) + NIST CSF identifying-protect-detect-respond functions.

Vulnerability disclosure

Found a security issue? Please email security@gillside.com with details. We aim to acknowledge within 5 business days.

Programmatic info: /.well-known/security.txt (RFC 9116).

Last updated: 2026-04-27. We update this page when controls change.