OpenCyber AcademyLesson map
Lesson 18. Map, example, EX064.
flowchart TD
J["Judgment: a standard account would likely have stopped the startup adds"] --> F["Future change: standard accounts"]
L["Labs: hashes and names"] --> Q{"Did a lab print an account type?"}
Q -->|No| K["Do not convert the judgment into a cause"]
The lesson names a control. The scripts do not test it.
Logical drawing
judgment, not a lab row
a standard account would likely have blocked the startup adds
not measured
that administrator rights were used
an account-type column
future change
standard accounts for volunteers
Learning outcomes
After this chapter, you should be able to:
- Keep the standard-account sentence as a judgment.
- Say what the labs actually print.
- Refuse "admin rights were used" as a measured fact.
18.1 The lesson estimates a control. The prints do not show the account.
Chapter 4's lesson list includes a standard account without administrator rights, on the grounds that such an account would likely have stopped the installer from registering startup programs. "Would likely" is the mark of a judgment. ISO/IEC 27042 asks an examiner to keep interpretation distinct from the trace. The traces in the labs are hashes, labels, lengths, and startup names. None of those lines names an account type.
No test in this course showed that the installer ran with administrator rights. Saying "admin was used" borrows the feeling of the judgment and states it as history. The future change is still worth making: volunteers get standard accounts, so a later installer has a harder time registering startup programs. That change is a decision about the next laptops. It is not a result row from lab_startup.py, and it is not proof about Tuesday's account.
The other lessons stay in their own lanes. Templates from known sites, a current baseline, and Tomás's early report are separate changes. This chapter does not fold them into the account judgment, and it does not score the judgment as a confirmed cause.
Lesson table; scroll horizontally to read all columns →
| Sentence | Kind |
|---|---|
| Would likely have stopped the startup adds | Judgment |
| Admin rights were used on Tuesday | Not measured |
| Standard accounts for volunteers | A change going forward |
| Hash rows and NEW lines | What the labs print |
18.2 Worked example
Lesson table; scroll horizontally to read all columns →
| Offered sentence | Kind of claim | Decision |
|---|---|---|
| "A standard account is a likely barrier, not a tested cause." | Judgment kept as a judgment | Keep |
| "The labs print names and hashes, not an account type." | What is on the page | Keep |
| "The installer used administrator rights." | Unmeasured history | Refuse |
| "The startup script proved the account type." | No such column | Refuse |
Synthetic case. The account change is a food-bank decision after the incident.
Errors and limits
Do not launder a likelihood into a timestamped cause.
Apply
- EX064 — Judgment. A classmate writes that administrator rights were used because a standard account would likely have stopped the startup entries. What is measured, and what is only a judgment?
Show marking criteria
Rubric: 3 = the likely-stop sentence is a judgment; neither lab prints an account type; admin use was not measured; standard accounts are a later change;; 2 = the sentence stays a judgment and the labs have no account column;; 1 = one claim;; 0 = none.