Syncpedia · CyberSync

Cybersecurity,
practiced in the lab.

A 12-week cohort. You start with the network and the host, test web and APIs in a guided lab, and close with a supervised assessment and a report.

12 weeks · 144 hours · Madhapur desk

  • 12 weeks

    144 hours, hybrid. Online or at the Madhapur desk.

  • Defence labs

    Networking, hosts, web, APIs, then a supervised capstone.

  • A capstone report

    A supervised assessment and a report you can walk an employer through.

A security lab reviewing a network together

The path

Defence is a sequence, not a toolbox.

The cohort follows the order a review actually takes: the machine, the network, the application, the operation, then the written assessment.

Walk through the 12-week path with the Madhapur desk.

Talk to the desk

At the desk

Rajesh Kumar

Cybersecurity and ethical hacking mentor

Ex-Amazon mentor for cybersecurity foundations and ethical hacking labs.
Rajesh Kumar

Who it is for

Four seats in a security review.

Each seat maps to a role companies are hiring for right now: SOC analyst, Linux and Windows admin, penetration tester, and assessment lead.

The labFull cohort: 12 weeks · 144 hours
An engineer working at a filled network rack

On this seat

You cover computer fundamentals, the OSI model, and the services a network already runs.

Weeks 1–3

Network analyst

A defence starts with the machine and the path a packet actually takes.

Full cohort: 12 weeksWeeks 1–3

What you cover

Want to see how the weeks run?

Read the syllabus

Our impact

Real colleges, real companies, real placements.

  • 101+Companies we collaborate with
  • 10k+Students we trained
  • Telangana & Andhra PradeshColleges we collaborate with

Placements we created

  • B. Karthikeya6 LPA · TCS
  • Bhanu7.2 LPA · Amazon
  • C. Akash5.5 LPA · Microsoft
  • D. Avinash8 LPA · Tech Mahindra

In the lab

What you practice each block.

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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

Roadmap

Twelve weeks, in the order a review meets them.

Hybrid · online or at the desk · foundations through the capstone report.

  1. Weeks 1–3

    Foundations. The computer, the network, the host, and Python for the lab.

    1. Computers and networking

      Architecture, operating systems, and the path from DNS to the firewall.

      • Virtual machines
      • TCP/IP, DNS, and routing
    2. Linux and Windows

      Accounts, services, and the permissions a host should keep.

      • Linux administration
      • Windows security
    3. 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
  2. Weeks 4–6

    The application. Security foundations, then the web stack you will test.

    1. Security foundations

      Threats, controls, and the habit of writing what you observed.

      • What you are allowed to test
      • How a finding is recorded
    2. Web technologies

      The request, the session, and the browser behavior the test depends on.

      • HTTP and the session
      • How the app is built
    3. 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
  3. Weeks 7–8

    Operations. APIs, the network around them, and the work of a security desk.

    1. API and network security

      Calls the app makes, and the traffic you can explain.

      • API labs
      • Packet analysis
    2. Security operations

      What a team watches after the system is already running.

      • Alerts worth opening
      • A note the next shift can read
  4. Weeks 9–10

    The estate. Cloud, the newer attack surface, and the enterprise around it.

    1. 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
    2. Enterprise security

      Identity, access, and the review a larger environment needs.

      • Access reviews
      • A control you can demonstrate
  5. Weeks 11–12

    The close. How you present the work, then the supervised capstone.

    1. Professional skills

      A report, a portfolio, and a walkthrough another person can follow.

      • Technical writing
      • The portfolio you can open
    2. Capstone assessment

      A team assessment in a controlled environment, from scope to the final presentation.

      • Scope and risk
      • Mitigations and the report
Learners reading a packet graph together

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.

Configuring a host beside a small server

The host

Lock the machine you were given

Linux and Windows labs end with the account, the service, and the permission you changed.

Marking a web finding beside the laptop

The application

Write the web finding down

A web lab counts when the note says what you tried, what happened, and what should change.

Capstone

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
A group marking a system on the board
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
A team presenting the capstone
The capstone presentation

Where this leads

Roles this skill set is hired for.

The twelve weeks are built around the day-to-day work behind these titles, not a single tool or exam.

  1. SOC analyst

    Security operations centres hire for exactly the alert-triage and log-reading skills the operations weeks build.

  2. Penetration tester

    The web, API, and host labs map to the junior pentest and VAPT roles companies are actively hiring for.

  3. Security analyst

    Networking, host hardening, and reporting together cover what a generalist security analyst role expects on day one.

  4. Cloud security

    The cloud and estate weeks give you the configuration-review vocabulary cloud security teams screen for.

  5. GRC and compliance

    The capstone's scope-risk-mitigation report is the same structure compliance and audit teams expect from a reviewer.

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.

  • Skills-based, not a seat-time badge
  • Backed by the capstone report
  • Verifiable with the Madhapur desk

From the desk

Notes from Syncpedia.

Ask about the CyberSync cohort

Tell the Madhapur desk whether you want the foundation path or the longer ethical-hacking path.

  • 12 weeks. 144 hours. Hybrid, online or at the desk.
  • Networking, hosts, web and APIs, then the capstone report.
  • Certificate of completion after the capstone.
  • 4th Floor, Plot 853, Road No. 45, Madhapur, Hyderabad 500081.
  • 9032452123 · hr@syncpedia.in

Ask about CyberSync

  • 12-week hybrid cohort
  • Labs and the capstone report
  • Madhapur desk, or online

Frequently asked questions

Before you join the cohort.

12 weeks. 144 hours, hybrid. You can sit online or at the Madhapur desk.

Foundations, the application, operations, the wider estate, then a supervised capstone and a professional report.

A certificate of completion, a capstone report you can show in an interview, and a portfolio of the labs you ran.

Still deciding on the cohort?

Talk to the desk

Leave with a report you can walk through.

12 weeks from the packet to the capstone. Ask the desk before you join.