News for hackers. Stuff that matters.
Re:“Yes, you should test on production” – Why developer expe... by HL33tibCe7 on Monday August 14, 2023 @07:53AM (#37119975)
Risk = likelihood * severity
Re:“Yes, you should test on production” – Why developer expe... by contravariant on Monday August 14, 2023 @08:26AM (#37120236)
That's also an approach, but it may lead to endless discussions about how likely something is. It's easier to tell what the worst possible consequence is (what this article calls criticality). After that it's fairly straightforward to figure out if you're doing enough to prevent this scenario from being realized (which is more like coverage = risk * mitigations).
Re:“Yes, you should test on production” – Why developer expe... by hef19898 on Monday August 14, 2023 @08:06AM (#37120078)
Sometimes one has to include detectability as well.
Re:“Yes, you should test on production” – Why developer expe... by datadrivenangel on Monday August 14, 2023 @08:24AM (#37120224)
Severity should include detectability. If you never detect an issue, it's not an issue because nobody sees it.
Re:“Yes, you should test on production” – Why developer expe... by hef19898 on Monday August 14, 2023 @09:52AM (#37121030)
Usually it is a seperate factor, at least as far as P/D-MEAs are concerned. Quick and dirty, sure, it can be included in severity. Personally, I prefer the increased transparency and granularity of having detectability as a different factor.
Re:“Yes, you should test on production” – Why developer expe... by HL33tibCe7 on Monday August 14, 2023 @11:08AM (#37121906)
To me, that’s a subcomponent of severity