Shared Login Risk
Today
Find shared accounts, stop “everyone uses the same login,” and create proof that you fixed it.
Open risks
3
Need action
High severity
2
Fix first
Resolved (30d)
5
Proof saved
Why this matters
If something goes wrong, a shared login means you can’t prove who did what.
OBRYN turns this into: unique users + MFA + audit logs.
Detection
Shared Accounts
Account System Used By Risk Severity Status Last Seen
frontdesk@hotel.com
“Front Desk” shared account
 PMS
9 users
Front Desk (shift)
High: no accountability
 HIGH OPEN Today • 12:14 PM
accounting@hotel.com
“Accounting” shared account
 POS
3 users
Finance
High: refunds exposure
 HIGH OPEN Yesterday • 6:03 PM
maintenance
Local admin username
 Wi-Fi
4 users
Maintenance + Vendor
Medium: shared admin
 MED IN PROGRESS 2 days ago
nightaudit@hotel.com
Converted to unique users
 PMS
0 users
Replaced
Low: fixed
 LOW RESOLVED 12 days ago
4 items
Fix plan
Select an item
—
What OBRYN recommends
1
Create unique users
No more “frontdesk / accounting / admin” shared accounts.
2
Turn on MFA
Make staff confirm identity when logging in.
3
Limit permissions
Front desk doesn’t need admin permissions.
4
Log the fix
Save proof for audits and insurance.
Fix actions
All actions become an evidence trail (prototype).
Evidence (what gets exported)
Detection record
Account + system + severity.
Remediation proof
Tasks + MFA + timestamps.