3

I know this is kind of an odd question. An IDS/IPS basically autonomously recognizes and optionally prevents intrusions.

And while SELinux and AppArmor seem to be trying to do the same, they are never labelled as IDS/IPS. Am I missing something? This is a purely academic question.

Would such tool be considered Host Based IDS/IPS?

0

1 Answer 1

1
+100

Yes, LSM tools could be considered Kernel-based HIDS/HIPS.

Note that IDS (intrusion detection) and IPS (intrusion prevention) are not the same thing. Intrusion detection is typically more like a traditional virus scanner, it's going to scan for known bad patterns and alert you, but typically doesn't have the ability to prevent applications from taking certain actions.

AppArmor and SELinux proactively protect the OS and monitored applications from threats by enforcing good behavior and preventing some unknown attacks. These can both be considered a form of host based Intrusion Prevention, though you'll need to configure properly.

AppArmor security policies completely define what system resources individual applications can access and with what privileges.

If you're running a system with AppArmor, you can look /etc/apparmor.d/ for a list of the default profiles... You'll notice that most apps you have aren't actually covered.

An IDS/IPS basically autonomously recognizes and optionally prevents intrusions.

Both SELinux and AppArmor are more closely related to the idea of "sandboxing" than to the idea of "scanning for an intrusion". Your not going to get alerts that pop up saying:

Potentially bad dude is doing potentially dangerous thing

[_] Allow [_] Deny

Rather, when actually running these systems in enforcing mode, apps will silently not be permitted permission to do many things. You'll want to check out the logs to see exactly what is denied. Typically before turning these on (or up) you'll want to run in "complaining mode" (AppArmor) or "permissive mode" (SELinux) to allow them to run with your configured permissions settings, but only to log about denied access rather than outright denying access. Otherwise you're likely to cause your system to hang.

4
  • So from what I can gather. "Yes.......but no.". We're mostly relying on stretching definitions, which are kind of loose to begin with? Most definitions of IPS do tend to be, that it's an expansion of an IDS, but with functionality that lets you prevent the detected intrusion. Commented Jul 9, 2020 at 8:56
  • Correct. AppArmor and SELinux technically meet the definition of HIPS, but this is not how they are commonly understood, marketed and promoted. You mentioned you're looking at it from an academic perspective, so if you want a reference in print, here is "AppArmor" being discussed as a hosted based IPS: books.google.com.vn/… Commented Jul 9, 2020 at 9:17
  • Thanks. I will mention them as my thesis, but to be safe, won't focus on them much, even though I find them extremely interesting. Commented Jul 9, 2020 at 9:41
  • SELinux and AppArmor can form an important part of intrusion prevention mainly because they fight privilege escalation (in a broad sense): A process constrained by these cannot to what it shouldn't do if configured properly. Commented Jul 14, 2020 at 21:47

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.