Security Review

Across Azure · AWS · VMware / VCD · on-prem

Who it's for

Teams that want an honest check on how exposed their environment really is — without hiring a dedicated security vendor or sitting through a compliance-flavored audit that doesn't speak to actual risk. Especially useful where cloud and on-prem are stitched together and nobody is sure where the real trust boundaries are anymore.

What you actually get

• Access review Who can do what, where long-lived credentials live, and where privileges have quietly accumulated over time. Service accounts, break-glass identities, stale admins included.
• Exposure analysis What's reachable from the public internet and from inside the network — intentionally or not — including paths nobody intended to expose: misrouted VPN, over-broad peering, forgotten jump hosts.
• Configuration weaknesses Defaults left in place, forgotten debug endpoints, services running as root, and configurations nobody has revisited in years — the kind that silently become the weakest link.
• Backup & recovery gap check Whether your backups would actually get you back online — and how long it would really take. Most haven't been tested end-to-end. Some can't be, and nobody knew until the first real incident.
• Prioritized findings Ranked by real-world impact, not generic CVSS scores, with clear next actions you can actually hand to a team.
• Written findings Short report focused on what matters: what's exposed, what would break, what to fix first, what can wait.

Typical findings

Every environment is different, but these show up almost every time. Most of them were technically "known" — but nobody treated them as real risk.

• Long-lived credentials nobody rotates Shared service accounts, hard-coded secrets, certificates that quietly expire into outages, PATs older than the people who created them.
• Public exposure through unintended paths VPNs that route more than anyone realized, peerings that connect networks they shouldn't, load balancers quietly listening on an extra port.
• Overly permissive access that "just worked" Wide-open RBAC or network rules someone added during an incident years ago and never walked back. Nobody remembers why.
• Backups that exist but haven't been tested end-to-end They run green. Nobody has actually restored a full system from them, so nobody knows what's missing until they need it.
• Internal trust assumptions that break under compromise "Anyone on the corporate network can…" — fine until one machine gets popped and the blast radius is the entire environment.

What usually comes out of this

What you can reasonably expect from a full review:

• A clear picture of where the real risk is What to fix first, what can safely wait, and what's not worth fixing at all — without trying to fix everything at once.
• A small number of high-impact issues, not hundreds of low-value findings Usually 5–15 things that actually matter, with context, not a 200-page audit nobody will read.
• Known blast radius If an account or machine gets compromised, you'll know what it reaches and what it doesn't — before you have to find out the hard way.
• Backup & recovery reality check Honest answer on whether you can actually recover from a real incident, and how long it would take.
• Findings your team can actually act on Each item ranked by impact and effort, with enough context to fix it without a follow-up call.