Detection Oriented Security Architecture, with Kevin Fiscus
Detection Oriented Security Architecture
Risk can be defined as the likelihood that a threat exploits and vulnerability causing harm. To reduce risk, at least one factor in that definition must be reduced. There is little that can be done, in most cases, to reduce the threat leaving us with vulnerabilities and harm.
Security programs and security professionals have spend decades attempting to substantially reduce risk associated with vulnerabilities without significant success. As a result, we are left with attempting to reduce harm.
According the recent Ponemon Institute Cost of a Data Breach studies, one of the biggest factors in determining breach cost is dwell time: the amount of time an attacker is present in the network before detection, therefore reducing dwell time can significantly reduce breach cost and thus reduce overall risk.
The obvious goals therefore becomes to detect and respond to attacks as quickly as possible. This goal has resulted in myriad technologies that focus on "detection and response" such as EDR, ITDR, NDR, XDR, and SOAR. Unfortunately, if we achieved the goal of rapid detection and immediate response, we would actually be making our security worse and giving the attacker a significant advantage.
In this webinar we will discuss why automated detection and response is a concept that will always fail and we will discuss what a truly detection oriented security architecture would look like.
#detectionEngineering #infosec #blueteam
More Articles
100% is Easy, 99% is Hard
Success is far more likely when you are fully committed!
It doesn’t matter if it is about passing a certification, running, writing a book, or anything else.
Here is quick video of me after a have just completed running 20+ miles a week for 140 weeks in a row. Why? Because my health matters.
When something matters, whether it is professional, personal, or something else, 100%, being committed, makes a difference!
If you are doing 99% percent it is easy to slip to 98%, 97%, 80%, and much much lower!
Constant effect, even though progress may not always seem 100% upwards, is easy with some commitment.
Not trivial, but much easier than 99%!
The Hardest Part of Starting Consulting
What is the hardest part of starting consulting?
Getting Clients? Nope although that is obviously important.
(more here on getting clients: https://successfulinfosecconsulting.com/).
What is the second hardest thing? And what can do you do about these things?
The hardest part – is YOU.
I know I flip flopped back and forth when I decided, between “I’m going to start consulting” and “Who am I to do this?” Feelings of “I’m too young” or “I’m too old” and more are common. Some of this is imposter syndrome which is normal. What do you do about this?
Are Entrepreneurs Risk Takers?
Are Entrepreneurs risk takers? The answer may surprise you!The answer, no surprise, is “It Depends.”
A great many entrepreneurs are rick adverse, and know exactly how much risk their ventures entail – and everything has risk, including having corporate job and going to the supermarket.
Some entrepreneurs are willing to accept a large amount of risk, and although there are exceptions, generally know that they are.
Is Consulting More Risky than having a “Job” ?
Is consulting risky – specifically is it more risky than having a full time job?
The conventional wisdom says “yes” – and is absolutely wrong! Maybe it was “once upon a time but it isn’t now.”
If you have a job and lose it, you are unemployed – it’s binary: “job” or “no job.” And unfortunately people lose their jobs, especially during difficult times.
Consultants typically have multiple clients. If you lose a client, you still have others. Typical consultants have 3-6 clients per year. If one client doesn’t have any work for you, perhaps they “fire” you, go out of business, or are having a difficult time, you still have work from other clients.