1.5Separate work & personal use
The essentials in 30 seconds
- Two distinct worlds: accounts, devices, passwords never shared — one compromise does not contaminate the other.
- Transfer = leak: sending work to your personal email is a data leak, often banned by the charter.
- Real need = approved tool: shadow IT creates invisible flaws — ask IT instead of tinkering.
Threaded mini-case — Karim draws the line in Algiers
Karim used to send his work files to his personal email “to finish at home” and used the same password on both sides. He lists his crossings, removes every shared password, brings his files back onto company tools and asks his IT for an approved tool for large transfers instead of his personal service. Final episode: his digital hygiene is complete.
Final episode of cases 1.1-1.4 — Karim partitions what he secured.
1. Two distinct worlds
Work/personal separation: each world has its own accounts, emails, devices and passwords — one compromise does not contaminate the other. Accounts, devices, passwords: work and personal never mix.
Karim removes the worst first: no more shared password between his two worlds — his manager makes this easy.
2. Shadow IT and leaks
Shadow IT (unapproved tools: personal transfer, personal email, home USB stick) creates invisible flaws. Moving work files to your Gmail is a data leak literally — often banned by the charter.
Karim brings his files back onto company tools instead of his personal email: convenience is not worth a leak.
3. Supervised BYOD
A personal device used for work follows the company's BYOD rules — or is not used. For a real need not covered: ask IT for the approved tool instead of tinkering.
Karim asks for the approved transfer tool for his large files: the need is legitimate, the answer is the approved tool.
🔎 Concrete example — 🔎 Concrete example — The boundary audit
Fix the worst first.
Crossings: work files on the family PC? work emails in personal?
No more shared work/personal passwords AT ALL (the manager helps).
Bring work files back onto company tools.
→ a personal hack no longer hits the company (and vice versa)Takeaway: listing crossings makes the leak visible.
Lesson: uncovered need = ask for the approved tool.
Section vocabulary
- Work/personal separation
- Each world at home: distinct accounts, emails, devices and passwords — one compromise does not contaminate the other.
Simple example: Karim no longer shares any password between work and personal life.
What it is not: the same passwords and permanent transfers between both worlds.
Reflex: work and personal never mix.
- Shadow IT
- Using unapproved tools for work: handy… and outside any security control.
Simple example: The personal transfer service Karim drops for the approved tool.
What it is not: the transfer tool provided and monitored by IT.
Reflex: real need = approved-tool request, never tinkering.
- Personal email at work
- Moving work files to your personal email: a data leak literally.
Simple example: The files Karim sent himself “to finish at home”.
What it is not: working through the company cloud tools provided for it.
Reflex: no work file to personal, ever.
- BYOD
- Using personal devices for work, supervised (or banned) by company rules.
Simple example: Karim's personal PC: dedicated session and company tools, or no work on it.
What it is not: working on your personal device with no rules or protection.
Reflex: BYOD allowed and supervised, or request work equipment.
In practice — In practice — The work/personal boundary audit
- List your current crossings: work files on the family PC? work emails forwarded to personal? password shared across both worlds?
- Fix the worst first: NO more shared password between work and personal (the 1.1 manager makes this easy).
- Bring back: work files return to company tools, not the personal cloud.
- For a real need not covered (large file transfer, etc.): ask IT for the approved tool instead of tinkering.
Ready-to-say script — ask IT for an approved tool (30 s)
“I need to transfer large files for my work. Which approved tool do you recommend? I am bringing everything back onto company tools and stopping transfers to my personal email.”
Say to internal support; list your current crossings before the exchange.
Copy-paste template — boundary audit
CROSSINGS: work files outside the company _______________
PERSONAL TRANSFERS: _______________ | SHARED PASSWORDS: _______________
FIXED: shared removed [ ] | files brought back to _______________
UNCOVERED NEED: _______________ | APPROVED TOOL REQUESTED: _______________Used to personal transfers
Cut cleanly: bring files back onto company tools this week, then ask for the approved tool — convenience never justifies the leak.
Office in Algiers
Karim checks his internal charter and local BYOD rules with his manager: in Algiers as elsewhere, the company rule applies.
Work from home
If the company allows it: dedicated session, company cloud tools with no local copies, updated, encrypted and locked device — otherwise request work equipment.
Small company with no IT
With no dedicated IT: at minimum partition accounts and passwords, bring back onto the existing company tool and get the need approved by management.
✓ Best practices
- Zero shared passwords.
- Work files on work tools.
- Approved tool if needed.
✗ Common pitfalls
- Transfers to personal email.
- Tinkered shadow IT.
- Personal outside BYOD.
Key takeaways
- Accounts, devices, passwords: work and personal never mix.
- Transferring to your personal email is a data leak, not a convenience.
- Shadow IT creates invisible flaws: the need is legitimate, the answer is the approved tool.
- A personal device used for work follows the company's BYOD rules — or is not used.
48h Challenge - apply tomorrow
List your work/personal crossings (template above), remove every shared password and bring one work folder back onto company tools. 30 minutes is enough.
- I can explain why the personal transfer is a leak.
- I know what shadow IT is and its remedy.
- I listed my crossings + removed shared + brought back.
Frequently asked questions
Can I check my personal emails at the office?
Occasional checking is usually tolerated (see charter). The problem is TRANSFERRING work data to personal, and the reverse: installing personal software on the work workstation.
I sometimes work on my personal computer: how to limit risks?
BYOD framework if the company allows it: dedicated session, company cloud tools (no local copies), updated, encrypted and locked device. Otherwise, the real answer is work equipment — to be requested.
Karim sends a work file to his personal Gmail. Verdict?