BULWARKADVISORY · BY IVAN PISKUNOV
Service 05

AWS Security Assessment

A focused AWS security review combining automated evidence collection with expert analysis of identities, networking, data, workloads, logging, and cloud-native delivery paths.

Lean-team friendlyRemote-first · worldwideFrom $3,500
AWSIAMCloudEKS
Request a scope →All services
Starting priceFrom $3,500

Indicative USD baseline for a clearly bounded scope.

Typical delivery1–3 weeks

Calendar timing depends on access, evidence, target size, and stakeholder availability.

Commercial modelFixed scope

Scope, assumptions, deliverables, timeline, and price are confirmed before delivery begins.

Baseline scopeA small or bounded AWS environment/account set covering IAM, networking, workloads, data, logging, and product attack paths.

No surprise hourly overages on agreed packaged work. If the scope changes materially, additional work is agreed in writing before it starts.

When this service fits

Recognize the decision before choosing the scope.

Good fit when
  • AWS usage has grown through migration, product expansion, acquisitions, or multiple engineering teams.
  • IAM, public exposure, networking, workload identity, or account boundaries are difficult to reason about confidently.
  • An enterprise buyer, diligence process, or incident has created a need for evidence beyond configuration scans.
Questions this engagement answers
01

Which identity, network, workload, and data paths could realistically affect the product or customer trust?

02

Where are privilege boundaries weak or exposure broader than intended?

What we review

Focused on the controls that change real product risk.

The exact evidence set is tailored during discovery. A typical engagement covers the areas below.

  • Organizations, accounts, IAM, roles, and privilege boundaries
  • VPCs, security groups, public exposure, and network paths
  • S3, RDS, EC2, Lambda, EKS, and workload configuration
  • KMS, secrets, sensitive data, and encryption controls
  • CloudTrail, detection services, logging, and auditability
  • CI/CD, IaC, workload identity, and cloud-to-product attack paths
Deliverables

A decision package — not a scanner export.

Recommendations are prioritized, contextualized, and structured so engineering and leadership can move from findings to action.

AWS security scorecard

Included or adapted to the agreed engagement scope.

Prioritized findings with business context

Included or adapted to the agreed engagement scope.

Identity and exposure review

Included or adapted to the agreed engagement scope.

Cloud attack-path observations

Included or adapted to the agreed engagement scope.

Quick wins and hardening recommendations

Included or adapted to the agreed engagement scope.

Remediation roadmap and validation plan

Included or adapted to the agreed engagement scope.

“Automated tooling is used for breadth. Human review is used to determine what matters to the product, where attack paths exist, and what should be fixed first.”Engagement principle
Engagement shape

Clear scope. Evidence. Priorities. Remediation.

01Discover

Goals, environment, constraints, evidence, and success criteria.

02Review

Technical and process assessment with targeted automation where useful.

03Prioritize

Risk, attack paths, engineering effort, and business context.

04Enable

Report, roadmap, workshop, and optional remediation validation.

Typical engagement: 1–3 weeks, depending on account count and environment complexity.

Client side of the engagement

Know what changes, what is needed, and what can follow.

Outcome

What changes after

  • Cloud remediation is prioritized around realistic exposure and attack paths rather than benchmark volume.
  • Identity and public-access decisions become easier to explain and validate.
Inputs

What we need from you

  • Read-only AWS evidence for the agreed accounts or environment plus a current architecture overview.
  • Representative IaC, CI/CD, workload-identity, and secrets-management context where relevant.
Related

Build a broader engagement.

01

Product Security Program Assessment

Know where your Product Security program stands — and what to improve first.

02

Secure SDLC Assessment

Build security into the way software moves from idea to production.

03

Secure Architecture & Threat Modeling

Find architectural risk before it becomes production vulnerability.

Discuss this service

Bring the architecture, problem, or current security backlog.

We can define the smallest useful scope and a clear output before work begins.

Start a conversation →