Cybrary ForgeCYBRARY / FORGE

Governance lab catalog

Everything published here is what learners run — in the MCP portal and on the desktop console. Instructors publish from the authoring tab in the range master console.

Edit a lab's opening line, steps and scoring — saved to your account, published when you say so.

Security Engineering

Reduce real exposure on a live estate: find the control that is failing, close it at the source, and prove the closure without breaking the service.

SEC-101
The management port that came back
Shipped

An edge firewall change made during a Friday outage exposed RDP on the jump host to the internet, and the emergency rule was never reverted. Close the exposure without cutting off the administrators who are legitimately using it.

2 controls · 2 objectives · target 25 min · foundation

SEC-102
Privileged accounts nobody owns
Shipped

Four accounts in the domain admins group have no named owner, two of them have not authenticated in over a year, and one is a service account with a password older than the policy allows. Reduce the privileged population without breaking the job that depends on it.

2 controls · 2 objectives · target 30 min · foundation

SEC-103
Baseline drift on the finance workstations
Shipped

The hardened workstation baseline is applied to 96% of the estate. The missing 4% is the finance team, exempted for a spreadsheet add-in two years ago. Bring them back to baseline without breaking month-end.

2 controls · 2 objectives · target 35 min · practitioner

SEC-201
The bucket, the key and the analytics vendor
Shipped

A marketing analytics vendor was given access to an object store six months ago, through a long-lived key pasted into a shared document. The bucket policy that was supposed to scope it allows list on the whole account. Cut the access back to what the contract actually needs, without breaking the reporting.

2 controls · 2 objectives · target 35 min · practitioner

SEC-202
One flat network, two very different risk appetites
Shipped

The building management controllers share a broadcast domain with the corporate print VLAN because of a cabling decision made during a fit-out. A commodity worm on a printer would reach the controllers directly. Segment it without a change window that finance will refuse.

2 controls · 2 objectives · target 45 min · advanced

SEC-203
Secrets that survived the pipeline
Shipped

A build pipeline prints its environment on failure, and three months of failed builds sit in a log store half of engineering can read. One printed value is a production database password that still works. Rotate what leaked, purge the logs, and stop the pipeline printing secrets.

2 controls · 2 objectives · target 40 min · advanced

SEC-301
Capstone — the path from a laptop to the domain
Shipped

A red team reached domain admin in nine hours from a standard laptop, using no exploit. Your job is not to argue with the report: it is to break the path in the fewest changes that survive contact with the business, and to prove the path is broken.

2 controls · 2 objectives · target 60 min · expert

Compliance & Audit Readiness

Turn operational reality into defensible evidence: map the requirement to the system, collect proof an auditor accepts, and record the exceptions honestly.

CMP-101
The evidence that proves nothing
Shipped

An auditor rejected eleven of your fourteen evidence artifacts. Every one of them is a screenshot taken the week before the audit. Rebuild the evidence so it demonstrates the control operated across the whole period.

2 controls · 2 objectives · target 25 min · foundation

CMP-102
One control, four frameworks
Shipped

Access reviews are performed once and mapped to four frameworks. Three of the four mappings claim a scope the review does not actually cover. Fix the mapping before an auditor finds it for you.

2 controls · 2 objectives · target 30 min · foundation

CMP-103
The data map that was never true
Shipped

A subject access request arrives. The data map says customer records live in two systems. The request turns up copies in a support tool, an analytics warehouse and a spreadsheet on a shared drive. Answer the request and fix the map.

2 controls · 2 objectives · target 35 min · practitioner

CMP-201
Continuous control monitoring, honestly
Shipped

Leadership wants a live compliance dashboard. The first draft reports 98% green because every automated check queries the configuration intent rather than the running system. Rebuild the checks so green means something.

2 controls · 2 objectives · target 40 min · practitioner

CMP-202
The vendor questionnaire and the truth
Shipped

A critical vendor returned a perfect questionnaire. Their public attestation covers a different product line, their breach notification clause allows 90 days, and your own logs show them accessing production outside the agreed window. Assess them properly.

2 controls · 2 objectives · target 45 min · advanced

CMP-203
Retention, legal hold and the deletion job
Shipped

A nightly job deletes records older than 90 days. Litigation was filed six weeks ago covering one customer's records, and nobody told the platform team. Establish what was lost, stop the loss, and report it correctly.

2 controls · 2 objectives · target 45 min · advanced

CMP-301
Capstone — fieldwork week
Shipped

The auditors are on site for five days. Three control owners are on leave, one evidence source was migrated last month and the old system is decommissioned, and a control you know failed in March is in the sample. Run the week without lying and without collapsing.

3 controls · 2 objectives · target 60 min · expert

Incident Response Command

Run the incident, not the alert: declare, scope, contain, preserve, communicate on the clock, and prove recovery before you close it.

IR-101
Declare it or don't
Shipped

Three concurrent signals, a phishing report, an EDR quarantine and a helpdesk ticket about a slow laptop, all point at the same user. Nobody has declared anything and it has been four hours. Decide, declare, and get the machinery running.

2 controls · 2 objectives · target 25 min · foundation

IR-102
Scope before you swing
Shipped

One workstation is confirmed compromised. The obvious move is to reimage it. The credential that was used on it also authenticates to eleven other hosts, and you do not yet know which of them the attacker touched.

2 controls · 2 objectives · target 30 min · foundation

IR-103
Evidence that stands up
Shipped

The incident is likely to end in litigation and possibly in a regulator's inbox. Everything you collect from here has to be attributable, verifiable and unaltered — and the analyst who has been working the case has been copying files to a personal USB drive.

2 controls · 2 objectives · target 35 min · practitioner

IR-201
The 72-hour clock
Shipped

Twenty-nine hours in, you have reason to believe personal data for roughly 40,000 customers was accessed. You do not yet know exactly which records. Legal wants certainty and the clock does not care. Communicate correctly, internally and externally.

2 controls · 2 objectives · target 40 min · practitioner

IR-202
Eradication and the return of the attacker
Shipped

You contained, you cleaned and you restored. Nine days later the same actor is back through a persistence mechanism nobody looked for, and the restored systems came from a backup taken after the initial compromise. Run the second response and fix the reasoning that made the first one fail.

2 controls · 2 objectives · target 45 min · advanced

IR-203
Ransomware at 04:00 on a Sunday
Shipped

Encryption is spreading across the file estate. The on-call engineer has one hour before the finance systems are hit. Backups exist but the backup server authenticates with a domain account. Command the response.

2 controls · 2 objectives · target 50 min · advanced

IR-301
Capstone — the review that changes something
Shipped

A major incident closed three weeks ago. The draft post-incident review blames an analyst by name, lists eleven actions with no owners, and does not mention that the same failure occurred in two earlier incidents. Rewrite it into something that prevents the next one.

3 controls · 2 objectives · target 55 min · expert

Intelligence Production

Produce intelligence, not summaries: grade the source before you believe it, separate fact from assumption, state your confidence, and write a product a decision-maker can act on.

INT-101
Grade the source before you believe it
Shipped

Vet three sources reporting indicators for an active phishing wave against your sector. One has a two-year track record, one is a new community feed, one is an anonymous paste. The watchlist update is due in an hour. Grade each source, corroborate what you can, and admit only what earns its place.

2 controls · 2 objectives · target 25 min · foundation

INT-201
Fact, assumption, judgment
Shipped

Decide whether the intrusions hitting three of your suppliers are one campaign or copycats. The draft on your desk mixes corroborated facts with one analyst's guesses and quietly drops a dissenting report. Rebuild it so every sentence is labeled for what it is, and task collection for the gap that decides the question.

3 controls · 2 objectives · target 35 min · practitioner

INT-301
The warning bulletin
Shipped

Write the one-page warning product your executives asked for. Reporting suggests a ransomware crew will move against organizations like yours over the holiday window. Resist the pressure to sound certain. State your confidence, name the alternatives, and tell the reader what would change the judgment.

3 controls · 2 objectives · target 45 min · advanced