Advisory / Security Posture Baseline

Where does your
risk actually live?

Most organisations
don't have a security
problem. They have an
orientation problem.

The board asks about security posture. A compliance requirement surfaces a gap nobody can explain. A near-miss incident raises questions about what would actually happen if something failed tomorrow.

The obstacle is not the lack of tools or policies. It is not knowing where to look first. Generic security reviews produce long lists. Checklists produce scores. Neither answers the question a decision-maker actually needs answered: where does our risk actually live, and which of those risks matters most right now?

The Security Posture Baseline is built for that moment. It does not go deep into any single domain. It maps the whole surface at a level sufficient to identify where meaningful risk concentrates, produces one short, prioritised report, and ends with a roadmap your IT provider or your own team can follow.

Not a score.
Not a checklist.
Not a health check.

Security scores measure configuration against a framework. They tell you where you sit on a scale, not which risks carry weight in your specific environment. This engagement is not that.

i

Not this

A 100-item findings list

Long findings lists shift the problem rather than solve it. If everything is a finding, nothing is a decision. The Baseline produces a short, prioritised output, not an exhaustive catalogue.

ii

Not this

A framework compliance check

The checks follow published benchmarks such as CIS, so the evidence is recognised. The score is not the output. Risk in your actual environment is, and where a failed check does not matter here, the report says so and why.

iii

Not this

A route to ongoing dependency

The engagement ends. The deliverable belongs to you. There is no monitoring subscription, managed service, or tool licence attached. What you do with the output is your decision.

iv

Not this

A cheaper version of deeper advisory

The Baseline is deliberately shallow across a broad surface. It is not a discount version of the Microsoft Identity Assessment. It answers a different question for a buyer at a different moment in their thinking.

Four areas.
One prioritised report.

The Baseline reviews four domains at a level sufficient to identify where meaningful risk concentrates. It stops short of the depth required for a full decision framework on any single domain. That is intentional. The goal is orientation, not exhaustion.

What the Baseline does not cover: deep Entra ID tenant analysis, full Conditional Access policy review, Azure subscription-level posture, penetration testing, or compliance audit work. Those belong to deeper engagements and are deliberately out of scope here.

  • 01

    Identity access posture

    Who has access to what, whether core controls are enforced across the user base, and where authority concentrates in a way that creates meaningful blast radius. This is not a deep Entra ID assessment. It is a surface read sufficient to identify whether identity is a primary risk area or not.

  • 02

    External exposure

    What is visible from outside your perimeter: DNS posture, subdomain inventory, email authentication alignment, TLS configuration, and whether any services are exposed to the public internet that should not be. The same view an attacker or third party would assemble in the first hour.

  • 03

    Operational readiness indicators

    Whether the organisation would detect a significant event, and whether someone has the authority and capability to act on it. Not a full incident readiness assessment. Enough to identify whether response capability is a material gap or a manageable one.

  • 04

    Microsoft 365 configuration fundamentals

    For Microsoft-dependent environments: a read on whether foundational controls are enforced or absent. MFA coverage, admin account hygiene, email security configuration, and the most commonly misconfigured settings that create avoidable exposure.

A deliverable built
for decisions, not filing.

The output is short by design. Automated checks can fail by the hundred; the report brings them down to the few causes that matter and the order to fix them in. If a report requires two hours to read before anything can happen, it has failed.

The Baseline ends.
The work begins.

The roadmap is written to be carried out by whoever runs your Microsoft 365: your IT provider, or your own team. Advisory engagements do not include the fix, so nothing in the findings depends on selling the work.

When the changes are made, the included re-check runs the same checks again, within 60 days of the report, and shows what is fixed and what remains.

Sometimes the work surfaces a question the Baseline cannot answer at its depth. Then the report names the engagement that does: the Microsoft Identity and Cloud Security Assessment (£4,950) for identity and cloud controls, the External Exposure Review (£2,750) for the outside view, or the Incident Readiness Review (£3,500) for response and recovery.

A deeper engagement is recommended only when the evidence calls for it, never as a default. The recommendation follows from evidence.

The buyer this
engagement is built for.

The Baseline is not the right engagement for every organisation. These are the situations where it is.

i

Situation

The board conversation

Leadership has asked about security posture and nobody has a defensible answer. The Baseline produces one. Short enough to present, specific enough to act on.

ii

Situation

The compliance exposure

A customer, insurer, or regulator has asked about security controls. Before committing to a full assessment, the Baseline identifies what is actually in scope and what the honest answer looks like.

iii

Situation

The near-miss or incident

Something happened, or nearly happened. The Baseline provides a fast, independent read on the actual state of the environment, separate from any internal review that may be coloured by the incident itself.

iv

Situation

Before a deeper engagement

The organisation wants to commission deeper advisory work but is not yet sure which engagement addresses the right problem. The Baseline answers that question before a larger commitment is made.

What buyers
ask before engaging.

  • Q

    How does this differ from the Microsoft Identity Assessment?

    The Baseline is broad and deliberately shallow. It identifies where risk concentrates without the depth required to produce a full decision framework on any single domain. The Microsoft Identity Assessment goes deep into Entra ID posture, Conditional Access enforcement, privileged access exposure, and Azure control-plane configuration. The Baseline tells you which direction matters most. The Identity Assessment tells you exactly what is wrong and why.

  • Q

    What access is required?

    For the identity and M365 components, a read-only application registration in the Microsoft tenant is established with client approval before the engagement begins. External exposure work requires no access. All access is scoped to the engagement and removed on close.

  • Q

    Can we use the Baseline output with our board or leadership team?

    Yes. The report is written for two audiences: the person who will act on it technically, and the person who is accountable for the decision. It does not require a technical background to understand the summary or the roadmap.

  • Q

    Does the Baseline overlap with the External Exposure Review?

    There is a surface read of external exposure in the Baseline, but it is not the same depth as the standalone External Exposure Review. If the Baseline identifies external exposure as the primary risk area, the External Exposure Review is the recommended next step specifically because the Baseline did not exhaust that domain.

  • Q

    Our IT provider manages Microsoft 365. Can they do the work?

    Yes, and the roadmap is written for them: each action names the setting, the order to change it safely and what to test afterwards. They are welcome on the walkthrough call. Dettogni does not make the changes, so the review stays independent of the work it recommends.

  • Q

    What if we don't proceed to a deeper engagement afterwards?

    The Baseline stands on its own. Your IT provider or your own team carries out the roadmap, and the included re-check confirms the changes worked. A deeper engagement is only worth it if the report names a question the Baseline could not answer. There is no obligation.

Begin here

Three working days
to a clear answer.
£3,250 + VAT.

The first step is a short Discovery Call. Twenty minutes. Used to confirm the engagement is the right fit, agree on access requirements, and set the start date.

The Baseline is carried out personally by Alex Ulfeldt, the security engineer who operates Dettogni. No handoffs, no junior analysts.

If the Baseline is not the right engagement for your situation, that will be the outcome of the call rather than a sale. A 20-minute call that ends with a clear recommendation is a better use of your time than commissioning the wrong engagement.

Request a discovery call See all advisory engagements

Dettogni advisory is fixed in scope, fixed in price, and designed to end.
United Kingdom · Remote engagements