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.
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
01Identify internet-facing services and their technology
02Find leaked credentials or configuration in public sources
03Learn naming conventions, account IDs and identity structure
04Identify people with privileged access for phishing
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
SignalSource
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%
0 of 4 done
Saved only in this browser. Nothing is sent to Securitain.