Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Multiple Account support for AWS Security Hub #1654

Closed
1 of 6 tasks
saurabh2253 opened this issue Oct 11, 2023 · 0 comments · Fixed by #1655
Closed
1 of 6 tasks

Multiple Account support for AWS Security Hub #1654

saurabh2253 opened this issue Oct 11, 2023 · 0 comments · Fixed by #1655
Assignees
@saurabh2253
Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned

Comments

@saurabh2253
Copy link
Contributor

Additional context
User should be able to send notification to security hub of multiple accounts using single credentials.
The account for which credentials input are done would be allow listed in other accounts to report security hub findings.

Describe the solution you'd like
Read the cloud account id from scanned nodes and patch the findings with individual account id.

Components/Services

  • UI/Frontend
  • API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)
@saurabh2253 saurabh2253 added enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned labels Oct 11, 2023
@saurabh2253 saurabh2253 self-assigned this Oct 11, 2023
saurabh2253 added a commit that referenced this issue Oct 11, 2023
@saurabh2253
#1654 https://github.com/deepfence/enterprise-roadmap/issues/1929 rep…
373e9a6 
…ort to security hub with correct accId
@saurabh2253 saurabh2253 mentioned this issue Oct 11, 2023
Merged
saurabh2253 added a commit that referenced this issue Oct 13, 2023
@saurabh2253
#1654 Report to security hub with correct accId (#1655)
cce58b0 
* #1654 https://github.com/deepfence/enterprise-roadmap/issues/1929 report to security hub with correct accId

* Changes for report and scanID fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saurabh2253 saurabh2253

Labels
enhancement New feature or request needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#1654 Report to security hub with correct accId deepfence/ThreatMapper
1 participant
@saurabh2253