Identity and privileged access

Identity and access leadership for regulated firms that carry the obligation without the headcount.

Fractional security leadership and programme management for mid-size regulated firms, where identity and access is a regulatory obligation and the demands on it outrun the senior capacity available — because nobody owns it full time, because a programme needs someone to lead it, or both.

01 · The question

Everyone who can hold you to account is asking the same question.

Your regulator, your auditor, your largest customer and your board each put it differently. Underneath, it is always this: who and what can reach your systems, and who decided that?

Most firms your size can answer the first half. The second half is where the answer runs out — not because the tooling is wrong, but because nobody in the building owns the decision.

Answering it once is a project. Answering it every quarter is a role.

Your regulator

Who is accountable for access risk, and can they show how it is managed?

Your largest customer

Who approves privileged access, and how often is it reviewed?

Your auditor

Show us that leavers lose access, and that every exception was approved by someone.

Your board

If this goes wrong, whose decision was it?

Four questions. One desk. Whose?

02 · Three ways to work with us

Every engagement is fixed in scope before it starts.

A fixed price or a fixed monthly fee, set out in writing before any work begins — no day rate that drifts and no surprise invoices. If it is not obvious which of these fits, that is what the first conversation is for: we work out with you what your firm actually needs, and tell you if the answer is none of them.

01 · When you do not yet know

Identity and AI-agent access diagnostic

Two to three weeks · about six hours of your people’s time · fixed price

Who and what holds access across your estate — workforce, privileged, service accounts and AI agents — who owns it, and how far your controls sit from what your regulator and your enterprise customers expect.

Two deliverables, and neither is a report: a decision your leadership team takes in the room, and a one-page finding on who owns identity in your firm.

How it runs

02 · When something has to ship

Programme lead

Eight to twelve days a month · four to six months · fixed monthly fee

For work that has a name and a finish line: SSO consolidation, a stalled privileged access rollout, an identity tenant migration, joiner-mover-leaver rebuilt so HR drives identity, standing privilege eliminated, AI-agent access governed.

You name a full-time counterpart. Aevix leads and runs the steering rhythm; the counterpart runs the dailies.

What the engagement is

03 · When nobody owns it

Retained identity and access lead

Four to six days a month · ongoing · fixed monthly fee

Aevix owns the identity and access position for you: takes the day-to-day decisions inside authority your executive delegates in writing, brings the bigger ones to them with a recommendation, and prepares the evidence your regulator, auditors and enterprise customers expect.

Not an advisor on call. The role carries delegated authority, a decision log and a monthly report to your sponsor.

How the role works

03 · How fractional works

You keep the hands. We bring the head.

What makes it work

  • Someone on your side runs the day to day. On a programme, a named full-time counterpart (your PM, your engineering manager, the vendor’s engagement manager) runs the daily coordination. In the retained role, the people who already run identity carry on, with Aevix setting the direction.
  • Who decides what is written down first. On a programme, what your counterpart settles alone and what comes to Aevix. In the retained role, what Aevix decides alone and what goes to your executive with a recommendation.
  • Blockers do not wait for the next scheduled day. How escalations reach us, and how quickly they get a decision, is agreed in writing before the work starts.
  • Authority that matches accountability. A direct line to your sponsor, and every decision logged, so it holds on the days we are not there.

What we do not do

  • Hands-on engineering or administration. Aevix leads and decides; your engineers and vendors build and run the systems.
  • A role without authority. Not a project manager inside your PMO running your methodology, and not an advisor on call whose advice you then act on yourself.
  • Standing residency. Remote by default, on site when it matters: a kick-off, a cutover, a risk committee, an audit. Permanent presence on your floor is a hire.
  • Pretend a fraction is enough when it is not. Some programmes need a leader in the room every day, and some firms grow into a full-time identity role. If that is you, we will say so and help you scope the interim or the hire, rather than sell you a fraction of one.

04 · Who it is for

Regulated firms of roughly 150 to 2,000 people.

Fintech, payments, insurtech, wealth and asset management, building societies, and private-equity-backed companies in those sectors — firms that carry a regulator’s expectations on identity and access, and enterprise customers who ask the same questions, without a security function sized to answer them.

You have the obligation

A regulator that expects you to evidence who can reach what, a PCI DSS or SOC 2 audit, or a customer’s security questionnaire that arrives every quarter and asks who holds privileged access.

You have the people

Engineers, a platform, a vendor — the hands exist. What is missing is the senior head that directs them and takes the decisions they cannot.

You do not have the role

There is not five days a week of decisions to take, so the role goes unfilled, or gets bolted onto someone who already has a job.

05 · Writing

What we are writing about.

06 · Who runs it

Aevix is Silvio Sola.

You meet the person who has operated what he is leading.

He started and led a global bank’s group privileged-access programme, including the vendor assessment taken to the Group CISO and the internal and external regulatory approval of it across more than sixty legal entities. He returned to it as one of three workstream leads on a sixty-person programme, running thirty people across the migration off the legacy platform and the in-house automation that now onboards the majority of new privileged accounts.

2019

Started the programmeInitiation, definition, the vendor assessment, the first hires.

60+

Legal entitiesRegulatory approval of the programme led across more than sixty of them.

30+

People ledTwo substreams, each with multiple PMs: migration, and in-house software.

Next step

A 20-minute conversation.

It costs nothing, and if none of this is the right thing for you, we will say so.