Breachcraft Security

Managed security · Azure and Entra · UK

The work that
never stops,
on a schedule.

A retainer for drift, identity hygiene, baseline evidence and the pipeline. Same operator as the assessment, standing scope instead of a project, and a fix written by the person who found the hole.

Model
Monthly retainer, one tenant family
Cadence
Weekly drift and hygiene, monthly evidence pack
Starts with
A baseline month, priced as an assessment

01 / The month

Four things, on a cadence

Narrow on purpose. A retainer that promises everything becomes a dashboard nobody reads.

Baseline drift

Every control from the baseline month is re-checked weekly. New drift is reported with the change that caused it, not a score.

Weekly

Identity hygiene

Stale guests, lingering eligibility, expiring app secrets, service principals with more than they use. Cleared or raised, in writing.

Weekly

Pipeline and release

Federated credential subjects, service connection scope, who can approve what. Reviewed against the release that shipped that month.

Per release

Evidence pack

What changed, what was fixed, what is accepted risk and by whom. The artefact an auditor or insurer asks for, assembled as you go.

Monthly

02 / Start

The first month is the baseline

No retainer runs before the controls it watches exist. Month one is priced as an assessment and produces them.

  1. 01

    Standing scope

    In-scope identities, tenants and pipelines, break-glass and contacts. One page, signed once, revisited quarterly.

  2. 02

    Baseline month

    The assessment, delivered as runnable CIS-style controls with evidence and an accepted-risk column. This is what the retainer then watches.

  3. 03

    Handover of the cadence

    Report format, the weekly slot, and the escalation rule: what interrupts you, and what waits for the pack.

  4. 04

    Quarterly review

    Controls retired, added or re-scoped, with the reason. A retainer that never changes is measuring the wrong things.

03 / Honesty

What this is not, yet

Written down because a retainer page that claims a SOC will be compared against one.

04 / Credentials

Who signs the pack

Every claim below is held and checkable. Certificate slots are placeholders until the credential record is published with an issuer, an id and an expiry.

Microsoft Certified Trainer

Issuer
Microsoft
Credential
placeholder
Expires
placeholder

OSEP

Issuer
OffSec
Credential
placeholder
Expires
No expiry

CTL

Issuer
placeholder
Credential
placeholder
Expires
placeholder

Azure certifications, professional level

Issuer
Microsoft
Count
20 held, five professional
Verification
placeholder, transcript link

Ten years of penetration testing and Azure engineering, QinetiQ to NCC Group. Training delivered under the academy arm.

05 / Contact

Send the shape of the estate

Tenant family, what has been tested before, and who carries the risk. A scoping call follows within one working day.

hello@breachcraftsecurity.com

If a retainer is not the right shape yet, the reply says so and points at the assessment instead.