Security
A plain statement of what data protection exists in Provider Core today, and what does not. This is an early-stage platform — we would rather tell you the gaps directly than let you assume they’re filled.
What exists today
Append-only audit trail
Every mutation across the platform emits an audit event (actor, action, resource, before/after references, reason) through a shared audit package — not bolted on per-feature.
Credentials stored as vault references, never as secrets
Provider credentials (e.g. payment gateway keys) are modeled as an opaque vault-reference path plus metadata. No column anywhere stores a plaintext secret value.
Environment isolation for credentials
Sandbox, staging, and production credentials are tracked as separate rows and never mixed in a lookup — a sandbox key cannot silently answer for a production one.
Cross-tenant data isolation at the API layer
Requests are scoped to the requesting organization; one customer's data is not returned to another's request.
Structured logging with credential redaction
Application logs redact Authorization and Cookie headers rather than writing them in the clear.
Payments gated behind sandbox-only defaults
Live payment processing code paths are off by default and require an explicit, separately-confirmed opt-in — nothing charges a real card without that step.
What does not exist yet
- No SOC 2 report, ISO 27001 certification, or any other third-party security certification.
- No penetration test has been performed against this platform.
- No independent security audit has been performed.
- No metrics, tracing, or monitoring dashboard exists in production — only structured logs and the audit trail.
- No backup has ever been taken, and no automated backup schedule is configured.
- No disaster-recovery exercise has ever been performed.
- No production Moyasar (payment) account has ever processed a real transaction through this platform.