Skip to content
ES Let's talk

Solutions · Shield

An audit or a security incident is coming

We sort out who can access what, close what was left exposed and document all of it. So you reach the audit with the evidence in order, and your team can keep it that way.

Tell us what worries you Try the express assessment

When we get the call

From what is happening to what changes

This is how most enquiries start, and this is what changes once we solve it.

  1. “We have an audit coming and do not know where to start.”

    Evidence, ready

    You know what will be reviewed, what is missing and in which order to fix it, and the logs are ready to show.

  2. “Every device has its own password, and nobody has them all.”

    Access under control

    Who can access what, in one place, with role-based permissions and a log of every entry.

  3. “We get strange emails and do not know if someone already fell for one.”

    Your team, prepared

    People recognise an attack attempt and know what to do if something happens.

See it in a case

A thousand devices and no master key

It was handled from inside, as part of the client’s team, until the new way of operating was the normal one.

In
A thousand network devices, each with its own key
Out
Centralised access, run by the client’s own team
Read the case

How we do it

Step by step, with the blocks it takes

  1. 01 Shield

    Assess

    We review access, configurations and exposure, and prioritise by the real risk to your operations.

    You keep The risk map, by priority.

  2. 02 Shield

    Fix

    We centralise access, close what is exposed and leave backups that can be restored.

    You keep The controls up and running.

  3. 03 Shield

    Prepare

    We put the evidence in order for the audit and train your team, so they can keep it up on their own.

    You keep The evidence ready, and your team trained.

How long it takes An assessment with its fixes takes about a month; a full programme, up to six. Scope and price are closed before we start.

What we need from your side

  • Access to the systems and to whoever runs them.
  • What the audit asks for, if you already have it.
  • Time from your team for the training.

What it looks like

What an audit asks for, control by control

This is how an example case progresses: each control goes from pending to resolved, with its evidence.

12 of 12 controls resolved

  • Device inventory Resolved Pending
  • Role-based access Resolved Pending
  • Two-factor authentication Resolved Pending
  • Admin passwords Resolved Pending
  • Backups Resolved Pending
  • Tested restore Resolved Pending
  • Access log Resolved Pending
  • Up-to-date devices Resolved Pending
  • Written security policy Resolved Pending
  • Team training Resolved Pending
  • Incident plan Resolved Pending
  • Evidence in order Resolved Pending

Questions

What people ask us before we start

Can you help us with a specific standard?

Yes: we organise the controls around what the audit asks for —a standard, a customer or a regulator— and get the evidence ready to show.

Do we have to change our tools?

Not necessarily. First we make the most of what you have, properly configured; we only add what is missing.

What if it is the network that needs redoing?

If it needs a redesign, Connect takes it on, in the same project and with the same team.

See Connect
Is it a one-off?

The foundation is. Keeping it current —reviews, updates, access for people who join and leave— is what Sustain does.

See Sustain

Next step

Let's start with what is going on

A conversation to understand the problem before talking about technology. If after that there is nothing to build, we will tell you.

Book a call

Or write to us at hello@alubyte.com