A watercolour of a lighthouse and a harbour under glowing domes at dusk, two guards on the quay.

Security

Name the boundary before anyone gets a login.

How your security gets scoped before anything is touched. Read it as our method, not a certification, a legal opinion, or a promise to clear every regulator you answer to.

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

Scoping

What has to be true before access is granted.

The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

  1. Before scope

    Define the data boundary

    What data the workflow needs, where it is stored, who processes it, and what may cross systems or borders.

  2. Before access

    Limit access and actions

    User and service-account permissions, credentials, and the approvals each change needs. An AI workflow should not receive broad permissions merely because it may need them later.

  3. Before build

    Know who else is in the path

    Every platform, model, integration and provider the workflow depends on, written down. Each becomes something you answer for.

  4. Before launch

    Agree who operates what

    Logging, monitoring, incidents, backup and recovery, each with a named owner and the evidence needed before launch.

Whose certificate

A vendor’s certificate covers the vendor.

The vendor’s certificate covers

Your implementation still needs

The vendor’s own platform and controls.
Your data boundary, written down.
The vendor’s own staff and data centres.
Permissions sized to the job, not to “later”.
What the vendor’s report names, for the period it names.
A named owner for logs, incidents and recovery.
A vendor’s certification is not a certification of Mindcat, and it is not a certification of your implementation.

Examples

Who asks for the boundary, and what they get.

  • Example

    Risk lead, Dubai exchange house

    Today: Asked to approve an AI agent that would read customer records, with no list of what it touches.

    After: The data boundary in writing first: what the workflow needs, where it is stored, and what may cross borders.

    Financial services
  • Example

    IT manager, Riyadh hospital group

    Today: A vendor’s certificate was sent as the answer to every security question.

    After: Every platform, model and provider in the path, written down, each with what you answer for.

    Healthcare
  • Example

    CTO, US software company

    Today: A service account got admin rights “for now”, and nobody owns the logs.

    After: Permissions sized to the job, and a named owner for logs, incidents and recovery before launch.

    For CTOs
Examples typical of the work, not client stories.

The brief

Send the situation.

Name the systems and the data. We will tell you if we can take the work. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.