Skip to main content

Security

Security in BoxNCase combines platform controls operated by BoxNCase with configuration and access decisions owned by each customer. This page describes the supported controls without exposing internal infrastructure or deployment configuration.

Identity and access​

  • Staff members use individual accounts; shared logins are not recommended.
  • Role-based permissions limit access to catalog, customers, orders, payments, fulfillment, apps, and settings.
  • App credentials are scoped to an environment and the permissions approved at installation.
  • Sensitive tokens belong in a secret manager, never in storefront code, browser storage, support tickets, or logs.
  • Access should be reviewed when staff roles change and immediately revoked during offboarding.

See Authentication and Permissions for supported flows.

API and webhook protections​

BoxNCase validates authenticated API requests, applies query-cost and platform limits, and isolates managed workspaces. For integrations:

  • use HTTPS for every endpoint;
  • request only the permissions required by the workflow;
  • validate webhook signatures before processing payloads;
  • make webhook handlers idempotent and safe to retry;
  • restrict API origins and storefront traffic when a workspace is private; and
  • rotate credentials after suspected exposure or a provider change.

Outbound platform requests are protected against unsafe network destinations, redirect abuse, and unbounded response times. If an integration requires a private network path or unusual destination, contact support for an approved connectivity design.

Customer and order data​

Customer, order, and fulfillment data is available only to authorized staff and apps in the relevant workspace. Payment-card details are handled by the payment provider and are not stored in full by BoxNCase. See Order privacy for role and data boundaries.

Files and rich content​

Uploads are checked against supported extensions and media types. Rich text is sanitized before display to reduce script-injection risk. Use common image, document, and archive formats; do not attempt to distribute executable or active web content through catalog media.

Shared responsibility​

BoxNCase operates hosting, platform patching, backups, availability controls, and managed service updates. Customers and partners are responsible for:

  • maintaining accurate staff access and business contacts;
  • protecting their identity provider, email, devices, domains, and DNS;
  • securing third-party systems that receive BoxNCase data;
  • reviewing app permissions and removing unused integrations; and
  • reporting suspected security incidents promptly.

Report a security issue​

Send suspected vulnerabilities or account compromise to [email protected]. Include the affected workspace, the time observed, reproduction steps, and non-sensitive evidence. Do not include passwords, API tokens, full payment data, or unnecessary customer information.

For urgent operational help that is not a vulnerability, contact [email protected].