§ 01Field notes

Written by the people who did the work

The nine notes below rest on three things: bench work on our own estate, close reading of published regulatory text, and the roles our people held before they joined the firm. Each note states its basis in the first line. Nothing here is presented as a client engagement. Prior employers are described by type and scale and are never named, and any measurement quoted was taken on our own systems.

Read the latest field note

§ 02Latest

The latest field note

18 August 2026 · Governance, Risk and Compliance · Sofia Marchetti · 4 min read

Two register cycles under DORA: the questions supervisors put in writing

The register of information is filed, validated and then queried. Two cycles worked earlier in my career, and the feedback published since, put the cost in records rather than in interpretation.

Read the field note

§ 03Archive

Earlier field notes

Each note names the service line that produced the work, the person who wrote it and the basis it rests on.

Purple team on our own estate: what our detection missed

We ran 22 ATT&CK techniques against our own estate and counted alerts rather than rules. Alerts fired on 12, evidence without an alert on 6, and nothing at all on 4. Three of the 12 fired only because they recognised our tooling.

Aleksandra Nowak

Managed Detection and Response

Timing a real failover: the steps that never get rehearsed

We declared a total loss of our own primary region and ran the run book as written. The storage was never the problem. The credentials, the run book's own location and DNS were.

Tobias Reinhardt

Continuity and Disaster Recovery

Admission control policies: the ones we ship and the ones we withdrew

We built one Gatekeeper constraint library and ran it against our own clusters before we would put it in a proposal. Twelve constraints went into audit. Nine we ship. Three we withdrew, and one of those we broke ourselves.

Diego Sotomayor

Cloud and Infrastructure Engineering

§ 04The briefing

A monthly briefing on regulation, detection and recovery

The briefing carries new field notes, the regulatory dates worth diarising and what the bench work on our own estate turned up that month. It goes out on the first Tuesday of each month. Subscribing does not add an address to a sales list.

01

What each issue carries

New field notes, one regulatory date with the obligation it triggers, and one note from bench work on our own estate.

02

Plain text, no attachments

Issues are plain text with links to eigenvector.group. We never attach files. An issue carrying an attachment did not come from us.

03

Consent, and how to withdraw it

We send the briefing on the basis of your consent. Every issue carries a working unsubscribe link, and one click ends it. Our privacy notice sets out retention and your rights.

04

Where addresses are held

Addresses are held in the United States, processed only to send the briefing, and never sold or passed to anyone outside the firm and its email provider. To be removed by hand rather than by link, write to enquiries@eigenvector.group.

Subscribe to the briefing

§ 05Next step

Scoping is done by the lead who will sign the report

Send an outline of the estate, the regulatory deadline you are working to, and the date you need cover in place. The first scoping call carries no fee; a baseline assessment, if one follows, is fixed-fee against a written scope. Every enquiry is answered by a named person within one working day.