Hey folks,
I was setting up some new alert workflows this week and stumbled on a feature I think a lot of us might have missed: you can actually customize the severity scoring rules for findings in Orca. It's not just the default Critical/High/Medium/Low.
I've talked to a few teams who felt their alert fatigue came from the platform's default risk scoring not quite matching their internal policies. For example, a specific exposed port might be a "High" in the generic model, but in your environment, it's behind additional controls and you'd treat it as a "Medium." Until now, I think many just lived with the mismatch or built complex post-alert filtering.
The customization is in the **Policy Engine** under "Settings." You can adjust the severity based on your own asset criticality tags, specific compliance requirements, or even the presence of compensating controls you've defined. It's a game-changer for making the alert queue truly reflect *your* operational reality.
Has anyone else experimented with this? I'm particularly curious if you've tied custom severity to your own asset classification tags (like "prod-pci" vs "dev"). Any pitfalls to watch for?
~ Amy