Just Enough Keys
Who this book is for
Người làm công nghệ và AI trong doanh nghiệp Việt Nam: nhân viên IT một mình hay trong nhóm nhỏ, lập trình viên, người dựng tính năng AI, trưởng nhóm kỹ thuật ở công ty vừa và nhỏ; vừa phải giữ hệ thống chạy ổn, vừa được giao đưa công cụ và AI mới vào công việc của các phòng khác.
Sound familiar?
- Accounts of staff who left months ago are still open.
- A whole team shares one admin login.
- Every access request is granted to avoid friction.
- No list shows who can access which system.
After reading, you can
Help tech staff know who has what access and trim it to what the job needs.
Each chapter answers one question
Chapter 1: Do we actually know who holds which key?
Can I list who has access to each system?
If you cannot inventory access, you cannot manage it.
Chapter 2: Granting access to whoever asks: what could go wrong?
What access does a new employee need on day one?
Access should follow the job role, not the person asking.
Chapter 3: They left months ago, so why does their key work?
When someone leaves, how soon is all their access revoked?
The leaving date is the easiest to forget and the highest-risk moment for access.
Chapter 4: Is a strong password enough to guard the door?
Which important company accounts are protected only by a password?
A leaked password should not be enough to open the door.
Chapter 5: When did everyone's access quietly grow so large?
When did I last review all access rights?
Access rights swell over time if nobody reviews them.