Rotating Access Keys

By Ashwin Venugopal -

 






Rotating IAM User Access Keys (Console)

Access keys can be rotated from the AWS Management Console.

To rotate access keys for an IAM user without interrupting your applications (console)

  • You can create a second access key even if the first one is still active, which will lead to the user having two active access keys.

  • Now you will have to update all the applications and tools in order to use the new access key.

  • You can also check if the first access key is still in use with the help of Last used column for the oldest key.

  • You can choose Make inactive to deactivate the first access key instead of completely deleting it because it has never been in use recently.

  • If you want to confirm that your applications are working, then use only new access key, but, you can also choose Make active to reenable the first one and then return to the step 3 above and update the application to use the new key.   

  • You can definitely delete the first access key after waiting for sufficient time period to make sure that all the applications and tools have been updated.                                                                                                                                                                                                                                                                                                                                                                                            

To determine when access keys need rotating (console)

  1. Sign-in to the AWS Management Console and open the IAM console at https:// console.aws.amazon.com/iam.
  2. Select Users in the navigation pane.
  3. Add the Access key age column to users table if required.
  4. As the Access key age column shows the number of days since the oldest active key was created, this information can help in locating the users with access keys that need rotating. For users with no access keys, None will be displayed on the column.

Rotating Access Keys (AWS CLI)

The AWS Command Line Interface can help in rotating access keys.

To rotate access keys without interrupting your applications (AWS CLI)

  1. Even if the first access key is still active, you can create a second one (active by default) by running this command- aws iam create-access-key.
  2. Now update all applications and tools to use the new access key.
  3. You can find out if the first access key is still in use via this command- aws iam get-access-key-last-used.
  4. It's recommended to not delete the first access key, instead make it inactive with the help of this command- aws iam update-access-key.
  5. In order to confirm that your applications are working, use the new access key only. However, you can still activate the first one and then return to step 2 and update this application to use the new key.
  6. After successfully waiting for some period of time to update all the applications and tools, the first access key can deleted with this command- aws iam delete-access-key.


Rotating Access Keys (AWS API)

The AWS API can help in rotating access keys.

To rotate access keys without interrupting your applications (AWS API)

  1. Even if the first access key is still active, you can create a second one (active by default) by calling this operation- CreateAccessKey.
  2. Now update all applications and tools to use the new access key.
  3. You can find out if the first access key is still in use via this operation- GetAccessKeyLastUsed.
  4. It's recommended to not delete the first access key, instead make it inactive with the help of this operation- UpdateAccessKey.
  5. In order to confirm that your applications are working, use the new access key only. However, you can still activate the first one and then return to step 2 and update this application to use the new key.
  6. After successfully waiting for some period of time to update all the applications and tools, the first access key can deleted with this operation- DeleteAccessKey.




























Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more