Skip to content
    Security & Trust

    Security as part of the architecture — not a bolt-on layer

    Monokaido is a multi-tenant SaaS PIM with e-commerce features. We openly describe the specific measures — encryption, customer isolation, access control and our development rules.

    Our approach to security

    Three principles we build on

    Security by design

    We design security controls together with the feature they protect.

    Defence in depth

    Key areas are protected by several independent layers. The failure of one of them does not mean a compromise.

    Least privilege

    Every component and every user has access only to what they strictly need.

    Encryption

    Data protected in transit and in storage

    Standard, proven cryptographic libraries — we do not write our own cryptography.

    TLS 1.2/1.3

    All communication runs over HTTPS with HSTS enabled, old protocols are disabled and unencrypted access is redirected automatically.

    AES-256-GCM

    We encrypt sensitive credentials with authenticated encryption, each with its own IV and authentication tag.

    Key check at start-up

    The strength and integrity of the encryption key are verified when the system starts — if the configuration is incorrect, the service does not start.

    Authentication

    Identity under control, passwords under lock and key

    We protect sign-in at every step, from storing the password to resetting it.

    bcrypt hashing

    We never store passwords in readable form — only as a one-way hash with an appropriate computational cost.

    Brute-force protection

    After repeated attempts the account is locked, and the lockout gets progressively longer.

    Anti-enumeration

    An attacker cannot tell a non-existent account from a wrong password, either from the response or from its timing.

    Secure password reset

    High-entropy tokens: single-use, short-lived and stored only as a hash.

    Two-factor authentication with a passkey

    A second factor via a passkey (Face ID, Touch ID, Windows Hello or a security key) and 10 single-use backup codes — the password alone is then not enough to sign in. The feature is being rolled out gradually.

    An alert for every change

    A new password, a passkey added or removed, or two-factor authentication switched off — you receive an e-mail about every change to your account's security.

    Sessions

    Secure cookies and access tied to the account's status

    HttpOnly cookies

    Tokens stored in cookies are not accessible from JavaScript — not even a script injected into the page can read them.

    Secure + SameSite cookies

    Cookies are sent only over HTTPS, belong only to the application's domain, and the browser does not attach them to a write request coming from another website.

    Verification on every request

    A deactivated or locked account loses access immediately.

    A security change signs out other sessions

    After a change of password, passkey or two-factor authentication, all other sessions of the account are ended.

    Re-authentication for sensitive changes

    Adding or removing a passkey and similar actions require a fresh identity check, valid for five minutes.

    Multi-tenancy

    Strict data isolation between customers

    Both the application and the database enforce it, each independently of the other.

    Data separation at the application level

    Every access to data is tied to a specific customer. A user sees only the data of their own organisation.

    Row-Level Security (fail-closed)

    The isolation policies in the database return no data if the customer context is missing.

    RBAC verified on the server

    Roles are verified against the database; a user cannot raise their own permissions or switch into another organisation.

    OWASP Top 10

    Systematic protection against known classes of attack

    SQL injection

    Parameterised queries, and allow-lists for elements that cannot be parameterised (e.g. sorting).

    Cross-Site Scripting (XSS)

    Centralised sanitisation with DOMPurify, plus CSP and X-Content-Type-Options headers.

    CSRF

    We verify every write that carries cookies by the origin of the request (Sec-Fetch-Site and Origin). A request from another site — even from an online shop on our own domain — is rejected by the server.

    SSRF

    Validation of target addresses, verification of the actual IP, and blocking of the internal network and metadata services.

    E-commerce and payments

    Orders, prices and stock under the server's control

    We do not store cards

    Payments are processed by certified providers in compliance with PCI DSS — card numbers never touch our systems.

    The server recalculates prices

    The final order total is always calculated on the server from trusted data, regardless of what the client sends.

    Signed webhooks

    Payment notifications are verified cryptographically, with protection against replay and duplicate processing.

    Atomic stock and discount operations

    Database locking prevents a discount from being applied twice or unavailable goods from being sold.

    Infrastructure

    Operations with the smallest possible attack surface

    Isolated containers

    They run as unprivileged users (not as root), in a separate internal network.

    A single entry point

    A reverse proxy server handles TLS, security headers and rate limiting.

    Errors without internal details

    Error states do not return internal technical details or database output.

    Secure SDLC

    Only a reviewed change reaches the main branch

    Tests with every change

    We cover fixes with regression tests and new features with unit and integration tests.

    Quality gates in CI

    Static analysis, type checking and tests must be green.

    Code review without exception

    Every change is read by a second developer and checked by an automated security tool.

    Summary

    Security at a glance

    AreaKey measures
    EncryptionTLS 1.2/1.3 in transit, AES-256-GCM for stored sensitive credentials
    Authenticationbcrypt, account lockout, rate limiting, protection against enumeration, passkeys and two-factor authentication
    SessionsHttpOnly + Secure + SameSite cookies, account status verified on every request, other sessions signed out when security settings change
    Customer isolationData separation in the application and Row-Level Security in the database
    Access controlRBAC verified on the server
    Attack protectionParameterised queries, sanitisation, CSP, SSRF protection and origin verification of writes (CSRF)
    PaymentsNo stored cards, prices recalculated by the server, verified webhook signatures
    InfrastructureIsolated unprivileged containers, HTTPS only
    DevelopmentTests with every change, quality gates in CI, code review without exception

    Security Pass

    A public overview of our security model (PDF in Slovak).

    Download Security Pass PDF

    Questions about security?

    We'll gladly go through them with your IT or compliance team.