AWS agents: connect each credential to a verifiable task
An agent’s authorization needs to follow the task the business approved. AWS’s new API calls for an assessment that also covers the receiving process and evidence of what it can do.
Читати португальськоюBy Pentesty
Start with the task agreement
Choose a small operation with a data owner and a clear result. An agent might prepare an analysis from one business unit’s documents without changing the source files. Record which resources belong to the assignment, an appropriate deadline and who can approve an expansion. This gives the team a basis for reviewing the policy instead of starting with a developer’s permission list.
In its November 20 announcement, AWS introduced GetScopedCredentials. The API reference describes temporary credentials retaining the same identity, with permissions constrained by policy intersection and duration limited to the originating session. Treat the mechanism as part of the authorization design, with acceptance criteria for your environment.
Check the path to the originating credential
Map who authenticates the request, selects the resource and delivers the credential to the executor. The chosen business unit or customer needs to follow a relationship validated by the application. A customer name written in a prompt should not act as authorization. Separate the component deciding scope from the component processing the documents as well.
In an authorized environment, check which credential sources the process can reach. Include variables, files, integrations and services available to its runtime. If it can still obtain a broader credential, record that path as an isolation issue requiring resolution. Our AWS service-role permissions analysis connects identity to the actual reach of a workload.
Make refusal part of acceptance
Prepare resources and synthetic data for two independent contexts. Run the approved task in the first and check refusal of an action or resource outside that agreement. Define expected outcomes before testing and record the policy, artifact and identity used. A correct answer from the agent alone does not demonstrate that inappropriate access would be denied.
Examine termination too: a deadline reached, a cancelled task and a credential issuance failure. Agree on expected behavior and who can stop execution beforehand. Avoid a silent recovery path that hands broad access back to the agent simply to finish the job. Preserve failures as evidence and refer the decision to the owner, identifying the effect on the task.
Include service limits in the assessment
The IAM guide warns about unsupported services and KMS key caching that can affect the intended restriction. It also explains revocation together with the originating session. Include those limits in scope and response planning.
Bring application, identity and data owners together to assess actual dependencies. An operation might need another service or a decryption step missing from the initial design. Record the rationale, owner and next review for each exception. Where available evidence does not resolve an important condition, keep the deployment under assessment and request clarification from the vendor.
Keep evidence that explains delegation
Maintain a record connecting the approved request, executor, policy and result. In available audit records, identify issuance and subsequent actions belonging to the task. Use correlation identifiers and timestamps without copying tokens or secrets into reports. A shared originating identity requires care so the team can distinguish delegated jobs without treating every issued credential as a new person.
Closure should bring together the permitted test, expected refusal, isolation assessment and outstanding work. Choose checks that can be repeated when the agent or application changes. Our workload secret-containment review complements this work: the approved boundary needs to remain valid during execution and recovery, with enough evidence to explain the decision.
Frequently asked questions
Does the new API create a different identity for the agent?
The reference describes preservation of the originating identity. Plan task correlation and verify the records available to your application rather than assuming an independent user for every credential issued.
Does a restricted policy settle every isolation question?
The proposed assessment includes the process and its other access sources. Document discovered paths and verify that the executor receives only the credentials intended for the authorized assignment.
Which test should accompany a successful demonstration?
An authorized refusal test outside the approved resource or action, using synthetic data. Record the expected outcome, observed result and limits of the verification performed.
When can the team close the deployment?
When authorization, issuance, execution and termination are connected to agreed evidence, with support and exceptions assessed. A screenshot of the agent’s answer does not replace that acceptance evidence.
Sources and references
- AWS Security Blog: original November 20 GetScopedCredentials announcement
- AWS STS: GetScopedCredentials API reference
- AWS IAM: scoped credential evaluation, revocation and limitations
Original Pentesty analysis, published November 20, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.