SLApp Helpdesk
Security & trust

Built to be trusted with your clients' computers

An RMM has deep access to the machines it manages, so security is not a feature we add at the end. Below is exactly how SLApp Helpdesk protects your data, your technicians' accounts and your clients' computers — described as it is implemented, not as a marketing promise.

ISO/IEC 27001Aligned with ISO/IEC 27001:2022. Each measure below is mapped to the Annex A control it addresses. SLApp Helpdesk is not certified against ISO/IEC 27001; we describe the controls we have in place and are happy to answer your security questionnaire.

Sign-in with Microsoft — no passwords of ours

A.5.15A.5.17A.8.5

Technicians and your clients' contacts sign in with their Microsoft 365 / Entra ID account. SLApp Helpdesk never sees or stores their passwords.

  • Multi-factor authentication and conditional access are those of your own Microsoft 365 policy.
  • Every request is verified: the Microsoft token signature (RS256, Microsoft's published keys), its audience and its issuer.
  • Only your company's domains can create an account in your workspace; new technicians wait for an administrator's approval.
  • One browser session and one mobile session per user — opening the account elsewhere takes the seat over and the other device is told.

Entra ID · JWKS · RS256 · per-tenant domain allow-list

Access only to what each person needs

A.5.15A.5.18A.8.2

Roles keep sensitive areas to the people who should see them.

  • Administrator-only areas (users, licence, connectors, settings) are enforced on the server, not just hidden in the interface.
  • Modules per group and per user: each group of technicians can be given the modules it may open, and each user can have a module allowed or denied on top of their groups. A module without access disappears from the menu and the server refuses its requests.
  • Money, backups and the audit log only by explicit permission: Transactions, Hours & billing, Backups and the Audit log are never opened to a technician by default, and backup destinations and their passwords stay with administrators.
  • Alert emails follow the permissions: a technician only receives the alert emails of the modules they have access to — Alerts counts as every module — unless an administrator typed their address on a rule or a website.
  • Technician seats follow your licence: a user cannot be activated without a free seat.
  • In the client portal each contact sees only their own company — and only what their role allows.

server-side role checks · module permissions per group and user · licence seats · per-company scoping

Encrypted in transit

A.8.20A.8.24

The web app, the client portal, the API and every agent talk over encrypted connections.

  • HTTPS (TLS) for the application, the portal and the API.
  • The agent connects only over HTTPS and secure WebSocket (WSS), validating the server certificate.

TLS · HTTPS · WSS

Encrypted at rest

A.8.24A.5.33

The most sensitive data is encrypted inside the database, with a key that is not stored in the database.

  • AES-256-GCM for the technical password vault, BitLocker recovery keys, software licence keys and the passwords of connectors and backup destinations.
  • Revealing a BitLocker key or a stored password is recorded in the audit log, with who and when.
  • Files (ticket attachments, screenshots, photos) are stored in the database, never as loose files on the web server.

AES-256-GCM · random 96-bit IV · authentication tag

A password vault even we cannot open

A.8.24A.5.17

The personal vault of the client portal and browser extension is end-to-end encrypted on the user's own device.

  • The key is derived from the user's master password on their device (PBKDF2-SHA256, 210 000 iterations) and never reaches our servers.
  • Entries are encrypted with AES-256-GCM; shared folders use ECDH P-256 key exchange.
  • The server only stores ciphertext — nobody at SL Apps can read it, and repeated wrong unlock attempts are rate-limited.

zero-knowledge · PBKDF2-SHA256 · AES-256-GCM · ECDH P-256 + HKDF

An agent that only trusts what it can verify

A.8.19A.8.32A.8.7

The agent installed on each computer has its own identity and refuses anything it cannot check.

  • A unique, random credential per computer — not a shared key.
  • Every update is checked against its published SHA-256 hash before it runs; a missing or different hash means the update is refused and the file deleted.
  • Removing a computer in SLApp Helpdesk uninstalls its agent the next time it calls in — a removed machine cannot keep reporting.

per-device credential · SHA-256 update verification (fail-closed)

Remote access you control and can review

A.6.7A.8.15A.8.16

Remote control is the most powerful tool in an RMM, so it is the most closely recorded.

  • The user is asked to accept a remote session; you decide, per company, the consent policy and what happens when nobody answers or the screen is locked.
  • Connecting without asking and turning recording off are permissions of their own, off by default for every user, administrators included: only an administrator gives them, and the server checks them when each session starts.
  • Sessions can be recorded, with a retention period you choose; the user is told.
  • Tunnels (RDP, web interfaces of routers or NAS) only reach private network addresses of computers in your own company, through short-lived tokens; the agent that opens Remote Desktop on a technician's computer only accepts connections of the organizations it belongs to.
  • Every session and every command is kept in the computer's history: who, what, when and the result.

consent policy · recordings with retention · private-address tunnels · per-computer history

Your company's data kept apart

A.8.3A.5.10

SLApp Helpdesk is multi-tenant, and isolation is enforced on every request.

  • Every request runs in the context of its own company, and every query is filtered by it.
  • Your own database: a company can have its data in a dedicated database of its own.

per-request tenant context · optional dedicated database

Everything that matters is logged

A.8.15A.5.28

An audit log records who did what and when — with the old and the new value.

  • Changes to users, licences, clients, contacts, profiles, policies and connectors, revealed secrets, remote sessions and much more.
  • Administrators can filter and review the log at any time.

audit log · old/new values · ~60 action types

Privacy and your data in Portugal

A.5.34A.8.10ISO/IEC 27701

We process your data under the GDPR, as described in our Privacy Policy and Data Processing Agreement.

  • Hosted on our own servers in Portugal.
  • Data that keeps growing (monitoring history, logs) is deleted automatically after its retention period, which each company can shorten in Settings → General → Retention.
  • When a subscription ends, the company's data is deleted 90 days later, after notices on the way.
  • The AI assistant uses your own AI provider key or a model you host yourself — we do not send your data to an AI provider on our account.

GDPR · DPA · retention · end-of-contract deletion

Built carefully

A.8.25A.8.28A.8.29

Security is part of how every change is made.

  • Every change is tested on a separate development environment before it reaches production.
  • Content written by users is sanitised before it is shown, and the web server never serves the application's source files.
  • Secrets are kept out of the source code and out of the code repository.

dev/prod separation · HTML sanitisation · secrets outside the repository

What stays in your hands

Security is shared. Your Microsoft 365 policies (MFA, conditional access) protect every sign-in; your company decides who are administrators, which modules each technician may open, which domains may sign in, the consent policy for remote access and how long recordings are kept.

Have a security questionnaire or a specific requirement? Write to info@significado-logico.pt and we will answer it.

Security you can check

Ask us anything about how SLApp Helpdesk protects your data — or see it for yourself in a demo.

Request a demo