Security & Compliance
Authentication
All access to the Shoplogix IMS platform requires authentication:
- User sessions — OAuth 2.0 with Auth0, using industry-standard OIDC login flows. Users authenticate with their email address.
- SSO — Enterprise accounts can configure Single Sign-On so users authenticate through your organization's identity provider. See Single Sign-On for setup details.
- API / M2M access — OAuth 2.0 client credentials flow (client ID and secret). API credentials are scoped to specific customers and privilege levels.
Tokens are JWTs validated on every request. There is no cookie-based session state — all API calls are stateless.
Authorization
The platform uses role-based access control (RBAC) with eight privilege levels. Every API request is checked against the requester's scoped privileges before data is returned or modified. Privileges are scoped per customer — a credential issued for one customer account cannot access another customer's data.
See User Management & Access Control for the full list of roles.
Transport Security
- All communication between clients and the Shoplogix IMS platform uses TLS (HTTPS/MQTTS)
- The data broker supports MQTT over TLS (port 8883); direct AMQP access is not offered
- Webhook payloads are signed with HMAC-SHA256 using a per-subscription secret so you can verify that events came from Shoplogix
Data Handling
Multi-tenant isolation: Each customer's data is logically isolated. The message broker uses a dedicated virtual host per customer. API privilege scopes enforce per-customer access boundaries.
Data retention:
| Data Type | Retention |
|---|---|
| Raw sensor readings | ~1.5 years (548 days) |
| Sensor aggregates | ~6 months (180 days) |
| Event log | ~3 months (90 days) |
| Gateway status | ~1.5 years (548 days) |
File storage: User-uploaded files are stored in AWS S3. All file download requests are validated against your authentication token before content is served. File access is per-user.
Webhook Security
Webhook delivery uses the HTTP Signatures standard (draft-cavage-http-signatures-12) with HMAC-SHA256. Each webhook subscription has its own unique signing secret. Verify the Signature header on every incoming webhook to confirm the payload originated from Shoplogix.
See Webhooks for verification instructions.
Infrastructure Security
The platform runs on AWS infrastructure. Security practices include:
- All services run in private VPCs with controlled ingress/egress
- Secrets are managed via HashiCorp Vault with dynamic, time-limited credentials where possible
- Container images are scanned for known vulnerabilities as part of the build pipeline
- Dependency vulnerability tracking is performed continuously using industry-standard SBOM tooling
Questions & Compliance Documentation
If you have specific compliance requirements (SOC 2, ISO 27001, GDPR, etc.) or need a security questionnaire completed, contact your Shoplogix account team.