Compliance preset pack
A SkyeConnex configuration bundle that encodes a regulatory framework's expectations into the platform's policy primitives. Selecting a pack writes encryption posture, jurisdictional policy, retention defaults, format standards, and audit treatment in a single action.
The problem packs solve
Most compliance configuration is the same translation problem repeated per organisation: take a framework (PIPEDA, GDPR, SOC 2, HIPAA-BAA, FedRAMP), interpret it into encryption, geo, retention, and audit choices, document the mapping for auditors, then maintain it across configuration drift. Compliance preset packs perform this translation as a one-click action.
Packs shipped today
- PIPEDA — Canadian residency allow-list, Federal Privacy Act-aligned retention, signed audit log
- GDPR / UK-GDPR — EU residency allow-list, DSAR-ready audit log, signed deletion certificates
- SOC 2 Type II — control evidence collection, continuous monitoring, access controls
- HIPAA-BAA — BAA-able encryption posture, healthcare-grade audit, breach detection
- FedRAMP — US-only residency, IL2-IL5 amenable, continuous monitoring
- DGSI 100-8 (Sovereign / Defence) — Canadian Standards Council sovereign-cloud tier
What a pack actually writes
Encryption policy: algorithm class, key wrap strategy (including hybrid PQ wrap for sovereign-tier packs), per-frame IV scheme, AAD binding.
Geo policy: allow-list or block-list of jurisdictions for shard placement. Strict-mode hooks where the framework requires fail-rather-than-degrade behaviour.
Retention policy: per-class file retention, trash window, audit-log retention, certificate retention.
Audit treatment: event types signed by default, export format, streaming destinations.
The pack as documentation
Selecting a pack is the documentation of what was applied. Auditors read the pack definition line-by-line against the framework. There's no separate "compliance configuration matrix" to maintain — the pack IS the matrix, and it's enforced by the platform rather than by procedure.
Customisation
Packs are starting points, not handcuffs. Each policy element can be tightened (you can be stricter than the pack) or — within the bounds of the framework — adjusted to your specific risk model. Drift from the pack is logged and surfaced in compliance reports.
Multi-tenant packs
Different business units can have different packs. The effective-policy cascade (Reseller → Company → Account) handles inheritance and overrides cleanly.
Related terms
See also
Posts that mention Compliance preset pack
Healthcare data residency: PIPEDA + HIPAA + provincial — a survival guide
Healthcare data in 2026 must satisfy PIPEDA, HIPAA, provincial health acts, and emerging AI compliance — often simultaneously. The architect…
Read → Regulation · 9 min readSchrems II two years on: what actually changed for EU-US data transfers
The 2020 CJEU ruling invalidated Privacy Shield. Five years and one EU-US Data Privacy Framework later, the underlying problem remains. Here…
Read → Regulation · Canada · 7 min readPIPEDA and cloud storage: what most providers get wrong
PIPEDA predates the cloud. Applying it to multi-cloud workloads requires architectural thinking that most providers don't do. Here's the gap…
Read →