The cohort runs 12 weeks and 144 hours, hybrid, online or at the Madhapur desk. You start with the computer, the network, and the host, then test a web app and an API in a guided lab. The later weeks cover cloud and enterprise security, and the close is a supervised assessment with a report the team can read.
Read the network
Weeks 1–3 start with architecture, operating systems, and the path from DNS to the firewall. You work with virtual machines, TCP/IP, DNS, and routing. The lab is ready when you can point at the traffic and say what it is doing.
Lock the host
Those same weeks cover Linux and Windows accounts, services, and the permissions a host should keep. You write a small Python script that repeats a check you would otherwise do by hand, and you keep the evidence. The host work ends with the account, the service, and the permission you changed.
Test the application
Weeks 4–6 are threats, controls, and the web stack the test depends on: the request, the session, and how the app is built. You find a flaw in a guided lab and write what the owner should change. Weeks 7–8 add API labs, packet analysis, and the alerts a security desk actually opens.
Own the report
Weeks 9–10 are cloud configuration and an access review you can demonstrate. Weeks 11–12 are the report, the portfolio, and a supervised assessment in a controlled environment. You leave the scope, the risks, the mitigations, and a presentation the team can repeat.
Skills you practice
Networking
Linux
Windows
Python
Web defence
API security
Cloud
Reporting
Networking
Linux
Windows
Python
Web defence
API security
Cloud
Reporting
Roadmap
Twelve weeks, in the order a review meets them.
Hybrid · online or at the desk · foundations through the capstone report.
Weeks 1–3
Foundations. The computer, the network, the host, and Python for the lab.
Computers and networking
Architecture, operating systems, and the path from DNS to the firewall.
Virtual machines
TCP/IP, DNS, and routing
Linux and Windows
Accounts, services, and the permissions a host should keep.
Linux administration
Windows security
Python for the lab
Small scripts that repeat a check you would otherwise do by hand.
Automation for a security task
Evidence you can show
Weeks 4–6
The application. Security foundations, then the web stack you will test.
Security foundations
Threats, controls, and the habit of writing what you observed.
What you are allowed to test
How a finding is recorded
Web technologies
The request, the session, and the browser behavior the test depends on.
HTTP and the session
How the app is built
Web application security
Find a flaw in a guided lab and say what the owner should change.
A guided web lab
The fix, written down
Weeks 7–8
Operations. APIs, the network around them, and the work of a security desk.
API and network security
Calls the app makes, and the traffic you can explain.
API labs
Packet analysis
Security operations
What a team watches after the system is already running.
Alerts worth opening
A note the next shift can read
Weeks 9–10
The estate. Cloud, the newer attack surface, and the enterprise around it.
Cloud and the newer surface
Where a workload sits, and what changes when the host is not in the room.
Cloud configuration
What you still have to check
Enterprise security
Identity, access, and the review a larger environment needs.
Access reviews
A control you can demonstrate
Weeks 11–12
The close. How you present the work, then the supervised capstone.
Professional skills
A report, a portfolio, and a walkthrough another person can follow.
Technical writing
The portfolio you can open
Capstone assessment
A team assessment in a controlled environment, from scope to the final presentation.
Scope and risk
Mitigations and the report
Networking
Read the packet before you name the flaw
The lab is ready when you can point at the traffic and say what it is doing.
The host
Lock the machine you were given
Linux and Windows labs end with the account, the service, and the permission you changed.
The application
Write the web finding down
A web lab counts when the note says what you tried, what happened, and what should change.
Simulations
The lab you can walk.
Open a card. The simulation runs on its own page. Pause it and come back on the same step.
A supervised assessment and the report that goes with it.
In class
Each block ends in something you can show.
The weeks are instructor-led. You work in the lab, online or at the desk.
Packets
Hosts
Web and API
The system, before the test
Capstone
Scope, review, and a presentation.
Teams complete a supervised assessment in a controlled environment.
You leave the scope, the risks, the mitigations, and a report someone else can read.
Scope
Risk
Report
Presentation
The capstone presentation
Certificate
A certificate of completion for this cohort.
Syncpedia issues a certificate of completion after the 12 weeks and the capstone. It names the program. It does not list a salary, a placement rate, or a job offer.
Syncpedia
Certificate of completionCyberSyncIssued after the 12 weeks and the capstone