Know your role before touching a system
See this course’s project requirements
Run the fictional print-center tabletop using your five prepared security records and document two improvements.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Map work assets, owners and permitted actions.
- Prepare a minimal suspicious-request report using independent verification.
- Resolve access and device scenarios through approved roles.
- Compare a sample restore drill with recovery and data-loss targets.
- Complete an incident chronology and tabletop improvement plan.
Review and revise
Use these criteria to check your work and choose what to improve.
- Authorization: actions stay within the stated workplace role.
- Reporting: facts and interaction history reach the correct route.
- Recovery: time and content evidence are distinguished from assumptions.
- Coordination: fallback contacts and restart decisions are clear.
Want more background?
The idea in everyday life
Workplace security differs from securing your own accounts because systems, evidence and decisions may belong to several people. A helpful action in one role can disrupt another team’s response. You will use a fictional community print center and a supplied responsibility map. There is no need to access an employer network or change any real device setting.
A cybersecurity action needs both a reason and the authority to perform it.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
List three fictional assets: a shared job queue, a workstation and an approved backup store. For each, describe the work it supports and what an outage would prevent.
- 2
Assign roles: operator uses the queue, supervisor prioritizes work, and IT responder manages accounts, containment and restoration. Use role labels only; no real names or contact information are needed.
- 3
Define operator permissions: enter approved job details, lock the screen, report suspicious behavior and follow the documented response card. Scanning networks, changing security controls and accessing other users’ files are outside that role.
- 4
Create a contact route using fictional labels: known internal help channel, then supervisor if unavailable. Record that contacts must come from established organizational information, not a suspicious message.
- 5
Write one risk per asset and an owner question, such as who confirms that a backup can be restored. Save the asset-role map as the foundation for all later response decisions.
See how it works.
Fictional asset map: the job queue tells operators which prints to prepare; the workstation provides access to it; the backup store holds approved recovery copies. The operator may report a strange login alert but cannot investigate coworkers’ accounts. The supervisor can pause affected work and contact the IT responder. The IT responder decides authorized containment and recovery steps. If the help channel is unavailable, the operator uses the prelisted supervisor route. This map turns "do something" into a bounded action while protecting the evidence and systems that another role is responsible for assessing.
Did you cover these?
- Each asset has a purpose and owner.
- Operator actions and limits are explicit.
- The fallback reporting route is predefined.
What to finish
A three-asset responsibility map and permitted-action card.
Watch for this
Assuming helpful intentions grant permission to investigate or alter workplace systems.
How can I tell I understand it?
Choose an authorized action and identify the role responsible for the next step.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read the public course overview emphasizing account, data, system and software risks at home and work. Optional deeper study only; original workplace scenarios here.
Access: Free OpenCourseWare reading/videos; external submissions require an edX account. Verified certificates or credit-bearing courses require separate enrollment and may cost money. Life Starter provides no Harvard affiliation, credit or certification.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Source & access notes · checked 2026-09-10
Opened full nine-page guide; read asset owners, need-based access, backups and testing, detection and response authority. General voluntary guidance, not compliance certification.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.