01
The detection declares the context it cares about
Actor privilege, source reputation, target sensitivity, environment, outcome, whether the principal was MFA-backed — authored alongside the rule, along with the direction each pushes the severity.
Contextual severity · cloud eventsThe same API call, twice,
The same API call, twice,
is not the same event.
Detection rules carry one severity, so a role assumption by your deploy pipeline pages someone at the same volume as the identical call from an unknown IP at 3am. Cloudanix scores an event against the occurrence — who did it, from where, against what, in which environment — and the alert threshold respects the result.
- Per occurrence, not per rule
- Notification gate reads the same value
- UEBA verdict as an escalation factor
cloudanix · events · effective severity
detectionIAM Role Assumed From Unrecognized Sourcebase: High
sts:AssumeRole · 03:14 UTC
- unknown source IP↑
- admin-capable role↑
- production account—
- UEBA: off-baseline↑
effective severityCriticalHigh → Critical · escalated
sts:AssumeRole · CI runner
- known pipeline identity↓
- scoped deploy role↓
- dev account↓
- UEBA: on-baseline—
effective severityLowHigh → Low · routine automation
One rule, two occurrences, minutes apart. Only one of them is worth waking someone up for.
The problem
Alert fatigue is mostly a severity-modelling failure.
Teams do not tune out because detections are wrong. They tune out because a rule cannot distinguish its most alarming firing from its most routine one.
01
One severity per rule, thousands of firings
The rule severity has to cover both the pipeline doing its job and the attacker doing theirs. Whichever way the author leans, half the firings are mis-ranked.
02
Thresholds become useless
If "notify me on High and above" includes routine automation, people either widen the threshold until they miss real events, or mute the rule. Both outcomes are worse than no rule.
03
Late signals never get to matter
Behavioral verdicts often arrive after the event does. If severity was stamped once and never revisited, an anomaly confirmed a minute later cannot raise the alarm on the event that caused it.
How it works
How an event gets its severity.
The same model as the rest of the platform, with one difference that matters: the context read is the occurrence, not just the asset it touched.
02
The occurrence is scored
As the event lands, the factors resolve against that specific firing — this principal, this source, this target, this account — rather than against a rule-level average.
03
Behavioral verdicts fold in
A UEBA detector that flags the event as off-baseline is itself a factor, so an anomalous firing escalates rather than arriving as a second, separate alert. See Cloud UEBA.
04
The notification gate reads the same number
This is the part that matters operationally. The list, the aggregate charts, the severity filter and the notification threshold all resolve one effective severity — otherwise the inbox is quiet and the pager is not.
The factors
The context an event is weighed against.
These read the occurrence, not just the asset it touched — which is what lets one detection rule tell your pipeline apart from an intruder using the same API call.
Actor privilege
Is the principal admin-capable, or can it escalate? The same call from a scoped deploy role and from a break-glass identity are different events.
Source reputation
Whether the source IP appears on the threat-intel indexes the platform already maintains for threat intelligence correlation.
Target sensitivity
What the event touched — a scratch bucket, or a store holding regulated data. Read from the same asset graph the rest of the platform uses.
Environment
Production versus everything else. Already resolving for posture findings, and the same resolver serves events.
Behavioral verdict
Whether the platform's per-identity baseline considers this firing off-pattern. The marquee events factor, and the reason a second-pass stamp exists at all.
Outcome and MFA
Succeeded or denied, and whether the principal was MFA-backed. A denied attempt is not free of signal, but it is not the same as a successful one.
Why Cloudanix
What changes when detections score the occurrence.
A threshold you can actually set
"Page me on Critical" becomes a usable instruction, because Critical stops including your CI pipeline. That single change is worth more than another dozen detection rules.
Behavioral analysis stops being a side channel
A UEBA verdict that escalates the underlying event is more actionable than a separate anomaly alert that a responder has to correlate by hand at 3am.
Point-in-time, on purpose
An event is a historical record — it fired then, under those conditions. Its severity reflects the context at firing time rather than being quietly rewritten weeks later when the environment has moved on.
What Our Users Are Saying
Customer Reviews
Cloudanix is trusted by security leaders worldwide to deliver proactive, reliable, and cutting-edge cloud security.
One day, I changed the password of a root account, and my CTO called me within less than a minute to confirm if I did so. I was not expecting a reaction this quick. He told me Cloudanix alerted him of this password change and that he wanted to confirm as it was a critical security notification. I couldn't believe it!
Ritesh Agarwal
CEO, Airgap Networks
Compliance is one way of staying secure, but what I want is the ability to go deeper and attain 'true security.' Cloudanix provides us the capability to do so.
Vishal Madan
Head of Engineering, iMocha
Cloudanix is building for the future of the cloud, which makes the product all the more desirable.
Ritesh Agarwal
CEO, Airgap Networks
Cloudanix gave us the visibility we were missing. Being able to move from permanent access to a robust Just-In-Time (JIT) workflow has fundamentally changed our security posture without slowing down our engineering velocity.
Pavan Kumar Lekkala
SRE Lead, HugoHub
We are excited to leverage Cloudanix's comprehensive multi-cloud DevSecOps solution to secure our production workloads on AWS. Cloudanix has demonstrated that it can solve many challenges that DevSecOps teams face while continually adding new features such as SOC2 compliance and drift detection.
Satish Mohan
Co-founder & CTO, Airgap Networks
Managing third-party partner access was once a major concern for our security posture. With Cloudanix JIT Cloud, we've effectively achieved zero third-party risk. We can now grant access confidently, knowing that it is temporary, audited, and automatically revoked, resulting in a 100% reduction in our privileged access exposure.
Okesh Badhiye
Head of Technical Engineering, Finfinity
The snooze feature and responsible alerts have helped us save time and prioritize what to tackle first.
Satish Mohan
Co-founder & CTO, Airgap Networks
Implementing Cloudanix JIT internally allowed us to practice what we preach. By eliminating permanent access to our own clouds and databases, we've neutralized the risk of standing privileges, ensuring our own 'keys to the kingdom' are never left exposed.
Girish Manghnani
Managing Partner, Tech Inspira
The problem with permissions is a lot of times, the gaps are left open due to oversights from inside the organization itself. With Cloudanix's CIEM, we get a complete view of user permissions and access. This enables us to update the permissions, reducing the attack surface.
Nilesh Pethani
Application Architect, iMocha
In the world of Fintech, trust is our currency. Cloudanix provided the frictionless visibility we needed to secure our EKS workloads across AWS, ensuring we stay audit-ready for SOC2 and GDPR without slowing down our engineering velocity.
Amol Naik
Head of Security & Infrastructure, HugoHub
Cloudanix delivered value within 5 minutes of onboarding. Continuous monitoring, timely detection, and excellent documentation helped us attain a great cloud security posture.
Divyanshu Shukla
Senior DevSecOps, Meesho
Technology strategies and business strategies are in a state of constant change which includes centralization and decentralization of responsibilities. Regardless of strategic shift, we still have intellectual property to protect. Cloudanix are critical partners for us in our public cloud security posture across our three cloud providers.
Jerry Locke
Senior Director Global Solutions Engineering, Eversana
Cloudanix has been amazing. They opened up a common Slack channel with us — and it feels like we are talking to our own team and getting things done with Cloud security. The support team is always available, friendly, helpful, and ready to go out of their way.
Satish Mohan
CTO, Airgap Networks
Beyond just access management, Cloudanix CSPM has given us a unified view of our AWS environment. The real-time alerting and anomaly detection allow us to prevent any untoward activity before it happens, which is critical for a marketplace connecting 50+ financial institutions.
Okesh Badhiye
Head of Technical Engineering, Finfinity
For a Fintech company, data is our most valuable — and most sensitive — asset. Cloudanix DAM hasn't just improved our visibility; it has given us control. The ability to mask data and prevent unauthorized queries in real-time is a game-changer for our compliance and customer trust.
Jiten Gala
President Engineering and Product, Kapittx
Our clients, especially in the Middle East financial sector, demand absolute accountability. Cloudanix JIT Cloud has been a competitive differentiator for us, allowing us to provide secure, governed access to customer accounts that meet their strictest audit and compliance requirements.
Girish Manghnani
Managing Partner, Tech Inspira
Cloudanix is always on my team's lips because of its exceptional support. Be it a small or big query, Cloudanix has gone above and beyond to resolve them. This one's a keeper for us.
Sujit Karpe
CTO, iMocha
For a long-lasting partnership, great support goes a long way. Cloudanix has delivered exceptional support whenever required. Their edge is their team is always ready to go beyond to solve any issues that we have. This speaks volumes about the culture at Cloudanix.
Akash Maheshwari
Co-founder, MoveInSync
Beyond the technology, Cloudanix feels like an extension of our own team. Their willingness to stand up a dedicated Middle East tenant for us and provide exceptional support at a sensible price makes them a long-term partner for Hugosave.
Surya Tamada
CTO, HugoHub
The real-time notifications that Cloudanix provides are a real lifesaver. Their adaptive notifications ensure that my team stays productive and doesn't get interrupted all the time.
Digvijay Singh
Staff Security Engineer, Meesho
The whole point in technological evolution is to help improve the world we live in. We must protect that and to do so requires an effective and efficient security strategy. The Cloudanix team helped make our public cloud security posture management strategy a reality. The symbiotic relationship we have allows for a continuous feedback loop which is how business should operate.
Larry Wheat
Staff Solutions Engineer, Eversana
Common questions
Asked plainly.
What is contextual severity for cloud events?
It is detection severity decided per occurrence instead of per rule. The same detection is weighed against the actor, source, target, environment and behavioral verdict of that specific firing, so it can arrive Critical once and Low the next time — with the reasons attached either way. The full model is on the contextual severity overview.
How is this different from CDR noise filtering?
They stack. Noise filtering drops operational chatter before detection runs at all — events you never wanted. Contextual severity handles the events you do want, but which are not equally urgent every time they fire. Filtering decides whether to look; severity decides how loud.
Does the alert threshold respect the contextual value?
Yes, and this is the part most implementations get wrong. The notification gate resolves the same effective severity as the list view. If the two disagreed, the feature would be worse than useless — a quiet inbox and a noisy pager.
Why is event severity point-in-time rather than recomputed?
Because an event is an immutable record of something that happened. Posture findings describe current state and are re-evaluated every run; an event describes a moment, so its severity should describe the risk at that moment. Retroactive re-scoring of history is a deliberate non-goal.
Does this work with existing detection rules, or do I author new ones?
Existing ones. Contextual severity is a property of the rules you already run — you are not rebuilding a detection library to get it. Switching a rule's severity mode changes how its firings are ranked, not what it detects.
Ready to see your graph?
Connect a cloud account in under 30 minutes. See every finding rooted in identity, asset, and blast radius — with a fix path attached.
Book a Demo