Security at Moicon

Security at Moicon is ongoing engineering work. This page describes how we protect the Moicon Digital Twin Platform, the data you trust to us, and the infrastructure that runs it. For how we handle personal data, see our Privacy Policy.

Shared Responsibility

Moicon is responsible for the security of the platform: the infrastructure, application code, deployment pipeline, monitoring, and the controls described on this page. Customers are responsible for security in the platform: account hygiene, managing user access within their organization, and protecting credentials and integration secrets they configure.

Infrastructure and Hosting

  • Hosted on Amazon Web Services (AWS) in the eu-north-1 region (Stockholm). Customer data does not leave the EU. AWS is independently certified against SOC 2, ISO 27001, ISO 27018, and PCI DSS.
  • Environment isolation. Production, staging, and development run in separate AWS accounts with no shared credentials or networking.
  • Edge protection.Native AWS infrastructure sits in front of public endpoints to handle traffic filtering, DDoS mitigation, and overall edge security.
  • Network controls. Security groups and private subnets restrict service-to-service traffic to the minimum required. Production databases are not reachable from the public internet.
  • High availability. Multi-AZ deployments and managed failover for stateful services. Capacity scales horizontally to absorb load spikes.

Encryption

  • In transit. All traffic to Moicon services is encrypted using TLS 1.2 or higher. HTTP requests are redirected to HTTPS, and HSTS is enforced. We do not accept unencrypted traffic.
  • At rest. All stored data, including databases, file storage, and backups, is encrypted with AES-256.
  • Key management. Encryption keys are managed through AWS KMS with rotation and audit logging.

Application Security

  • Authentication. User identity and authentication are managed securely through Xsolla. User sessions are issued as JSON Web Tokens (JWT) signed with HMAC, which are short-lived and invalidated upon logout or password change.
  • Authorization. Access controls are enforced server-side on every request, not in the user interface.
  • API design. Endpoints return only the data required for the request. Sensitive data filtering happens at the API layer, not the UI.
  • Dependency hygiene. Automated scanning for known vulnerabilities in third-party dependencies, with regular patching cycles.
  • Platform updates. New platform versions are released regularly and roll out to all customer environments. Updates include operating system, runtime, framework, and Moicon component patches.

Payments

Payment processing is handled by PCI DSS Level 1 compliant providers. Moicon never stores credit card numbers, CVVs, or full payment instrument data.

Operational Security

  • Monitoring. Application errors, security events, and performance metrics are collected via Sentry and AWS CloudWatch and reviewed continuously.
  • Logging. Authentication events, administrative actions, and access to sensitive resources are logged. Logs are stored in tamper-resistant retention.
  • Backups. Encrypted daily backups with 30-day retention. Both local and offsite copies are maintained.
  • Uploaded files. Customer-uploaded files are automatically deleted 30 days after upload.
  • On-call. Engineers are on call 24/7, including weekends and holidays, with a defined escalation path for security and availability incidents.

Personnel and Access

  • Least privilege. Employee access to production systems is limited to the minimum required for the role.
  • Authentication for staff. Moicon employees authenticate to internal tooling through single sign-on with multi-factor authentication.
  • Offboarding. Access is revoked promptly when an employee leaves the company.

Testing and Assurance

  • Penetration testing. Independent third-party penetration tests are conducted to validate the security of our infrastructure and application. Findings are tracked through to remediation.
  • Vulnerability scanning. Automated scanning of infrastructure, container images, and dependencies.
  • Code review. All production changes go through peer review before merge.

Incident Response

Our incident response process is documented. It covers detection, containment, eradication, recovery, and post-incident review.

If a security incident affects customer data, we will:

  • Notify affected customers without undue delay, and within 72 hours of becoming aware where personal data is involved, in line with GDPR Article 33.
  • Provide details of what occurred, what data was affected, what we have done to contain the incident, and what steps customers should take.

Reporting a Vulnerability

If you believe you have found a security vulnerability in Moicon, please email security@moicon.net with details. We ask that you:

  • Give us a reasonable opportunity to investigate and remediate before public disclosure.
  • Do not access, modify, or delete data that is not your own.
  • Do not run automated scans against production infrastructure without prior coordination.

We will acknowledge your report and keep you updated on remediation progress.

Privacy and Data Protection

This page covers how we protect the platform. For how we collect, use, retain, and delete personal data (including your rights under GDPR), see our Privacy Policy.

Changes to this Policy

We update this page when our practices change. Material changes will be reflected in the date below. For questions, contact us.