[Managed Security Services Provider]

Managed security infrastructure, delivered to you.

You own the environment.We keep it secure and compliant.

Lightning strikes the sea ahead of a destroyer, seen from the ship looking over the bow.
  • You ownTenant, licenses, dataIn your name from the first day.
  • We provideEngineers and platformWe build it in your tenant, then stay on as the support team.
  • CloudsMicrosoft 365 and AzureCommercial and government.
  • Our roleBuild and supportWe do not certify the environment; an independent assessor does.
[How it works]

Your environment. Our engineers. One clear line.

Some providers host you inside an environment they own. We build yours in accounts that belong to you.

[Your side]

You own it.

  • TenantYour Microsoft tenant, your users, your administrator rights.
  • DevicesWorkstations, firewall and equipment at your site.
  • DataStays in your environment.
  • LogsCollected in your own subscription.

Billed to you by Microsoft and your vendors

[Our side]

We keep it secure and compliant.

  • EngineersThe support team: the people who patch, review and respond.
  • PlatformThe automation that builds your environment and re-checks it.
  • RecordsChanges made through the platform are logged.

The central platform runs in our cloud, at our cost

FIG. 01Who owns what, and where our team works.

How the platform builds and re-checks it

[The recurring work]

What we do after the build.

A secure environment starts drifting the day after it is built.

  • Patching and updates

    Workstations, servers and network equipment kept current.

  • Access and accounts

    New hires, departures and role changes handled as requests.

  • Logging and review

    Logs from your tenant, workstations and network equipment collected and reviewed.

  • Alerts and incident response

    Alerts triaged, and incidents worked with you.

  • Change, backup and recovery

    One recorded change process, with backup and recovery included.

  • Documentation upkeep

    Policies, asset inventory and responsibility matrix updated as the environment changes.

What managed security does not include: a general help desk, shop-floor operational technology, and hardware purchasing. Day-to-day help desk can stay with your team or your current provider, or come from our managed IT service. The split is written into a responsibility matrix before we start.

[Billing]

Who pays for what.

Nothing is resold or marked up through us, so you can see what the environment costs without us.

  • You pay Microsoft and your vendors

    Licenses, cloud usage and hardware

    Billed to you directly. This includes the management pieces that live in your environment, such as log storage, the site VPN and the accounts our engineers use.

  • You pay Input Trace

    The managed service

    Scope and fee are agreed in writing before you sign.

  • Input Trace pays

    The platform behind the service

    The central automation and its tooling are our cost, not a line on your bill.

  • One time

    Design and build

    Scoped and priced before you buy anything, starting with a fixed-price architecture engagement.

[Straight answers]

The questions owners ask first.

Who owns the environment?

You do. The tenant, devices, data and logs stay on your side, and Microsoft and your vendors bill you directly.

Do you work in Microsoft 365 GCC High?

Yes, and in Azure Government. See Microsoft 365 and Azure.

[Next step]

Find out what it would take.

A consultation covers what you have today, what your contracts require, and what the support would involve. You leave with a clear next step, whether or not it is us.

Not ready to talk? See how an engagement starts