Skip to content

Commit

Permalink
Merge pull request #104 from equinor/postman-guidelines
Browse files Browse the repository at this point in the history
Postman guidelines
  • Loading branch information
sean-sinclair authored Oct 13, 2023
2 parents 9250cdc + 30b0245 commit 2b3912d
Show file tree
Hide file tree
Showing 2 changed files with 26 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/guidelines/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,4 +8,5 @@ title: Appsec guidelines
This section contains guidelines relevant anyone writing code in Equinor.

- [Snyk](/snyk)
- [Scanning for Secrets in code](secret-scanning)
- [Scanning for Secrets in code](secret-scanning)
- [Postman](postman)
24 changes: 24 additions & 0 deletions docs/guidelines/postman.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Guidelines on using Postman

## Lightweight API Client

- This is the default client before the user is logged in to Postman services.
- The lightweight API client only stores client save data locally.
- Our recommendation is to use the lightweight client unless you need features from the logged-in client.

## Logged-in client

Logging in with a user account enables most of the features within Postman, this however comes with some security caveats.

- When using workspaces, collections and environments you potentially expose data.

**Best practices**:

- Avoid storing sensitive data anywhere except in environments.
- Storing variable values **only** in the `Current value` field, will ensure that the data is never shared with Postman.
- You should also use environment variables with a secret type to store sensitive data and credentials, including API keys and access tokens.

### Resources to read more on Postman

- [Postman Security & Trust Portal](https://security.postman.com/)
- [Security | Postman Trust Center](https://www.postman.com/trust/security/)

0 comments on commit 2b3912d

Please sign in to comment.