Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› How should security teams use AWS STS to…
Cyber Security

How should security teams use AWS STS to reduce standing access in cloud environments?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Cyber Security

Security teams should use AWS STS to replace long lived credentials with short lived, task scoped access. Issue temporary credentials only when a user or workload needs them, map access through roles rather than direct account permissions, and revoke or expire sessions quickly. This reduces standing privilege, limits blast radius, and makes cloud access easier to govern across teams and environments.

Why AWS STS changes the access model in cloud environments

aws sts is useful because it changes access from something persistent to something that is issued only when needed. Instead of letting users or workloads keep reusable credentials for long periods, teams can broker short-lived sessions through roles. That makes access easier to constrain, easier to review, and harder to reuse after the original task is complete.

The practical shift is from identity possession to session-based authorisation. A role can express what the caller may do, while STS issues a temporary set of credentials for a bounded time and context. That is a better fit for cloud operations where access should be time-limited, task-limited, and environment-aware.

For teams formalising that model, the Cloud Workload Identity Guide is the broad reference point for replacing static keys with workload and federation patterns across clouds.

How to structure STS usage around roles, sessions and trust

Use STS so that the caller assumes a role rather than receives direct standing permissions on an account or resource. That keeps the permission set in one place and lets you attach trust conditions, session boundaries and audit context to the temporary session itself. It is especially important where different teams, pipelines or accounts need different scopes for different tasks.

Trust policy design matters as much as the role permissions. If the trust relationship is too broad, STS simply creates temporary standing access. Good practice is to make the trust relationship specific enough that only the intended user, workload or external identity can request the role, and to keep the resulting session narrow in duration and scope.

In AWS-specific implementations, AWS STS and AssumeRole Guide is the most direct companion because it focuses on trust conditions, session tags, source identity, role chaining and revocation.

What strong STS governance looks like across accounts and workloads

Governance becomes simpler when STS is part of a wider control model, not just an authentication shortcut. Cloud teams should be able to answer who can assume which role, from where, for how long, and under what conditions. That is what makes the access model governable across multiple accounts, environments and deployment paths.

For workloads, STS is strongest when it replaces static secrets in automation, CI/CD and service-to-service access. For humans, it works best when elevated or sensitive access is time-bound and traceable rather than permanently assigned. The same pattern supports least privilege, but only if role sprawl and unconstrained trust relationships are kept under control.

The Multi-Cloud Identity Guide and the AWS Multi-Account Security Reference Architecture Guide help place STS inside broader privilege governance and account design rather than treating it as a standalone feature.

Risk and Threat Considerations

The main risk with STS is false confidence: short-lived credentials reduce standing access, but they do not fix overly broad roles, weak trust rules or poor session visibility. If an attacker can assume a role, misuse a federated identity, or obtain session credentials during their valid lifetime, they can still act with the privileges of that session.

Failure mechanism: Over-permissive role policies, weak trust conditions or exposed session material let an adversary gain temporary but still highly effective access. Short-lived does not mean low impact if the session can reach sensitive resources.

Impact: The blast radius is smaller than with long-lived keys, but not eliminated. Mis-scoped STS usage can still enable data access, privilege escalation, persistence through repeated re-assumption, or lateral movement across accounts and environments.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CSA Cloud Controls Matrix and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
CSA Cloud Controls MatrixIAM — Identity and Access ManagementSTS role-based temporary access is a cloud IAM control problem.
Recommendation — Use IAM controls to issue short-lived role access instead of standing credentials.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementSTS reduces reliance on long-lived authenticators and session material.
AC-2 — Account ManagementRole assumption and session governance depend on controlled account and privilege assignment.
AC-6 — Least PrivilegeSTS is used to narrow privileges to task-scoped sessions.
Recommendation — Manage credential lifecycle so temporary access replaces persistent secrets. Constrain who can assume roles and review standing permissions regularly. Grant only the minimum role permissions needed for each session.
ISO/IEC 27001:2022A.5.15 — Access controlSTS operationalises time-bound access control instead of permanent access.
Recommendation — Implement access control so permissions are issued only for active need.

Practitioner Guidance

What to prioritise: Start by identifying every place where long-lived IAM user keys, embedded secrets or reusable access tokens are still used for cloud access. Those are the easiest candidates for replacement with STS-backed roles and short session durations.

What to verify: Check that each role has a narrow trust policy, a bounded session duration, and a clear source of identity in logs. If you cannot tell who assumed the role, why, and from where, the access model is not yet governable.

Decision rule: If a session can reach production data or infrastructure, treat role design, trust conditions and revocation as the primary controls, not the convenience of temporary credentials. Temporary access is only safer when it is also observable and tightly scoped.

Practitioner takeaway: STS reduces standing access only when teams replace static credentials with tightly governed role assumption, then prove they can review and revoke those sessions quickly when risk changes.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org