Update secrets #39
Open
Update secrets #39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![jit-ci[bot]](https://avatars.githubusercontent.com/in/142441?s=60&v=4){kind=small}
aws/secrets
Outdated
| @@ -1 +1,2 @@ | |||
| MY_AWS_SECRET = "AKIALALEMEL33EEXAMPLEE" | |||
| MY_AWS_SECRET = "AKIALALEMEL43EEXAMPLEE" | |||
Contributor
There was a problem hiding this comment.
Security control: Secret Detection
Type: Aws-Access-Token
Description: AWS
Severity: HIGH
Jit Bot commands and options (e.g., ignore issue)
You can trigger Jit actions by commenting on this PR review:
#jit_ignore_fpIgnore and mark this specific single instance of finding as “False Positive”#jit_ignore_acceptIgnore and mark this specific single instance of finding as “Accept Risk”#jit_undo_ignoreUndo ignore command
ghost
reviewed
May 10, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
 Failed |
Secrets | 1 0 0 0 |
| @@ -1 +1,2 @@ | |||
| MY_AWS_SECRET = "AKIALALEMEL33EEXAMPLEE" | |||
| MY_AWS_SECRET = "AKIALALEMEL43EEXAMPLE" | |||
Contributor
There was a problem hiding this comment.
Security control: Secret Detection
Type: Aws-Access-Token
Description: AWS
Severity: HIGH
Jit Bot commands and options (e.g., ignore issue)
You can trigger Jit actions by commenting on this PR review:
#jit_ignore_fpIgnore and mark this specific single instance of finding as “False Positive”#jit_ignore_acceptIgnore and mark this specific single instance of finding as “Accept Risk”#jit_undo_ignoreUndo ignore command
ghost
reviewed
May 10, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 10, 2023
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 10, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 11, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 11, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Passed |
Vulnerabilities | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 11, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
ghost
reviewed
May 15, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Vulnerabilities | 0 0 0 0 |
ghost
reviewed
May 15, 2023
ghost
left a comment
ghost
left a comment
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority |
|---|---|---|
| Passed |
Infrastructure as Code | 0 0 0 0 |
| Failed |
Secrets | 1 0 0 0 |
adviri
reviewed
May 16, 2023
| @@ -1 +1,4 @@ | |||
| MY_AWS_SECRET = "AKIALALEMEL33EEXAMPLEE" | |||
adviri
requested review from
a user and
adviri
and removed request for
a user and
adviri
| @@ -1 +1,6 @@ | |||
| MY_AWS_SECRET = "AKIALALEMEL33EEXAMPLEE" | |||
| MY_AWS_SECRET = "AKIALALEMEL43EEXAMPLE" | |||
| MY_AWS_SECRET_2 = "AKIALALEMEL53EEXAMPLE" | |||
Contributor
There was a problem hiding this comment.
Security control: Secret Detection
Type: Aws-Access-Token
Description: AWS
Severity: HIGH
Jit Bot commands and options (e.g., ignore issue)
You can trigger Jit actions by commenting on this PR review:
#jit_ignore_fpIgnore and mark this specific single instance of finding as “False Positive”#jit_ignore_acceptIgnore and mark this specific single instance of finding as “Accept Risk”#jit_undo_ignoreUndo ignore command
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.