Before an incident

Cloud Security Assessment

Understand what access could become.

We review cloud identity, permissions and configuration against the attack paths we investigate.

Pipeline tokenone credential PermissionPossible reach Read all repositories Write to storage Assume a deploy role Secrets in code Customer files Admin settings
Illustrative · possible reach, not observed activity

Where we look

Three places access grows

We examine the agreed environment and explain which weaknesses matter first.

Identity

Identity and permissions

Who and what can sign in, consent and act.

Configuration

Exposed configuration

Settings that open a way in.

Paths

Paths to sensitive resources

Where permitted access leads.

Sample consequence

A small credential. A wider reach.

An overly broad token can extend access across connected services. A useful finding names the permissions, the possible reach and the changes to make first.

InvictusCloud Security Assessment
Sample organisation · Microsoft 365 and AWS

Access findings

Sample · fictional data
Cloud Security Assessment · Access findings · p. 3Sample · fictional data
FindingPermissionsPossible reachChange first
A pipeline token can read every repository and write to production storageRead: all repositories · Write: production storageSecrets kept in code, and the files in that storageScope the token to one repository and remove storage write
Confidential · prepared for the sample organisationp. 3

Specialist noteCut this permission first: it reaches the most for the least business use.

What you receive

Which permission to cut first, and why.