Security overview
Security that works with your infrastructure, not against it.
StoreShield is designed for self-hosted deployment. The key idea is simple: brands keep control of their infrastructure, data, access rules, and operational security model while StoreShield provides the product logic and deployment guidance.
1. No vendor lock-in
StoreShield does not assume the brand must run inside a single hosted environment. Deployment is designed to fit the customer’s existing infrastructure strategy.
- Deploy on a brand-owned VM, private cloud, on-prem machine, or managed environment.
- Use Docker Compose for simple self-hosted setup, or Terraform for infrastructure-as-code operations.
- Choose a cloud marketplace option when the brand wants a provider-native deployment model.
- Keep configuration, networking, and scaling choices under the customer’s control.
2. Data protection
StoreShield is built to be used inside the customer’s own security boundary. The brand remains responsible for protecting the data it stores and processes.
- Encryption at rest is managed through the customer’s storage and database configuration.
- Secrets are stored and rotated through the customer’s chosen secret management system.
- Backup, retention, deletion, and disaster-recovery procedures remain under customer ownership.
- Audit logs and access records should be retained according to the customer’s internal policy and compliance needs.
3. Own your infrastructure
StoreShield is not meant to replace the customer’s operational security model. It is meant to fit inside it.
- Operating system patching and hardening remain the customer’s responsibility.
- Identity, single sign-on, MFA, and role policy are configured in the customer environment.
- Network segmentation, firewall rules, and outbound controls are defined by the brand’s infrastructure team.
- Monitoring, incident response, and policy enforcement remain operational responsibilities of the customer.
4. Secure-by-design, not automatic compliance
StoreShield should be described as secure self-hosted software by design, not as a certification that automatically makes a brand compliant.
- Customer environments must still be assessed against relevant requirements.
- If payment-adjacent systems are involved, PCI DSS and related controls must be reviewed across the full environment.
- StoreShield’s deployment does not certify the brand’s POS, network, payment processor, people, or procedure design.
5. Shared responsibility model
StoreShield provides secure product design, deployment guidance, hardening recommendations, and implementation support. The customer remains responsible for the operational controls around the environment that runs it.
- StoreShield provides structure and guidance.
- The customer owns the runtime environment, security controls, and day-to-day operations.
- Security posture depends on the customer’s infrastructure decisions and operational discipline.
6. Operational security checklist
For a secure deployment, the implementation should support the following at minimum:
- TLS for API and dashboard traffic.
- Strong API authentication.
- Role-based access control.
- Optional SSO for enterprise deployments.
- MFA where supported by the identity provider.
- Secure secret storage and rotation.
- Audit logs and access review.
- Network isolation and restricted outbound access.
- Regular patching and hardened container images.
- Backup, restore, and retention procedures.
- Rate limiting and request validation.