Welcome to Jetplain. Pull up a chair.
cat welcome.txt
WELCOME TO JETPLAIN
Real tech. Clear explanations. A mechanic’s curiosity. A lifelong love of tech. Learn. Investigate. Build. Fix.
01 / PULL UP A CHAIR
cat welcome.txt
WELCOME TO JETPLAIN
Real tech. Clear explanations. A mechanic’s curiosity. A lifelong love of tech. Learn. Investigate. Build. Fix.
tree Jetplain-Lab
START WITH ONE USEFUL JOB
Jetplain-Lab/ ├── Notes/ ├── Projects/ ├── Scratch/ └── README.txt One computer. One job. A notebook.
cat recovery-checklist.txt
BUILD A WAY BACK
[ ] Find the files you’d miss [ ] Make separate copies [ ] Keep one copy offsite [ ] Test a file restore Start with one important folder.
READ THE RECORD BEFORE THE HEADLINE.
FICTIONAL TEACHING SCENARIO · NOT A REAL INCIDENT
A loud headline, three records, and a few missing pieces. What would you be comfortable repeating?
THE CLAIM“A failed login proves someone broke into my account.”
Open each finding to compare it with the packet. You can read everything in any order.
Record A establishes that the fictional log recorded one failed attempt. It does not identify who made the attempt.
Basis: Record A.
No. The claim jumps from a failed attempt to successful access. This packet contains no evidence that establishes that jump. Missing records also do not prove that successful access never happened.
Basis: Records A and C. The claim exceeds the evidence.
Check the original log source, timezone, nearby successful sign-ins, session history, and account-owner context. The owner's explanation is one possibility to test, not a confirmed answer.
Basis: Records B and C. These are proposed next checks, not records already obtained.
A useful finding can include “we don’t know yet.”
Try the Windows sign-in field notes →KEEP FOLLOWING THE RECORD
These small exhibits use the same fictional packet above. They are learning tools, not real incident artifacts.
The display keeps an observed timestamp, a recollection, and a missing event separate. Order alone does not establish cause.
time: 09:14
result: unsuccessful sign-in
timezone: not supplied
actor identity: not establishedThis is teaching text, not an exported Windows event. It supports a recorded failed attempt, not attribution or successful access.
“I mistyped my password around then.”
A possible explanation. The packet does not independently confirm it. Preserve the distinction between a statement and a verified event.
No successful sign-in records, session history, original log file, or clock settings are supplied. These gaps constrain the finding; they do not become evidence that nothing else happened.
Choose a route to see what it could establish. All routes remain readable; there is no score and no hidden result.
This would help establish where the record came from and how its timestamp should be interpreted. A trustworthy timestamp still does not identify the actor by itself.
Next question: which account, host, and event source produced the record?
This could supply evidence of successful access, if such records exist. Success does not automatically establish unauthorized access; compare the account-owner context and event details.
Next question: what distinguishes expected activity from activity that needs investigation?
The packet does not support the headline’s certainty. A defensible description is: one failed attempt is recorded, the owner offers a possible explanation, and successful access remains unestablished.
Next question: what specific evidence would justify stronger wording?
02 / THE RUNNING NOTEBOOK
Cyber Security & Privacy
What RIKEN has confirmed about the November 2026 intrusion, the exposed credentials, and the questions still unanswered.
Cyber Lab
Cyber Lab 002: investigate six fictional authentication events without jumping to conclusions.
Cyber Lab
Cyber Lab 001: a 15-minute introduction to Windows authentication evidence.
Life & 40+
Start with the files you would miss, make recoverable copies, and check that you can get them back.
Mechanics & Maker
Give a spare computer one useful job and build a learning setup without a shopping spree.
Workshop Notes
Real tech, clear explanations, and a place to figure things out without the attitude.
GOOD NOTES. CLOSE AT HAND.
Find a tool, follow a question, or pick up where you left off.