Steps Towards Achieving a Secure Linux Server
summary
An Ubuntu web server with a deliberate code‑injection flaw allows arbitrary shell commands, letting the attacker overwrite index.html with "you've been hacked" and send 100 spam messages to demo@oss-demo.com. Hardening steps shown include file‑permission fixes, AppArmor profiles (56 profiles loaded, enforce mode) that block writes outside the web path, and isolating services in a Docker container network so the web process can no longer reach the mail files.
AI-written summary · about
chapters (11)
- 0:00Linux server security intro
- 4:39Attack surface and defense
- 6:46Access control and least privilege
- 8:55File permissions and DAC
- 11:47Mandatory access control with AppArmor
- 18:21Isolation with containers and VMs
- 22:41Firewalls and network filtering
- 25:29System maintenance
- 26:33Social engineering risks
- 28:19Security practices summary
- 29:03Q&A
related talks
41mLive Hacking: Breaking into Your Web App
47mLive Hacking: Breaking into Your Web App
45mUsing Linux Securely in the Cloud
40mSecuring Containers by Breaking in
39mHow to think like a hacker
40mLive hacking: Breaking into your web app
26mJourney to Command Injection: Hacking the Lenovo ix4-300d
26mStranger Danger: Your Attack Surface Just Got Bigger