Identify (ID): Know Your Assets, Risks and Where to Improve
Asset management, risk assessment and continuous improvement
TL;DR (for busy owners)
- What it is: Identify (ID) is about understanding what you have and what could go wrong with it: assets, risks and how you get better over time.
- Why it matters: You cannot protect, monitor or recover what you do not know exists. Forgotten accounts, unused access keys and unowned data stores are where many cloud incidents start.
- Quick action: List every AWS account, who owns it, and which ones hold customer or regulated data.
The three Identify categories
| Code | Category | In plain English |
|---|---|---|
| ID.AM | Asset Management | Hardware, software, services, data, people and suppliers are inventoried and prioritized |
| ID.RA | Risk Assessment | Threats, vulnerabilities and their likely impact are understood |
| ID.IM | Improvement | Lessons from assessments, exercises and incidents feed back into the program |
Signs Identify is weak
- Nobody can produce a current list of cloud accounts, or of the identities and access keys in them.
- Sensitive data is discovered during an incident rather than before it.
- Risk assessments are a yearly document that does not change anything.
What it looks like in AWS
In cloud, "assets" include accounts, IAM users, roles and access keys, trust relationships with other accounts, S3 buckets, databases, secrets and the third-party integrations that reach them. Identities are assets too: a role that can assume administrator access elsewhere is as important to inventory as a server. Risk assessment then asks which combinations of access and data create the most exposure — see the attack scenario library for how those combinations are exploited.
Fast checks (30 minutes)
Identify quick assessment
- Every cloud account has a named owner and purpose (ID.AM)
- Repositories holding customer or regulated data are listed (ID.AM)
- IAM users, access keys and roles are inventoried, including unused ones (ID.AM)
- Third parties with access to data or accounts are listed (ID.AM, GV.SC)
- A risk assessment was done in the last 12 months and produced actions (ID.RA)
- Findings from incidents or tests are tracked to completion (ID.IM)
What to watch over time
Signals that the inventory is drifting
New accounts or regions in use without an owner
Access keys not used in 90 days
New roles trusting external accounts
New data stores without classification
Map to frameworks
NIST CSF 2.0 Identify categories
Where Securitain fits
Identity inventory for AWS
IAM identity and trust inventory
A current view of identities, credentials and trust relationships across connected AWS accounts supports ID.AM and ID.RA.
- 1Connect accounts with the read-only role
- 2Review IAM users, roles, access-key configuration and trust relationships
- 3Prioritize identities with sensitive permissions or privilege-escalation paths
Next steps
Inventory first
Start with accounts and owners, then identities and data stores. A short, accurate inventory is more useful than a long, stale one.
Sources & References
- 1.The NIST Cybersecurity Framework (CSF) 2.0 — NIST CSWP 29
Official framework text
- 2.NIST CSF 2.0: Small Business Quick-Start Guide (SP 1300)
Practical starting actions for small organizations
Read-only analysis of IAM users, roles, access keys and trust relationships across your accounts.
Inventory AWS identities and trust