Contact
All services Service

Security review

The review covers identity and access, network exposure, configuration, and backup and recovery, across cloud and on-premises. The result is a short report: usually 5–15 findings, ranked by impact and effort, each with a next action.

Describe what you need

What you get

  • A short written report of what is exposed, what would break, what to fix first and what can wait
  • A ranked list of findings, usually 5–15, each with its impact, effort and next action
  • An access review: who can do what, where long-lived credentials live and where privileges have accumulated
  • An exposure analysis: what is reachable from the internet and from inside the network, including unintended paths
  • The blast radius of critical accounts and machines: what each one reaches if compromised
  • An assessment of whether the backups would bring the systems back online, and how long that would take

How it works

  1. 01

    Agree scope and access

    We agree which environments are in scope, across Azure, AWS, VMware / VCD and on-premises, and work from read access to them.

  2. 02

    Review identity and exposure

    We review who can do what and where long-lived credentials live, then what is reachable from the internet and from inside the network.

  3. 03

    Check configuration and backups

    We check for defaults, debug endpoints, services running as root and configuration drift, then whether the backups would bring the systems back and how long that would take.

  4. 04

    Rank the findings

    Each finding is ranked by impact and by the effort to fix it, with a next action that can be handed to a team.

  5. 05

    Write the report

    We write a short report: what is exposed, what would break, what to fix first and what can wait.

Problems it solves

  • ProblemShared service accounts, hard-coded secrets and access tokens stay unchanged for years, so a leaked one keeps working.

    SolutionThe access review finds where long-lived credentials live and where privileges have accumulated, including service accounts, break-glass identities and stale admin accounts, and lists a next action for each.

  • ProblemA misrouted VPN, an over-broad peering or a forgotten jump host exposes systems that nobody meant to make reachable.

    SolutionThe exposure analysis maps what is reachable from the internet and from inside the network, through VPNs, peerings, jump hosts and load balancers. Each unintended path is listed with the change that closes it.

  • ProblemEverything on the internal network trusts everything else, so one compromised machine can reach the whole environment.

    SolutionThe review maps the blast radius: what a compromised account or machine reaches and what it does not, including trust paths between cloud and on-premises systems.

  • ProblemAudit reports list hundreds of findings without priorities, so nobody acts on them and the serious risks stay open.

    SolutionFindings are ranked by impact and by the effort to fix them. The report usually holds 5–15 findings, each with enough context to act on.

What it covers

  • Azure
  • AWS
  • VMware / VCD
  • On-premises
  • Access and privileges (RBAC)
  • Long-lived credentials and secrets
  • Network exposure, including VPNs
  • Blast radius of accounts and machines
  • Configuration weaknesses and drift
  • Backup and recovery check
Typical scope

Typical engagements run 3–8 days, depending on environment size and how much read access is available on day one. A focused review of identity or exposure takes less time; multiple environments, hybrid trust paths or backup validation take longer.

Next step

Send a short description of what you need and the systems involved. We reply with proposed next steps.

Describe what you need