Skip to content

Latest commit

 

History

History

README.md

AWS IAM Root User Account Without Hardware MFA

What It Does

This policy template reports if the root user account for an AWS account does not have hardware MFA (multi-factor authentication) enabled. Optionally, this report can be emailed.

Multi-factor authentication increases account security by requiring the user have access to another device in order to log into the account in addition to their username and password. Hardware MFA uses a hardware tool, such as a physical key, to authenticate. It is recommended that MFA be enabled on all accounts, and in some cases, hardware MFA is preferred.

Input Parameters

  • Email Addresses - Email addresses of the recipients you wish to notify.
  • Account Number - The Account number for use with the AWS STS Cross Account Role. Leave blank when using AWS IAM Access key and secret. It only needs to be passed when the desired AWS account is different than the one associated with the Flexera One credential. More information is available in our documentation.
  • Attach CSV To Incident Email - Whether or not to attach the results as a CSV file to the incident email.
  • Incident Table Rows for Email Body (#) - The number of results to include in the incident table in the incident email. Set to '0' to not show an incident table at all, and '100000' to include all results. Does not impact attached CSV files or the incident as presented in Flexera One.

Policy Actions

  • Sends an email notification.

Prerequisites

This Policy Template uses Credentials for authenticating to datasources -- in order to apply this policy template you must have a Credential registered in the system that is compatible with this policy template. If there are no Credentials listed when you apply the policy template, please contact your Flexera Org Admin and ask them to register a Credential that is compatible with this policy template. The information below should be consulted when creating the credential(s).

  • AWS Credential (provider=aws) which has the following permissions:

    • sts:GetCallerIdentity
    • iam:GetAccountSummary
    • iam:ListVirtualMFADevices

    Example IAM Permission Policy:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "sts:GetCallerIdentity",
                    "iam:GetAccountSummary",
                    "iam:ListVirtualMFADevices"
                ],
                "Resource": "*"
            }
        ]
    }
  • Flexera Credential (provider=flexera) which has the following roles:

    • billing_center_viewer

The Provider-Specific Credentials page in the docs has detailed instructions for setting up Credentials for the most common providers.

Supported Clouds

  • AWS

Cost

This policy template does not incur any cloud costs.