Information security policy for the La-Sofia.cz (Independency s.r.o.) online shop

Version: 1.0
Effective date: 8 November 2026
Approved by: Daniel Hauser / CEO
Applies to: all employees, suppliers and external collaborators who work with the systems and data of the La-Sofia.cz online shop.

Operator: Independency s.r.o. (Company ID (IČO): 61460788, VAT ID (DIČ): CZ61460788), Kersko 192, 289 12 Hradištko, Czech Republic
Online shop domain: la-sofia.cz
Platform: PrestaShop
Payment gateway: Comgate (redirect/hosted pages)


1) Purpose and objectives

  • To set out the rules and minimum security requirements for the protection of the information, systems and services of the La-Sofia.cz online shop.

  • To limit the risks of data leaks, fraud, outages and incidents.

  • To support compliance with legal and contractual obligations (in particular the GDPR, commercial and consumer law, and the requirements of payment gateways/PCI DSS to a reasonable extent).

2) Scope

This policy applies to:

  • The online shop website (production and test), the administration, APIs and integration interfaces. The shop has no mobile application.

  • The infrastructure (servers, cloud services, databases, CDN, backup systems).

  • User data (customers), business data (orders, products), internal documents.

  • Third parties: own VPS (Ubuntu, managed with Virtualmin), payment gateway Comgate, carrier Packeta (Zásilkovna). We use no external e-mailing tool and no CRM — shop e-mail is sent directly from the online shop server.

3) Definitions and abbreviations

  • Personal data (PD): information identifying a natural person (GDPR).

  • Sensitive data: passwords, tokens, keys, payment data (PAN), health data or other special categories of personal data.

  • ISMS: information security management system.

  • MFA: multi-factor authentication.

  • RPO/RTO: recovery objectives (data loss / recovery time).

  • DPO: data protection officer. The controller is not obliged to appoint one and has not done so; matters concerning personal data are handled by the company’s managing director.

4) Roles and responsibilities

  • Company management: approves the policy, provides the resources.

  • Security/IS manager (CISO/IS Manager): coordinates security, risk management and incidents.

  • IT administrator / DevOps: operation of the infrastructure, access rights, backups, patching.

  • Development team: secure development (secure coding), code review, testing.

  • Customer support / sales: handling customer data in line with the principle of "minimum access".

  • DPO: GDPR, DPIA, training, reporting of personal data breaches.

  • Suppliers: meet the security requirements under the contract and the DPA.

5) Information classification

  • Public – may be published (marketing texts).

  • Internal – for employees (operating procedures).

  • Confidential – contracts, business data, prices.

  • Sensitive/Personal – personal data, access credentials, keys, payment data.

Basic rule: the higher the classification, the stronger the protection (encryption, restricted access, audit records, shorter retention periods).

6) Principles for handling personal data (GDPR)

  • Minimisation: collect only the data necessary for the purpose.

  • Legal basis: contract, legitimate interest, consent (for marketing).

  • Transparency: up-to-date information in the personal data processing policy.

  • Retention: orders and tax documents 10 years (statutory archiving obligation), operational logs 90 days.

  • Data subject rights: a mechanism for access, rectification, erasure, portability and objection.

  • DPIA: carry one out where there is a high risk to rights and freedoms.

  • Data processing agreements (DPA): with every supplier that processes personal data.

7) Access and identity management (IAM)

  • PrestaShop Back Office: mandatory 2FA (module), changed admin URL, IP restriction for the "SuperAdmin" role.

  • MFA mandatory for administration, development, production access, e‑mail and cloud.

  • Passwords: at least 12 characters (secrets manager/Password Manager), regular rotation for service accounts.

  • Principle of least privilege: role‑based access (RBAC), regular access reviews (at least quarterly).

  • SSO wherever possible; shared accounts are prohibited.

  • Offboarding: deactivation of accounts within 24 hours of the end of the cooperation.

8) Application security (AppSec)

PrestaShop – specific measures:

  • Changing the URL and the name of the administration directory (e.g. admin123 → a custom name).

  • Enable 2FA for the Back Office (module) and an IP whitelist for sensitive roles.

  • Update the core and the modules; remove/disable unused modules.

  • Switch off dev mode/debug in production; restrict display_errors.

  • Login restrictions (rate‑limit, reCAPTCHA), blocking after X attempts.

  • Access to the PrestaShop API via tokens; rotation and minimum permissions.

  • No file editor via the web, deployment only through CI/CD (code review, commit audit).

  • Development in accordance with OWASP ASVS/Top 10, code review, SAST/DAST, dependency scanning (Dependabot/Snyk).

  • Secrets (payment gateway and carrier keys, database credentials) are never kept in the source repository. They live in the configuration and the database on the server, with access limited to the administrator. No separate secrets vault is in place.

  • API: authentication and authorisation (OAuth2/OIDC), rate‑limiting, audit logs.

  • Security headers (HSTS, CSP, X‑Content‑Type‑Options, Referrer‑Policy, etc.).

  • WAF (Cloudflare) in front of the production website.

  • Penetration test at least once a year and after significant changes.

9) Infrastructure and network

  • Encrypted traffic: TLS 1.2+ everywhere (HTTPS, administration, databases).

  • Segmentation: separation of the front‑end, application and DB layers.

  • Firewall/SG: deny‑by‑default, only the necessary ports.

  • Monitoring & alerting: metrics, logs, anomalies, capacity planning.

  • Basic hardening of the OS, switching off unnecessary services, regular updates.

10) Data and encryption

  • In transit: TLS 1.2+ (SSH, HTTPS, SMTPS, database connections).

  • At rest: encryption of disks/volumes (e.g. LUKS/EBS‑encryption), DB dumps and backups.

  • Key management: rotation, restricted access, audit.

11) Logging and audit

  • Audit logs: logins, administrator actions, changes of access rights, operational events.

  • Immutability: logs are protected against tampering by restricted access to the server; retention period 90 days.

  • Centralisation: central log collection (SIEM) is not in place; logs remain on the online shop server.

  • Time synchronisation: NTP everywhere.

12) Backup and recovery (BC/DR)

  • Daily backups of both the database and the files, performed by the server management tool.

  • RPO/RTO: with daily backups the maximum possible data loss is 24 hours (RPO). We have not formally set a recovery time (RTO).

  • Recovery test: at least once a quarter.

  • Backup storage: on the same server as the online shop. A copy outside the server is not yet in place — the backup therefore protects against data corruption, not against loss of the server. Adding off-site storage is planned.

13) Vulnerability management and patching

  • Patch cadence: OS and middleware within 14 days of release, critical ones within 72 h.

  • Scans (internal and external) quarterly.

  • Bug bounty / responsible disclosure: security contact [email protected] and disclosure policy.

14) Payment data and PCI DSS

  • Do not store card numbers (PAN), CVC or full magnetic stripe data.

  • Use the Comgate hosted payment pages (redirect); PCI scope: SAQ A (no card data passes through the online shop).

  • Verify the signatures and IP addresses of notifications/"callbacks" (Comgate), use HTTPS and rotate API keys.