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.

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

Cloud Posture Interface filter uses the incorrect benchmark type for SOC2 #2148

Open
1 of 6 tasks
tektite-io opened this issue May 14, 2024 · 0 comments
Open
1 of 6 tasks
Assignees
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned

Comments

@tektite-io
Copy link

Describe the bug
The cloud posture result interface allows filtering by benchmark type; however in the filter the value is SOC2 while in the scan result is SOC_2 , and therefore applying such filter will show no results.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Posture
  2. Click on AWS
  3. Click on one Account (assuming that there is a SOC2 scan result)
  4. Select filter and pick SOC2
  5. No results are diplayed

Expected behavior
Selecting SOC2 should filter by SOC2 benchmark type and show the correct results

Components/Services affected

  • UI/Frontend
  • API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)

Additional context
A quick fix would be to replace the SOC2 with SOC_2 in ComplianceScanConfigureForm.tsx

  aws: ['CIS', 'NIST', 'PCI', 'HIPAA', 'SOC_2', 'GDPR'],
  aws_org: ['CIS', 'NIST', 'PCI', 'HIPAA', 'SOC_2', 'GDPR'],
@tektite-io tektite-io added bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned
Projects
None yet
Development

No branches or pull requests

2 participants