Getting Credential Reports for your AWS Account

By Ashwin Venugopal -





Understanding the Report Format

Credential reports are formatted in Comma-Separated Values (CSV) files and they contain following columns:
  1. user- The friendly name of the user.
  2. arn- The Amazon Resource Name (ARN) of the user.
  3. user_creation_time- The date and time when a user was created, in ISO 8601 date-time format.
  4. password_enabled- This value is True when a user has a password, otherwise it's False. However, for AWS account root user, the value is not_supported.
  5. password_last_used- Date and time at which the IAM user's as well as the AWS account root user's password was last used, in ISO 8601 date-time format.
  6. password_last_changed- The date and time at which the user's password was last set (in ISO 8601 date-time format).
  7. password_next_rotation- This one also shows the date and time at which the user is required to set a new password (in ISO 8601 date-time format).
  8. mfa_active- If an MFA device is enabled for a user, then, this value is True otherwise it's False.
  9. access_key_1_active- If the access key is active, then, the value is True otherwise it's False. 
  10. access_key_1_last_rotated- It contains the date and time (in ISO 8601 date-time format) at which the access key was last created or changed. It's N/A if there's no access key.
  11. access_key_1_last_used_date- The date and time at which the user's was most recently used to sign an AWS API request.
  12. access_key_1_last_used_region- The AWS Region in which the access key was most recently used.
  13. access_key_1_last_used_service- The most recently accessed AWS service with the access key.
  14. access_key_2_active- If there's a second access key and it's Active this value is True otherwise False.
  15. access_key_2_last_rotated- The date and time at which the second access key was created or last changed.
  16. access_key_2_last_used_date- The date and time at which the second access key was most recently used to sign an AWS API request.
  17. access_key_2_last_used_region- The AWS Region in which the user's second access key was most recently used.
  18. cert_1_active- If the user's X.509 signing certificate's status is Active, then, this value is True otherwise it's False.
  19. cert_1_last_rotated- It's the date and time when the user's signing certificate was created or last changed.
  20. cert_2_active- If the user's second X.509 signing certificate's status is Active, then, this value is True otherwise it's False.
  21. cert_2_last_rotated- It's the date and time when the user's second signing certificate was created or last changed.

Getting Credential Reports (Console)

The AWS Management Console can help in downloading a credential report as a CSV file.

To download a credential report (console)

  1. Firstly, sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. Now, select Credential Report in the navigation pane.
  3. After that you can go for Download Report.

Getting Credential Reports (AWS CLI)

To download a credentials report (AWS CLI)
  1. First of all, generate a credentials report and as AWS only stores a single report, the new one will overwrite the previous one. aws iam generate_credential_report.
  2. Now, you can view the last generated report: aws iam get_credential_report.

Getting Credential Reports (AWS API)

To download a credentials report (AWS API)
  1. First of all, generate a credentials report and as AWS only stores a single report, the new one will overwrite the previous one. GenerateCredentialReport.
  2. Now, you can view the last generated report: GetCredentialReport.























































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