Use access and device controls within your role
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
An employee or volunteer may need access to work data without needing account-administration powers. Good security also depends on how approved tools are used day to day. You will review fictional requests for extra permissions, software installation and unexpected authentication prompts. The exercise focuses on role decisions, not changing an employer’s security configuration yourself.
Least privilege gives enough access for the task while keeping unnecessary powers out of reach.
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
Review the operator’s task: view assigned print jobs and mark them complete. Propose access limited to those functions instead of account administration or unrestricted export of every job.
- 2
Handle a colleague’s request to borrow the operator account by using the established access-request process. Shared credentials obscure responsibility and can bypass the intended account controls.
- 3
Multi-factor authentication (MFA) asks for more than one kind of proof to sign in. If you receive an approval prompt you did not expect, do not approve it; report it according to policy. Do not approve someone else’s sign-in just to dismiss the prompt.
- 4
Use approved installation and update channels for workplace devices. If an application requests disabling protection to open a file, stop and ask the authorized support role rather than weakening controls.
- 5
Create a four-scenario decision table: extra privilege, account sharing, unexpected prompt and unapproved software. For each, state the allowed immediate action and the owner who can authorize a change.
See how it works.
Fictional scenario: an operator needs to complete jobs but is offered administrator access "for convenience." The operator requests the narrower job-completion role. A coworker without access uses the official request process rather than borrowing the account. Later an unexpected sign-in approval appears while the operator is not signing in; they do not approve it and report the time. Finally, a downloaded utility asks to disable protection. The operator leaves it unopened and asks IT about an approved alternative. These actions reduce unnecessary access while allowing the responsible owner to resolve legitimate work needs.
Did you cover these?
- Privileges match job completion rather than administration.
- Account borrowing is replaced with a request process.
- Unexpected authentication requests are not approved.
What to finish
A four-scenario access and device decision table.
Watch for this
Solving an access problem by sharing credentials or disabling a managed protection.
How can I tell I understand it?
Choose a useful next step without exceeding the operator’s role.
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.