A financial technology startup is preparing for a compliance audit. An external auditing firm requires temporary, read-only access to the startup's AWS resources. The external auditors do not possess AWS accounts, and the startup's security policy strictly prohibits creating permanent IAM users for third-party entities. Which of the following is the most secure, AWS-recommended method to grant the auditors access?
- Configure AWS IAM Identity Center to federate the external auditors using their existing corporate identity provider, granting them temporary security credentials through an assigned IAM role.Cevap
- BCreate a shared IAM user named 'Auditor-Group' with read-only policies, generate a set of permanent access keys, and share them securely with the auditing firm.
- CCreate an IAM role with the required permissions and grant the startup's AWS Account Root User the ability to assume this role, then share the root user credentials with the auditors.
- DSubmit a ticket to AWS Support asking AWS to manage, monitor, and configure the temporary auditor access to the startup's resources on their behalf.
Cevap
Configure AWS IAM Identity Center to federate the external auditors using their existing corporate identity provider, granting them temporary security credentials through an assigned IAM role.
The correct option is to configure AWS IAM Identity Center to federate the external auditors using their existing corporate identity provider, granting them temporary security credentials through an assigned IAM role. This aligns with AWS security best practices by utilizing temporary security credentials, avoiding the creation of long-term IAM credentials (such as access keys), and maintaining the principle of least privilege without creating permanent IAM users in the startup's AWS account.
Adım Adım Çözüm
Anahtar Kavram
Identity Federation and Temporary Credentials