Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

Config Validator Severity not showing in CSCC or violations.csv #3522

Open
4 tasks
pdutch opened this issue Dec 10, 2019 · 7 comments
Open
4 tasks

Config Validator Severity not showing in CSCC or violations.csv #3522

pdutch opened this issue Dec 10, 2019 · 7 comments

Comments

@pdutch
Copy link

pdutch commented Dec 10, 2019

  • Which version of Forseti Security you're using (look in /home/ubuntu/forseti-security/google/cloud/forseti/init.py
    on the client).
    v.2.23

  • Which module(s) (inventory, scanner, enforcer, explain) you're having trouble with.
    Config Validator

  • Include errors, log output, and host operating system, including installed packages.
    No Errors specifically

  • Note how you deployed (via Deployment Manager, Terraform, local system, etc.).
    Terraform

A severity is set in the constraint templates, however this value is not output in the violation finding in either of the CSCC or the violations.csv. Is this an error or a feature request?

@auto-comment
Copy link

auto-comment bot commented Dec 10, 2019

Thank you for opening an issue. Our team's interrupts engineer will review your issue shortly.

Issue Resolution:

  • [Interrupts Engineer] Triage / apply categorization labels
  • [Interrupts Engineer] Verify / Reproduce the reported issue
  • [Forseti Engineer] Perform root cause analysis
  • Forseti Engineer] Add tasks and next steps to resolve this issue.

@stale
Copy link

stale bot commented Mar 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale items closed by Stale Bot label Mar 4, 2020
@pdutch
Copy link
Author

pdutch commented Mar 5, 2020

This is still an issue, please keep it open.

@stale
Copy link

stale bot commented May 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.

@pdutch
Copy link
Author

pdutch commented Oct 8, 2020

thanks @gkowalski-google for keeping this one alive!

@krab-skunk
Copy link

@gkowalski-google Any news regarding this feature? Is it planned ? I tried from master branch (pulled 2 days ago) and rules via config validator still doesn't show the Severity :(
Thanks :)

@nkaravias
Copy link

nkaravias commented Dec 22, 2020

Likewise, I encountered this also. Without severity recorded on SCC it becomes challenging to handle the findings in an automated way, especially when you have SCC findings collected from multiple sources, where the value is properly propagated.

image

rich-boyce added a commit to Prowler-io/terraform-google-forseti that referenced this issue Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants