Sansec security policy
by Sansec management team
Published in Guides
Security controls, data scope and hosting for eComscan and Shield. Written for vendor security reviews.
This page answers the questions that vendor risk teams usually ask about Sansec. It covers eComscan and Sansec Shield. It lists the controls we run and the data we receive, and also what we do not have.
| Company | Sanguine Security B.V. (Sansec), Utrecht, the Netherlands, founded 2015 |
| Owner of this policy | Sansec management team |
| Last reviewed | November 2026 (reviewed yearly and after any material change) |
| Security contact | support@sansec.io, see security.txt |
1. Data scope
eComscan and Shield run on the customer's own servers. Scanning and request filtering happen there. Sansec receives only the data listed below, for the customer's dashboard and reports.
| Product | Processed on the customer server | Sent to Sansec | Retention at Sansec |
|---|---|---|---|
| eComscan | Source code, system configuration, cron jobs, database structure and admin account settings | Scan findings: file path, matched signature, severity | 12 months, then deleted |
| Shield | HTTP headers and request arguments of incoming requests | Requests that match a Shield rule, with sensitive headers removed before sending | 7 days in hot storage, 3 months in cold storage, then deleted |
Both products report to the dashboard by default. Customers can turn this off at any time. Scanning and blocking keep working, and no scan findings or request data leave the server.
- eComscan: run scans with
--skip-dashboard. This cannot be combined with--reportor--monitor, which mail the results. - Shield:
bin/magento config:set sansec_shield/general/report_enabled 0
eComscan does not read order data, customer profiles or payment information. Sansec does not receive or store cardholder data, health data (PHI) or biometric data. Payments for Sansec licenses go through Chargebee and Stripe, so card data never reaches Sansec systems.
Under the GDPR, the customer is the data controller for personal data on its own servers. For the data that reaches Sansec through the dashboard or reporting, Sansec acts as processor under our Data Processing Agreement.
Customers keep ownership of their data. Dashboard data is deleted at the end of the contract or on request.
2. Hosting
Sansec does not operate its own datacenters. All Sansec servers run at Hetzner Online GmbH in Germany, in ISO 27001 certified datacenters. Physical security, power redundancy and network connectivity are provided by Hetzner. Dashboard data is stored in the EU.
Subprocessors
These subprocessors handle data of eComscan and Shield customers. Section 5 of our Data Processing Agreement refers to this list. We update it before we add or replace a subprocessor.
| Subprocessor | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Servers, dashboard data and Shield reports | Germany |
| Cloudflare, Inc. | DNS, CDN and TLS for sansec.io, the dashboard and the eComscan and Shield APIs | Global network (EU SCCs) |
| Postmark (ActiveCampaign LLC) | Transactional and alert email | EU / US (EU SCCs) |
| Fastmail Pty Ltd | Business email, including support correspondence | Australia / US (EU SCCs) |
| Functional Software, Inc. (Sentry) | Error reports from eComscan and Sansec servers | US (EU SCCs) |
| IPinfo, Inc. | Geolocation of attacker IP addresses in Shield reports | US (EU SCCs) |
| Chargebee, Inc. | Subscriptions and invoicing | US (EU SCCs) |
| Stripe Payments Europe, Ltd. | Card payments (PCI DSS Level 1) | Ireland / US (EU SCCs) |
3. Product security
The eComscan agent is a compiled Go binary with no runtime dependencies or interpreters. Its releases are signed with a GPG key stored on a hardware YubiKey. Only the Sansec management team can sign a release. Shield is a PHP module for Magento, open source under the MIT license. Customers install it with Composer and can review its code on GitHub.
Agent traffic to Sansec uses TLS. Each installation authenticates with a license token that Sansec can revoke. Customers can run the agent as an unprivileged user and restrict its outbound traffic to Sansec endpoints, or disable all reporting and run fully offline apart from signature updates.
The customer dashboard supports ownership and member roles and expires idle sessions.
4. Infrastructure
Servers run Ubuntu LTS. Security updates are installed automatically every day. Each server runs a host firewall that denies all incoming traffic by default and only exposes the public services it hosts.
Internal services and server administration are reachable only over a Tailscale VPN. SSH accepts key authentication only, no passwords. Logs are collected centrally. Alerts on availability and errors reach staff phones around the clock.
Production data is backed up daily. Backups are encrypted and kept for 30 days. We test a full restore at least once a year.
5. Staff and access
Sansec has fewer than 10 staff, all based in the EU. Every employment and contractor agreement includes a confidentiality clause. New staff get security training at onboarding.
Staff accounts are protected with hardware security keys (GitHub) and multi-factor authentication (email). Laptops use full-disk encryption and install OS updates automatically. Access is granted per role and revoked within 24 hours when someone leaves.
6. Development
All code lives in a GitHub organization that enforces two-factor authentication with hardware keys. The main branch is protected, and every change needs a reviewed pull request. CI runs linters and checks dependencies against known vulnerabilities. Confirmed vulnerabilities in our products or systems are fixed or mitigated within 24 hours.
7. Incident response
The management team handles security incidents. If an incident affects customer data, we notify the affected customers within 72 hours of confirming it. Sansec has had no breach of customer data since it was founded in 2015.
Security researchers can report issues via our bug policy.
8. AI use
eComscan and Shield detect threats with signatures and rules written by our researchers. Neither product uses AI models. Staff use AI coding and writing tools. Customer scan findings and Shield request data are not sent to external LLM providers.
9. What we do not have
Sansec does not hold a SOC 2 or ISO 27001 certification. Our hosting provider is ISO 27001 certified, and the products keep customer data on the customer's own servers. We have not had a third-party penetration test of our infrastructure. We do not run a 24/7 security operations center. Central logging and round-the-clock alerting cover that role. The customer dashboard does not yet support multi-factor authentication.
10. Documents and contact
Our Data Processing Agreement (GDPR Article 28) is signed by Sansec. Fill in your company details, sign it and email it to trust@sansec.io.
For questions about data processing or subprocessor changes, or to exercise data subject rights, email trust@sansec.io.
In this article
Protect your store now!
Block all known Magento attacks, while you schedule the latest critical patch until a convenient moment. No more downtime and instability from rushed patching.
Get Sansec Shield