Cybrary ForgeCYBRARY / FORGE
Bake-off metrics/Readiness report

Executive readiness

Response clocks, one readiness number and framework coverage — all of it computed from runs already recorded, with every part of the number shown so it can be argued with.

0Exposed

Overall readiness score

Readiness 0/100 — exposed. Too little proven to rely on under pressure. Weakest part: coverage proven at 0.

Leading 85+
Ready 70+
Developing 50+
Exposed 0+Too little proven to rely on under pressure.

What the number is made of

  • Coverage proven0 · 30% weight

    0 of 24 capabilities the range can teach have been passed.

  • Quality of work0 · 25% weight

    Nothing passed yet.

  • Speed under pressure0 · 25% weight

    No run has recorded its clocks yet, so speed scores nothing.

  • Practice kept current0 · 10% weight

    0 graded activities in the last 90 days; eight is full marks.

  • Passes first time0 · 10% weight

    Nothing graded yet.

Score over time

May
Jun
Jul
Aug
Sep
Oct

Monthly mean best score against this program's own earlier windows. The field band appears here once a field can be drawn honestly. The full comparison is in "How you compare".

Clocks

Response clocks

Measured from the moment the incident starts in the exercise. 0 of 0 runs recorded their clocks. Nothing is timed yet — run a graded incident and the times appear here.

MTTD

Target 15m

Time to detect

--:--

Not timed yet — run a graded incident.

Median
—
Best
—
Runs
0

MTTR

Target 30m

Time to respond

--:--

Not timed yet — run a graded incident.

Median
—
Best
—
Runs
0

MTTC

Target 1h 00m

Time to contain

--:--

Not timed yet — run a graded incident.

Median
—
Best
—
Runs
0

MTTClose

Target 2h 00m

Time to close

--:--

Not timed yet — run a graded incident.

Median
—
Best
—
Runs
0
Program

Your organization, rolled up

Rolling the organization up…

Field

How you compare

Placing you against the field…

Coverage

Framework coverage

Proven by a passed runOn the range, not yet provenNot on the range — an honest content gap

MITRE ATT&CK

Enterprise techniques carried on the range's own labs

0 of 64 proven · 0%

Initial Access0/8 · 0%

Execution0/5 · 0%

Persistence0/7 · 0%

Privilege Escalation0/3 · 0%

Defense Evasion0/7 · 0%

Credential Access0/9 · 0%

Discovery0/5 · 0%

Lateral Movement0/4 · 0%

Collection0/2 · 0%

Command and Control0/3 · 0%

Exfiltration0/3 · 0%

Impact0/8 · 0%

MITRE ATLAS

AI attack techniques tagged on the AI range catalog

0 of 15 proven · 0%

Resource Development0/1 · 0%

Initial Access0/3 · 0%

Execution0/1 · 0%

Persistence0/1 · 0%

Defense Evasion0/1 · 0%

Exfiltration0/2 · 0%

Impact0/3 · 0%

AI Attack Staging0/1 · 0%

Defense Evasion / Privilege Escalation0/1 · 0%

Initial Access / Execution0/1 · 0%

NICE work roles

NIST SP 800-181 Rev. 1 work roles and capabilities

0 of 26 proven · 0%

Cybersecurity Policy and Planning0/2 · 0%

Defensive Cybersecurity0/4 · 0%

Digital Forensics0/2 · 0%

Incident Response0/5 · 0%

Security Control Assessment0/5 · 0%

Systems Authorization0/1 · 0%

Systems Security Management0/1 · 0%

Threat Analysis0/4 · 0%

Vulnerability Analysis0/2 · 0%

Biggest gaps

  • Credential Access — 9 of 9 unproven (MITRE ATT&CK)
  • Initial Access — 8 of 8 unproven (MITRE ATT&CK)
  • Impact — 8 of 8 unproven (MITRE ATT&CK)
  • Persistence — 7 of 7 unproven (MITRE ATT&CK)
  • Defense Evasion — 7 of 7 unproven (MITRE ATT&CK)
  • Execution — 5 of 5 unproven (MITRE ATT&CK)
  • Discovery — 5 of 5 unproven (MITRE ATT&CK)
  • Incident Response — 5 of 5 unproven (NICE work roles)
Every figure on this page is computed from runs this program actually recorded — nothing is estimated, sampled from a market report, or carried over from a demo.Loading your record…