Zalewski — The Tangled Web: A Guide to Securing Modern Web Applications
Main reference of the module (No Starch Press, 2011). Deep dive into browser security mechanisms and Web application vulnerabilities.
Master 2
Personal course page for the Web & Mobile Application Security module — Master 2 CS (Computer Security), University of Skikda. This page provides centralized access to lectures, labs, pedagogical resources, and module information.
Course progress
The Web & Mobile Application Security module, part of the Master 2 CS (Computer Security) program at the University of Skikda, is available on www.al-moualime.com. It covers Web and mobile application security: browser security model, OWASP Top 10, injection, XSS/CSRF, HTTPS/TLS, Content Security Policy, session & authentication security, XML/Web services security, and mobile application security. Semester 3, 4 credits, coefficient 3. Prerequisite: Network security and vulnerability analysis. Assessment: Continuous assessment and exam.
Main reference of the module (No Starch Press, 2011). Deep dive into browser security mechanisms and Web application vulnerabilities.
IEEE Access, 2016. Complementary reference for the mobile security chapter.
IEEE Access, 2018. Case study on mobile application data protection.
IEEE S&P, 2018. Complementary reference for the module.
Discovers open ports, running services and their versions on an authorized target; Zenmap is its graphical interface.
Queries domain registries: owner organization, registrar, creation and expiry dates, name servers (passive).
Resolve a name to its addresses (A, AAAA) and list its name servers (NS) and other DNS records.
Sends HTTP requests by hand and shows the response headers, e.g. to read a Web server banner.
Collects public addresses and subdomains associated with a domain from search engines and certificate logs (passive).
Built into Chrome, Firefox and Edge: observe blocked requests, CORS errors and HTTP headers exchanged between two origins.
The built-in http.server module serves two sites on two ports; a short Flask script adds the CORS header.
General introduction to the Web & Mobile Application Security module: objectives, the attacker/defender mindset, the e-commerce scenario running through the course, and organization of lectures/labs.
Hacker types, red/blue/purple teams; intrusion phases, zero-day flaws, malware, social engineering.
The browser as an operating system; permissions and secure contexts; the Same-Origin Policy and its limits; cross-origin communication with postMessage and CORS.
The mechanisms behind the chapters, from the local network to the browser (IP, ARP, NAT, BGP, TCP, UDP, DNS, HTTP, TLS, cookies, HTML, Same-Origin Policy): for each one, how it works, its design weakness, the attack and the defense, with exercises. After M. Zalewski, The Tangled Web.
⚠️ Responsibility & legal framework
The tools used in these labs (Nmap, theHarvester, curl…) are the same ones attackers use. Only use them on the targets named in each lab (for example scanme.nmap.org, made available by the Nmap authors for practice) or on your own machines. Scanning or testing a system without its owner’s written authorization may be illegal, in Algeria as elsewhere, even without malicious intent.
Each student is solely responsible for the use they make of these tools and techniques. Any use outside the authorized scope of the labs is their sole responsibility, both civil and criminal; the teacher and the University of Skikda accept no liability for any misuse or illegal use.
Mapping a target application’s attack surface and entry points.
Hands-on exploration of browser origin isolation and cross-origin resource sharing.