DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Partner Who Kept Full Admin for Three Years

By Deepak Kumar, CISSP

The problem: To speed up a rollout, the IT admin gives the implementation partner a login with full administrator rights, meaning the right to change anything in the company’s main systems. The rollout takes twelve weeks. Three years later, the account is still active. Four people at the partner use the same login, and nobody at the company can say why it still exists.

Words used here: administrator rights, or admin rights, let someone change settings, users and data across a system. A named account belongs to one person. A shared account is used by several. Least privilege means giving people only the access they need, for only as long as they need it.

Think of the builder with the master key

A builder renovates a house and the owner gives him a master key so he can come and go. The job ends. The builder says, “I will drop the key back.” He does not, and nobody asks. Years later, the builder has moved to another firm, and the key has been copied twice. The owner has no idea how many master keys exist.

The master key is the admin account.

The builder with the master key
One master key, copied twice
I will drop the key back.
Builder
How many keys exist now?
Owner
The job ended. The key did not.

What it looks like at work

The rollout partner is reputable and the engineers were helpful. Giving them full admin was a shortcut, because working out exactly which rights they needed would have taken a week. The IT admin said, “We will tidy it up afterwards.” These are example numbers.

Afterwards, the team moved onto the next project, and the account looked like any other. At the annual audit, the auditor sees an account with top rights, no named owner, no end date, and sign-ins from places the company does not recognise. The partner’s manager says four engineers share it for support.

How temporary admin rights become permanent
  1. 11. ShortcutFull admin granted to save a week
  2. 22. “Tidy up later”Never scheduled, no end date set
  3. 33. Project endsThe account stays like any other
  4. 44. Years passFour engineers share one login
  5. 55. AuditUnknown sign-ins, no named owner
Nobody owned the end of the access.

Both sides have a fair point. The IT admin needed the work done and cannot spend a week on every access request. The partner needs enough access to do and support the job. Neither side wants a problem. But access given for a short job has been left in place for years, with no one owning the end of it.

You will notice it when:

  • An outside company has an account with admin rights.
  • Nobody can say when the account was supposed to end.
  • Several people share one login.
  • The account was created “just for the project”.
  • The list of outside accounts has never been reviewed.

What exactly needs fixing

The fix is not to refuse partners access. It is to set an end date when the account is created, give each person their own account, and check the list every quarter. This card shows the whole problem on one page:

Admin access that never ended
WHAT IS BROKEN

A partner’s full admin account is still active three years after the rollout, shared by four people.

HIGH
WHERE IT IS

The main systems, and the list of outside accounts.

WHAT COULD GO WRONG

The shared admin login is stolen and used to change or copy everything.

WHAT IT COSTS US
  • A breach
  • Failed audit
  • No clear owner
  • Legal question on blame
THE FIX, IN THREE MOVES
  1. 1
    1. Set an end dateEvery outside account expires unless renewed
  2. 2
    2. Named accountsOne person, one account, with only the rights the job needs
  3. 3
    3. Review each quarterA quarterly check of who still needs what, in the calendar now
WHO FIXES IT

Who fixes it: IT admin and the security lead

BY WHEN

By when: audit of outside accounts in 2 weeks

A blank copy of this card is in the Tools section.

Why it happens

  • Full admin is the quick option. Narrow rights take more thought.
  • Nobody owns the end. The project closes, the account does not.
  • Shared logins are convenient for the partner. Nobody checks.
  • There is no list of outside accounts. So no review is possible.
  • “We will tidy it up later” is never scheduled.

What happens if you ignore it

An old account becomes one of the easiest ways into the company.

  • The shared password can leak from the partner’s side.
  • An attacker who gets it holds the keys to the whole system.
  • Nobody can say which person did what, because four share it.
  • The contract may not cover the partner’s duties after the project ended.

At a glance

QuestionAnswer
How likely is it to hurt us?Likely, wherever outside accounts are created in a hurry.
Worst case?The shared admin login is stolen and used to change or copy everything.
What does it cost?A breach, a failed audit, and a legal question about who is responsible.
What if we wait?The account ages and so does the risk.
What does the fix cost?A review afternoon and a new account rule.

How to fix it, step by step

Set an end date, use named accounts, then review each quarter.

  1. List every outside account with admin rights. Start with the biggest rights.
  2. Ask who still needs each one, and why. In writing, from the partner’s manager.
  3. Remove what is not needed. If in doubt, disable the account first and watch who complains.
  4. Replace shared logins with named ones. One person, one account.
  5. Cut rights down to the job. Support might need a few rights, not all of them.
  6. Set an end date on every outside account. The system should expire it unless renewed.
  7. Review the list every quarter. Put the date in the calendar now.
End date, named accounts, quarterly review
1. End dateEvery outside account expires unless renewed.
2. Named accountsOne person, one account, only the rights needed.
3. ReviewCheck the list every quarter.
The end date is the cheapest step and removes the most risk.

The picture shows the order: set an end date, use named accounts, then review each quarter. The end date is the cheapest step and removes the most risk.

Who to bring in: The IT admin (removes and creates accounts), the partner’s manager (confirms who needs access), the security lead (sets the rule), and the contract owner (checks what the contract says about access).

Tools and templates

Outside account review

AccountCompanyRightsNamed personStill needed?End date
Account 1Full adminYes / NoYes / No
Account 2Yes / NoYes / No
Account 3Yes / NoYes / No

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a failed audit, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the partner

Subject: Reviewing outside access after the rollout

Hi. As part of our regular review, I see an account used by your team with full admin rights since the rollout. Could you tell me who still needs it, and for what? I would like to give each person a named account with only the rights they need, and to set an end date. I am not questioning your team. We are reviewing all outside accounts. Can we meet for 30 minutes this week?

Field tip

When you grant access to an outsider, write the end date in the same message. It is easiest to set when it is first granted.

Words used in this chapter

  • Admin rights: the right to change settings, users and data across a system.
  • Named account: a login that belongs to one person.
  • Shared account: a login used by several people.
  • Least privilege: giving only the access needed, for only as long as needed.
  • Expiry: a set date when access ends on its own.
  • Access review: a regular check of who has what.