Skip to content

Trust Centre

How we look after your clients' information

Every control on this page is one we run today. An automated test checks each statement against the code that carries it out. If that code changes, the test fails until the statement here is corrected.

ISO/IEC 27001

Preparing for certification. Not certified.

ImmiIQ is building its information security management system to ISO/IEC 27001:2022. Certification is awarded by an independent certification body after an external audit. That audit has not happened yet. We will say so here when it has.

Drafted

  • Information security policy (A.5)
  • Access control policy (A.5.15 to A.5.18, A.8.2 to A.8.5)
  • Incident response plan (A.5.24 to A.5.28)

Still to come

  1. An external gap assessment against the standard
  2. The remaining policies, the risk register and the Statement of Applicability
  3. An internal audit and a management review
  4. Stage 1 and Stage 2 audits by an accredited certification body

Protecting client data

  • Annex A A.8.24

    A client's identifying details encrypted with a key for each firm

    On a client's own record, the passport number and country, the date of birth, the parents' and spouse's names, the addresses and identity card numbers are encrypted with AES-256-GCM under a key derived for each firm.

  • Annex A A.8.3

    A client record checked against the firm

    A request for a client's record checks that it belongs to the signed-in firm and refuses another firm's record.

Who can get in and what they can reach

  • Annex A A.8.5

    Encrypted sessions that expire

    Sign-in sessions are held in an encrypted cookie and end after 24 hours without use.

  • Annex A A.8.5

    Passkeys for firm staff

    Agents and firm staff can sign in with a passkey - the device's own face, fingerprint or PIN check - added under Settings, Security.

  • Annex A A.8.5

    Repeated failed sign-ins locked out

    Sign-in attempts are recorded. Repeated failures lock the sign-in for a while.

  • Annex A A.8.20

    Sign-in limited to a firm's own networks, on request

    A firm can ask for sign-in to be limited to its own IP addresses. A sign-in from anywhere else is refused and recorded.

  • Annex A A.5.15

    Each member sees what an admin allows

    Admins decide whether a member sees all clients, their team's clients or only their own. The limit is applied on the server, not only on the screen.

Records that cannot be quietly changed

  • Annex A A.8.15

    An audit log of changes to client records

    Edits and deletions of a client record are written to the firm's audit log with who made them and when.

  • Annex A A.5.33

    A trust ledger that cannot be rewritten

    Trust ledger entries are never deleted or edited. A mistake is corrected by a reversal that points back at the original. The database itself refuses anything else.

The platform itself

  • Annex A A.8.6

    Rate limits

    Requests, AI requests among them, are limited per minute according to the firm's plan.

  • Annex A A.8.26

    Payment events verified

    Payment notifications are accepted only with a valid signature from the payment processor.

  • Annex A A.8.26

    App pages cannot be framed by other sites

    Pages of the app tell browsers not to show them inside another site's frame, which guards against clickjacking.

Questions from your firm's security review

Our supplier list, data locations and policy drafts are available on request for a procurement or security review. More detail on hosting and encryption is on the data security page.

Trust Centre | ImmiIQ