NeuraSec

Secure and compliant AI

Adopt AI without losing control of the business.

Secure and compliant AI is help to adopt and run AI so you know what it can see, what it can do, and whether you can explain that to a client, a board or a regulator. It is not a certificate, and it is not legal advice.

The usual trigger is practical. Microsoft 365 Copilot is being switched on. Someone has built an agent that can update a record or send an email. Staff are already pasting client material into public tools. The cost of drawing the line now is much lower than the cost of explaining it later.


The problem

The risk is rarely a clever attack. It is an unclear boundary.

Something reads information it was never meant to reach, takes an action nobody authorised, or is used by someone it was not designed for. Usually because nobody drew the line while the design was still easy to change.

  • Who is using it
  • What it may read
  • A person approves
  • You can see what happened

Inside the line

  • The people it is actually for
  • Approved company and client information
  • The systems it is allowed to use
  • The actions it is allowed to take
  • A record of what it did, and who can see that record

Outside the line

  • Everyone it was not designed for
  • Information you have deliberately kept out
  • Systems it has no reason to reach
  • Consequential actions with nobody in the loop
  • Anything nobody agreed before it went live
The controls across the top are what make the line real. Without knowing who is asking, the line is a preference. Without a record, you cannot tell whether it held.

What the work covers

The decisions a leader actually needs.

We use the specialist words once, then stick to the question they stand for.

  • AI governance

    Who is accountable, who can approve a new use, and where that decision is written down. Light enough to use, firm enough that “someone in IT” is not the answer.

  • AI risk

    What could go wrong for clients, staff or the firm, and which of those risks are worth a control now. A contained pilot is not treated like a system that moves money.

  • Data protection and UK GDPR

    What personal data the AI can reach, on what basis, and how you would explain that. We flag the questions. Your counsel owns the legal opinion.

  • EU AI Act awareness

    Whether you are simply using a tool or have become the organisation that put it into service, and what that changes. A longer explainer is in our EU AI Act and UK regulation article. It is general information, and the rules move.

  • Secure Copilot and agent rollout

    A controlled way to turn on Microsoft 365 Copilot, or an agent that can act, for the right people, over the right information, with a person involved where the action matters.

  • AI assurance

    A structured check that the controls you agreed are actually in place, and a short account of what still is not. Assurance here means a check you can rely on, not a certificate. Where AI use is changing, the check can be repeated at agreed intervals, so the evidence stays current as permissions, platforms and use cases move.


What we work through

Questions worth answering before go-live.

The point is a set of decisions your team understands. A read-only assistant over published policies is a different conversation from an agent that can raise a purchase order.

  • Who can use it?

    The intended people, how they are identified, and who can change that.

  • What can it read?

    The information in scope, and what is deliberately left out, including client and personal data.

  • Are existing permissions respected?

    Whether people only see through the AI what they could already see, or whether a different control is needed.

  • What can it do?

    Which actions are allowed, which need a person to approve them, and which are never unattended.

  • How could it be misused?

    Staff pasting the wrong thing in, or someone persuading the system to step outside its remit.

  • How would you know, and how would you stop it?

    What is recorded, who can look, and how the service can be narrowed or switched off.

What changes

You can say yes, or not yet, with a reason.

The value is a rollout that moves, and a story you can tell without a translator.

  • You know which AI is in use, including the tools people adopted quietly.
  • You know what the important ones can see and do.
  • Personal and client information has a boundary you can explain.
  • Someone is accountable, and a person stays in the loop where the action matters.
  • The board gets a short account of the risk and the decision.

Enough control to move safely. Not enough bureaucracy to stop moving.


An example

A foundation, not a programme.

  • A well-known national charity

    A short engagement as it started its AI journey: practical AI principles and governance, and design input for a future data capability. A foundation, not an organisation-wide AI programme, and not a certificate of compliance.


Where this fits

We are the security half of the conversation.

NeuraSec does not build your AI, and does not run it day to day. Building it sits with another practice in the same group, and running it usually sits with your IT team or provider, so the security questions can arrive early.

NeuraAI builds it

Strategy, use cases, Copilot foundations and delivery. If you need the capability designed, start there and bring us in for the boundary.

Copilot and AI delivery foundations

Readiness, when a standard is the question

ISO/IEC 42001 is the international standard for running AI in a managed way. A gap assessment against it sits with security readiness, not with a claim that you are certified.

ISO/IEC 42001 readiness

Keeping it improving after launch

Your IT team or provider runs the service day to day. NeuraAI's ongoing AI support keeps it useful and evidenced.

Ongoing AI support

If the AI you are introducing is there to help the security team itself, that conversation is AI for security. The boundary questions on this page still apply: a tool that can read your alerts can read some of the most sensitive material you hold.

Questions

Short answers.

  • What is secure and compliant AI?

    It is practical help to adopt and run AI so you know who can use it, what it can read, what it can do, and how that sits with data protection and the rules that apply to you. NeuraSec helps you put that in place. It does not mean NeuraDigital certifies you as compliant.

  • Does this cover Microsoft Copilot and AI agents?

    Yes. A common starting point is a controlled rollout of Microsoft 365 Copilot, or of an agent that can take actions in your systems. The same questions apply to other assistants. Naming Copilot is an example of what clients are rolling out, not a partnership.

  • Do you give legal advice on UK GDPR or the EU AI Act?

    No. We help leaders understand the practical questions: what data is involved, what the AI is allowed to do, who is accountable, and what evidence you would want in front of a client or a regulator. Legal interpretation stays with your counsel. Our EU AI Act article is general information, not advice.

  • What should we leave a secure AI engagement with?

    A plain account of which AI is in use, the boundary around the important ones, the decisions still open, and who owns the next step. Where you also need a gap assessment against ISO/IEC 42001, that sits with security readiness.

Start with what you are about to switch on

What is the first thing you want it to be allowed to do?

That question usually reveals the boundary faster than a long assessment. Tell us what you are adopting and who it is for.