AI in software delivery

Rules for using AI tools in a development team — so the speed-up does not come at the cost of control over code and data.

We address the technical requirements of
NIS2UKSCISO 27001
Rules for working with AI
  1. Promptswhat may be pasted, and what never
  2. Datano client data or secrets
  3. Generated codethe same review and scans
  4. Integrationsminimal permissions
  5. Dependenciessuggested libraries verified
  6. Teamtraining on real examples

The team still works faster — just within known limits.

How it looks today

AI assistants are in use; the rules are not.

The team already uses AI assistants, usually without agreed rules. Code is produced faster, but no one checks what goes into the prompt, where the generated fragment comes from, or whether it passed the same controls as hand-written code.

  1. AI assistant
  2. Client data pasted in
  3. Generated code
  4. No review
  5. Production

What we do

We define the scope after an assessment — starting with the element that lowers your risk fastest.

Rules instead of a gray zone.

We establish what may be pasted into an AI tool and what never — taking into account client data and code covered by contracts. We put generated code through the same review process as hand-written code, without exceptions, because a fragment's origin does not change its risk. We tidy up the access of assistants and integrations, so they get only the permissions they genuinely need. We train the team on concrete examples instead of imposing a blanket ban no one follows anyway.

Four stages

Each stage leaves you with a concrete result, not meeting notes.

  1. 01

    We set the rules of use

    What may be pasted into the tool and what never — taking client data into account.

    ResultShort rules: what may be pasted into an AI tool, and what never

  2. 02

    We bring generated code under control

    The same review process as for hand-written code, without exceptions.

    ResultGenerated code under the same controls as everything else

  3. 03

    We tidy up tool access

    The assistant and integrations get only the permissions they genuinely need.

    ResultAssistant and integration permissions narrowed to what is needed

  4. 04

    We train the team

    Concrete examples instead of a blanket ban no one follows.

    ResultA team trained on examples from your own work

What you get in practice

Rules for using AI

One page of rules instead of a ban nobody follows.

The team knows which AI tools it may use, what never goes into a chat and who approves exceptions.

AI code checked like any other

No password or key reaches the repository, whoever wrote the code.

Code suggested by AI goes through the same automatic checks as code written by hand.

Limited access for AI assistants

The tool gets only the permissions it actually needs.

An AI assistant can reach only the repositories and actions its task requires — nothing more.

What stays with you

Company and client data do not leak through prompts

Generated code passes the same controls as everything else

The team has clear rules instead of a gray zone

Frequently asked questions

How long does it take?+

We define the scope after a call and an assessment. Smaller engagements close in a few weeks; larger ones we split into stages, so the result is visible after the first.

Do we have to give you access to the code?+

Usually not to all of it. In most cases access to the build pipeline configuration and organization settings is enough. We define the scope in writing before we start.

Does our team have to get involved?+

Yes, but not full time. We need contact with someone who knows the system, and a review of our changes. The rest is on us.

What if we already have tools?+

We plug into what already works for you. Replacing a tool is the most expensive and least often necessary way to improve security.

Do we become dependent on you?+

No. We work with standards and tools your team knows or will quickly learn. Everything is documented and handed over.

Won't this slow down releases?+

We wire controls so they run in the background. If one starts blocking work, we tune it or move it to a different point in the process.

Let's find where risk
enters your delivery process

We reply within 24h on business days