In a previous lesson we talked about security contexts and how they are broken up into four different
coal on separated fields.
In this movie we're going to focus on the third field the type.
This type is used by the targeted policy to make it's access control decisions.
Because of this we often say that the targeted policy implements a technology called type enforcement.
The way this works objects with the same security requirements get grouped into the same type then objects
of the same type are allowed to access and interact with each other.
For example if you've ever been to a football game you may have noticed that football fans often get
separated in the stadium by security personnel.
This is normally done to mitigate conflicts and hooliganism.
The same principle applies with security enhanced Linux use in type enforcement processes and configuration
files that are in the same domain can all interact with each other without interference from objects
in other domains.
This way if objects get compromised they can only damage themselves and not the entire system.
If you take a look here you can see we've got a number of files and processes sharing for some type
in the context of processes.
We often refer to type as domain.