Skip to content

Access Request Form

Access Request Form template: The record of one request to create an account or change a person's access to a system, with the prerequisite checks, separation of duties check, approvals and provisioning, and a register of every request, as SP 800-53 AC-2 requires.

TypeProgram stageStatusTemplate versionNIST basis
Form or registerCoreDraft1.0.0SP 800-53 release 5.2.0

The record of one request to create an account or change a person’s access to a system, with the prerequisite checks, separation of duties check, approvals and provisioning, and a register of every request, as SP 800-53 AC-2 requires.

ControlTitle
AC-2Account Management
AC-2(2)Automated Temporary and Emergency Account Management
AC-5Separation of Duties
AC-6Least Privilege
AC-6(2)Non-privileged Access for Nonsecurity Functions
VariantReady to adoptAnnotated
All baselinesWord · MarkdownWord · Markdown

The register as a spreadsheet: CSV, with one column per field.

SystemRequest IDRequest typeDate submittedStatus
Fill in: system name and identifierFill in: unique request IDFill in: new account, added access, change of access, or temporary accountFill in: dateFill in: submitted, approved, rejected, provisioned or closed
  • The requester completes Parts A and B. A supervisor may request for a person they supervise.
  • The Account manager completes Parts C and D before the request goes for approval.
  • The approvers complete Part E. Group and role membership needs Fill in: prerequisites and criteria for group and role membership Typical: a completed access request, a signed access agreement and completed security awareness training (AC-2c), and account creation needs approval by Fill in: personnel or roles required to approve requests to create accounts Typical: the user’s supervisor, plus the system owner or data owner for privileged roles (AC-2e). No one approves a request for their own access.
  • The Account manager provisions only what Part E approves, completes Part F, and enters the request in the register.
  • To remove access, use the onboarding, transfer and termination checklist or a notice under section 5.5 of the account management procedure, not this form.
FieldEntry
NameFill in: full name
Unique identifierFill in: employee or contractor number, or existing user ID
Organization or employerFill in: organizational unit, or the company for a contractor
PositionFill in: job title
SupervisorFill in: name and contact
Requested by, if not the userFill in: name and role
FieldEntry
Account typeFill in: individual, privileged, service, temporary, or other type the system allows
Roles or groups requestedFill in: role or group names, as the system defines them
Business needFill in: the duties that need this access
Information accessedFill in: types of information, and whether it includes personally identifiable information
Start dateFill in: date
End dateFill in: for a temporary account or a fixed-term role, the date access ends; otherwise none
Other attributesFill in: restrictions to apply, from the attributes the account management procedure records for each account
Remote access neededFill in: no; or yes, and the approved method from the remote access standard

The account record holds the authorized user, group and role membership, access authorizations and Fill in: attributes (as required) for each account Typical: an expiration date for temporary accounts, and time-of-day or location restrictions where the system supports them (AC-2d). A temporary account is set to be disabled automatically at its end date, and an emergency account after Fill in: the time period after which to automatically remove or disable temporary or emergency accounts Typical: 72 hours for emergency accounts, and the end date approved at creation for temporary accounts (AC-2(2)).

For a privileged account, the user also keeps a separate non-privileged account for email, web browsing and other nonsecurity functions (AC-6(2)). Name it here: Fill in: non-privileged account ID.

PrerequisiteMet?Evidence
Screening required for the position completed (PS-3)Fill in: yes or noFill in: date, from the personnel security office
Access agreement signed (PS-6)Fill in: yes or noFill in: date, from the access agreement register
Rules of Behavior acknowledged (PL-4)Fill in: yes or noFill in: date
Security and privacy awareness training completed (AT-2)Fill in: yes or noFill in: date, from the training record log
Role-based training, for a privileged or specialist role (AT-3)Fill in: yes, no, or not neededFill in: date
Other prerequisites for this system or roleFill in: yes, no, or noneFill in: evidence
Checked byDate
Fill in: account manager nameFill in: date
QuestionAnswer
Does the user already hold a role that conflicts with one requested, under section 4 of the account management procedure?Fill in: no; or yes, with the conflict
If yes: how it was resolvedFill in: role removed, request changed, or exception approved by the system owner with compensating review
Checked by and dateFill in: account manager name and date
ApproverRoleDecisionDate
Fill in: nameSupervisorFill in: approved or rejected, with any roles removedFill in: date
Fill in: nameFill in: system owner or data owner, for privileged roles or sensitive informationFill in: approved or rejectedFill in: date
Fill in: nameFill in: other approver the system requires, or not applicableFill in: approved or rejectedFill in: date
FieldEntry
Account identifierFill in: user ID or account name
Roles and groups grantedFill in: as approved in Part E
Attributes setFill in: end date and restrictions applied
Created or changed byFill in: account manager name
Date and timeFill in: date and time, which is after every approval in Part E
Initial authenticator issuedFill in: how and when, or not applicable
User notifiedFill in: date
Request IDUserSystemTypeRoles requestedPrerequisites checked (date)Conflict foundApproved by and dateProvisioned by and dateEnd dateClosed
Fill in: IDFill in: name or IDFill in: systemFill in: request typeFill in: rolesFill in: dateFill in: no; or yes and resolutionFill in: names and datesFill in: name and dateFill in: date or noneFill in: date

Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.