What are auto-provisioning and auto-deactivation? Give the typical examples.
Auto-provisioning watches an authoritative source and creates users on systems and applications automatically, for instance when a new student record appears in the student administration database; auto-deactivation watches a source such as the HR application and deactivates the user objects on other systems automatically when an employee record disappears or is marked inactive.
* Auto-provisioning creates accounts from the authoritative source; auto-deactivation disables them when the source record goes. *
Both are provisioning triggered by events in the source rather than by tickets:
- Auto-provisioning: a new record in StudAdmin means a new student, so accounts on the learning platform, e-mail and Wi-Fi are created without anyone asking.
- Auto-deactivation: an HR record vanishing or being flagged inactive means the person has left, so their accounts elsewhere are disabled immediately.
Auto-deactivation is the more important of the two for security. Onboarding gets done anyway because the new employee complains when it does not; offboarding is what silently fails without automation, leaving orphaned accounts with live access, which is one of the most common findings in access audits.