| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:generic:account-audit-portal [2026-01-15 10:10] – frey | technical:generic:account-audit-portal [2026-01-15 12:00] (current) – frey |
|---|
| The IT Research Cyberinfrastructure (IT-RCI) team conducts periodic audits of all user accounts on the research computing systems in accordance with the University of Delaware IT Security guidelines. These account audits are critical to protecting the integrity and security of our HPC systems and other University assets. Unused or outdated accounts pose a significant security risk: compromised credentials could allow unauthorized access to research computing resources and potentially other UD systems. | The IT Research Cyberinfrastructure (IT-RCI) team conducts periodic audits of all user accounts on the research computing systems in accordance with the University of Delaware IT Security guidelines. These account audits are critical to protecting the integrity and security of our HPC systems and other University assets. Unused or outdated accounts pose a significant security risk: compromised credentials could allow unauthorized access to research computing resources and potentially other UD systems. |
| |
| All accounts have at least one sponsor on the system(s) so, under an account audit, sponsors must indicate the ongoing status of every extant account previously approved. To collect these dispositions, a web portal has been created to be used by sponsors. The portal presents and queries only the pertinent information: the format is (hopefully) intuitive and self-guiding. | All accounts have at least one workgroup sponsor on the system(s) so, under an account audit, administrative contacts for the workgroups must indicate the ongoing status of every extant account previously approved. To collect these dispositions, a web portal has been created to be used by workgroups' administrative contacts. The portal presents and queries only the pertinent information: the format is (hopefully!) intuitive and self-guiding. |
| |
| ===== An audit begins ===== | ===== An audit begins ===== |
| |
| Every IT-RCI workgroup has one or more individuals listed as contacts for administrative functions. When IT-RCI begins an account audit, all such individuals will be emailed to direct them to login to the audit portal and fill-out disposition records for every user present in the workgroup at that time. | Every IT-RCI workgroup has one or more individuals listed as contacts for administrative functions. When IT-RCI begins an account audit, all such individuals will be emailed to direct them to login to the audit portal and fill-out disposition records for every user present in the workgroup at that time. |
| | |
| | <note important>The audit portal embodies workgroup memberships //as of the date the audit began//. New accounts added //after the audit has begun// will not appear in the portal.</note> |
| |
| ===== Login ===== | ===== Login ===== |
| Most workgroup contacts possess an IT-RCI account, and that account should be used to authenticate on the audit portal. For example, the IT-RCI user ''trainf'' acting as contact on a workgroup should authenticate with the username ''trainf'' and the IT-RCI password. | Most workgroup contacts possess an IT-RCI account, and that account should be used to authenticate on the audit portal. For example, the IT-RCI user ''trainf'' acting as contact on a workgroup should authenticate with the username ''trainf'' and the IT-RCI password. |
| |
| Contacts who do **not** possess an IT-RCI account will have a UDelNet Id and password for central University systems (including email). In this case, the contact's email address and UDelNet password should be used to authenticate on the audit portal. For example, Betty Crocker is an administrative contact on workgroup ''chocochip'' but has no IT-RCI account; she should use her UD email address, ''crocker@udel.edu'', and UDelNet password. | Contacts who do **not** possess an IT-RCI account will have a UDelNet ID and password for central University systems (including email). In this case, the contact's email address and UDelNet password should be used to authenticate on the audit portal. For example, Betty Crocker is an administrative contact on workgroup ''chocochip'' but has no IT-RCI account; she should use her UD email address, ''crocker@udel.edu'', and UDelNet password. |
| |
| The portal exists at [[https://www.hpc.udel.edu/acct-audit/|https://www.hpc.udel.edu/acct-audit/]]. | The portal exists at [[https://www.hpc.udel.edu/acct-audit/|https://www.hpc.udel.edu/acct-audit/]]. |