Shared Responsibility Model

What Shipber secures

1. Cloud infrastructure and platform — Security “of” the cloud: hosting environment, network perimeter, load balancing, and underlying systems we control.
2. Application security — Secure SDLC, code review, dependency scanning, and regular penetration testing for Shipber-managed components.
3. Encryption — TLS for data in transit; encryption at rest for customer data stored by Shipber.
4. Secrets and key handling — Secure storage and rotation of service credentials we generate and manage for the platform.
5. Shipber workforce access — Least-privilege access, strong MFA, and just-in-time controls for Shipber personnel.
6. Backups and service continuity — Regular backups, tested restore procedures, and resiliency measures to meet our availability targets.
7. Vulnerability and patch management — Continuous monitoring, patching, and risk-based remediation of Shipber-managed systems.
8. Logging and detection — Centralized logging for security-relevant events, alerting, and abuse detection on the platform.
9. Security incident response — Triage, containment, investigation, and customer notification per our Security Incident Management guideline and the DPA.
10. Subprocessor oversight — Vendor due diligence, security and privacy reviews, and contractual safeguards for approved subprocessors.
11. Compliance program — Policies, training, and externally attested controls aligned to common standards; details are published in our trust materials.
12. Product guardrails — In-product controls (for example: role-based access, audit logs, API rate limits, webhook signing) and secure defaults.

What you secure

1. Identity and access — Your SSO/MFA settings, password policy, SCIM provisioning, role assignments, and periodic access reviews.
2. Tenant configuration — Organization settings, allowed domains, session timeouts, IP allow lists, and other security options in the admin UI.
3. Data governance — What data you upload, lawful basis and notices, retention choices, and redaction/pseudonymization as needed.
4. Endpoint and network hygiene — Your devices, browsers, local networks, and email security (phishing protection, DMARC, etc.).
5. Admin processes — Joiner-mover-leaver/offboarding, change management, and approvals for elevated privileges.
6. API & webhook secrets — Storage, rotation, and usage of your API keys, signing secrets, and OAuth client credentials.
7. Marketplace apps you install — Vetting, approvals, scopes granted, data flows enabled, and ongoing review of third-party apps.
8. Integrations & custom code — Secure development, secret handling, and monitoring for any scripts, middleware, or iPaaS you operate.
9. Carrier accounts and credentials — Provisioning, rotation, and compliance with carrier terms for accounts you connect to Shipber.
10. Your business continuity — Local exports, playbooks, and contingencies specific to your operations.

Shared responsibilities (by area)

1. Marketplace apps & integrations
   1. You: decide which apps to install; grant minimum required scopes only; review vendor security/privacy; periodically re-authorize or remove unused apps; monitor activity and revoke access when no longer required.
   2. You (periodic review): run a quarterly permissions review with app owners; compare granted scopes vs. actual use; remove stale webhooks/credentials.
   3. Shipber: provide an integration framework, OAuth scopes, webhook signing, logs where available, and the ability to disable apps that violate policies.
   4. Third-party vendors (apps/connectors/carriers): operate under their own terms and privacy notices. Their obligations are not assumed by Shipber.
2. APIs and webhooks
   1. You: protect and rotate API keys; secure webhook endpoints (TLS, auth, replay protection); handle retries idempotently.
   2. Shipber: enforce TLS, authentication, rate limits, event signing, and provide developer documentation and sandbox resources.
3. Data retention and deletion
   1. You: choose retention settings, delete data you no longer need, and request deletion per your policies.
   2. Shipber: expose admin controls and APIs; perform secure deletion upon request/contract end; manage backups with lifecycle controls.
4. Incident management
   1. You: promptly report suspected account compromise or exposed credentials; cooperate in response and remediation.
   2. Shipber: investigate and notify per our Security Incident Management guideline and the DPA; share indicators and recommended actions.
5. Continuity and recovery
   1. You: maintain operational playbooks (for example, alternative workflows if an integration is down).
   2. Shipber: maintain platform-level backup/restore and service resiliency.

Carrier accounts and external services

1. You own the credentials and terms for any carrier or external service you connect.
2. Shipber transmits and stores such credentials securely and uses them only to provide the features you enable.
3. If we detect misuse, invalid credentials, or material risk, Shipber may temporarily suspend a connection to protect your data and the platform; you will be notified with next steps.
4. Carriers and external services determine their own security, data handling, and adjustments under their contracts with you.

Quick admin checklist

1. Enforce SSO and MFA for all admins; prefer SCIM for provisioning.
2. Assign least-privilege roles and review access quarterly.
3. Review installed marketplace apps and audit granted scopes.
4. Rotate API keys and webhook secrets; enable IP allow lists where available.
5. Configure retention and deletion; test a sample deletion workflow.
6. Monitor audit logs and set alerts for sensitive actions.
7. Offboard users promptly and revoke stale tokens.
8. Validate carrier/integration credentials on a schedule; remove unused connections.
9. Ensure your Security Contact and Admins enable relevant notification subscriptions; verify email deliverability; choose channels (in-product or email).

Related reading

• Security Incident Management (how we triage, contain, and notify)
• Data Processing Addendum (roles, instructions, deletion/return, subprocessors, and audits)
• Shipber Services Agreement (commercial terms, limitations, dispute resolution)