Discussions
-
How much auditing is actually needed for access management?
I’ve been thinking about access governance and one question keeps coming up: How much audit information do teams actually need? For example, should an access audit record only capture major events like: * Access requested * Access approved/rejected * Access provisioned * Access revoked Or should it go deeper and capture: *…
-
Okta Can Provision Access. But Who Decides What Access Someone Should Have?
Okta is really good at managing identities. It can create users, manage groups, assign applications, and automate a lot of the repetitive work around user lifecycle management. Jira Service Management is good at something different: requests, approvals, workflows, etc., So what happens when you put the two together? The…
-
Your HRMS Knows Who Joined. Does Your IT Team Know What Access They Should Have?
When a new employee joins, HR, management, and payroll are aligned. But IT is often left guessing which groups or permissions are required. HR knows the employee. IT has to know the access. HRMS platforms track identity details like department and role. However, they don't automatically define security boundaries. For…
-
Why most Jira Service Management onboarding processes break after Day 1
Many teams automate employee onboarding in Jira Service Management, but the workflow often stops once the ticket is closed. The bigger challenge starts afterwards: * Who verifies users still need access after 90 days? * How do you remove access when someone changes teams? * How do you prove to auditors who approved each…
