A guided cybersecurity internship · invitation only
Start at a blank shell. Finish in real machines.
CyberOps Spectrum is a cybersecurity internship you work your way down into. It assumes nothing — not a shell, not a network, not an alert. Every answer is checked against a key held on the server, a named supervisor reviews what you actually did, and the world opens as you earn it. No points, no streaks. Access is the reward.
This is the trainee's roadmap. Five territories are ready to enter; six are not written yet, and the map draws them as unmapped rather than pretending. Pick a place and the world turns to face it.
A stage is teaching, one question, and a shell to find the answer in.
This is the daily surface, laid out as the trainee meets it. The teaching sits on the left, the practice machine on the right, and the question can only be answered by running something. Inside, the answer goes to the server. Here, nothing is marked — find it anyway.
Reading the account file
Local user accounts live in /etc/passwd. Despite
the name it holds no passwords — those moved to
/etc/shadow, which ordinary users cannot read.
Each line is one account, written as fields joined by colons.
The last field is the account's login shell — the
program it gets when it signs in. /bin/bash is a
real command line, so that account can log in and type.
/usr/sbin/nologin refuses to start at all, which
is how a service account is marked as not for people.
How to read a file
cat prints a file's contents to the screen. Type cat, a space, then the path:
sam@web-01:~$ cat /etc/hostname web-01
Try it
Run cat /etc/passwd in the shell and read down the
last field of every line. A service account with a real shell
is the thing to notice.
Question
Read /etc/passwd in the shell above and look
down the last field of every line. One account is named like
a background service but has been given a real login shell
anyway. Which account is it?
Hint: an account name, as the first field prints it.
Inside the platform an answer box sits here and your answer is checked against a key held on the server. This page holds no key and no box, so nothing you find here is marked. Find it anyway.
Checked on the server
The answer key never reaches your browser, and nothing in the browser decides what you have completed. Progression is earned.
A miss is not a wall
Three misses in fifteen minutes pause the box for three minutes, with the time shown. Keep missing and your supervisor sees a needs-support signal, not a score.
Everything is recorded
Attempts, evidence and reviews survive the internship ending. The record is the organization's to keep, and yours to read.
One continuous world. Three places in it.
The roadmap, the facility and the command centre are areas of one environment, not a set of pages. Moving down into a more real one is the strongest progression signal the platform has, and it is the only thing that gets ceremony.
Click a machine to light what it is wired to
Lab Forge — the facility floor
Nine linked machines on one estate: a gateway, a switched fabric, an attack station, a domain-joined endpoint, a resolver, a honeypot, a sensor, a SIEM and an automation node. What any machine can see depends on where it sits. Pick one and the floor lights everything it is wired to.
When it opens, this is where the shell stops being simulated: real machines, real targets, and evidence you fetch yourself.
The floor is mapped and wired. No machine is open to a trainee yet, and the platform says so on the door rather than pretending.
Choose one from the archive
Finishing a topic opens its mission on its own. Nobody grants it to you.
- Grading serviceserver-side
- Evidence storereachable
- Mission runtimelive
- Progress savedon exit
Mission HQ — where investigations launch
A mission is an investigation: the evidence arrives raw, most of it is noise, and you are graded on the conclusion rather than the route you took to it. Finishing a topic opens its mission on its own, and it launches only from here.
Five missions written and published. Objectives are checked on the server, progress is saved when you step out, and the outcome goes on your record.
Inside the room, one line is always the current ask:
Failure is taught as a skill, not hidden as an error.
Running a technique is the easy part. Every module carries its own Systems & Debugging content on how failure presents itself in that layer, and at least one lesson on recording a failure you could not resolve — because real work does not always close.
The silent no-op
A service reports started and does nothing. You learn to ask the system what it is really doing instead of what it says.
The silent misroute
Nothing is blocked. The wrong path was chosen. You rule out each layer with a direct command rather than a guess.
The missing alert
Indistinguishable from no attack. You work backward through the pipeline one gate at a time until you find where it went quiet.
Most platforms track what a team consumed. This one supervises what one person did.
Every trainee has a named supervisor who reads the actual evidence, writes a review, and can lift a cooldown or escalate. You see the rating; the written body stays between your supervisor and your organization. That record outlives the internship, and it belongs to the organization that ran it.
- A named supervisor, assigned to you, who sees only the trainees assigned to them.
- A written review of real submitted work, confidential between supervisors. You see the rating.
- Escalation to your organization's administrator, with a recorded response when somebody is struggling.
- Every managerial write is audited — a lifted cooldown, a removed member, a renamed organization.
- The platform's owner is denied your data by database policy: no break-glass, no support exception.
Five modules are written, published and graded. Six are mapped and not written.
Authored from work actually performed and failures actually hit — a purple-team learning journal kept while doing the work — not from invented exercises. Every stage carries teaching, one question, an answer key held on the server, and an explanation.
The six unmapped modules have a name and a direction and nothing else. Their outlines are undecided, so nothing here pretends to know what they will contain.
Three strata, and you move down them.
-
Sandbox
Browser-native exercises, graded on the server. The stage above is one of them.
Built and published -
Lab Forge
Hosted machines you drive directly, with real targets and real evidence.
Being built — not open to trainees yet -
Your own lab
You build the environment yourself, guided. A capstone that depends on Lab Forge.
Not built
Access is by invitation.
There is no sign-up form, and that is deliberate rather than unfinished. Every account belongs to an organization, holds exactly one role in it, and is created by that organization’s administrator. Two-factor authentication is mandatory for everyone, with no opt-out.
If your organization is already here, your administrator sends you an invitation and the link in it creates your account. If it is not, and you would like it to be, get in touch with Belal Elsaadany directly — this is a platform being built for a named academy first, not a product taking open registrations.
A trainee never pays and never needs a foreign-currency card. The organization holds the account.
BUILT BY A LEARNER, FOR THE NEXT ONE
The curriculum is seeded from a purple-team learning journal kept while doing the work: technique and detection pairs, and failures recorded honestly.
What is not built yet
- Lab Forge as an environment a trainee can launch. The floor is mapped; no machine is open.Being built
- Certificates. Nothing is issued and nothing on this site implies otherwise.Not built
- Modules six through eleven. Named on the world, outlines undecided.Not written
- A phone. The platform is built for a keyboard and a desktop or laptop screen.Deferred