If you would like to request access to a KUDOgov account, please review the requirements below then contact your dedicated CSM or CSR and copy firstname.lastname@example.org on the request.
Before an account can be created, it must be formally requested. KUDO’s DevOps is responsible for the entire account lifecycle, from the time that the account is provisioned and access is granted to the time that the account is disabled/removed.
Requesting Access: Contact DevOps and use the form that was created for this purpose by DevOps. Be prepared to provide detailed explanation, including at minimum:
- Solid business justification for requesting access
- Intended usage and level of access requested
- Anticipated duration for the requested access, start and end date
- Name and the contact information of the designated approving manager
- Other attributes if requested by DevOps or InfoSec
Review of the Access Request: Every access request requires (1) the approval of the requestor’s manager, and (2) the approval of the information security department, before account is created and access is provisioned.
NOTE: The requestor and the approving manager can’t be the same individual.
Privileged Access: KUDO DevOps enforces Role-Based-Access-Control (RBAC), hence, accounts with privileged access must be reserved for only exceptional circumstances, where elevated privileges are absolutely necessary to allow the requesters to complete their job duties.
NOTE: Individuals requesting privileged access, must be ready to comply with multi-factor authentication requirements that will be imposed by DevOps.