Application Security and DevSecOps Internship
This application security internship teaches you to catch problems before code ships: review code, scan dependencies and put security checks into the CI pipeline that every pull request passes through.
sast = scan(code)
deps = audit(packages)
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
- SAST
- DAST
- OWASP ZAP
- GitHub Actions
- Secure code review
- Dependency scanning
Fixing it before release costs far less than fixing it after
Most security issues start as ordinary code. Application security is about catching them in review and in the pipeline, before customers ever see them. That is what the twelve weeks train.
- 1You get a real codebase and its CI pipeline
- 2You review code against secure coding practice
- 3Your mentor challenges every finding and every fix
- 4You add automated checks so the issue cannot return
You should already write code in at least one language. Secure coding basics are covered in weeks 1 to 3.
# Week 8: security checks on every pull request name: security on: [pull_request] jobs: checks: steps: - name: Static analysis (SAST) - name: Dependency audit - name: OWASP ZAP baseline (DAST) # fail the build on high severity
What you will be able to do after this application security internship
Secure code review
Spotting risky patterns in a pull request and explaining the fix.
OWASP Top 10
Knowing the common web weaknesses and how code prevents them.
SAST
Running static analysis and triaging what it reports.
DAST
Scanning a running app with OWASP ZAP in a test environment.
Dependency scanning
Finding outdated or risky packages and upgrading safely.
CI/CD security
Adding security gates to GitHub Actions.
Secrets handling
Keeping keys and passwords out of code and logs.
Clear write-ups
Explaining risk and fix so a developer agrees and acts.
The 12-week application security internship plan
Four phases. Each one ends in a deliverable that is reviewed and graded before the next opens.
Foundations
How web apps fail.
- How web applications handle requests and data
- OWASP Top 10 in plain language
- Secure coding basics
- Git and pull request workflow
A secure code review checklist applied to a sample pull request.
Code and dependencies
Find it in the code.
- Manual secure code review
- Static analysis (SAST) and triage
- Dependency scanning and safe upgrades
- Secrets detection
A code review report with triaged findings and proposed fixes.
Pipeline security
Make it automatic.
- CI/CD basics with GitHub Actions
- Adding SAST and dependency checks to CI
- DAST with OWASP ZAP in a test environment
- Setting sensible failure thresholds
A CI pipeline that runs security checks on every pull request.
Ship it
From findings to habits.
- Fixing and verifying findings
- Writing a security guide for the team
- Measuring what the checks catch
- Portfolio case study, CV rewrite, mock interview
A secured pipeline, a fixed codebase and a short security guide for developers.
Every intern leaves a pipeline that blocks insecure code
You take a real codebase, review it, fix what matters and add automated checks so the same problems are caught on every future pull request.
- A secure code review with triaged findings
- Automated SAST, dependency and DAST checks in CI
- A short security guide the team can follow







What the application security internship includes
Three things that make this different from a course you watch on a screen.
Live client briefs
You work on real Ezitech projects with real deadlines and real revision rounds, not recycled practice exercises.
A mentor, not a playlist
Weekly reviews with someone who does this work for a living, plus a team of interns around you to build with.
Portfolio and experience letter
You finish with shipped work you are allowed to show and a letter that says exactly what you delivered.
Verified certificate
Issued by Ezitech Institute and verifiable by employers.
Experience letter
On company letterhead, stating exactly what you delivered.
A secured pipeline
CI security checks on a real codebase, with the fixes you made.
Interview preparation
CV rewrite, portfolio case study and a technical mock interview.
A route into the team
Top performers are considered first for paid junior roles.
Confidence in review
Twelve weeks of defending your own work to a senior practitioner.
Built for you if
- You are an undergraduate or fresh graduate in CS, SE, IT or cyber security
- You already write code in at least one language
- You want to make software safer, not just break it
- You need a substantial final-year project
Not a fit if
- You want a certificate without doing the work
- You cannot give 25 hours a week for 12 weeks
- You do not want to read or write code
- You want to skip review and work alone
Application security internship: questions people ask
Everything applicants email us about, answered before you apply.
What is the difference between application security and penetration testing?
Do I need to know how to code?
Is it remote or onsite?
Is there a fee?
Can final-year students apply?
How do I apply?
Not sure Application Security is the one?
Every cyber security internship runs three months, hybrid, with the same mentor model. Or take the six-month All-in-One Cyber Security flagship. Still choosing a field? Read which cyber security roles hire in Pakistan, or browse cyber security FYP ideas.
Penetration Testing
Test authorised lab targets and write findings developers can fix.
View trackCloud Security
Lock down cloud accounts, permissions and logging.
View trackSOC Analyst
Triage alerts in a SIEM and write reports a team acts on.
View trackGRC
Map controls to ISO 27001 and run a risk assessment.
View trackLearn to stop insecure code before it ships
Three months, one shipped piece of real work, a mentor who reviews you every week. Registration takes five minutes.
Ezitech Institute · Rawalpindi, Pakistan · info@ezitech.org · +92 345 5555396