# Policy Sentry
IAM Least Privilege Policy Generator.
[](https://github.com/salesforce/policy_sentry/actions?query=workflow%3Acontinuous-integration)
[](https://policy-sentry.readthedocs.io/en/latest/?badge=latest)
[](https://gitter.im/salesforce/policy_sentry?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](https://twitter.com/kmcquade3)
[](https://pypi.org/project/policy-sentry)
[](#)
[](https://pepy.tech/project/policy-sentry)
- [Tutorial](#tutorial)
* [Installation](#installation)
+ [Package managers](#package-managers)
+ [Shell completion](#shell-completion)
* [Step 1: Create the Template](#step-1--create-the-template)
* [Step 2: Copy/paste ARNs](#step-2--copy-paste-arns)
* [Step 3: Write-policy command](#step-3--write-policy-command)
- [Cheat sheets](#cheat-sheets)
* [Policy Writing cheat sheet](#policy-writing-cheat-sheet)
* [IAM Database Query Cheat Sheet](#iam-database-query-cheat-sheet)
* [Local Initialization (Optional)](#local-initialization--optional-)
- [Other Usage](#other-usage)
* [Commands](#commands)
* [Python Library usage](#python-library-usage)
* [Docker](#docker)
* [Terraform](#terraform)
- [References](#references)
## Documentation
For walkthroughs and full documentation, please visit the [project on ReadTheDocs](https://policy-sentry.readthedocs.io/en/latest/index.html).
See the [Salesforce Engineering Blog post](https://engineering.salesforce.com/salesforce-cloud-security-automating-least-privilege-in-aws-iam-with-policy-sentry-b04fe457b8dc) on Policy Sentry.
## Overview
Writing security-conscious IAM Policies by hand can be very tedious and inefficient. Many Infrastructure as Code developers have experienced something like this:
* Determined to make your best effort to give users and roles the least amount of privilege you need to perform your duties, you spend way too much time combing through the AWS IAM Documentation on [Actions, Resources, and Condition Keys for AWS Services][1].
* Your team lead encourages you to build security into your IAM Policies for product quality, but eventually you get frustrated due to project deadlines.
* You don't have an embedded security person on your team who can write those IAM Policies for you, and there's no automated tool that will automagically sense the AWS API calls that you perform and then write them for you with Resource ARN constraints.
* After fantasizing about that level of automation, you realize that writing least privilege IAM Policies, seemingly out of charity, will jeopardize your ability to finish your code in time to meet project deadlines.
* You use Managed Policies (because hey, why not) or you eyeball the names of the API calls and use wildcards instead so you can move on with your life.
Such a process is not ideal for security or for Infrastructure as Code developers. We need to make it easier to write IAM Policies securely and abstract the complexity of writing least-privilege IAM policies. That's why I made this tool.
Policy Sentry allows users to create least-privilege IAM policies in a matter of seconds, rather than tediously writing IAM policies by hand. These policies are scoped down according to access levels and resources. In the case of a breach, this helps to limit the blast radius of compromised credentials by only giving IAM principals access to what they need.
**Before this tool, it could take hours to craft an IAM Policy with resource ARN constraints — but now it can take a matter of seconds**. This way, developers only have to determine the resources that they need to access, and **Policy Sentry abstracts the complexity of IAM policies** away from their development processes.
### Writing Secure Policies based on Resource Constraints and Access Levels
Policy Sentry's flagship feature is that it can create IAM policies based on resource ARNs and access levels. Our CRUD functionality takes the opinionated approach that IAC developers shouldn't have to understand the complexities of AWS IAM - we should abstract the complexity for them. In fact, developers should just be able to say...
* "I need Read/Write/List access to `arn:aws:s3:::example-org-sbx-vmimport`"
* "I need Permissions Management access to `arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret`"
* "I need Tagging access to `arn:aws:ssm:us-east-1:123456789012:parameter/test`"
...and our automation should create policies that correspond to those access levels.
How do we accomplish this? Well, Policy Sentry leverages the AWS documentation on [Actions, Resources, and Condition Keys][1] documentation to look up the actions, access levels, and resource types, and generates policies according to the ARNs and access levels. Consider the table snippet below:
<table class="tg">
<tr>
<th class="tg-fymr">Actions</th>
<th class="tg-fymr">Access Level</th>
<th class="tg-fymr">Resource Types</th>
</tr>
<tr>
<td class="tg-0pky">ssm:GetParameter</td>
<td class="tg-0pky">Read</td>
<td class="tg-0pky">parameter</td>
</tr>
<tr>
<td class="tg-0pky">ssm:DescribeParameters</td>
<td class="tg-0pky">List</td>
<td class="tg-0pky">parameter</td>
</tr>
<tr>
<td class="tg-0pky">ssm:PutParameter</td>
<td class="tg-0pky">Write</td>
<td class="tg-0pky">parameter</td>
</tr>
<tr>
<td class="tg-0pky">secretsmanager:PutResourcePolicy</td>
<td class="tg-0pky">Permissions management</td>
<td class="tg-0pky">secret</td>
</tr>
<tr>
<td class="tg-0pky">secretsmanager:TagResource</td>
<td class="tg-0pky">Tagging</td>
<td class="tg-0pky">secret</td>
</tr>
</table>
Policy Sentry aggregates all of that documentation into a single database and uses that database to generate policies according to actions, resources, and access levels.
## Tutorial
### Installation
#### Package managers
* Homebrew
```bash
brew tap salesforce/policy_sentry https://github.com/salesforce/policy_sentry
brew install policy_sentry
```
* Pip
```bash
pip3 install --user policy_sentry
```
#### Shell completion
To enable Bash completion, put this in your `.bashrc`:
```bash
eval "$(_POLICY_SENTRY_COMPLETE=source policy_sentry)"
```
To enable ZSH completion, put this in your `.zshrc`:
```
eval "$(_POLICY_SENTRY_COMPLETE=source_zsh policy_sentry)"
```
### Step 1: Create the Template
* To generate a policy according to resources and access levels, start by
creating a template with this command so you can just fill out the ARNs:
```bash
policy_sentry create-template --output-file crud.yml --template-type crud
```
* It will generate a file like this:
```yaml
mode: crud
name: ''
# Specify resource ARNs
read:
- ''
write:
- ''
list:
- ''
tagging:
- ''
permissions-management:
- ''
# Actions that do not support resource constraints
wildcard-only:
single-actions: # standalone actions
- ''
# Service-wide - like 's3' or 'ec2'
service-read:
- ''
service-write:
- ''
service-list:
- ''
service-tagging:
- ''
service-permissions-management:
- ''
# Skip resource constraint requirements by listing actions here.
skip-resource-constraints:
- ''
# Exclude actions from the output by specifying them here. Accepts wildcards, like kms:Delete*
exclude-actions:
- ''
# If this policy needs to include an AssumeRole action
sts:
assume-role:
- ''
assume-role-with-saml:
- ''
assume-role-with-web-identity:
- ''
```
### Step 2: Copy/paste ARNs
* Copy/paste the ARNs you want to include in your policy. You can delete lines that you don't use, or just leave them there.
```yaml
mode: crud
read:
- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'
write:
- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'
list:
- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'
tagging:
- 'arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret'
permissions-management:
- 'arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret'
```
### Step 3: Write-policy command
* Then run this command:
```bash
policy_sentry write-policy --input-file crud.yml
```
* It will generate these results:
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "SsmReadParameter",
"Effect": "Allow",
"Action": [
"ssm:GetParameter",
"ssm:GetParameterHistory",
"ssm:GetParameters",
"ssm:GetParametersByPath",
"ssm:ListTagsForResource"
],
"Resource": [
"arn:aws:ssm:us-east-1:123456789012:parameter/myparameter"
]
},
{
"Sid": "SsmWriteParameter",
"Effect": "Allow",
"Action": [
"ssm:DeleteParameter",
"ssm:DeleteParameters",
"ssm:LabelParameterVersion",
"ssm:PutParameter"
],
"Resource": [
"arn:aws:ssm:us-east-1:123456789012:parameter/myparameter"
]
},
{
"Sid": "SecretsmanagerPermissionsmanagementSecret",
"Effect": "Allow",
"Action": [
"secretsmanager:DeleteResourcePolicy",
"secretsmanager:PutResourcePolicy"
],
"Resource": [
"arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret"
]
},
{
"Sid": "SecretsmanagerTaggingSecret",
"Effect": "Allow",
"Action": [
"secretsmanager:TagResource",
"secretsmanager:UntagResource"
],
"Resource": [
"arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret"
]
}
]
}
```
Notice how the policy above recognizes the ARNs that the user supplies, along with the requested access level. For instance, the SID `SecretsmanagerTaggingSecret` contains Tagging actions that are assigned to the secret resource type only.
This rapidly speeds up the time to develop IAM policies, and ensures that all policies created limit access to exactly what your role needs access to. This way, developers only have to determine the resources that they need to access, and we abstract the complexity of IAM policies away from their development processes.
## Cheat sheets
### Policy Writing cheat sheet
```bash
# Create templates first!!! This way you can just paste the values you need rather than remembering the YAML format
# CRUD mode
policy_sentry create-template --output-file tmp.yml --template-type crud
# Actions mode
policy_sentry create-template --output-file tmp.yml --template-type actions
# Write policy based on resource-specific access levels
policy_sentry write-policy --input-file examples/yml/crud.yml
# Write policy based on a list of actions
policy_sentry write-policy --input-file examples/yml/actions.yml
```
### IAM Database Query Cheat Sheet
```bash
###############
# Actions Table
###############
# NOTE: Use --fmt yaml or --fmt json to change the output format. Defaults to json for querying
# Get a list of actions that do not support resource constraints
policy_sentry query action-table --service s3 --resource-type "*" --fmt yaml
# Get a list of actions at the "Write" level in S3 that do not support resource constraints
policy_sentry query action-table --service s3 --access-level write --resource-type "*" --fmt yaml
# Get a list of all IAM actions across ALL services that have "Permissions management" access
policy_sentry query action-table --service all --access-level permissions-management
# Get a list of all IAM Actions available to the RAM service
policy_sentry query action-table --service ram
# Get details about the `ram:TagResource` IAM Action
policy_sentry query action-table --service ram --name tagresource
# Get a list of all IAM actions under the RAM service that have the Permissions management access level.
policy_sentry query action-table --service ram --access-level permissions-management
# Get a list of all IAM actions under the SES service that support the `ses:FeedbackAddress` condition key.
policy_sentry query action-table --service ses --condition ses:FeedbackAddress
###########
# ARN Table
###########
# Get a list of all RAW ARN formats available through the SSM service.
policy_sentry query arn-table --service ssm
# Get the raw ARN format for the `cloud9` ARN with the short name `environment`
policy_sentry query arn-table --service cloud9 --name environment
# Get key/value pairs of all RAW ARN formats plus their short names
policy_sentry query arn-table --service cloud9 --list-arn-types
######################
# Condition Keys Table
######################
# Get a list of all condition keys available to the Cloud9 service
policy_sentry query condition-table --service cloud9
# Get details on the condition key titled `cloud9:Permissions`
policy_sentry query condition-table --service cloud9 --name cloud9:Permissions
```
### Local Initialization (Optional)
```bash
# Initialize the policy_sentry config folder and create the IAM database tables.
policy_sentry initialize
# Fetch the most recent version of the AWS documentation so you can experiment with new services.
policy_sentry initialize --fetch
# Override the Access Levels by specifying your own Access Levels (example:, correcting Permissions management levels)
policy_sentry initialize --access-level-overrides-file ~/.policy_sentry/overrides-resource-policies.yml
policy_sentry initialize --access-level-overrides-file ~/.policy_sentry/access-level-overrides.yml
```
## Other Usage
### Commands
* `create-template`: Creates the YML file templates for use in the `write-policy` command types.
* `write-policy`: Leverage a YAML file to write policies for you
- Option 1: Specify CRUD levels (Read, Write, List, Tagging, or Permissions management) and the ARN of the resource. It will write this for you. See the [documentation][13]
- Option 2: Specify a list of actions. It will write the IAM Policy for you, but you will have to fill in the ARNs. See the [documentation][14].
* `query`: Query the IAM database tables. This can help when filling out the Policy Sentry templates, or just querying the database for quick knowledge.
- Option 1: Query the Actions Table (`action-table`)
- Option 2: Query the ARNs Table (`arn-table`)
- Option 3: Query the Conditions Table (`condition-table`)
* `initialize`: (Optional). Create a SQLite database that contains all of the services available through the [Actions, Resources, and Condition Keys documentation][1]. See the [documentation][12].
### Python Library usage
If you are developing your own Python code and you want to import Policy Sentry as a third party package, you can skip the initialization and leverage the local database file that is bundled with the Python package itself.
This is especially useful for developers who wish to leverage Policy Sentry’s capabilities that require the use of the IAM database (such as querying the IAM database table). This way, you don’t have to initialize the database and can just query it immediately.
The code example is located [here](https://github.com/salesforce/policy_sentry/blob/master/examples/library-usage/example.py). It is also shown below.
```python
from policy_sentry.querying.actions import get_actions_for_service
def example():
actions = get_actions_for_service('cloud9') # Then you can leverage any method that requires access to the database.
for action in actions:
print(action)
if __name__ == '__main__':
example()
```
The results will look like:
```
cloud9:CreateEnvironmentEC2
cloud9:CreateEnvironmentMembership
cloud9:DeleteEnvironment
cloud9:DeleteEnvironmentMembership
cloud9:DescribeEnvironmentMemberships
cloud9:DescribeEnvironmentStatus
cloud9:DescribeEnvironments
cloud9:GetUserSettings
cloud9:ListEnvironments
cloud9:ListTagsForResource
cloud9:TagResource
cloud9:UntagResource
cloud9:UpdateEnvironment
cloud9:UpdateEnvironmentMembership
cloud9:UpdateUserSettings
```
### Docker
If you prefer using Docker instead of installing the script with Python, we support that as well. From the root of the repository, use this to build the docker image:
```bash
docker build -t kmcquade/policy_sentry .
```
Use this to run some basic commands:
```bash
# Basic commands with no arguments
docker run -i --rm kmcquade/policy_sentry:latest "--help"
docker run -i --rm kmcquade/policy_sentry:latest "query"
# Query the database
docker run -i --rm kmcquade/policy_sentry:latest "query action-table --service all --access-level permissions-management"
```
The `write-policy` command also supports passing in the YML config via STDIN. If you are using the docker method, try it out here:
```bash
# Write policies by passing in the config via STDIN
cat examples/yml/crud.yml | docker run -i --rm kmcquade/policy_sentry:latest "write-policy"
cat examples/yml/actions.yml | docker run -i --rm kmcquade/policy_sentry:latest "write-policy"
```
### Terraform
The Terraform module is published and maintained [here](https://github.com/salesforce/policy_sentry/tree/master/terraform_module).
## References
* The document scraping process was inspired and borrowed from a similar [ansible hacking script][3].
* [Identity-Based vs Resource-based policies][5]
* [Actions, Resources, and Condition Keys for AWS Services][7]
[1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html
[2]: https://nose.readthedocs.io/en/latest/
[3]: https://github.com/ansible/ansible/blob/stable-2.9/hacking/aws_config/build_iam_policy_framework.py
[4]: https://github.com/evilpete/aws_access_adviser
[5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_identity-vs-resource.html
[6]: https://docs.aws.amazon.com/IAM/latest/APIReference/API_SimulatePrincipalPolicy.html
[7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html
[8]: https://docs.aws.amazon.com/awssupport/latest/user/Welcome.html
[9]: https://docs.aws.amazon.com/signer/latest/api/Welcome.html
[10]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/permissions-reference-cwe.html
[11]: https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-policy-keys
[12]: https://policy-sentry.readthedocs.io/en/latest/user-guide/initialize.html
[13]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#crud-mode-arns-and-access-levels
[14]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#actions-mode-lists-of-iam-actions
[15]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#folder-mode-write-multiple-policies-from-crud-mode-files
Raw data
{
"_id": null,
"home_page": "https://github.com/salesforce/policy_sentry",
"name": "policy-sentry",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": null,
"keywords": "aws iam roles policy policies privileges security",
"author": "Kinnaird McQuade",
"author_email": "kinnairdm@gmail.com",
"download_url": "https://files.pythonhosted.org/packages/7e/7a/7fbb394f21a3c43edcb7d04382b6d93567900b4c8ea4b224b284656115ed/policy_sentry-0.12.11.tar.gz",
"platform": null,
"description": "# Policy Sentry\n\nIAM Least Privilege Policy Generator.\n\n[](https://github.com/salesforce/policy_sentry/actions?query=workflow%3Acontinuous-integration)\n[](https://policy-sentry.readthedocs.io/en/latest/?badge=latest)\n[](https://gitter.im/salesforce/policy_sentry?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\n[](https://twitter.com/kmcquade3)\n[](https://pypi.org/project/policy-sentry)\n[](#)\n[](https://pepy.tech/project/policy-sentry)\n\n\n\n- [Tutorial](#tutorial)\n * [Installation](#installation)\n + [Package managers](#package-managers)\n + [Shell completion](#shell-completion)\n * [Step 1: Create the Template](#step-1--create-the-template)\n * [Step 2: Copy/paste ARNs](#step-2--copy-paste-arns)\n * [Step 3: Write-policy command](#step-3--write-policy-command)\n- [Cheat sheets](#cheat-sheets)\n * [Policy Writing cheat sheet](#policy-writing-cheat-sheet)\n * [IAM Database Query Cheat Sheet](#iam-database-query-cheat-sheet)\n * [Local Initialization (Optional)](#local-initialization--optional-)\n- [Other Usage](#other-usage)\n * [Commands](#commands)\n * [Python Library usage](#python-library-usage)\n * [Docker](#docker)\n * [Terraform](#terraform)\n- [References](#references)\n\n## Documentation\n\nFor walkthroughs and full documentation, please visit the [project on ReadTheDocs](https://policy-sentry.readthedocs.io/en/latest/index.html).\n\nSee the [Salesforce Engineering Blog post](https://engineering.salesforce.com/salesforce-cloud-security-automating-least-privilege-in-aws-iam-with-policy-sentry-b04fe457b8dc) on Policy Sentry.\n\n## Overview\n\nWriting security-conscious IAM Policies by hand can be very tedious and inefficient. Many Infrastructure as Code developers have experienced something like this:\n\n * Determined to make your best effort to give users and roles the least amount of privilege you need to perform your duties, you spend way too much time combing through the AWS IAM Documentation on [Actions, Resources, and Condition Keys for AWS Services][1].\n * Your team lead encourages you to build security into your IAM Policies for product quality, but eventually you get frustrated due to project deadlines.\n * You don't have an embedded security person on your team who can write those IAM Policies for you, and there's no automated tool that will automagically sense the AWS API calls that you perform and then write them for you with Resource ARN constraints.\n * After fantasizing about that level of automation, you realize that writing least privilege IAM Policies, seemingly out of charity, will jeopardize your ability to finish your code in time to meet project deadlines.\n * You use Managed Policies (because hey, why not) or you eyeball the names of the API calls and use wildcards instead so you can move on with your life.\n\nSuch a process is not ideal for security or for Infrastructure as Code developers. We need to make it easier to write IAM Policies securely and abstract the complexity of writing least-privilege IAM policies. That's why I made this tool.\n\nPolicy Sentry allows users to create least-privilege IAM policies in a matter of seconds, rather than tediously writing IAM policies by hand. These policies are scoped down according to access levels and resources. In the case of a breach, this helps to limit the blast radius of compromised credentials by only giving IAM principals access to what they need.\n\n**Before this tool, it could take hours to craft an IAM Policy with resource ARN constraints \u2014 but now it can take a matter of seconds**. This way, developers only have to determine the resources that they need to access, and **Policy Sentry abstracts the complexity of IAM policies** away from their development processes.\n\n### Writing Secure Policies based on Resource Constraints and Access Levels\n\nPolicy Sentry's flagship feature is that it can create IAM policies based on resource ARNs and access levels. Our CRUD functionality takes the opinionated approach that IAC developers shouldn't have to understand the complexities of AWS IAM - we should abstract the complexity for them. In fact, developers should just be able to say...\n\n* \"I need Read/Write/List access to `arn:aws:s3:::example-org-sbx-vmimport`\"\n* \"I need Permissions Management access to `arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret`\"\n* \"I need Tagging access to `arn:aws:ssm:us-east-1:123456789012:parameter/test`\"\n\n...and our automation should create policies that correspond to those access levels.\n\nHow do we accomplish this? Well, Policy Sentry leverages the AWS documentation on [Actions, Resources, and Condition Keys][1] documentation to look up the actions, access levels, and resource types, and generates policies according to the ARNs and access levels. Consider the table snippet below:\n\n<table class=\"tg\">\n <tr>\n <th class=\"tg-fymr\">Actions</th>\n <th class=\"tg-fymr\">Access Level</th>\n <th class=\"tg-fymr\">Resource Types</th>\n </tr>\n <tr>\n <td class=\"tg-0pky\">ssm:GetParameter</td>\n <td class=\"tg-0pky\">Read</td>\n <td class=\"tg-0pky\">parameter</td>\n </tr>\n <tr>\n <td class=\"tg-0pky\">ssm:DescribeParameters</td>\n <td class=\"tg-0pky\">List</td>\n <td class=\"tg-0pky\">parameter</td>\n </tr>\n <tr>\n <td class=\"tg-0pky\">ssm:PutParameter</td>\n <td class=\"tg-0pky\">Write</td>\n <td class=\"tg-0pky\">parameter</td>\n </tr>\n <tr>\n <td class=\"tg-0pky\">secretsmanager:PutResourcePolicy</td>\n <td class=\"tg-0pky\">Permissions management</td>\n <td class=\"tg-0pky\">secret</td>\n </tr>\n <tr>\n <td class=\"tg-0pky\">secretsmanager:TagResource</td>\n <td class=\"tg-0pky\">Tagging</td>\n <td class=\"tg-0pky\">secret</td>\n </tr>\n</table>\n\nPolicy Sentry aggregates all of that documentation into a single database and uses that database to generate policies according to actions, resources, and access levels.\n\n## Tutorial\n\n\n### Installation\n\n#### Package managers\n\n* Homebrew\n\n```bash\nbrew tap salesforce/policy_sentry https://github.com/salesforce/policy_sentry\nbrew install policy_sentry\n```\n\n* Pip\n\n```bash\npip3 install --user policy_sentry\n```\n\n#### Shell completion\n\nTo enable Bash completion, put this in your `.bashrc`:\n\n```bash\neval \"$(_POLICY_SENTRY_COMPLETE=source policy_sentry)\"\n```\n\nTo enable ZSH completion, put this in your `.zshrc`:\n\n```\neval \"$(_POLICY_SENTRY_COMPLETE=source_zsh policy_sentry)\"\n```\n\n### Step 1: Create the Template\n\n* To generate a policy according to resources and access levels, start by\ncreating a template with this command so you can just fill out the ARNs:\n\n```bash\npolicy_sentry create-template --output-file crud.yml --template-type crud\n```\n\n* It will generate a file like this:\n\n```yaml\nmode: crud\nname: ''\n# Specify resource ARNs\nread:\n- ''\nwrite:\n- ''\nlist:\n- ''\ntagging:\n- ''\npermissions-management:\n- ''\n# Actions that do not support resource constraints\nwildcard-only:\n single-actions: # standalone actions\n - ''\n # Service-wide - like 's3' or 'ec2'\n service-read:\n - ''\n service-write:\n - ''\n service-list:\n - ''\n service-tagging:\n - ''\n service-permissions-management:\n - ''\n# Skip resource constraint requirements by listing actions here.\nskip-resource-constraints:\n- ''\n# Exclude actions from the output by specifying them here. Accepts wildcards, like kms:Delete*\nexclude-actions:\n- ''\n# If this policy needs to include an AssumeRole action\nsts:\n assume-role:\n - ''\n assume-role-with-saml:\n - ''\n assume-role-with-web-identity:\n - ''\n```\n\n### Step 2: Copy/paste ARNs\n\n* Copy/paste the ARNs you want to include in your policy. You can delete lines that you don't use, or just leave them there.\n\n```yaml\nmode: crud\nread:\n- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'\nwrite:\n- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'\nlist:\n- 'arn:aws:ssm:us-east-1:123456789012:parameter/myparameter'\ntagging:\n- 'arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret'\npermissions-management:\n- 'arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret'\n```\n\n### Step 3: Write-policy command\n\n* Then run this command:\n\n```bash\npolicy_sentry write-policy --input-file crud.yml\n```\n\n* It will generate these results:\n\n```json\n{\n \"Version\": \"2012-10-17\",\n \"Statement\": [\n {\n \"Sid\": \"SsmReadParameter\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"ssm:GetParameter\",\n \"ssm:GetParameterHistory\",\n \"ssm:GetParameters\",\n \"ssm:GetParametersByPath\",\n \"ssm:ListTagsForResource\"\n ],\n \"Resource\": [\n \"arn:aws:ssm:us-east-1:123456789012:parameter/myparameter\"\n ]\n },\n {\n \"Sid\": \"SsmWriteParameter\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"ssm:DeleteParameter\",\n \"ssm:DeleteParameters\",\n \"ssm:LabelParameterVersion\",\n \"ssm:PutParameter\"\n ],\n \"Resource\": [\n \"arn:aws:ssm:us-east-1:123456789012:parameter/myparameter\"\n ]\n },\n {\n \"Sid\": \"SecretsmanagerPermissionsmanagementSecret\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"secretsmanager:DeleteResourcePolicy\",\n \"secretsmanager:PutResourcePolicy\"\n ],\n \"Resource\": [\n \"arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret\"\n ]\n },\n {\n \"Sid\": \"SecretsmanagerTaggingSecret\",\n \"Effect\": \"Allow\",\n \"Action\": [\n \"secretsmanager:TagResource\",\n \"secretsmanager:UntagResource\"\n ],\n \"Resource\": [\n \"arn:aws:secretsmanager:us-east-1:123456789012:secret:mysecret\"\n ]\n }\n ]\n}\n```\n\nNotice how the policy above recognizes the ARNs that the user supplies, along with the requested access level. For instance, the SID `SecretsmanagerTaggingSecret` contains Tagging actions that are assigned to the secret resource type only.\n\nThis rapidly speeds up the time to develop IAM policies, and ensures that all policies created limit access to exactly what your role needs access to. This way, developers only have to determine the resources that they need to access, and we abstract the complexity of IAM policies away from their development processes.\n\n## Cheat sheets\n\n### Policy Writing cheat sheet\n\n```bash\n# Create templates first!!! This way you can just paste the values you need rather than remembering the YAML format\n# CRUD mode\npolicy_sentry create-template --output-file tmp.yml --template-type crud\n# Actions mode\npolicy_sentry create-template --output-file tmp.yml --template-type actions\n\n# Write policy based on resource-specific access levels\npolicy_sentry write-policy --input-file examples/yml/crud.yml\n\n# Write policy based on a list of actions\npolicy_sentry write-policy --input-file examples/yml/actions.yml\n```\n\n### IAM Database Query Cheat Sheet\n\n```bash\n\n###############\n# Actions Table\n###############\n# NOTE: Use --fmt yaml or --fmt json to change the output format. Defaults to json for querying\n\n# Get a list of actions that do not support resource constraints\npolicy_sentry query action-table --service s3 --resource-type \"*\" --fmt yaml\n\n# Get a list of actions at the \"Write\" level in S3 that do not support resource constraints\npolicy_sentry query action-table --service s3 --access-level write --resource-type \"*\" --fmt yaml\n\n# Get a list of all IAM actions across ALL services that have \"Permissions management\" access\npolicy_sentry query action-table --service all --access-level permissions-management\n\n# Get a list of all IAM Actions available to the RAM service\npolicy_sentry query action-table --service ram\n\n# Get details about the `ram:TagResource` IAM Action\npolicy_sentry query action-table --service ram --name tagresource\n\n# Get a list of all IAM actions under the RAM service that have the Permissions management access level.\npolicy_sentry query action-table --service ram --access-level permissions-management\n\n# Get a list of all IAM actions under the SES service that support the `ses:FeedbackAddress` condition key.\npolicy_sentry query action-table --service ses --condition ses:FeedbackAddress\n\n###########\n# ARN Table\n###########\n\n# Get a list of all RAW ARN formats available through the SSM service.\npolicy_sentry query arn-table --service ssm\n\n# Get the raw ARN format for the `cloud9` ARN with the short name `environment`\npolicy_sentry query arn-table --service cloud9 --name environment\n\n# Get key/value pairs of all RAW ARN formats plus their short names\npolicy_sentry query arn-table --service cloud9 --list-arn-types\n\n######################\n# Condition Keys Table\n######################\n\n# Get a list of all condition keys available to the Cloud9 service\npolicy_sentry query condition-table --service cloud9\n\n# Get details on the condition key titled `cloud9:Permissions`\npolicy_sentry query condition-table --service cloud9 --name cloud9:Permissions\n```\n\n### Local Initialization (Optional)\n\n```bash\n# Initialize the policy_sentry config folder and create the IAM database tables.\npolicy_sentry initialize\n\n# Fetch the most recent version of the AWS documentation so you can experiment with new services.\npolicy_sentry initialize --fetch\n\n# Override the Access Levels by specifying your own Access Levels (example:, correcting Permissions management levels)\npolicy_sentry initialize --access-level-overrides-file ~/.policy_sentry/overrides-resource-policies.yml\n\npolicy_sentry initialize --access-level-overrides-file ~/.policy_sentry/access-level-overrides.yml\n```\n\n## Other Usage\n\n### Commands\n\n* `create-template`: Creates the YML file templates for use in the `write-policy` command types.\n\n* `write-policy`: Leverage a YAML file to write policies for you\n - Option 1: Specify CRUD levels (Read, Write, List, Tagging, or Permissions management) and the ARN of the resource. It will write this for you. See the [documentation][13]\n - Option 2: Specify a list of actions. It will write the IAM Policy for you, but you will have to fill in the ARNs. See the [documentation][14].\n\n* `query`: Query the IAM database tables. This can help when filling out the Policy Sentry templates, or just querying the database for quick knowledge.\n - Option 1: Query the Actions Table (`action-table`)\n - Option 2: Query the ARNs Table (`arn-table`)\n - Option 3: Query the Conditions Table (`condition-table`)\n\n* `initialize`: (Optional). Create a SQLite database that contains all of the services available through the [Actions, Resources, and Condition Keys documentation][1]. See the [documentation][12].\n\n### Python Library usage\n\nIf you are developing your own Python code and you want to import Policy Sentry as a third party package, you can skip the initialization and leverage the local database file that is bundled with the Python package itself.\n\nThis is especially useful for developers who wish to leverage Policy Sentry\u2019s capabilities that require the use of the IAM database (such as querying the IAM database table). This way, you don\u2019t have to initialize the database and can just query it immediately.\n\nThe code example is located [here](https://github.com/salesforce/policy_sentry/blob/master/examples/library-usage/example.py). It is also shown below.\n\n```python\nfrom policy_sentry.querying.actions import get_actions_for_service\n\n\ndef example():\n actions = get_actions_for_service('cloud9') # Then you can leverage any method that requires access to the database.\n for action in actions:\n print(action)\n\nif __name__ == '__main__':\n example()\n```\n\nThe results will look like:\n\n```\ncloud9:CreateEnvironmentEC2\ncloud9:CreateEnvironmentMembership\ncloud9:DeleteEnvironment\ncloud9:DeleteEnvironmentMembership\ncloud9:DescribeEnvironmentMemberships\ncloud9:DescribeEnvironmentStatus\ncloud9:DescribeEnvironments\ncloud9:GetUserSettings\ncloud9:ListEnvironments\ncloud9:ListTagsForResource\ncloud9:TagResource\ncloud9:UntagResource\ncloud9:UpdateEnvironment\ncloud9:UpdateEnvironmentMembership\ncloud9:UpdateUserSettings\n```\n\n### Docker\n\nIf you prefer using Docker instead of installing the script with Python, we support that as well. From the root of the repository, use this to build the docker image:\n\n```bash\ndocker build -t kmcquade/policy_sentry .\n```\n\nUse this to run some basic commands:\n\n```bash\n# Basic commands with no arguments\ndocker run -i --rm kmcquade/policy_sentry:latest \"--help\"\ndocker run -i --rm kmcquade/policy_sentry:latest \"query\"\n\n# Query the database\ndocker run -i --rm kmcquade/policy_sentry:latest \"query action-table --service all --access-level permissions-management\"\n```\n\nThe `write-policy` command also supports passing in the YML config via STDIN. If you are using the docker method, try it out here:\n\n```bash\n# Write policies by passing in the config via STDIN\ncat examples/yml/crud.yml | docker run -i --rm kmcquade/policy_sentry:latest \"write-policy\"\n\ncat examples/yml/actions.yml | docker run -i --rm kmcquade/policy_sentry:latest \"write-policy\"\n```\n\n### Terraform\n\nThe Terraform module is published and maintained [here](https://github.com/salesforce/policy_sentry/tree/master/terraform_module).\n\n## References\n\n* The document scraping process was inspired and borrowed from a similar [ansible hacking script][3].\n* [Identity-Based vs Resource-based policies][5]\n* [Actions, Resources, and Condition Keys for AWS Services][7]\n\n[1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html\n[2]: https://nose.readthedocs.io/en/latest/\n[3]: https://github.com/ansible/ansible/blob/stable-2.9/hacking/aws_config/build_iam_policy_framework.py\n[4]: https://github.com/evilpete/aws_access_adviser\n[5]: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_identity-vs-resource.html\n[6]: https://docs.aws.amazon.com/IAM/latest/APIReference/API_SimulatePrincipalPolicy.html\n[7]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html\n[8]: https://docs.aws.amazon.com/awssupport/latest/user/Welcome.html\n[9]: https://docs.aws.amazon.com/signer/latest/api/Welcome.html\n[10]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/permissions-reference-cwe.html\n[11]: https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-policy-keys\n[12]: https://policy-sentry.readthedocs.io/en/latest/user-guide/initialize.html\n[13]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#crud-mode-arns-and-access-levels\n[14]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#actions-mode-lists-of-iam-actions\n[15]: https://policy-sentry.readthedocs.io/en/latest/user-guide/write-policy.html#folder-mode-write-multiple-policies-from-crud-mode-files\n\n\n\n",
"bugtrack_url": null,
"license": null,
"summary": "Generate locked-down AWS IAM Policies",
"version": "0.12.11",
"project_urls": {
"Code": "https://github.com/salesforce/policy_sentry/",
"Documentation": "https://policy-sentry.readthedocs.io/",
"Homepage": "https://github.com/salesforce/policy_sentry",
"Red Team Report": "https://opensource.salesforce.com/policy_sentry",
"Twitter": "https://twitter.com/kmcquade3"
},
"split_keywords": [
"aws",
"iam",
"roles",
"policy",
"policies",
"privileges",
"security"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "417a4082579f442c6e153c4417292c2014e371df1bd31aae476794d208236c6d",
"md5": "57189d27746e46d71cc4cfc93cf2b3c2",
"sha256": "2c12bde203b4de563437bbdda995d12ecd31c0b3776f50dd5f56f73e34eaf908"
},
"downloads": -1,
"filename": "policy_sentry-0.12.11-py3-none-any.whl",
"has_sig": false,
"md5_digest": "57189d27746e46d71cc4cfc93cf2b3c2",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 4328187,
"upload_time": "2024-04-06T13:40:27",
"upload_time_iso_8601": "2024-04-06T13:40:27.260096Z",
"url": "https://files.pythonhosted.org/packages/41/7a/4082579f442c6e153c4417292c2014e371df1bd31aae476794d208236c6d/policy_sentry-0.12.11-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "7e7a7fbb394f21a3c43edcb7d04382b6d93567900b4c8ea4b224b284656115ed",
"md5": "1d73393f60082f18fb665fe95b8b60f7",
"sha256": "8db1ea570e835d87c57ef51bf6f2372a8b78d463549a5f9c65cb5f8103cd1ed8"
},
"downloads": -1,
"filename": "policy_sentry-0.12.11.tar.gz",
"has_sig": false,
"md5_digest": "1d73393f60082f18fb665fe95b8b60f7",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 3690084,
"upload_time": "2024-04-06T13:40:30",
"upload_time_iso_8601": "2024-04-06T13:40:30.555406Z",
"url": "https://files.pythonhosted.org/packages/7e/7a/7fbb394f21a3c43edcb7d04382b6d93567900b4c8ea4b224b284656115ed/policy_sentry-0.12.11.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-06 13:40:30",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "salesforce",
"github_project": "policy_sentry",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "click",
"specs": [
[
"==",
"8.1.7"
]
]
},
{
"name": "beautifulsoup4",
"specs": [
[
"==",
"4.12.2"
]
]
},
{
"name": "requests",
"specs": [
[
"==",
"2.31.0"
]
]
},
{
"name": "PyYAML",
"specs": [
[
"==",
"6.0.1"
]
]
},
{
"name": "schema",
"specs": [
[
"==",
"0.7.5"
]
]
}
],
"lcname": "policy-sentry"
}
JSON
