Now that we are on a subject of testing security and breach/attack simulation tools, one more interesting questions arises: if you test security, what constitute a “pass”? Or, alternatively, at what level do you test?
Think back the infamous bear analogy. In security, it is NOT a certainty that it is enough to outrun the slowest competitor [who the bear can then eat…chomp-chomp], you may actually have to outrun the bear [a Russian APT joke is here somewhere I am sure].
So, there are good arguments that you need to test at the level of your likely adversary. But how do you know that? Even if your threat assessment is not shitty, this is likely achievable by a tiny minority only… people who basically know what “threat assessment” (some actually call it “threat modelling” despite the appsec connotations) even means…
Here is what I am thinking:
|Conceptual test level||Pros||Cons|
|Test at maximum possible level||You can test whether your security posture will withstand the best of the best||Gap may be so huge, that no clear action plan is evident|
|Test at the level of your current security||Can test the freshly deployed controls; can actually ace the test||Not immediately motivating for improvements|
|Test at the level of your current security PLUS 10%||Easy to figure what to improve||How do you actually define and measure it?|
|Test at the level of your past adversary||Has solid data, that can be turned into test methods||Not a good prediction of the future|
|Test at the level of your likely adversary||Philosophically, this is the best scenario!||Hard to gather solid data on this, and figure it out|
Now, hilarity ensues if “level of your likely adversary” is MUCH higher than “level of your current security”
Blog posts related to this project:
- On Negative Pressure or Why NOT Objectively Test Security?
- The Bane of All Security Tests: Acting on Results
- Threat Simulation – How real does it have to be? (by Augusto)
- New Research: How to Actually Test Security?
- Threat Simulation Call to Action for 2018
This is a Security Bloggers Network syndicated blog post authored by Anton Chuvakin. Read the original post at: Anton Chuvakin