Security Overview

This page summarises how NodaShell Technologies Ltd. ("NodaShell", "we") approaches security, both in the software we build and in how we run our company. It is a summary, not a contract; your Order and our Software Licence Agreement set out our commitments to you.

Where your data lives

Our software is installed on infrastructure you control. Your transactions, user accounts, audit records and configuration are stored in your own database, on your own network.

• The software does not send your operational data to us.
• The licence is verified on your own server, so the software does not need to contact us to run.
• We have no standing access to your installation. Any access is granted by you, for a stated purpose, and can be withdrawn by you.

Security built into the software

• Encrypted in transit. Clients connect over TLS.
• Authentication. Passwords are stored as salted hashes using a modern algorithm. Sessions use short-lived access tokens with rotating refresh tokens, and a reused token is treated as a sign of theft.
• Roles and privileges. Access is checked on the server for every request, not only hidden in the interface. Changing a user's role ends their active sessions.
• Server-side validation. Every transaction is validated on the server before it is posted, whatever device or client it came from.
• No duplicate postings. Each transaction carries a unique key, so a retry or a replayed request cannot post twice.
• Audit trail. Sign-ins, transactions and administrative changes are recorded in an append-only log with the user, device and time.
• Device control. Handhelds are approved by an administrator before they can be used.
• Abuse protection. Requests are rate limited.
• Secrets. Connection credentials held by the software are encrypted at rest.
• Least privilege. The server runs as a non-root process in its container.

How we build it

• Source code is kept in access-controlled repositories.
• Automated tests run against every release.
• We track the third-party components we use and update them when security fixes are published.
• We do not build backdoors or hidden access into our software.
• Security fixes are prioritised by risk and delivered as described in our Support & Maintenance Policy.

How we run our company

• Access to our systems is limited to the people who need it, and removed when it is no longer needed.
• Accounts are protected by strong authentication, and credentials are kept in a password manager.
• Devices used for our work are kept up to date and protected against unauthorised access.
• Information you share with us, such as logs or sample data sent for a support request, is treated as confidential, used only for that purpose, and deleted when it is no longer needed.
• Where we rely on service providers, we choose ones that commit to protecting the information they handle.

Shared responsibility

Because you operate the environment, some of the security is yours: the servers, network and database the software runs on, operating system updates, backups, physical security, and the users and roles you set up. We are glad to advise on a secure deployment.

If something goes wrong

If we become aware of a security incident affecting information you have entrusted to us, we will tell you without undue delay, explain what we know, and work with you on the response. If we find a vulnerability in the software that affects you, we will tell you and provide a fix or a way to reduce the risk.

Reporting a vulnerability

If you believe you have found a security issue in our software or this website, please email email@nodashell.com with the details. We will acknowledge your report, investigate, and keep you informed. Please give us reasonable time to fix an issue before sharing it publicly.

Changes

We improve our security practices over time and update this page when they change. Changes will not reduce the overall level of protection.