TA0043Tactic 1 of 15

Reconnaissancein cloud and AI environments

What can attackers learn about our cloud environment before they attack?

ATT&CK v20.1Updated Official tactic page
Reconnaissance technique map12 techniques in Reconnaissance, 0 of them apply to cloud platforms. Highlighted: T1593, T1596, T1595, T1589.T1589T1593T1595T1596TA004312 TECHNIQUES
Key for cloud (this guide)Applies to cloud platformsOther platforms
12
Techniques
34
Sub-techniques
0
Apply to cloud platforms
4
Defensive controls
2
Detection signals

What the tactic means

Reconnaissance is information gathering that happens before the adversary interacts with your systems in a way that needs credentials. It includes searching public code, documentation, job postings, DNS, certificate transparency logs and data leaks, and actively scanning internet-facing endpoints.

The adversary is trying to gather information they can use to plan future operations.

Reconnaissance consists of techniques that involve adversaries actively or passively gathering information that can be used to support targeting. Such information may include details of the victim organization, infrastructure, or staff/personnel. This information can be leveraged by the adversary to aid in other phases of the adversary lifecycle, such as using gathered information to plan and execute Initial Access, to scope and prioritize post-compromise objectives, or to drive and lead further Reconnaissance efforts.

MITRE ATT&CK TA0043 description

Why it matters: cloud, AWS and AI

Cloud environments

Cloud environments leak structure through predictable resource names, public endpoints and infrastructure-as-code published in repositories. Account IDs, role names and bucket names are not secrets, but together they make later steps faster and more targeted.

AWS specifics

Common AWS reconnaissance targets include S3 bucket names in front-end code, account IDs in public CloudFormation templates or AMIs, role ARNs in documentation, and API Gateway or Lambda function URLs. Access keys committed to public repositories are routinely discovered by automated scanners within minutes of publication.

AI & workloads

Public model cards, prompt examples, system-prompt leaks and documentation about which tools an AI assistant can call help attackers craft prompt-injection payloads. ATLAS tracks AI-specific reconnaissance separately (for example searching for publicly available research about a target’s models).

What the attacker is trying to achieve

  1. 01Identify internet-facing services and their technology
  2. 02Find leaked credentials or configuration in public sources
  3. 03Learn naming conventions, account IDs and identity structure
  4. 04Identify people with privileged access for phishing

Techniques that matter most in cloud

What it needs, and what breaks it

Attacker needs

  • Information published or exposed publicly
  • Internet-reachable endpoints

Defenders control

  • Secret scanning for public and private repositories, including history
  • Review what infrastructure detail is published in docs, templates and AMIs
  • Minimize internet-facing management endpoints
  • Security awareness for engineers with privileged access

Detection signals and telemetry

Signal
  • Public secret-scanning alerts for your keys

    Repository provider / AWS notification of exposed keys
  • Scanning traffic against public endpoints

    High volume, low signal; useful mainly for context.

    WAF, load balancer and VPC flow logs

For leadership

What this means for the business

Most reconnaissance cannot be prevented, only reduced. The practical business question is whether anything the company publishes — code, documentation, templates — gives an attacker a shortcut such as working credentials.

Common misconceptions

Myth

“Our AWS account ID is a secret.”

Reality

AWS states account IDs are not secret. Security must not rely on them being unknown, but there is no reason to publish them unnecessarily.

Myth

“Private repositories are safe places for keys.”

Reality

Private repositories are shared with many people and tools and are themselves targeted; keys should not be in source code at all.

Practical security checklist

0 of 4 done

Saved only in this browser. Nothing is sent to Securitain.

Related attack scenarios

Where Securitain fits

  • Securitain can assess todayCredential prioritization — surfacing access keys and identities whose permissions make a leak more damaging. Learn more
  • Securitain can assess todayPublic and cross-account exposure checks on S3, KMS, SQS, SNS and Secrets Manager resource policies. Learn more

Official sources and references

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain