![Enterprise Cloud Security and Governance](https://wfqqreader-1252317822.image.myqcloud.com/cover/344/36700344/b_36700344.jpg)
Application control
Application control is yet another good feature that can be used in the production environment. Application control basically allows only certain trusted software/scripts to be run on the servers and rest all other software and scripts will be blocked, even if you are running it as a root user.
Let's look at one of the good parts of this approach. Assume that you have whitelisted a script named test.sh, which has the following contents:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_33.jpg?sign=1739335791-dYSiNVu90jZsErVhrCSUFk8xXOWtdeDr-0-3e36056c82fd32b10882a05e5fa45653)
We have whitelisted this specific script and user. With the appropriate permission, we will be able to execute the script:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_303.jpg?sign=1739335791-BVGR59yRzZ0o8C5iiIP943oGQ2ryBYMc-0-37ff67bf1e474e8a1ae7a14ddd826465)
If the script is modified (which is typical in case of web-based attacks to include custom vector) as a part of application control, even though the script is allowed but modified, then the application control feature will block the executing of the script even when it runs as a part of the root user.
In order to demonstrate the preceding point, I have added a small dot on the second line:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_288.jpg?sign=1739335791-Kuno3zx39pUIjLXWwPptMDEwZJgL6PxP-0-4b7400e949be5577497f1e0971b02879)
Now, since the contents of the file are modified, which can be considered as a malicious action (without proper whitelisting ), if we try and run the script, the action will be blocked:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_31.jpg?sign=1739335791-gVJJGGp6TUdYn8bylFyhyjpal36akMmM-0-413c193aec18fd76453bfcec0ce2fa89)
Similarly, when we try to start some software that is not whitelisted, we will not be allowed to do it, even though we are trying it with the root user:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_51.jpg?sign=1739335791-qtZn1f6xLdu02RVKwPnW4mCTfMm4yD9c-0-9dca353289c0ba946ac0acd8321680ad)
All the actions that have been blocked are logged and will be visible in the central Deep Security manager dashboard. This dashboard will also help us understand if there are some scripts that tried to execute it but got blocked and the security engineer will be alerted:
![](https://epubservercos.yuewen.com/F6ABA3/19470399208914606/epubprivate/OEBPS/Images/Chapter_7.jpg?sign=1739335791-VeVDyfMTMBqwPhFy8Mpulzn1HeXLWRmZ-0-1a340a9014e31b18411f4614f7aa6c09)
This concludes the section on application control, and we can now move on to yet another more important module called IPS functionality.