Course · Free with an account
Security internship prep
Get ready for an application or web security internship: Linux, HTTP, authentication, the OWASP Top 10, XSS, API security, secure coding, vulnerability assessment and writing a clear security report. Every chapter ends with scenario questions and the interview questions you are likely to be asked.
Open the courseChapters, a study plan and timed practice exams.Chapters
1. What a security intern does and how to prepare 20 min
The kinds of security internships, what a normal day looks like, the core tools, and the legal and ethical rules you must follow from day one.
- Describe the main security internship tracks (application security, penetration testing, security operations, governance) and what each one does day to day.
- Name the core tools of a web security tester (Burp Suite, ZAP, nmap, browser devtools, curl) and what each is used for.
- Explain the rules of engagement: written permission, scope, data handling and confidentiality.
- Set up a safe local practice lab that is not reachable from the network.
2. Linux commands and OS fundamentals 40 min
The Linux you need as a security intern: the filesystem, users and permissions, processes, networking commands, logs, packages and shell pipes.
- Read an ls -l line and set permissions correctly with chmod, chown and umask.
- Explain setuid, the sticky bit and sudo, and why each matters for security.
- Find and stop processes and see which program is listening on which port.
- Search logs for suspicious activity with journalctl, grep and a pipeline.
- Keep a system patched with the distribution's package manager.
3. HTTP, HTTPS and web application architecture 40 min
How a browser talks to a web app: requests and responses, methods, status codes, headers, cookies and sessions, TLS, DNS, proxies and CDNs, REST APIs and the three-tier architecture.
- Walk through everything that happens between typing a URL and seeing the page.
- Read a raw HTTP request and response and explain each part.
- Choose the right method and status code, including 401 versus 403.
- Explain how cookies create sessions over a stateless protocol and which cookie flags matter.
- Explain what TLS does and does not protect, and the security role of proxies, CDNs and each tier.
4. Authentication, authorisation and access control 45 min
Proving who a user is and deciding what they may do: password storage, MFA, sessions versus JWTs, OAuth 2.0 and OpenID Connect, RBAC and ABAC, least privilege, and 401 versus 403.
- Explain the difference between authentication and authorisation, with the matching status codes.
- Store passwords safely with a slow, salted hash such as Argon2id or bcrypt, and say why fast hashes fail.
- Compare server-side sessions with JWTs and list the checks every JWT must pass.
- Describe the OAuth 2.0 authorisation code flow with PKCE and what OpenID Connect adds.
- Design access control with least privilege, deny by default and object-level checks.
5. Common web security risks and the OWASP Top 10 45 min
The OWASP Top 10 2021 categories, each with a realistic example and the fix, plus how the list changed in the 2025 edition.
- Name all ten OWASP Top 10 2021 categories in order and give an example of each.
- Classify a described vulnerability into the right category.
- Give the standard fix for injection, broken access control, misconfiguration and SSRF.
- Explain what changed in the OWASP Top 10 2025 and why the Top 10 is an awareness list, not a full standard.
6. Cross-site scripting (XSS) 40 min
How attacker-controlled script ends up running in a victim's browser, the three types of XSS, what it can do, and the layered defences: output encoding, sanitisation, CSP and cookie flags.
- Explain reflected, stored and DOM-based XSS and identify each from a description.
- Describe what an attacker can do with XSS beyond stealing cookies.
- Apply context-aware output encoding and know where frameworks stop protecting you.
- Use an allow-list HTML sanitiser, a strict CSP and cookie flags as additional layers.
- Tell XSS and CSRF apart.
7. API security 40 min
Why APIs fail differently from web pages: the OWASP API Security Top 10 2023, BOLA and IDOR, broken authentication, excessive data exposure and mass assignment, rate limiting, input validation and CORS.
- Name the OWASP API Security Top 10 2023 categories and match a scenario to each.
- Find and fix BOLA (IDOR) with an ownership check, and explain why random IDs are not a fix.
- Prevent excessive data exposure and mass assignment with response and request DTOs.
- Protect an API with rate limits, size limits and schema validation.
- Explain what CORS does, what it does not do, and how it is commonly misconfigured.
8. Secure coding practices 45 min
The habits that prevent most vulnerabilities: input validation, parameterised queries, secrets management, dependency scanning, safe error handling and logging, security headers, and a security code review checklist, with ASP.NET Core examples.
- Validate input on the server with an allow-list approach, and explain why it is not enough on its own.
- Write parameterised queries with ADO.NET and EF Core and handle values that cannot be parameterised.
- Keep secrets out of source code and respond correctly when a secret leaks.
- Scan dependencies, handle errors without leaking details, and log security events safely.
- Add the main security headers and review a pull request with a security checklist.
9. Vulnerability assessment 40 min
How an authorised assessment runs from scoping to retest: reconnaissance, automated scanning versus manual testing, verifying findings and false positives, rating severity with CVSS v3.1 and v4.0, and responsible disclosure.
- Explain the difference between a vulnerability assessment, a penetration test and a bug bounty.
- Plan an assessment: scope, rules of engagement, recon and test coverage.
- Combine scanners with manual testing and verify findings to remove false positives.
- Score a finding with CVSS v3.1, read a vector string, and name what changed in CVSS v4.0.
- Describe responsible (coordinated) disclosure.
10. Security documentation and remediation recommendations 45 min
How to write findings developers can fix and managers can act on: report structure, the anatomy of a finding, executive summary versus technical detail, clear remediation advice, retesting, and a complete sample finding.
- Structure a security report for its different readers.
- Write a finding with every essential field: title, severity, asset, description, steps to reproduce, impact, evidence, remediation and references.
- Write an executive summary in plain business language.
- Turn a vague recommendation into a specific, verifiable fix.
- Run a retest and record the outcome.