Outsourced ProgrammersPowered by StealthAgents

What share of outsourced production work uses a shared admin account?

A protocol for finding human-used service accounts, measuring their exposure, and separating automation from borrowed admin access.

What share of outsourced production work uses a shared admin account?
WORK_LANE / RESEARCH BRIEF / DELIVERYREVIEW QUEUEACCEPTANCEPASSowner review requiredEVIDENCE TRAILTICKET → BRANCH → REVIEW → CLIENT RELEASE
Table of contents
  1. Research context
  2. Practical application
  3. Operating controls
  4. Sources
  5. Frequently asked questions

Research context

This protocol asks what share of outsourced production work is performed through an account that more than one person can use. The unit is one production change record in the window, identified by the change identifier and the actor account. The study measures whether the actor was a named person, a shared human-used account, or an application service account. It does not judge whether the change itself was correct.

Define the three actor types before collection begins. A named account belongs to one person, a shared human-used account can be opened by several people, and an application account is used only by software with no interactive login. Record the evidence for the classification, such as the account owner field and the login source. A vague label will produce an unreliable share.

Set the scope to one client, one production environment, and one change policy. Record the systems, the account inventory, and the review window at the start. If a new identity tool is introduced during the window, keep the earlier definition for changes already recorded and analyze the later cohort separately. A migration can look like an improvement when it is only a different account model.

Define the population as every production change in the window, including changes that were later reverted or completed by a vendor. The unit is the change record, not the account, because one account can perform many changes. A change executed by a script under a shared human account is still a shared-account event. Test the definition on two recent changes before collection begins.

Record the change identifier, the system, the actor account, the account type, the change type, the timestamp, the approver, and the evidence used for classification. Add the account owner and the last access review date. Keep the access inventory and the change log linked. A second reviewer should be able to confirm the type from the record.

Practical application

Ask the engineers how they would perform the same change without the shared account. If the answer is that the named path does not exist, the finding is a tooling gap rather than a discipline problem. Record the missing role or permission. The review should distinguish a shortcut from a forced workaround.

Check the emergency path separately. A shared break-glass account may be legitimate during an incident, but it should be rare, logged, and rotated after use. Record the incident identifier and the post-use review. A high share of emergency use may mean the normal named path is too slow.

Report the number of changes, the share by actor type, and the share of shared-account changes that were approved by the same person who executed them. Show the counts by system and change type. Present the number of distinct people who used each shared account. Use the same denominator for every rate and show incomplete records.

A useful additional view is the share of shared-account changes that could not be attributed to a person after the fact. An unattributable change is the core risk of the shared credential, even when the change was safe. Record whether the team could name the operator from logs or memory. The review should report that share beside the usage share.

Inspect the systems with the highest shared-account use and describe the pattern without naming individuals. A legacy console may lack single sign-on, while a vendor portal may charge per named user. Compare the result with the change volume and the approval path. Report emergency changes separately because they follow a different rule.

Operating controls

Do not assume that a service account is safe because it is not used by a person. A service account with interactive login enabled and a password in a wiki is a shared admin account in practice. Record the interactive flag and the secret storage location. The classification should follow the actual use, not the account label.

The record cannot show whether a shared account was used maliciously or whether the change would have been safer under a named login. It can show only which account executed the change and whether a person could be identified. A high shared-account share is not proof of an incident, but it is proof of weak attribution. The protocol also cannot capture a change made directly in a vendor console that exports no log.

Check whether the client has a contractual rule about named access. A contract clause can make the finding easier to act on, while a missing clause may require a policy change first. Record the clause and the owner who can enforce it. The study should not assume that a technical fix is the only available response.

Give the result to the client security owner and the offshore lead and ask them to choose one observable change. The change might be a named role for one system, a short-lived credential, a break-glass process, or a monthly account review. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions.

Close the review with one change and a date to re-measure. The change should target the system with the most unattributable changes, not the account that is easiest to rename. Record the expected effect and the evidence that will prove it. A ban that is not measured will be replaced by a new shared login during the next busy release.

Sources

  1. NIST SP 800-53 access control
  2. NIST SP 800-63B digital identity guidelines
  3. OWASP secrets management cheat sheet
  4. CIS Benchmarks

Frequently asked questions

What should happen first?

Begin with a bounded ticket, approved access, explicit acceptance evidence, and a named reviewer.

Who approves production changes?

The client's technical owner keeps final merge and release authority.

Related research

How long do revoked offshore credentials stay usable after an exit?

How much review queue time comes from missing acceptance criteria?

Build a programming lane your technical owner can review.

Bring the stack, backlog, acceptance checks, and release boundaries. We will help scope the role around the work.

Discuss your programming needs