Table of contents
- Quick read
- Readiness check
- Inventory the accounts the QA lane uses
- Give each account a purpose and an owner
- Separate shared fixtures from personal logins
- Set creation and expiry rules
- Disable accounts when a sprint closes
- Audit the accounts that survive a handover
- Keep the inventory beside the test plan
- Role brief
- Frequently asked questions
- Sources
Is the handoff ready?
Use these checks before access expands or the first ticket begins.
Account inventory
Ready: List each account, environment, role, storage location, and owner.
Needs work: The lane has no written record for this check.
Purpose record
Ready: Write the test each account supports and the date it was confirmed.
Needs work: The lane has no written record for this check.
Expiry rule
Ready: Set a default expiry, a reminder owner, and an extension ticket.
Needs work: The lane has no written record for this check.
Close-out check
Ready: Disable unused accounts at sprint close and verify the login fails.
Needs work: The lane has no written record for this check.
Inventory the accounts the QA lane uses
List every account the QA lane uses in staging, preview, and any vendor sandbox. Include personal logins, shared fixtures, service accounts, and the credentials inside automated tests. Record where each account is stored and who can read it. An inventory built only from the test plan will miss the accounts created during a previous sprint.
Record the environment, the role, and the data each account can reach. Mark the accounts that can approve a payment, send a message, or change a setting that a customer would notice. Note the accounts that use a real person's email or phone number. The risky accounts are the ones that look ordinary in a test plan.
Give each account a purpose and an owner
Write one sentence about the test the account supports and the person accountable for it. Record a backup owner who can disable the account when the primary is away. Name the sprint or release that justifies the account. An account described only by its email address has no owner in practice.
Separate an account that tests a customer role from an account that tests an admin or support role. Use that distinction when the team reviews access. Record the date the purpose was last confirmed. A purpose nobody can confirm is a reason to disable the account.
Set creation and expiry rules
Require a ticket and a named owner before a new test account is created. Record the environment, the role, the expiry date, and the test it supports. Give the account the smallest role that still exercises the path. An account created by asking a colleague in chat leaves no record and no expiry.
Set a default expiry that matches the sprint or the release, and require a new justification to extend it. Record the reminder date and the person who receives it. Disable rather than delete the account until the evidence is needed. An expiry date that nobody checks is a suggestion, not a rule.
Disable accounts when a sprint closes
At the end of a sprint, list the accounts created for it and confirm each one with its owner. Disable the ones that are no longer needed and record the date and the person who did it. Check that the login fails after the disable step. A disabled flag that the identity provider ignores is not a disable.
Check the accounts used by automated tests as well as the human ones. A fixture that stays active after the test is retired still holds a token. Record the test that used it and the ticket that retired it. Remove the secret from the test store when the fixture is disabled.
Audit the accounts that survive a handover
Before a contractor or a pod leaves, compare the account list with the people who still work on the lane. Disable the accounts owned by people who are leaving and transfer the fixtures to a named owner. Record the transfer and the new owner. A handover that keeps the logins alive keeps the access alive too.
Check the accounts created by the departing person but owned by nobody. Treat them as orphaned until a current owner claims them. Record the evidence and the decision. An orphaned test account with an admin role is a finding, even when the environment is not production.
Keep the inventory beside the test plan
Store the inventory where the QA team already works, and link it from the test plan and the release checklist. Record the account, the owner, the environment, the role, the expiry, and the last review. Give read access to the delivery lead and the client technical owner. An inventory in one person's notes disappears when that person is unavailable.
Review the inventory each month and after every sprint close. Record the accounts added, disabled, and still awaiting an owner. Report the oldest active account and the count with no expiry. A short monthly view is easier to act on than a long table nobody opens.
Copy-ready brief
Put the operating agreement in writing.
List personal, shared, and automated accounts with their environments and roles.
Name the person and the test that justify each account.
Tie the default lifetime to the sprint and require a ticket to extend it.
Disable or transfer accounts before a contractor or pod leaves.
Frequently asked questions
Can the team use one shared login for all QA?
No. Shared logins hide who acted and cannot be revoked for one person.
Should unused accounts be deleted right away?
Disable first, confirm the login fails, and delete after the evidence retention period.
Who owns an automated test fixture?
A named engineer on the QA lane, with a backup who can rotate or disable it.
What happens to accounts when a contractor leaves?
They are disabled or transferred before the last day, and the change is recorded.
Sources
- OWASP Application Security Verification Standard
Authentication, session, and access control requirements.
- NIST SP 800-53 security and privacy controls
Account management and access review controls.
- OWASP Web Security Testing Guide
Testing authentication and authorization paths.
- CIS Controls
Account inventory and access lifecycle safeguards.
