Skip to content

Conversation

@udgover
Copy link

@udgover udgover commented Jun 4, 2025

What does this PR do?

  • New attack technique

Motivation

Simulates an attacker enumerating Bedrock models in multiple regions. Attackers frequently use this enumeration technique after having compromised an access key, to use it to answer their prompts.

Checklist

  • The attack technique emulates a single attack step, not a full attack chain
  • We have factual evidence & references that the attack technique was used by real malware, pentesters, or attackers
  • The attack technique makes no assumption about the state of the environment prior to warming it up

@udgover udgover requested a review from christophetd June 5, 2025 06:30
@udgover udgover changed the title Add new technique to invoke bedrock model in multiple regions New technique: invoke bedrock model in multiple regions Jun 10, 2025
@christophetd christophetd requested a review from Copilot June 23, 2025 12:48
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a new attack technique that simulates an attacker enumerating Bedrock models across multiple AWS regions.

  • Registers the new attack technique in the main registry.
  • Implements the attack logic in a new Go file under the aws discovery folder.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
v2/internal/attacktechniques/main.go Adds import for the new Bedrock enumeration technique.
v2/internal/attacktechniques/aws/discovery/bedrock-enumerate-models-multiple-regions/main.go Implements the new attack technique with multi-region Bedrock model invocation.
Comments suppressed due to low confidence (1)

v2/internal/attacktechniques/aws/discovery/bedrock-enumerate-models-multiple-regions/main.go:29

  • There is an inconsistency between the usage of 'bedrock:InvokeModel' in the detonation section and 'InvokModel' in the detection section. Consider standardizing the naming to 'InvokeModel' to avoid potential confusion.
Through CloudTrail's <code>InvokModel</code> events. 


Detonation:

- Perform <code>bedrock:InvokeModel</code> to check if bedrock model is available.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that's invoking it

`,
Platform: stratus.AWS,
IsIdempotent: true,
MitreAttackTactics: []mitreattack.Tactic{mitreattack.Discovery},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to self:

  • Map to AWS threat catalog

}

func detonate(_ map[string]string, providers stratus.CloudProviders) error {
log.Printf("Get aws connection")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • remove debug code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants